Hi all, hope you guys doing great. I am non programmer however i followed the instruction as per above. the problem i am facing that i cannot see the device or the child zigbee device which is paired though zigbee2mqtt platform. additionally i am getting the attached message
though i added the xiaomi drivers separately its still showing me this. can any one help?
thank
also how i can find the devices after this problem is fixed? i am only able to create a virtual device with one driver type
It looks like from your warning log this integration does not support your specific devices.
Yup. In the first post are the ones I've added Z2M support for.
If someone has a little time the WXKG01LM should be easy to add, the "drivers" for this are essentially just a map of Z2M to HE values.
Also, there's no two-way comms in this driver at the moment, so controlling a smart plug wouldn't work. Even if the mapping was added HE could receive states, but not change them.
If you have a C-8 hub, you can try again to pair it directly to Hubitat (this will not work on C-7 and older plugs). It is hard to keep it connected, but I finally succeeded using the option 'Try to avoid Zigbee 3.0 repeaters while pairing'.
If you stay on Z2M, you can bring the plug to Hubitat using the Home Assistant Device Bridge
Hi kkossev,
I am currently using C8, and whenever I am trying to connect directly, it is showing "Found a Zigbee device, initializing..." and gets time out. I am using aqara devices and tuya smart plugs ( download your drivers for it) but none of the connect direct or works. that is why i chose z2m . can you suggest me the best way to connect these devices? i tried using homeassistant device bridge but i was unable to add any device. I am totally new to this platform
yes now it seems soo
Do you have any Zigbee devices from brands different than Tuya and Aqara?
yes
@renovatio it may be better if you create a new thread in this forum where we can try to identify these devices. This thread is dedicated to the Zigbee2MQTT Routing Driver by @birdslikewires
This routing driver now supports the healthStatus custom attribute, so will no longer misuse presence as a means of reporting connectivity to your MQTT broker.
Use @kkossev's Device Health Status to give yourself a nice system overview.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
