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

<div class="post-metadata">

**Author:** ![Pepa\_Vlcek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pepa_vlcek/32/79854_2.png) [@Pepa\_Vlcek](https://community.homey.app/u/Pepa_Vlcek)\
**Post date:** [February 5, 2024, 3:02pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/225 "2024-02-05T15:02:21Z")

</div>

Ok, I dont have problem for donate you to buy the device.  
How much is it in your country?  
Thank you.

---

<div class="post-metadata">

**Author:** ![Kringloper](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kringloper/32/70714_2.png) [@Kringloper](https://community.homey.app/u/Kringloper)\
**Post date:** [February 7, 2024, 12:44pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/226 "2024-02-07T12:44:53Z")

</div>

> [@Kringloper](#):
>
> Is it possible for you (without the physical device) to add a third state and maybe differentiate naming for the three buttons?

@Gruijter , I managed to change some of your code in a local development version. A center option is added and for triggers also a left, right, center are now differentiated. However, the state of all three is still ‘Aangezet’ which can be on or off. Couldn’t find the place to change that.  
I am not familiair how to initiate a pull request, so for now i can just use my local development version.

---

<div class="post-metadata">

**Author:** ![Magnus\_Reiten](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/magnus_reiten/32/9740_2.png) [@Magnus\_Reiten](https://community.homey.app/u/Magnus_Reiten)\
**Post date:** [February 9, 2024, 1:39pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/227 "2024-02-09T13:39:46Z")

</div>

Hi,  
Very helpful application and guidance.

I’ve set up a RP4 with zigbee2mqtt, and paired 4 Aqara Temp sensors WSDCGQ11LM. The sensors are added to my Homey and are working as expected, but the temperature is not recognised by the vThermo or \< group \> app. The vHumidity works ok.  
In \< group \> app the temp variable is presented like this: capability.measure\_temperature.sensor.title

What am I doing wrong?

---

<div class="post-metadata">

**Author:** ![Alex069](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/alex069/32/79555_2.png) [@Alex069](https://community.homey.app/u/Alex069)\
**Post date:** [February 9, 2024, 2:11pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/228 "2024-02-09T14:11:14Z")

</div>

Hello, then what’s the reason to bet the homey pro if you need an additional bridge?

Just asking out of curiosity…

The homey already has the Zigbee inside… so why an additional bridge…

---

<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 9, 2024, 2:40pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/229 "2024-02-09T14:40:41Z")

</div>

> [@Alex069](#):
>
> why an additional bridge…

See first post of this thread.

---

<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 9, 2024, 2:42pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/230 "2024-02-09T14:42:07Z")

</div>

> [@Magnus\_Reiten](#):
>
> \< group \> app

Better ask the developer of the GROUP app 😉

---

<div class="post-metadata">

**Author:** ![Alex069](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/alex069/32/79555_2.png) [@Alex069](https://community.homey.app/u/Alex069)\
**Post date:** [February 9, 2024, 6:55pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/231 "2024-02-09T18:55:19Z")

</div>

it’s not like i didn’t read the first post, BUT, still how to connect it to the homey, not creating a new HA… because that’s not the point

---

<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:** [February 9, 2024, 6:56pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/232 "2024-02-09T18:56:36Z")

</div>

Quick answer: zigbee2mqtt is much better at Zigbee than Homey is.

---

<div class="post-metadata">

**Author:** ![Magnus\_Reiten](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/magnus_reiten/32/9740_2.png) [@Magnus\_Reiten](https://community.homey.app/u/Magnus_Reiten)\
**Post date:** [February 9, 2024, 7:24pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/233 "2024-02-09T19:24:17Z")

</div>

Ok, anyone got the vThermo app working with Aqara temp sensor? It doesn’t recognise any temp values. The vHumid app works fine and gets the right values…

---

<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 9, 2024, 7:38pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/234 "2024-02-09T19:38:41Z")

</div>

@balmli might be able to help, since he is the creator of the vThermo app. I suspect the capability name needs to be added to his app.

---

<div class="post-metadata">

**Author:** ![Magnus\_Reiten](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/magnus_reiten/32/9740_2.png) [@Magnus\_Reiten](https://community.homey.app/u/Magnus_Reiten)\
**Post date:** [February 12, 2024, 1:09pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/235 "2024-02-12T13:09:40Z")

</div>

I find this error message strange, what does it mean? Something I do wrong?

 ![IMG_7114](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/4/f45315cf1604902dc0d3bd3e5a219106bdcef679.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 12, 2024, 5:01pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/236 "2024-02-12T17:01:35Z")

</div>

> [@Magnus\_Reiten](#):
>
> this error message

Wrong forum. That is not a Homey error. Tou can go to the zigbee2mqtt discord for help.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [February 13, 2024, 1:54am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/237 "2024-02-13T01:54:31Z")

</div>

OT, sorry Robin, but just bumped into this,

 ![Screenshot_20240213-024415_Chrome](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/d/fdf524eee06f9edf6b64c44bd37c1336c4c1ba3f.jpeg)  
To get rid of the error, @Magnus_Reiten you just have to enter a value for ‘temperature calibration’ of that device, at the Z2M interface; start with a `0` for instance:  
 ![Screenshot_20240213-025046_Chrome](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/8/f855a64d140228b81fe256f3538b83ebf3129365.jpeg)

---

<div class="post-metadata">

**Author:** ![Magnus\_Reiten](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/magnus_reiten/32/9740_2.png) [@Magnus\_Reiten](https://community.homey.app/u/Magnus_Reiten)\
**Post date:** [February 14, 2024, 8:53pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/238 "2024-02-14T20:53:37Z")

</div>

Thanks @Peter_Kawa, the error messages are gone!

But I´m still struggling with the capability ID for temperature. The device is registered with the capablility ID measure\_temperature.sensor in the Homey App, but it should be measure\_temperature without the .sensor at the end. I asked the developer of zigbee2mqtt and he says it has to be changed in the Homey App.  
So I´m stuck with two developers point at each other 🙂

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [February 14, 2024, 9:27pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/239 "2024-02-14T21:27:18Z")

</div>

YW!

> [@Magnus\_Reiten](#):
>
> measure\_temperature.sensor

Why do you think that is a problem? I’ve those all over Homey, but I use the HA community app to connect my Z2M (as HA add-on) devices

![Screenshot from 2024-02-14 22-23-46](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/b/0bb5b9aa49b125e84859959d9b1f8a4c0e6c7179.png)

 ![Screenshot from 2024-02-14 22-24-57](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/5/85443868c1d2a4668b59a287ce1afaacadf2754a.png)

Works fine here…

---

<div class="post-metadata">

**Author:** ![Laurent\_Chardin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/laurent_chardin/32/99190_2.png) [@Laurent\_Chardin](https://community.homey.app/u/Laurent_Chardin)\
**Post date:** [February 15, 2024, 10:07am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/240 "2024-02-15T10:07:07Z")

</div>

@Peter_Kawa Looks like your setup is : Sensor \> Z2m \> HA \> Homey with HA app.

I believe @Magnus_Reiten has: Sensor \> Z2m \> Homey with Z2M app.

Therefore it is possible that HA is doing some datamodel normalization and your devices are exposed in Homey through the HA app.

I guess here the issue is about the way the “Homey Z2M App” is mapping z2m data into homey devices data.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [February 15, 2024, 11:17pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/241 "2024-02-15T23:17:15Z")

</div>

Correct, Laurent, but it shouldn’t matter. So I installed this zigbee2mqtt app and tested some temperature sensors;  
The connection now used is:  
_Sensor \> Z2M \> MQTT Broker \> Homey Z2M app \> Homey (so no HA in between)_.

As you can see at the developer page screenshot below, the only temp sensor is exposed as sub-capability `measure_temperature.sensor`, and both lux values are exposed as capability `measure_luminance` and as sub-capability `measure_luminance.lux`, and it works fine.  
And we can rule out HA is ‘normalizing’ anything.

I agree the first temperature capability _should_ be named `measure_temperature`, to follow standards, but naming it as a sub-capability `measure_temperature.sensor`, does not change the functioning in Homey as far as my knowledge reaches.  
Except it will fail with thermostat devices, when the _target\_temperature doesn’t have the same dot suffix_:

> ![Screenshot from 2024-02-16 00-41-21](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/9/c9ebe318f823dfb689280f01beffb5aed5729d84.png)  
> .  
> [Source](https://apps.developer.homey.app/the-basics/devices/capabilities)

 ![Screenshot from 2024-02-15 23-28-10](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/d/6d017937418a381b0afa8ce987c57138b3323484.png)

.

As you can see in MQTT Explorer screenshot below, Z2M just sends ‘temperature’ as sensor name, not ‘temperature.sensor’, or ‘temperature\_sensor’

> [@Laurent\_Chardin](#):
>
> I guess here the issue is about the way the “Homey Z2M App” is mapping z2m data into homey devices data.

Agreed, the Homey Z2M app in some way seems to add `.sensor ` to the first, or only, ` measure_temperature` capability.

 ![Screenshot from 2024-02-16 00-15-11](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/9/d914080ee31d198d3ce420565be7ad1f53ad96bb.png)

---

<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 18, 2024, 11:18am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/242 "2024-02-18T11:18:26Z")

</div>

> [@Peter\_Kawa](#):
>
> omey Z2M app in some way seems to add `.sensor ` to the first, or only, ` measure_temperature` capability.

That is because in Z2M there are multiple capabilities that have a measure\_temperature. In Homey they all need to be mapped in a unique way. I could switch around `temperature` with `local_temperature`. But this would mean that zigbee devices that use local\_temperature wil not be seen by other thermostat apps in Homey. So someone else might get duped when I switch it. I will think about it a bit more..

---

<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 18, 2024, 11:26am UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/243 "2024-02-18T11:26:51Z")

</div>

New version 2.3.0 available as test: [Zigbee2MQTT | Homey](https://homey.app/a/com.gruijter.zigbee2mqtt/test/)

- Added support for center button on three-way switch. (Thx @Kringloper).
- Replaced mapping for temperature and temperature.local capabilities.
- Fixed capabilities naming and units migration.
- Added open\_window mapping.

@Magnus_Reiten Please test the interface with vThermo app  
@Laurent_Chardin @Peter_Kawa Please check if measure\_temperature capabilities still work for your use case

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [February 18, 2024, 9:05pm UTC](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214/244 "2024-02-18T21:05:14Z")

</div>

As quick as always 😉  
Here it works for z2m sensors having max. one temperature value, both existing and new added sensors got the `measure_temperature` capability now

 ![Screenshot_20240218-214949_Firefox](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/2/d2e77c858590beeb18991804078ed8e9f8e3fb27.jpeg)

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

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