I am now testing with Z2M v2.0.0-latest-dev. It seems to run fine with the Homey app. I did not encounter any issues so far.
Happy Hollidays 
3 Likes
Awesome thanks for testing!
1 Like
Hello everyone. I have a problem. Due to the failure of the Tuya interface in November, I connected my Tuya Zigbee devices, i.e. switches and dimmers, to Homey via the Zigbee2MQTT interface. This worked very quickly and well. Now that I have completed the connection, I unfortunately have to realize that all devices registered to Homey via Zigbee2MQTT are not passed on to Alexa for control by Homey via the Alexa interface. The only strange exception, a Phillips Hue White 1100, which I also registered on Zigbee2MQTT for testing, appears in Alexa via Homey and can be controlled. If I create virtual switches in Homey and control a dimmer in Zigbee2MQTT via flows, for example, this virtual switch is also passed on from Homey to Alexa and the control works. But the direct connection to the Zigbee2MQTT devices in Alexa via Homey does not work.
What am I doing wrong? What can I do? The controls work as expected under Homey. All other Homey devices also work in Alexa. Please help me.
Happy Hollidays 
Hello, I installed the latest Homey firmware as well as the Zigbee2MQTT application. I am trying to add an IKEA VALLHORN motion detector. I press the button 4 times, and it blinks red for pairing. However, when I try to add it in the Zigbee2MQTT application, it says that no device is found. I’ve been trying for an hour, but nothing works. On the other hand, if I use the IKEA application, it is detected immediately. Did I miss something? My goal is to retrieve the battery status of my IKEA devices, which is not possible with the IKEA app. Could you explain how to pair the module, please? Thank you. For your information, I do not have HA.
You first have to pair the device with Zigbee2MQTT itself before you can import it into Homey.
Well, apparently, I’m missing something because that’s exactly what I’m doing. I create a new device, select Zigbee2MQTT, then “Device,” while putting the module in pairing mode, but it doesn’t detect it. Is this not the correct procedure?
Are you sure you know what Zigbee2MQTT actually is?
No, I don’t think so. For me, it’s an application like IKEA. Could you explain the procedure? And do I need additional devices to make Zigbee2MQTT work?
It’s explained in the first post of this thread.
In short: Zigbee2MQTT is an external Zigbee implementation that needs to be running on some other piece of hardware, like a Raspberry Pi or a NAS. The Homey app for Zigbee2MQTT (what this thread is about) can be used to import devices handled by Zigbee2MQTT into Homey.
The VALLHORN device is supported by the “official” IKEA app for Homey, so unless you have a specific reason not to use that app, you should.
1 Like
Ok, thank you. It’s just to retrieve the battery information, which is not available in the official IKEA app.
New version 2.7.0 is ready for testing: Zigbee2MQTT | Homey
- Added offline device counter in Bridge.
- Set device unavailable when Z2M device is offline.
- Added AI translations for all languages.
Besides having AI translate the app to all Homey languages, the app now will show a device as unavailable when it is offline in Z2M.
3 Likes
Could you please help me? I installed the Zigbee2MQTT app and try to connect the ZG 204ZM but get a message saying ‘cannot find bridge device in Homey. Bridge needs to be added first’. But as I understood it the Homey is a bridge in itself so what am I missing? What do I need to do in order to connect a battery operated presence sensor like the ZG 204ZM? I admit that I am fairly new to this so I realize I probably ask a stupid question but I’m really stuck. Any help would be appreciated.
@Gert_Brussen Did you read the ‘how to setup’ from the first post? You are missing Step 1. [APP][PRO] Zigbee2MQTT
Thanks for the update!
The latest version immediately sets all groups as unavailable as soon as the app starts. Don’t know if this is an issue on my end (z2m version or anything), but I can no longer control any groups
Same for me. Zigbee Groups can no longer be controlled via homey and z2m
Ill look into it.
2 Likes
Quick Update. I removed all groups and re added them. They were working for a few hours. Now I cannot control them anymore again.
This issue exists since the last update of the Z2M Homey App. I updated Z2M to the latest version a couple days ago. Everything was working until the recent App update.
I think I should disable Auto Updates in the future, as there is no way to roll back 
It is possible to manually “fix” it by publishing
{
"state": "online"
}
to the availability topic of the group e.g. zigbee2mqtt/group_name/availability
Ok found out whats happening… If the zigbee2mqtt configuration has no availability setting it will default to availability enabled: false (Device-Availability | Zigbee2MQTT)
If availability is not enabled devices will have no availability topic and thus will not be considered offline in homey, but group availability is determined by the availability of devices in that group (Device-Availability | Zigbee2MQTT). According to the manual this should work when the availability is enabled, but if availability is not enabled it still (wrongly imo) publishes “offline” to the groups availability topic…
So basically somewhat of a bug on the side of zigbee2mqtt… Would be nice to have an option to disable availability checking entirely in the homey app
I have enabled availability in the zigbee2mqtt configuration and disabled availability for some switches and now everything seems to be working fine again 
1 Like
v2.7.1 is ready for testing: Zigbee2MQTT | Homey
- Ignore group unavailable/offline.
