i have swapped my conbee 2 to sonoff dongle (p version) and have a few issues.

I have 2 xiaomi temp sensor (same model) and i’ve only be able to link one, other one i shown as unsupported. Same thing happened with 2 tuya temp sensor, only one is shown as supported.

I have updated sonoff dongle firmware but that didn’t change anything, chnaged batteries and tried to pair multiple times but no luck

Any reason why, any tips?

  • pafOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    i’m pretty sure i have the P version, and i did flash latest firmware for P version, i did a complete Z2M setup as i also swapped my raspberry for a mini pc at the same time but i haven’t tried with an usb extender, will try that in a few hours and will update my comment. Is there a way to check visually if i have the P version ? Thanks for your answer

    Edit: can confirm i have P version, model: ZBDongle-P Edit2: just tried to pair them again with an usb extender but still same

    • spckls@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Can you provide the part numbers of sensors you’re trying to pair? You said you managed to successfully pair one of each, that would indicate that the sensors are supported by both Z2M and your router. Did you physically move the router away from the USB ports? How are you running HA? Bare metal, VM, container, supervised?

      • pafOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        1 year ago

        thanks for helping, I’m running a VM with HA OS (proxmox), i just realised that z2m crash when trying to pair those devices and watch dog isn’t starting z2m back. I might load a backup when i was using my raspberry with conbee 2 and replace sonoff dongle by conbee 2 to see if same thing is happening which would indicate it has something to do with my proxmox VM

        here are the logs when i try to pair:

        Zigbee2MQTT:info 2023-11-28 16:13:42: Zigbee2MQTT started! Zigbee2MQTT:info 2023-11-28 16:13:48: Zigbee: allowing new devices to join. Zigbee2MQTT:info 2023-11-28 16:13:48: MQTT publish: topic ‘zigbee2mqtt/bridge/response/permit_join’, payload ‘{“data”:{“time”:254,“value”:true},“status”:“ok”,“transaction”:“fh35x-1”}’ Zigbee2MQTT:info 2023-11-28 16:13:52: Device ‘0xa4c138d5784acca7’ joined Zigbee2MQTT:info 2023-11-28 16:13:52: MQTT publish: topic ‘zigbee2mqtt/bridge/event’, payload ‘{“data”:{“friendly_name”:“0xa4c138d5784acca7”,“ieee_address”:“0xa4c138d5784acca7”},“type”:“device_joined”}’ Zigbee2MQTT:info 2023-11-28 16:13:52: Starting interview of ‘0xa4c138d5784acca7’ Zigbee2MQTT:info 2023-11-28 16:13:52: MQTT publish: topic ‘zigbee2mqtt/bridge/event’, payload ‘{“data”:{“friendly_name”:“0xa4c138d5784acca7”,“ieee_address”:“0xa4c138d5784acca7”,“status”:“started”},“type”:“device_interview”}’ Zigbee2MQTT:info 2023-11-28 16:13:53: MQTT publish: topic ‘zigbee2mqtt/bridge/event’, payload ‘{“data”:{“friendly_name”:“0xa4c138d5784acca7”,“ieee_address”:“0xa4c138d5784acca7”},“type”:“device_announce”}’ Error: Unhandled error. (TypeError: Cannot destructure property ‘vendor’ of 'data.device.definition’ as it is null. at EventEmitter. (/app/data/extension/miboxer-fut089z-controls-exposer.js:151:21) at EventEmitter.emit (node:events:525:35) at EventBus.emitDeviceMessage (/app/lib/eventBus.ts:102:22) at Controller. (/app/lib/zigbee.ts:108:27) at Controller.emit (node:events:513:28) at Controller.selfAndDeviceEmit (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:527:14) at Controller.onZclOrRawData (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:738:18) at ZStackAdapter. (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:144:70) at ZStackAdapter.emit (node:events:513:28) at ZStackAdapter.onZnpRecieved (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:823:30)) at new NodeError (node:internal/errors:387:5) at ZStackAdapter.emit (node:events:502:17) at emitUnhandledRejectionOrErr (node:events:394:10) at processTicksAndRejections (node:internal/process/task_queues:85:21)`

        here are the devices that failed to pair: https://www.zigbee2mqtt.io/devices/WSDCGQ11LM.html (i have 3 of those and one is failing to pair)

        https://www.zigbee2mqtt.io/devices/TH02Z.html#tuya-th02z (did a mistake as i have 2 of them and none are pairing)

        couple more devices that fails since i started thi post: https://www.zigbee2mqtt.io/devices/AB3257001NJ.html#osram-ab3257001nj

        https://www.zigbee2mqtt.io/devices/ERS-10TZBVK-AA.html#tuya-ers-10tzbvk-aa

        Edit: HA fail to load my backup file, saying it needs a .tar file (but i did point to a .tar file), will do a fresh install and load my backup to see if same is happening

        Edit2: issue with backup file was due to firefox, works in chrome

        Edit3: using my backup and conbee, everything works fine (at one exception, a zigbee remote which i remember was a pain to setup. remote is paired but not working yet… https://www.zigbee2mqtt.io/devices/FUT089Z.html