My Homey Pro (2023) has updated the Zigbee2MQTT app to version 3.2.0 and now all devices added through Zigbee2MQTT show up as offline in Homey. The devices can be controlled just fine from the Zigbee2MQTT WindFront Web UI. The Zigbee2MQTT bridge looks fine, with no offline devices and no offline bridge. I’ve already restarted the Homey Pro entirely and the Zigbee2MQTT app specifically, but no luck. Any ideas?
Can you send an app diagnostics report?
Yes of course: ee77ead3-a37e-44eb-a198-6a4d4409afdd
Same here, but on SHS.
556dd25d-c269-448c-a2b6-a21f6455d9ab
Same here.
The devices works, but not from homey. 
e6c8db1a-4ca6-41f5-ade6-04c4d679f509
And what Z2M version are you guys all using?
I use this in portainer:
org.opencontainers.image.url GitHub - Koenkk/zigbee2mqtt: Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨 · GitHub
org.opencontainers.image.version 2.9.1
I’m using Zigbee2MQTT 2.6.3 with Mosquitto 2.0.22.
New version 3.2.1 is ready for testing: Zigbee2MQTT | Homey
- Fix bridge and mqtt (re)connection issues
- Added last_seen
- Added dynamic capability mapping based on status reports
- Extend preset and indicator_mode capabilities
- Stability improvements
Although I cannot reproduce the issue, i hope this version solves the devices offline issue. Please test @praseodym @JossNL @Victoryus
This version also adds mapping capabilities that were previously hidden during discovery. These capabilities will be mapped when the device first reports them to Homey. A device migration will happen once.
I had the same issue and 3.2.1 fixed it for me
Many thanks for your donation @kjeet90 ! 
I’m not at home, but now I see the devices in Homey.
Thanks!
@OeTeJr @SteveOswald Many thanks for your donations! Much appreciated ! 
Version 3.2.1 fixed the issue for me as well, thank you!
My professor always said: read, read, read, before you write.
I had meanwhile switched to an old version from GitHub, but now tested this with success!
Thanks for your quick efforts.
Hello, I read earlier in this thread, that multiple areas for mmWave devices couldn’t be added, due to an issue with Homey. I have a Inovelli mmWave device, which has “Up to 4” areas for mapping. I Setup the mapping, and it is reporting correctly (Area 1, Area 2, Area 3 and Area 4) in HA. I much rather use Homey, so switched the Zigbee2MQTT to Homey and use your program. However, it is just using the “Motion Alarm” when using the program. All other Areas are missing. Is this functionality still missing (Due to Homey). Do you know if I can use your program to Map the additional Areas into the Device Tab?
I just didn’t know if Homey was still the issue, or, if I am doing something wrong. The Device is a Smart Presence Switch VZM-32. I have 8 of them, and many have different Areas/Zones I would like to make available to Homey (Programmed through Zigbee2MQTT). They are mapping correctly with different areas of HA, but I am trying to get rid of Home Assistant.
Lyle
I need to extend the Homey app. See first post of this thread. If you donate (the funds to buy) a device, I am willing to spend effort to try and achieve this.
I need to extend the Homey app. See first post of this thread. If you donate (the funds to buy) a device, I am willing to spend effort to try and achieve this.
Done. Thank you for your efforts. Even if it can’t be done, no problem. I do appreciate the trying.
