# \[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:** 21

<div class="post-metadata">

**Author:** ![Eirik\_Solheim](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eirik_solheim/32/111412_2.png) [@Eirik\_Solheim](https://community.homey.app/u/Eirik_Solheim)\
**Post date:** [January 10, 2025, 3:39pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/408 "2025-01-10T15:39:35Z")

</div>

First of all thank you very much for making this app. The built in zigbee implementation is not stable enough with many devices. And it is a pain to add lots of hubs and end up with lots of zigbee networks. Zigbee2mqtt support a wide range of devices and is a very stable and powerful system. Being able to integrate it into Homey is very nice!

I have added a lot of different devices, and most of them works fine. Currently there are some problems with specific Ikea remotes, but this is a problem in Zigbee2mqtt and not the app for Homey.

But I have one request: I added the Vindstyrka air quality monitor from Ikea. It exposes temperature, humidity, PM2.5, VoC and link quality to Zigbee2mqtt. But only temperature, humidity and link quality all the way to Homey. Would this be possible to fix in a future version?

---

<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:** [January 10, 2025, 3:51pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/409 "2025-01-10T15:51:34Z")

</div>

> [@Eirik\_Solheim](#):
>
> Would this be possible to fix in a future version?

Probably. But I would need a device to develop, test and maintain. See 1st post how to donate.

---

<div class="post-metadata">

**Author:** ![SvenM](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/svenm/32/113028_2.png) [@SvenM](https://community.homey.app/u/SvenM)\
**Post date:** [January 14, 2025, 5:51pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/410 "2025-01-14T17:51:21Z")

</div>

Can’t anyone help me?

---

<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:** [January 15, 2025, 12:20pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/411 "2025-01-15T12:20:15Z")

</div>

@Eirik_Solheim many thx for your kind donation. Much appreciated! ❤🍺

---

<div class="post-metadata">

**Author:** ![Eirik\_Solheim](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eirik_solheim/32/111412_2.png) [@Eirik\_Solheim](https://community.homey.app/u/Eirik_Solheim)\
**Post date:** [January 15, 2025, 12:22pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/412 "2025-01-15T12:22:13Z")

</div>

I understand. Regardless of the air quality device: I really appreciate this app. So I’ve sent a donation your way. Keep up the good work.

---

<div class="post-metadata">

**Author:** ![Eirik\_Solheim](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eirik_solheim/32/111412_2.png) [@Eirik\_Solheim](https://community.homey.app/u/Eirik_Solheim)\
**Post date:** [January 15, 2025, 12:45pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/413 "2025-01-15T12:45:27Z")

</div>

I guess this is an example of a message from the Vindstyrka air quality sensor:

Topic: zigbee2mqtt/Ikea Vindstyrka LuftmålerQoS: 0

{“humidity”:26,“linkquality”:168,“pm25”:4,“temperature”:23,“update”:{“installed\_version”:16777233,“latest\_version”:16777233,“state”:“idle”},“voc\_index”:89}

---

<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:** [January 15, 2025, 3:25pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/414 "2025-01-15T15:25:16Z")

</div>

I will have a look what I can do in the blind.

---

<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:** [January 16, 2025, 3:01pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/415 "2025-01-16T15:01:19Z")

</div>

new version 2.8.0 is ready

- Added support for voc, voc\_index, pm10, pm25 (@Eirik_Solheim please test)
- Mapping of smoke\_concentration changed to pm1
- Fixed joining action and timer for Z2M\>=2.0

The joining/joining timer in Homey works with the new V2 Z2M. If you are still on V1, please upgrade for maximum compatibility with Homey: [Zigbee2MQTT 2.0.0 breaking changes · Koenkk/zigbee2mqtt · Discussion #24198 · GitHub](https://github.com/Koenkk/zigbee2mqtt/discussions/24198)

---

<div class="post-metadata">

**Author:** ![Eirik\_Solheim](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eirik_solheim/32/111412_2.png) [@Eirik\_Solheim](https://community.homey.app/u/Eirik_Solheim)\
**Post date:** [February 4, 2025, 11:04am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/416 "2025-02-04T11:04:57Z")

</div>

Looks perfect. We now have PM2.5 and VOC index in both the main display of the device and in “insights”. Thank you!

---

<div class="post-metadata">

**Author:** ![Eirik\_Solheim](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eirik_solheim/32/111412_2.png) [@Eirik\_Solheim](https://community.homey.app/u/Eirik_Solheim)\
**Post date:** [February 4, 2025, 11:05am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/417 "2025-02-04T11:05:39Z")

</div>

![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/e/2eaca21d946480b457e9ead1db9f3ef4ff13bc65.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:** [February 4, 2025, 11:58am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/418 "2025-02-04T11:58:00Z")

</div>

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

- Added support for Bosch [TwinGuard](https://www.zigbee2mqtt.io/devices/8750001213.html#bosch-8750001213)
- Added Self\_test, Pre\_alarm, Heartbeat, AQI, sensitivity, alarm\_sound and siren\_state.
- Added smokealarm class and icon.
- Fix onoff button titles.

---

<div class="post-metadata">

**Author:** ![coyotte508](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/coyotte508/32/121433_2.png) [@coyotte508](https://community.homey.app/u/coyotte508)\
**Post date:** [February 14, 2025, 7:56pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/420 "2025-02-14T19:56:52Z")

</div>

Very nice integration, using it with [Legrand 412171 control via MQTT | Zigbee2MQTT](https://www.zigbee2mqtt.io/devices/412171.html) and [Legrand 412172 control via MQTT | Zigbee2MQTT](https://www.zigbee2mqtt.io/devices/412172.html)

Feedback regarding the contactor (412171)

By default, with a brand new contactor the `device_mode` is set to `auto` (then state depends on wire inputs, cannot be defined via mqtt). I had to set it to `switch` manually (via a mqtt command line tool), and then it works fine in the app.

Recommendation: when changing state, if `device_mode` is set to `auto`, set it to `switch`. Or allow user to change `device_mode`.

Note: an electrician set up those devices for me in the electrical panel, do not recommend doing the contactor on your own if you’re not an electrician, as serious juice can go through it and it’s in the electrical panel.

---

<div class="post-metadata">

**Author:** ![daniel3](https://avatars.discourse-cdn.com/v4/letter/d/a4c791/32.png) [@daniel3](https://community.homey.app/u/daniel3)\
**Post date:** [February 24, 2025, 3:08am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/421 "2025-02-24T03:08:08Z")

</div>

When I add a Philips Hue light via Zigee2MQTT to Homey I have an option to change the ‘effect’ as well as the ‘Power on Behavior’ within the list selector of the device itself. But when I add an ‘Then’ card for that light, I can only select ‘Set Power On Behavior to’ and don’t have an option to change the effect. Would it be possible to add this card to the app?

---

<div class="post-metadata">

**Author:** ![Geim](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/geim/32/113356_2.png) [@Geim](https://community.homey.app/u/Geim)\
**Post date:** [February 24, 2025, 1:40pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/422 "2025-02-24T13:40:42Z")

</div>

Great, flowcard works fine for setting the Valve opening degree. So instead of an on-off regulation I could implement a PID regulator. But… I’m no expert in PID, do you have it implemented for yourself? Care to share it?

---

<div class="post-metadata">

**Author:** ![daniel3](https://avatars.discourse-cdn.com/v4/letter/d/a4c791/32.png) [@daniel3](https://community.homey.app/u/daniel3)\
**Post date:** [February 28, 2025, 12:52pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/423 "2025-02-28T12:52:53Z")

</div>

I noticed that I can also change the effect with “Set payload to” then card. That helps with setting up the effect. Unfortunately this card isn’t available for groups. Could this card also be made available for light groups?

---

<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:** [March 2, 2025, 7:00am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/424 "2025-03-02T07:00:26Z")

</div>

PSA: don’t update zigbee2mqtt to 2.1.2, unless you want a lot of problems.

---

<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:** [March 2, 2025, 7:02am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/425 "2025-03-02T07:02:36Z")

</div>

Oow… what kind of trouble?

---

<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:** [March 2, 2025, 7:07am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/426 "2025-03-02T07:07:54Z")

</div>

Devices that become unavailable. It _might_ be a Home Assistant-only thing, but the only thing that changed is the z2m version, and 2.1.2 introduced a very big change (that in theory is really cool: it greatly decreases the amount of memory used by z2m) that might have introduced these issues.

Issue reports are popping up both on the HA forum and on the z2m Github issue tracker.

**EDIT** : it’s related to another change, and it’s causing lights that support colors to fail. More info [here](https://github.com/Koenkk/zigbee2mqtt/issues/26553).

**EDIT 2** : appears to be fixed in 2.1.3: [2.1.2 - makes the hue lighbulb NOT report to MQTT, show as "not available". · Issue #26557 · Koenkk/zigbee2mqtt · GitHub](https://github.com/Koenkk/zigbee2mqtt/issues/26557#issuecomment-2692607724)

---

<div class="post-metadata">

**Author:** ![daniel3](https://avatars.discourse-cdn.com/v4/letter/d/a4c791/32.png) [@daniel3](https://community.homey.app/u/daniel3)\
**Post date:** [March 17, 2025, 10:22am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/427 "2025-03-17T10:22:41Z")

</div>

> I noticed that I can also change the effect with “Set payload to” then card. That helps with setting up the effect. Unfortunately this card isn’t available for groups. Could this card also be made available for light groups?

@Gruijter Would it be possible to create a “Set payload to” card for groups? That would really help with the flows I’m trying to build 🙂

---

<div class="post-metadata">

**Author:** ![Henk\_Renting](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_renting/32/87634_2.png) [@Henk\_Renting](https://community.homey.app/u/Henk_Renting)\
**Post date:** [March 27, 2025, 3:28pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/428 "2025-03-27T15:28:32Z")

</div>

Zigbee2MQTT beginner here, so please bear with me.. 🙂

I am having this remote:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/7/e776327cd99ef713f4f1a6c878d955f6d9ca330c.png)

which reports only “on” for all on-buttons 1-4 and “off” for all off-buttons 1-4.  
But is it reporting a different “action\_group” for each set of on-off buttons 1-4.  
on/off buttons 1: 6401  
on-off buttons 2: 6402  
etc.

Like on button 1:

```auto
{
    "battery": 25,
    "last_seen": "2025-03-27T16:22:27+01:00",
    "linkquality": 102,
    "action": "on",
    "action_group": 6401
}

```

And on button 2:

```auto
{
    "battery": 25,
    "last_seen": "2025-03-27T16:22:51+01:00",
    "linkquality": 87,
    "action": "on",
    "action_group": 6402
}

```

(“action\_group” is published to MQTT as well, checked in MQTT Explorer)

When making a flow in Homey I can only choose a “action” variable:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/8/18bba0de6f1a474122ea3e845c7d1761c1c118a8.png)

Is there a way to choose a “action\_group” variable as well (AND-flowcard)?  
Google tells me there are multiple remotes using this: [link](https://www.google.com/search?q=zigbee2mqtt+%22action_group%22&rlz=1C9BKJA_enNL1077NL1078&oq=zigbee2mqtt+%22action_group%22&gs_lcrp=EgZjaHJvbWUyBggAEEUYOTIGCAEQRRg80gEJMjA0NTNqMGo3qAIJsAIB4gMEGAEgXw&hl=nl&sourceid=chrome-mobile&ie=UTF-8)

Or are there other ways to get this remote to work for all buttons separately?

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

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