# \[APP\]\[Pro\] Zigbee2MQTT - Use Zigbee devices via MQTT

**URL:** <https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214>\
**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:** 17

<div class="post-metadata">

**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:** [August 17, 2024, 3:51am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/327 "2024-08-17T03:51:18Z")

</div>

Are you planning to support device and group scenes?

> **[Scenes | Zigbee2MQTT](https://www.zigbee2mqtt.io/guide/usage/scenes.html)**
>
> Zigbee to MQTT bridge, get rid of your proprietary Zigbee bridges

---

<div class="post-metadata">

**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:** [August 17, 2024, 6:34am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/328 "2024-08-17T06:34:55Z")

</div>

> [@OH2TH](#):
>
> Are you planning to support device and group scenes?

No. Scenes should be done by Homey if you need that.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [August 17, 2024, 6:52am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/329 "2024-08-17T06:52:49Z")

</div>

But z2m scenes are much more performant, Homey’s performance when controlling multiple devices is terrible.

---

<div class="post-metadata">

**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:** [August 17, 2024, 7:11am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/330 "2024-08-17T07:11:33Z")

</div>

I’m open to PR’s 🤗

---

<div class="post-metadata">

**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:** [August 17, 2024, 9:09pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/331 "2024-08-17T21:09:56Z")

</div>

Anyone facing unavailable Zigbee2MQTT devices after Homey restart and only way to fix it is to restart Zigbee2MQTT ? What is strange, I keep getting stats for bridge, like number of messages, device paired etc. but all devices have red exclamation mark until Zigbee2MQTT restart. 🤔

---

<div class="post-metadata">

**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:** [August 20, 2024, 10:44am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/332 "2024-08-20T10:44:25Z")

</div>

v2.4.6 is ready for testing: [Zigbee2MQTT | Homey](https://homey.app/a/com.gruijter.zigbee2mqtt/test)

- Added support for Mode and Sensor setting of MOES BHT series thermostat.

---

<div class="post-metadata">

**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:** [August 23, 2024, 2:22pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/333 "2024-08-23T14:22:46Z")

</div>

@OH2TH any feedback on the MOES support?

---

<div class="post-metadata">

**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:** [August 23, 2024, 4:15pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/334 "2024-08-23T16:15:20Z")

</div>

System mode works, sensor selection doesn’t show up.

---

<div class="post-metadata">

**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:** [August 26, 2024, 6:00am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/335 "2024-08-26T06:00:11Z")

</div>

Re: support for scenes

Reading the source through, but can’t figure out how add a custom action card to the group device.

One card for devices/groups “Set scene to [autocomplete]”, where autocomplete would be the indexed list of available scenes on the device/group.

---

<div class="post-metadata">

**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:** [September 9, 2024, 3:40pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/336 "2024-09-09T15:40:39Z")

</div>

v2.4.7 is ready for testing: [Zigbee2MQTT | Homey](https://homey.app/a/com.gruijter.zigbee2mqtt/test/)

- Extended light effect options.
- Added flow card for setting light effect.
- Fixed MOES thermostat. (Thx @OH2TH )
- Added Sensor setting for thermostats and presence detectors.

---

<div class="post-metadata">

**Author:** ![Martin\_H](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_h/32/7964_2.png) [@Martin\_H](https://community.homey.app/u/Martin_H)\
**Post date:** [September 12, 2024, 6:45pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/337 "2024-09-12T18:45:45Z")

</div>

Everything works great in the new release

Thanks

---

<div class="post-metadata">

**Author:** ![JvdMeulen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jvdmeulen/32/71049_2.png) [@JvdMeulen](https://community.homey.app/u/JvdMeulen)\
**Post date:** [September 18, 2024, 8:16pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/338 "2024-09-18T20:16:47Z")

</div>

I;ve added a presence sensor ( FP1E ), and if i add it to homey i see the following which is great.

 ![Capture 2024-09-18 at 22.11.45@2x](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/c/3cb8a6bcbbcd59a5892d235fab338aabf0ad112f.jpeg)

I see the distance on the device-page, but i can’t work with the distance except in logic-cards.  
It would be great if you could add for presence/distance support for it on the if/else-cards.  
For presence it would be nice to have the “is on” on the else-card

 ![Capture 2024-09-18 at 22.14.02@2x](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/0/a02afa1c24201e6553edc3b08935aa236b79da65.jpeg)

---

<div class="post-metadata">

**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:** [September 19, 2024, 1:31am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/339 "2024-09-19T01:31:11Z")

</div>

> [@JvdMeulen](#):
>
> except in logic-cards.

Exactly! Logic cards can already do what you need.

---

<div class="post-metadata">

**Author:** ![JvdMeulen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jvdmeulen/32/71049_2.png) [@JvdMeulen](https://community.homey.app/u/JvdMeulen)\
**Post date:** [September 19, 2024, 6:16am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/340 "2024-09-19T06:16:12Z")

</div>

Except that i can’t trigger when i get near the sensor for example ( while already beiing detected ).  
Because there’s only the card: when motion is detected… but because i’m already detected it’s not possible.  
And furthermore, in simple-flows i can’t use the else-statement anymore because i would have need to add the logic-card with distance.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [September 19, 2024, 6:37am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/341 "2024-09-19T06:37:05Z")

</div>

> [@JvdMeulen](#):
>
> Because there’s only the card: when motion is detected… but because i’m already detected it’s not possible.

I think you’re asking for a card “When the distance has changed”?

It might be possible to implement, but my guess is that this will trigger too often and will activate the flow rate limiter (which disables flows if they get called too many times).

---

<div class="post-metadata">

**Author:** ![JvdMeulen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jvdmeulen/32/71049_2.png) [@JvdMeulen](https://community.homey.app/u/JvdMeulen)\
**Post date:** [September 19, 2024, 7:01am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/342 "2024-09-19T07:01:33Z")

</div>

> [@robertklep](#):
>
> I think you’re asking for a card “When the distance has changed”?

yeah, sort of

> [@robertklep](#):
>
> his will trigger too often and will activate the flow rate limiter

Ah, didn’t know that.  
I get/see why it isn’t there

---

<div class="post-metadata">

**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:** [October 3, 2024, 6:42am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/344 "2024-10-03T06:42:58Z")

</div>

Hi @Gruijter , seems there is something wrong with triggers - I setup simple conditions to be fired when socket is ON or OFF and I got mutliple fires.

![off](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/e/3e5f948c38bb894b8df019456b8b2567e92b23aa.png) ![on](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/5/d5d9c5fd6292590931de15e7c47d1a00fb06673e.png)

![timeline](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/2/b2d9082482fbb13db390236c2c296db0b82b3dc2.png)  
(I pressed ON / OFF / ON button)

When I initiated ON/OFF from Zigbee2MQTT, it gets triggered just once as it should.  
Diag : e8a15697-4f15-4777-ac49-92d3b35e6f78

Not sure it’s problem on my side ?

---

<div class="post-metadata">

**Author:** ![Jan\_Z](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan_z/32/114085_2.png) [@Jan\_Z](https://community.homey.app/u/Jan_Z)\
**Post date:** [October 8, 2024, 4:08pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/345 "2024-10-08T16:08:21Z")

</div>

Hey guys,

I am new to the mqtt thing and tried to get it up and running with Homey Pro 2023, Zigbee2MQTT and MQTT Broker apps.  
At this point I am stuck adding the bridge. I set up the broker, added a cert and a user.  
I can see in the logfiles, that my created user gets authenticated, does things like subscribing and logs off. In the screen to add the bridge I always get the message: “Error: MQTT settings OK, but no Zigbee2MQTT bridge info found.”  
I dont know which values to enter in the last field to add the bridge. Leaving it blank results in the error message above.

I searched for it but didnt find a proper solution. All software is running on the Homey Pro 2023.

Thanks for any advice.  
Jan

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [October 8, 2024, 4:37pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/346 "2024-10-08T16:37:53Z")

</div>

Have you configured zigbee2mqtt properly so it uses the MQTT broker on your Homey? What do the z2m logfiles say?

---

<div class="post-metadata">

**Author:** ![Jan\_Z](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan_z/32/114085_2.png) [@Jan\_Z](https://community.homey.app/u/Jan_Z)\
**Post date:** [October 8, 2024, 5:48pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/347 "2024-10-08T17:48:42Z")

</div>

I installed MQTT Broker, set up TLS, Ports, Cert and User.  
Then I installed Zigbee2MQTT, filled in the ipv4 (127.0.0.1, localhost etc results in the same error), user, pw, and left the last field blank during bridge device add wizard.

In the Broker Log, I can see the user I entered in Zigbee2mqtt logging in, subscribing etc.  
So, the connection itself seems to be fine.

Did I miss something?

[Previous page](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214.md?page=16)

[Next page](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214.md?page=18)
