You should read the first post of this topic for intructions.
You need to setup first the Zigbee2MQTT server where you configure SLZB-06 as the zigbee controller. You will also need MQTT broker and finally you can setup this app.
SLZB-06 must be in controller mode and there is no support for the hub mode.
New test version 2.9.0 is available: Zigbee2MQTT | Homey
@owuerker many thx for your kind donation! 
I have installed Z2M on my synology and homey. First I added several tuya indoor and some nous A4Z outdoor double plugs to have a decent mesh to build on.
However, the Nous A4Z are powering off by itself and I dont know why. So far I created no flows for themselves. I cant see why they are powering off in the z2m webfrontend. Homey just says that they were powered off by z2m. Its the same info no matter if the auto power off or if I power them off in webfrontend myself. Just toggling in homey makes a difference in the homey device log.
I also tried updating the Nous A4Z firmware on the OTA page but they are the only devices without fw info although they are listed as compatible.
Any hints how I could tackle these issues?
@Gruijter: Is it possible to change this name?
In Z2M, my temp/hum/press T1 sensors from Aqara report both “temperature” (= measured temperature) and “device_temperature” (temperature of the sensor itself). Multiple Aqara T1(?) Devices report “device_temperature” by the way.
{
"battery": 26,
"device_temperature": 23,
"humidity": 51.45,
"last_seen": "2025-06-14T08:17:40+02:00",
"linkquality": 65,
"power_outage_count": 15,
"pressure": 1009.6,
"temperature": 23.71,
"voltage": 2889
}
Both enter Homey as “temperature”:
That’s just difficult, because you can’t distinguish one from the other:
Shouldn’t “device_temperature” simply appear with the same name in Homey?
I have a working setup with Homey Pro and Z2M installed on a Raspberry Pi 3, and I want to migrate to a mini PC. So I installed Proxmox with MQTT and Z2M in LXC, as well as HomeAssitant in a VM: everything works fine.
My problem is that in Homey, when I want to add the bridge (so I give it all the information to connect to the mini PC’s MQTT: IP login PSW topic), it can’t add the bridge, and I have no idea why.
Any ideas? Thanks.
I am also running Homeassistant and I use there a USB zigbee stick with zigbee2MQTT.
I can add from within HA zigbee devices via zigbee2mqtt and within mqtt I can find and use these devices in HA.
Of-course I can use the HA community app the create a device in Homey and then use it.
But is it not possible to use the zigbee2mqtt directly?
The HA integration connect to a MQTT broker running on my NAS.
So is it not possible that Homey connect to that broker aswell and also retrieves those devices?
That way I only have to add them once (via HA) and then I can use the device in both systems (HA+Homey) without to have to create and setup each HA enitity in Homey.
Simply connect the Homey app to the same broker.
Thought you were on a well deserved holiday, @Gruijter. 
Did you see my post here above? Any idea if this can be changed?
The app automatically uses the naming that Z2M uses internally. Since this mapping is automatic I cannot change it in the Homey app.
Thanks for the reply, @Gruijter.
Are there other “internal” names then?
Because in the Z2M interface that I see, there are different names for each:
It should use those. Maybe restart app helps?
Unfortunately restarting the app didn’t help.
Could it be that every value in °C is shown as “temperature”?
In MQTT Explorer I see that “device_temperature” is actually reported from Z2M to MQTT
I sent you a report if that helps:
6def9c62-b767-45d7-82c7-228b54388e09
I installed the app to Homey, added my broker which is running on my NAS.
When I add a device it finds the zigbee devices which are also in HA.
When i Add a device into homey it is added, but then it stops.
The devices do not show any data and also cannot be controlled…
I restarted the APP but nothing seems to be changing..
What is wrong here, did I miss something?
Probably.
I just installed the z2m bridge device and after that, all 55 z2m devices without any issues.
But, I use the MQTT Broker add-on on Homeassistant → maybe you should restart the broker on your NAS, or install a Homey MQTT Broker app to see if that works better?
(This app may be overkill, but it has a broker built-in)
Meanwhile I tried to hide the value/capability from Homey by filtering out the attribute in Z2M:
But in Homey it keeps showing up, even after deleting the device from Homey, restarting Z2M and MQTT and re-adding the device in Homey.
That could have been a workaround, but it seems better when Homey indicated “device temperature” as the attribute is called in MQTT…
Device temperature is still a nice-to-have… 
Any idea, @Gruijter?
I sent you a report with number 6def9c62-b767-45d7-82c7-228b54388e09
Will have a look when I have time. Not top of my list though 
Would be great, thanks in advance, @Gruijter.
Is there an option (flow card etc) to check when bridge is offline and then a card ro restart it?
I noticed that the bridge goes reguarly offline and you manually have to push the button to restart it, this happens when there is a hickup in the network connection (or a reboot/update of HA etc)
Now the device are suddenly offline, but the broker is not. A simple restart bridge fixes mosttimes this problem.
I wanted to created a flow something like this:
If bridge goes offline → wait X → AND bridge is offline → Then restart brigde
But it seems that there are no card triggers when bridge goes offline and also no card to restart the bridge (there is a restart button, so why no card?)
I hope this can be added (or better, a watchdog which automaticly reconnects/restart when it goed offline)
These options are available in the app :).
There is the following option in the When cards:
The Offline Alarm turned On
The And card can be fixed with a logic card:
Bridge offline is equal to ‘yes’
Then on the Then cards you have the following option:
Restart Z2M
So you have the following flow:
