欧瑞博（ORVIBO）门磁SM10ZW接入zigbee2mqtt问题

comeon_000 · 发表于 2020-12-13 16:48:45

本帖最后由 comeon_000 于 2020-12-13 17:13 编辑

上个月在网上买了一批欧瑞博的门磁，型号是SM10ZW，尝试了各种办法无法接入，版本从1.15.0切换到1.16.0再到最新的1.16.2，总是配对失败，其他设备都是没问题的，网上也查了很久，没有找到针对此问题的解决办法。
设备都是全新的，而且卖家也确实都能成功接入，相信不是设备的问题，想请论坛的大佬帮忙看看是哪里的问题
下面是配对失败的日志：

2020-12-13 08:55:15        stdout        [32mZigbee2MQTT:info [39m 2020-12-13 08:55:15: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00124b000cc9080c","ieee_address":"0x00124b000cc9080c","status":"failed"},"type":"device_interview"}'
2020-12-13 08:55:15        stdout        [31mZigbee2MQTT:error[39m 2020-12-13 08:55:15: Failed to interview '0x00124b000cc9080c', device has not successfully been paired
2020-12-13 08:55:15        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:55:15: Skipping message, definition is undefined and still interviewing
2020-12-13 08:55:15        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:55:15: Received Zigbee message from '0x00124b000cc9080c', type 'readResponse', cluster 'ssIasZone', data '{"zoneState":0}' from endpoint 1 with groupID 0
2020-12-13 08:55:14        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:55:14: Skipping message, definition is undefined and still interviewing
2020-12-13 08:55:14        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:55:14: Received Zigbee message from '0x00124b000cc9080c', type 'readResponse', cluster 'genBasic', data '{}' from endpoint 1 with groupID 0
2020-12-13 08:55:14        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:55:14: Skipping message, definition is undefined and still interviewing
2020-12-13 08:55:14        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:55:14: Received Zigbee message from '0x00124b000cc9080c', type 'readResponse', cluster 'genBasic', data '{"dateCode":"20151210        "}' from endpoint 1 with groupID 0
2020-12-13 08:55:14        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:55:14: Skipping message, definition is undefined and still interviewing
2020-12-13 08:55:14        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:55:14: Received Zigbee message from '0x00124b000cc9080c', type 'readResponse', cluster 'genBasic', data '{"hwVersion":1}' from endpoint 1 with groupID 0
2020-12-13 08:55:13        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:55:13: Skipping message, definition is undefined and still interviewing
2020-12-13 08:55:13        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:55:13: Received Zigbee message from '0x00124b000cc9080c', type 'readResponse', cluster 'genBasic', data '{}' from endpoint 1 with groupID 0
2020-12-13 08:55:12        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:55:12: Skipping message, definition is undefined and still interviewing
2020-12-13 08:55:12        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:55:12: Received Zigbee message from '0x00124b000cc9080c', type 'readResponse', cluster 'genBasic', data '{"appVersion":"v1.13_20151212\u0000"}' from endpoint 1 with groupID 0
2020-12-13 08:55:12        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:55:12: Skipping message, definition is undefined and still interviewing
2020-12-13 08:55:12        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:55:12: Received Zigbee message from '0x00124b000cc9080c', type 'readResponse', cluster 'genBasic', data '{"zclVersion":1}' from endpoint 1 with groupID 0
2020-12-13 08:55:12        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:55:12: Skipping message, definition is undefined and still interviewing
2020-12-13 08:55:12        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:55:12: Received Zigbee message from '0x00124b000cc9080c', type 'readResponse', cluster 'genBasic', data '{"powerSource":3}' from endpoint 1 with groupID 0
2020-12-13 08:55:06        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:55:06: Skipping message, definition is undefined and still interviewing
2020-12-13 08:55:06        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:55:06: Received Zigbee message from '0x00124b000cc9080c', type 'readResponse', cluster 'genBasic', data '{"manufacturerName":"中性"}' from endpoint 1 with groupID 0
2020-12-13 08:54:48        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:54:48: Skipping message, definition is undefined and still interviewing
2020-12-13 08:54:48        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:54:48: Received Zigbee message from '0x00124b000cc9080c', type 'attributeReport', cluster 'genIdentify', data '{"1989":"0x00124b000cc9080c"}' from endpoint 1 with groupID 0
2020-12-13 08:54:47        stdout        [32mZigbee2MQTT:info [39m 2020-12-13 08:54:47: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"0x00124b000cc9080c"},"type":"device_announced"}'
2020-12-13 08:54:47        stdout        [32mZigbee2MQTT:info [39m 2020-12-13 08:54:47: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00124b000cc9080c","ieee_address":"0x00124b000cc9080c"},"type":"device_announce"}'
2020-12-13 08:54:47        stdout        [34mZigbee2MQTT:debug[39m 2020-12-13 08:54:47: Device '0x00124b000cc9080c' announced itself
2020-12-13 08:54:46        stdout        [32mZigbee2MQTT:info [39m 2020-12-13 08:54:46: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_started","meta":{"friendly_name":"0x00124b000cc9080c"},"type":"pairing"}'
2020-12-13 08:54:46        stdout        [32mZigbee2MQTT:info [39m 2020-12-13 08:54:46: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"friendly_name":"0x00124b000cc9080c"},"type":"device_connected"}'
2020-12-13 08:54:46        stdout        [32mZigbee2MQTT:info [39m 2020-12-13 08:54:46: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00124b000cc9080c","ieee_address":"0x00124b000cc9080c","status":"started"},"type":"device_interview"}'
2020-12-13 08:54:46        stdout        [32mZigbee2MQTT:info [39m 2020-12-13 08:54:46: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00124b000cc9080c","ieee_address":"0x00124b000cc9080c"},"type":"device_joined"}'
2020-12-13 08:54:46        stdout        [32mZigbee2MQTT:info [39m 2020-12-13 08:54:46: Starting interview of '0x00124b000cc9080c'

看这几个z2m的版本里都是支持这款门磁的

    {
        zigbeeModel: ['fdd76effa0e146b4bdafa0c203a37192', 'c670e231d1374dbc9e3c6a9fffbd0ae6'],
        model: 'SM10ZW',
        vendor: 'ORVIBO',
        description: 'Door or window contact switch',
        fromZigbee: [fz.ias_contact_alarm_1, fz.battery],
        toZigbee: [],
        exposes: [e.contact(), e.battery_low(), e.tamper(), e.battery()],
    },

comeon_000 · 发表于 2020-12-13 17:02:35

本帖最后由 comeon_000 于 2020-12-13 21:59 编辑

对比了卖家那边成功配对的日志，发现有一点差异的地方：
就是他的能收到modelID这条消息，进而识别到SM10ZW的型号信息，我这个不知道为啥一直没看到这条日志

2020-12-02 10:55:39        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:39: No converter available for 'SM10ZW' with cluster 'ssIasZone' and type 'readResponse' and data '{"zoneState":0}'
2020-12-02 10:55:39        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:39: Received Zigbee message from '0x00124b0009fe1224', type 'readResponse', cluster 'ssIasZone', data '{"zoneState":0}' from endpoint 1 with groupID 0
2020-12-02 10:55:38        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:38: No converter available for 'SM10ZW' with cluster 'genBasic' and type 'readResponse' and data '{}'
2020-12-02 10:55:38        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:38: Received Zigbee message from '0x00124b0009fe1224', type 'readResponse', cluster 'genBasic', data '{}' from endpoint 1 with groupID 0
2020-12-02 10:55:38        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:38: No converter available for 'SM10ZW' with cluster 'genBasic' and type 'readResponse' and data '{"dateCode":"20151210        "}'
2020-12-02 10:55:38        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:38: Received Zigbee message from '0x00124b0009fe1224', type 'readResponse', cluster 'genBasic', data '{"dateCode":"20151210        "}' from endpoint 1 with groupID 0
2020-12-02 10:55:38        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:38: No converter available for 'SM10ZW' with cluster 'genBasic' and type 'readResponse' and data '{"hwVersion":1}'
2020-12-02 10:55:38        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:38: Received Zigbee message from '0x00124b0009fe1224', type 'readResponse', cluster 'genBasic', data '{"hwVersion":1}' from endpoint 1 with groupID 0
2020-12-02 10:55:37        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:37: No converter available for 'SM10ZW' with cluster 'genBasic' and type 'readResponse' and data '{}'
2020-12-02 10:55:37        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:37: Received Zigbee message from '0x00124b0009fe1224', type 'readResponse', cluster 'genBasic', data '{}' from endpoint 1 with groupID 0
2020-12-02 10:55:37        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:37: No converter available for 'SM10ZW' with cluster 'genBasic' and type 'readResponse' and data '{"appVersion":"v1.13_20151212\u0000"}'
2020-12-02 10:55:37        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:37: Received Zigbee message from '0x00124b0009fe1224', type 'readResponse', cluster 'genBasic', data '{"appVersion":"v1.13_20151212\u0000"}' from endpoint 1 with groupID 0
2020-12-02 10:55:37        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:37: No converter available for 'SM10ZW' with cluster 'genBasic' and type 'readResponse' and data '{"zclVersion":1}'
2020-12-02 10:55:37        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:37: Received Zigbee message from '0x00124b0009fe1224', type 'readResponse', cluster 'genBasic', data '{"zclVersion":1}' from endpoint 1 with groupID 0
2020-12-02 10:55:37        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:37: No converter available for 'SM10ZW' with cluster 'genBasic' and type 'readResponse' and data '{"powerSource":3}'
2020-12-02 10:55:37        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:37: Received Zigbee message from '0x00124b0009fe1224', type 'readResponse', cluster 'genBasic', data '{"powerSource":3}' from endpoint 1 with groupID 0
2020-12-02 10:55:36        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:36: No converter available for 'SM10ZW' with cluster 'genBasic' and type 'readResponse' and data '{"manufacturerName":"中性"}'
2020-12-02 10:55:36        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:36: Received Zigbee message from '0x00124b0009fe1224', type 'readResponse', cluster 'genBasic', data '{"manufacturerName":"中性"}' from endpoint 1 with groupID 0
2020-12-02 10:55:36        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:36: No converter available for 'SM10ZW' with cluster 'genBasic' and type 'readResponse' and data '{"modelId":"fdd76effa0e146b4bdafa0c203a37192"}'
2020-12-02 10:55:36        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:36: Received Zigbee message from '0x00124b0009fe1224', type 'readResponse', cluster 'genBasic', data '{"modelId":"fdd76effa0e146b4bdafa0c203a37192"}' from endpoint 1 with groupID 0
2020-12-02 10:55:35        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:35: Skipping message, definition is undefined and still interviewing
2020-12-02 10:55:35        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:35: Received Zigbee message from '0x00124b0009fe1224', type 'attributeReport', cluster 'genIdentify', data '{"1989":"0x00124b0009fe1224"}' from endpoint 1 with groupID 0
2020-12-02 10:55:34        stdout        [32mZigbee2MQTT:info [39m 2020-12-02 10:55:34: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"0x00124b0009fe1224"},"type":"device_announced"}'
2020-12-02 10:55:34        stdout        [34mZigbee2MQTT:debug[39m 2020-12-02 10:55:34: Device '0x00124b0009fe1224' announced itself
2020-12-02 10:55:34        stdout        [32mZigbee2MQTT:info [39m 2020-12-02 10:55:34: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_started","meta":{"friendly_name":"0x00124b0009fe1224"},"type":"pairing"}'
2020-12-02 10:55:34        stdout        [32mZigbee2MQTT:info [39m 2020-12-02 10:55:34: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"friendly_name":"0x00124b0009fe1224"},"type":"device_connected"}'
2020-12-02 10:55:34        stdout        [32mZigbee2MQTT:info [39m 2020-12-02 10:55:34: Starting interview of '0x00124b0009fe1224'

xuyang · 发表于 2020-12-13 19:48:08

我的ORVIBO，能正常接入。多配对几次看看。

comeon_000 · 发表于 2020-12-13 21:58:59

xuyang 发表于 2020-12-13 19:48
我的ORVIBO，能正常接入。多配对几次看看。

从上个月到现在尝试了很多次了，每次都是一样的现象，缺少下面这个数据的上报
不知道是不是我的网关和这个设备的配合有点问题，丢消息了
Received Zigbee message from '0x00124b0009fe1224', type 'readResponse', cluster 'genBasic', data '{"modelId":"fdd76effa0e146b4bdafa0c203a37192"}' from endpoint 1 with groupID 0

ghostist · 发表于 2020-12-14 16:58:20

我用的一批盛世的，会有个别设备这样，没啥好办法就是重复的配对配对再配对
配上了就好了

comeon_000 · 发表于 2020-12-14 23:09:44

ghostist 发表于 2020-12-14 16:58
我用的一批盛世的，会有个别设备这样，没啥好办法就是重复的配对配对再配对
配上了就好了 ...

好的，感谢指导，我再配对尝试一下

feng4417 · 发表于 2020-12-22 15:45:53

我手头也有几个安居宝的zigbee设备，也是用不了

comeon_000 · 发表于 2020-12-22 22:25:17

本帖最后由 comeon_000 于 2020-12-22 22:29 编辑

feng4417 发表于 2020-12-22 15:45
我手头也有几个安居宝的zigbee设备，也是用不了

这个也是尝试了很多次了，就是缺了那一条关键的数据上报，正在考虑换一个网关试试

Clark · 发表于 2021-5-31 08:33:00

哪里可以买到盛世zigbee门磁呢？

mpuazxc · 发表于 2023-2-28 01:17:20

zigbee2mqtt网关接入后原来的面版还能用吗

		自动登录	找回密码
密码			立即注册

[求助] 欧瑞博（ORVIBO）门磁SM10ZW接入zigbee2mqtt问题