Zigbee2mqtt: getting rid of your proprietary Zigbee bridges (Xiaomi, Hue, TRADFRI)

Has anyone managed to implement the Ikea remote control? If so, can you please share that part of devices.js?

I use the IKEA dimmer(ICTC-G-1) with succes

When there is a new converter added, when/how will it be available with the Hassio-addon?

Somebody else got massive problems with connecting Hue dimmer switch’s RWL021?
Some Working fine with pairing - others refuses a typical output.

Jan 07 12:20:26 hassbian npm[534]:   zigbee2mqtt:error 2019-1-7 12:20:26 Cannot get the Node Descriptor of the Device: 0x00178801103f8e19 (Error: Timed out after 10000 ms)
Jan 07 12:20:33 hassbian npm[534]:   zigbee2mqtt:debug 2019-1-7 12:20:33 Received zigbee message of type 'devInterview' with data '"0x00178801103f8e19"'
Jan 07 12:20:33 hassbian npm[534]:   zigbee2mqtt:info 2019-1-7 12:20:33 Connecting with device...
 ---------------------- shortend  -----------------------------
Jan 07 12:20:39 hassbian npm[534]:   zigbee2mqtt:info 2019-1-7 12:20:39 New device with address 0x00178801103f8e19 connected!
Jan 07 12:20:40 hassbian npm[534]:   zigbee2mqtt:info 2019-1-7 12:20:40 MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_connected","message":"0x00178801103f8e19"}'
Jan 07 12:20:40 hassbian npm[534]:   zigbee2mqtt:debug 2019-1-7 12:20:40 Received zigbee message of type 'devStatus' with data '"online"' of device 'RWL021' (0x00178801103f8e19)
Jan 07 12:21:18 hassbian npm[534]:   zigbee2mqtt:debug 2019-1-7 12:21:18 Saving state to file /opt/zigbee2mqtt/data/state.json

pushing the button doesnt to a thing then.
in some cases I get a red light when leaving it first and pushing a button then.

Hi All!

Anyone has been able to make zigbee2mqtt and Hue bulbs work with Home Assistant scenes?

If so, can you please share your config?

Thanks in advance!

Renato Troitino

@koenkk I have been following this thread and project since you started, but I only just managed to get around to setting it up.

First battle was finding the cc devices in my study, they had hidden themselves quite well.

Then it was simple, all went according to the instructions, and apart from glitches due to my own hurried (mis)reading, it has all gone smoothly. I have three devices connected, all Xiaomi. A presence detector was the first one, all sweet.

Then my cube, which was a pain to get connected. I was disappointed that once connected it didn’t work in my kitchen, but my third device was a power plug, which once paired I plugged in half way between the server and the kitchen, the cube now works in the kitchen and a network map confirms that the cube is routed through the power plug.

Couldn’t be happier, and I still have three weeks summer holiday left!

Congrats on an excellent project.

PS. One small suggestion, on the setup page https://koenkk.github.io/zigbee2mqtt/getting_started/running_zigbee2mqtt.html it might pay to mention that the user running zigbee2mqtt needs to be in the dialout group. That may be so by default on raspberry pi, but it isn’t on ubuntu :slight_smile:

PPS, this network map custom component was also extremely easy to get going Zigbee2mqtt: show the networkmap in home assistant

Hi, I am trying to add ecosmart bulb to zigbee2mqtt and receive “Device with modelID ‘� �P’ is not supported” is it still possible to still add it to code to node_modules/zigbee-shepherd-converters/devices.js ? Even with non displayable chars in the modelID ‘� �P’ ?

I just submitted a PR to fix this yesterday.

Great addon!! I finally got it working. I have a heap of xiaomi human body sensors and temp/humidity sensors that I woud love to add. I have added one body sensor that works as expected but the two temp/humidity sensors will not update unless I hit the button on the sensor. Is there something I am missing?
According to the logs and the zigbee map I have set up its all online. Im stumped

