# \[APP\]\[Pro\] Zigbee2MQTT - Use Zigbee devices via MQTT **URL:** \ **Category:** Apps\ **Tags:** app, zigbee, tools, homey-pro\ **Created:** [June 26, 2023, 7:02am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214 "2023-06-26T07:02:44Z")\ **Posts on this page:** 20\ **Page:** 14
**Author:** ![Sre](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sre/32/73560_2.png) [@Sre](https://community.homey.app/u/Sre)\ **Post date:** [March 24, 2024, 7:27pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/265 "2024-03-24T19:27:28Z")
Yeah I renamed my device but its definitely a bug that I would like to resolve for others, not sure though when I would have time for it, I’m expecting a second baby this week 😅 ---
**Author:** ![Sre](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sre/32/73560_2.png) [@Sre](https://community.homey.app/u/Sre)\ **Post date:** [March 25, 2024, 2:11pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/266 "2024-03-25T14:11:32Z")
> [@Sre](#): > > I have an issue where devices that have simular names seem to react to events for example I have a light named “Office” and a blind named “Office blinds” and it looks like the office blinds also receive the office events, is includes/contains used to match events to devices resulting in “office blinds”.contains(“office”) reporting a false positive? I was able to spend some last minute time on this could you test this for me? > > > Devices that have names that are substrings of other device names react to inval…id events for example I have a light named “Office” and a blind named “Office blinds” and the office blinds also receive the office events, the fix is to replace a .includes if statement with a equals statements so that previously > “bridge/office blinds”.contains(“bridge/office”) would have given a false positive and now with “bridge/office blinds” == “bridge/office” it doesn't Thanks! ---
**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\ **Post date:** [March 26, 2024, 7:21am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/267 "2024-03-26T07:21:57Z")
> [@Gruijter](#): > > But due to that I need to map all possible Z2M ‘exposes’ to a unique ‘capability’ in Homey, support needs to be added in Heimdal itself. Just recent experience during testing of [Bticino/Legrand/Netatmo App for Homey | Homey](https://homey.app/en-us/app/com.galcar.netatmo/BticinoLegrandNetatmo/) from @Gal_Carmeli - we had similar problem, with multiple custom “alarm motion” capabilities, while actually Gal merge them into one/default `alarm_motion` capability (as example - any motion trigger default one ). Wouldn’t that be solution / workaround also for Zigbee2MQTT, eg. creating always default one for any kind of motion/tilt/vibration into `alarm_motion`, `alarm_contact` ? Just idea, not mine but works 😉 ![motion](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/5/750d37043adeea1e97270066b34f63799cfb5127.png) ---
**Author:** ![Gruijter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gruijter/32/1973_2.png) [@Gruijter](https://community.homey.app/u/Gruijter)\ **Post date:** [March 26, 2024, 7:26am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/268 "2024-03-26T07:26:29Z")
Thx @Sharkys ! I’ll think about it. ---
**Author:** ![L3nny](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/l3nny/32/102010_2.png) [@L3nny](https://community.homey.app/u/L3nny)\ **Post date:** [March 26, 2024, 11:37pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/269 "2024-03-26T23:37:34Z")
> [@Sharkys](#): > > Wouldn’t that be solution / workaround also for Zigbee2MQTT, eg. creating always default one for any kind of motion/tilt/vibration into `alarm_motion`, `alarm_contact` ? Is there any downside implementing it this way? ---
**Author:** ![Gruijter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gruijter/32/1973_2.png) [@Gruijter](https://community.homey.app/u/Gruijter)\ **Post date:** [March 27, 2024, 1:24am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/270 "2024-03-27T01:24:40Z")
Yes. Complexity in coding and therefore difficult to maintain the app. My time is limited. ---
**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\ **Post date:** [March 27, 2024, 6:11am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/271 "2024-03-27T06:11:45Z")
If you don’t believe it’s worth it or it’s too complex change, please don’t spend time on it - it was just suggestions, I thought adding new capabilities for newly registered devices (or repaired one - but looks like there is no repair function - so possibly newly added only) might be elegant and easy solution and also helping in others areas, not only Heimdall, but seems it’s not the case. Thank you for all you do. ---
**Author:** ![staeff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/staeff/32/79712_2.png) [@staeff](https://community.homey.app/u/staeff)\ **Post date:** [March 27, 2024, 3:53pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/272 "2024-03-27T15:53:51Z")
There currently are only 5 very niche devices which even expose both presence and occupancy. What about just mapping both to `alarm_motion`? ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/1/e186beeff13b5d84d25ad613e826feff0a2a9618.jpeg) ---
**Author:** ![L3nny](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/l3nny/32/102010_2.png) [@L3nny](https://community.homey.app/u/L3nny)\ **Post date:** [March 28, 2024, 2:20pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/274 "2024-03-28T14:20:16Z")
@Gruijter Can you add a AND flowcard for blinds, so you can check if the blind is closed or not. Could also something like more or less then value of position? ---
**Author:** ![Gruijter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gruijter/32/1973_2.png) [@Gruijter](https://community.homey.app/u/Gruijter)\ **Post date:** [March 28, 2024, 3:42pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/275 "2024-03-28T15:42:37Z")
> [@L3nny](#): > > AND flowcard for blinds, so you can check if the blind is closed or not You can already do that with a logic card. ---
**Author:** ![L3nny](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/l3nny/32/102010_2.png) [@L3nny](https://community.homey.app/u/L3nny)\ **Post date:** [March 28, 2024, 3:53pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/276 "2024-03-28T15:53:49Z")
> [@Gruijter](#): > > You can already do that with a logic card. Totally forgot about it 🤦‍♂️ Found it! ---
**Author:** ![Gruijter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gruijter/32/1973_2.png) [@Gruijter](https://community.homey.app/u/Gruijter)\ **Post date:** [March 30, 2024, 12:45pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/277 "2024-03-30T12:45:38Z")
new version 2.3.4 was just released. - Fixed device topic match. Thx @Sre and @staeff ! ---
**Author:** ![Radon](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/radon/32/8196_2.png) [@Radon](https://community.homey.app/u/Radon)\ **Post date:** [April 7, 2024, 6:35pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/278 "2024-04-07T18:35:09Z")
Hi, this morning none of my devices worked as it said my bridge was disconnected. Restarted app, and all devices came back. However, it still says my bridge is disconnected. But it is not. HP19, also restarted Homey to test. Everything works, just wanted to let you know about the false positive ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/1/719d58baf52626fb1b1e795f82c9d363038bf76c.jpeg) ---
**Author:** ![pikausp](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pikausp/32/79935_2.png) [@pikausp](https://community.homey.app/u/pikausp)\ **Post date:** [April 11, 2024, 9:26pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/279 "2024-04-11T21:26:55Z")
@Gruijter thank you for the great app. I have been using it to access aqara switches in decoupled mode. I bought a new Aqara T1M ceiling light as it’s now supported by z2m. I can control the light as expected directly, but when I import it to homey I can’t do anything at all (on/off, colors, brightness etc). The light has 2 light sources in case that might be an issue? > **[Aqara CL-L02D control via MQTT | Zigbee2MQTT](https://www.zigbee2mqtt.io/devices/CL-L02D.html)** > > Integrate your Aqara CL-L02D via Zigbee2MQTT with whatever smart home infrastructure you are using without the vendor's bridge or gateway. The light in question ---
**Author:** ![Gruijter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gruijter/32/1973_2.png) [@Gruijter](https://community.homey.app/u/Gruijter)\ **Post date:** [April 11, 2024, 11:49pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/280 "2024-04-11T23:49:33Z")
> [@pikausp](#): > > The light in question This one needs special stuff. If you are willing to donate a device I am willing to try adding support. ---
**Author:** ![OH2TH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oh2th/32/111414_2.png) [@OH2TH](https://community.homey.app/u/OH2TH)\ **Post date:** [April 21, 2024, 7:01am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/281 "2024-04-21T07:01:38Z")
I have [Moes BHT-002-GCLZB control via MQTT | Zigbee2MQTT](https://www.zigbee2mqtt.io/devices/BHT-002-GCLZB.html) thermostats, temperature and target\_temperature works perfectly. What does the Auto/Manual/Holiday preset selection do? I’d be in need to set `system_mode` between `heat` and `off` from a flow to turn of heating when A/Cs are cooling. Also condition cards for System mode is/isn’t heat/off would be useful for flows. ---
**Author:** ![OH2TH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oh2th/32/111414_2.png) [@OH2TH](https://community.homey.app/u/OH2TH)\ **Post date:** [April 21, 2024, 7:15am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/282 "2024-04-21T07:15:25Z")
Wouldn’t mind if the sensor selection IN/AL/OU would be visible. ---
**Author:** ![Gruijter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gruijter/32/1973_2.png) [@Gruijter](https://community.homey.app/u/Gruijter)\ **Post date:** [April 22, 2024, 6:03am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/283 "2024-04-22T06:03:43Z")
@josserke84 many thanks for your kind donation. Much appreciated! 🥰🍺 ---
**Author:** ![Gabriel\_Laguna](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gabriel_laguna/32/83144_2.png) [@Gabriel\_Laguna](https://community.homey.app/u/Gabriel_Laguna)\ **Post date:** [April 28, 2024, 9:29am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/284 "2024-04-28T09:29:22Z")
This is amazing! Thank you for making this happen! 😍 ---
**Author:** ![Gruijter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gruijter/32/1973_2.png) [@Gruijter](https://community.homey.app/u/Gruijter)\ **Post date:** [May 1, 2024, 3:18pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/285 "2024-05-01T15:18:31Z")
New version 2.4.0 is ready as test: [Zigbee2MQTT | Homey](https://homey.app/a/com.gruijter.zigbee2mqtt/test/) - Added support for more ikea devices. - Changed alarm\_motion key so that it is presented as zone activity. For devices that have multiple presence or motion alarm this update might cause issues. Please let me know if that is a problem for you. On the upside, this change will let more alarm devices report as Homey zone activity. Thx @Sre for the PR! [Previous page](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214.md?page=13) [Next page](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214.md?page=15)