igbee2mqtt:info 2019-1-9 19:20:00 Starting network scan...
  zigbee2mqtt:info 2019-1-9 19:20:00 Network scan completed
  zigbee2mqtt:info 2019-1-9 19:20:00 MQTT publish: topic 'zigbee2mqtt/bridge/networkmap/graphviz', payload 'digraph G {
  "0x00124b0018ed3f2c" [label="{0x00124b0018ed3f2c|Coordinator|No model information available|online}"];
  "0x00158d000204aa90" [label="{Kitchen Motion|EndDevice|Xiaomi Aqara human body movement and illuminance sensor (RTCGQ11LM)|online}"];
  "0x00158d000204aa90" -> "0x00124b0018ed3f2c" [label="50"]
  "0x00158d000239dbe3" [label="{Bathroom Temp|EndDevice|Xiaomi MiJia temperature & humidity sensor  (WSDCGQ01LM)|online}"];
  "0x00158d000239dbe3" -> "0x00124b0018ed3f2c" [label="68"]
  "0x00158d00022ae4c2" [label="{0x00158d00022ae4c2|EndDevice|Xiaomi MiJia temperature & humidity sensor  (WSDCGQ01LM)|online}"];
  "0x00158d00022ae4c2" -> "0x00124b0018ed3f2c" [label="113"]


I have some temp/humidity sensors and they work ok. They just do not update frequently, in general it is about one message per hour, sometimes even fewer if the conditions do not change much.

Thanks for the reply. One of them has come good and seems to have updated pretty frequently (3 or 4 times an hour). The other one how ever is reporting unknown for each sensor on the states page.

Yes I also want to know this. I’ve tried but I’m just not good enough with this stuff to get it working.

It might be the other one is too far away from the coordinator. You can try to move it closer just to check. Low battery might be another reason.

Hey, I changed the battery a week ago and the map is returning a higher signal strength than the motion sensor that works flawlessly. Im wondering if its just a bad sensor

I have the Xiaomi Cube paired with z2m and I wonder what the voltage attribute represents for this device. The attributes are:

voltage 2995
battery 55
linkquality 39

I am sure there aren’t 2995V in this thing, is it anything useful?

i think its 2.995v. The working voltage range is only a couple of hundred millivolts I think

Of course, why didn’t I think of that!

This is my method for removing DISCOVERED MQTT entities in HA. I am sure the node red guys could make it more elegant but it works for me. (Note, I use Node Red for the heavy lifting)

  1. Stop zigbee2mqtt - sudo systemctl stop zigbee2mqtt
  2. Edit the config and select homeassistant to false
  3. Open HA and delete the integration.
  4. Run the flow below. It will look for all homeassistant/# messages that have a retained flag. And publish a blank payload with retained set to true.
  5. Restart HA. (not sure if its required, I hate restarting HA)
  6. And start zigbee2mqtt up again. sudo systemctl start zigbee2mqtt

After you clean up your zigbee clients add true back to the config fiie.

This works for me.

`[{"id":"1a015620.b435fa","type":"mqtt out","z":"3d592ba0.d3cecc","name":"","topic":"","qos":"0","retain":"true","broker":"2c60d293.b2f0ae","x":710,"y":200,"wires":[]},{"id":"2c60d293.b2f0ae","type":"mqtt-broker","z":"","name":"Hassio","broker":"rp3nc.duckdns.org","port":"1883","clientid":"","usetls":false,"compatmode":true,"keepalive":"60","cleansession":true,"birthTopic":"","birthQos":"0","birthPayload":"","closeTopic":"","closeQos":"0","closePayload":"","willTopic":"","willQos":"0","willPayload":""}]`

What is wrong with a null message to the config topic?

Is your opinion based on experience with that?

Many button batteries have a voltage life span between ~3.2 Volt to 2.8 Volt after which the drop off in voltage accelerates. The behavior overall is not linear (especially above 3.0V) , therefore I don’t like the percentage translation but rather like the display of the real voltage. (I use a battery overview of all my devices) The specified voltage spec is 3.00 Volt. You can see discharge graphs in battery specifications like below.


But the batteries in all my (+20) xiaomi devices, most devices after a year use, are in the range of 3.02 to 2.98 Volt. So I think the time lifespan of batteries will probably be well above two years.

I’m very curious at what voltage level the devices stop working or misbehave, but cannot find any specs about this (in Aqara or Xiaomi specs) or read any experiences with lower voltage levels (e.g. 2.8 or 2.7 volt). And don’t have a laboratory power supply to test it. But with such information we could make a better estimate of the lifespan of devices which can be handy (especially for build in devices).

So would like to hear from others who have working devices with battery levels below 2.80 Volt. So please, for the sake of science, don’t change the battery before it stops working :slightly_smiling_face:

Chill man. I did add I think to the end of my premise!
For the sake of science, have you pulled the battery and powered it off a power supply? You could slowly lower the voltage and get a pretty good idea of the cut off voltage. Im pretty busy for the next 2-3 weeks but I might give it a go myself!
EDIT Just re-read your post. I have a quality power supply at work. Ill try in a few weeks and report my results