Finally i’ve been able to solve it…
There were no messages because casually mijia sensors were the first ones that i bought , and batteries had such low energy, so sensors couldn’t been detected by zigbee bridge.
Once replaced by new ones everything is working fine…
So, finally yesterday I received all the bits an pieces to try to make this work - and I did with rather very few complications.
Thank you very much, @Koenkk, for this great piece of software and the instructions on how to make it work!
I now have 2 Aqara temperature sensors connected and am already thinking about many other uses 
One quick question to the people who’ve been using it for a while with these sensors:
How long do you expect the batteries to last?
I have one of the sensors in my fridge, the other one in the freezer. Both have been running for roughly a day now, but the battery-%age has gone down significantly already.
I know it’s a rough environment for the batteries, but I’m still surprised about the battery drain so far.
I also know that the linkquality values of 35ish are probably not ideal either, but short of putting the RPi in the freezer as well 
I’m not sure what to do.
in your freezer the temperature changes will probably make your aqara sensor talks a lot more.
in mine it reports every 5minutes (ish)
about the linkquality, you can extend the range with a router.
Aqara/Xiaomi gives an estimate that batteries in sensors etc. should last at least 2 years in normal conditions. The batteries (e.g. CR2032) are new normally somewhat above 3.00 V and drop during use ~0,3 V after which the drop off accelarates. Under 2.7 V I regard them as not reliable anymore. I didn’t change any batteries in my sensors and switches now in use for over a year.
See pictures in former message.
So I’ve
- shutdown my wifi on channel 11
- switch zigbee2mqtt to channel 25
- remove the zigate from the host
- pair my 3 osram
Here’s the entire disposition with a side view of this part of my house:
And here’s what I have :
Prise 1 is ok
Prise 3 respond sometimes
Prise 2 miss almost all toggle order from ha.
So the network map does not seems to represent reality (prise 1 should not be ok because using prise 2)
And none of this can be use in my house.
Please consider that the concrete between floors is really huge this could explain the problem for 2 and 3…
But again zigate does not look to care about that.
Do I have a bad CC2531 key? Should I forget about this and focus on zigate only ?
Has anyone got this working using ESP8266(EspEasy Ser2Net) and socat? I want to put a CC2530 coordinator in the center of the house without a RPi.
Hi, I am trying to set this up, but having a few hurdles. First problem is that when I have my usb sniffer in an usb port, I get problems with my zwave dongle. My zwave USB dongle changes from ttyACM0 to ttyACM1 when I plug in the sniffer and restarts the computer. Changed the zwave usb path to ttyACM1, but it doesn’t seems to be that easy, since my zwave components is not available when hassio start up. Anyone else have this problem? Running on Intel Nuc with Ubuntu Server and Hassio through docker, and the Hassio add-on.
I’ve updated my instructions for generating a map of your Zigbee network above - it works great now and produces something like this:
Got now a second stick laying around after I don’t get more informations out of the aquara qube.
Now I ask me how to proceed.
I heard that I can include a second cc.
Do I have to flash it with the router firmware or can I use 2 coordinators?
Also - is the new firmware already to use? Or more a alpha?
Is there a way to get this visual graph to work with Hassio?
Hi, I am using this addon with Hassio. When it is starting I get the following message:
node index.js Zigbee2mqtt requires node version >=8.11 10, you are running v8.11.4!
Then my hassio crash until I remove the CC2531 from the usb port. Just by removing the CC2531 from USB port, HASSIO is revovering.
Does anyone as experience the same issue?
Automatically, or just one-off?
For one-off production of the graph, it’s pretty simple.
In hassio, at the very bottom of the left hand menu, click the second to last option at the bottom (hovertip is “dev-mqtt”). Once in the MQTT “Publish a packet” screen, enter “zigbee2mqtt/bridge/networkmap” in the topic, and “graphviz” in the payload. Click “Publish”.
Then goto the “Hassio” menu, click on the zigbee2mqtt plug-in, then at the bottom of the log it should have published the network map as text.
It will look something like this:
zigbee2mqtt:info 2018-11-16 18:02:55 MQTT publish, topic: ‘zigbee2mqtt/bridge/networkmap/graphviz’, payload: ‘digraph G {
node[shape=record];
“0x00124b0018ed2f8b” [label=“{0x00124b0018ed2f8b|Coordinator|No model information available|online}”];
“0x00124b0018ed2f8b” → “0x0022a300001af914” [label=“249”]
“0x00158d000244e585” [label=“{0x00158d000244e585|EndDevice|Xiaomi MiJia human body movement sensor (RTCGQ01LM)|online}”];
“0x00158d000244e585” → “0x00124b0018ed2f8b” [label=“75”]
“0x00158d00028ed383” [label=“{0x00158d00028ed383|EndDevice|Xiaomi MiJia door & window contact sensor (MCCGQ01LM)|online}”];
“0x00158d00028ed383” → “0x00124b0018ed2f8b” [label=“43”]
“0x0022a3000021e49a” [label=“{0x0022a3000021e49a|Router|GE ZigBee plug-in smart dimmer (45852GE)|offline}”];
“0x0022a3000021e49a” → “0x0022a300001af914” [label=“252”]
“0x00158d00029a9ea8” [label=“{0x00158d00029a9ea8|EndDevice|Xiaomi Aqara human body movement and illuminance sensor (RTCGQ11LM)|online}”];
“0x00158d00029a9ea8” → “0x00124b0018ed2f8b” [label=“21”]
“0x00158d00022878bb” [label=“{0x00158d00022878bb|EndDevice|Xiaomi MiJia wireless switch (WXKG01LM)|online}”];
“0x00158d00022878bb” → “0x00124b0018ed2f8b” [label=“53”]
“0x00158d0001f57f9b” [label=“{0x00158d0001f57f9b|EndDevice|Xiaomi MiJia temperature & humidity sensor (WSDCGQ01LM)|online}”];
“0x00158d0001f57f9b” → “0x00124b0018ed2f8b” [label=“52”]
“0x00158d00020b4c53” [label=“{0x00158d00020b4c53|EndDevice|Xiaomi MiJia human body movement sensor (RTCGQ01LM)|online}”];
“0x00158d00020b4c53” → “0x00124b0018ed2f8b” [label=“39”]
“0x0022a300001af914” [label=“{0x0022a300001af914|Router|GE ZigBee plug-in smart dimmer (45852GE)|online}”];
“0x0022a300001af914” → “0x0022a3000021e49a” [label=“254”]
}’
Copy that, starting with "digraph G " and ending with the last “}” and then go to this website. Paste your graph into the left hand side, and change the engine to “Circo”.
There’s your graph!
4 Likes
@Silicon_Avatar Thanks for the instructions!
I was finally able to get an Xioami sensor to use one of the plugs as a router. Below is the graph that shows the Xiaomi Occupancy sensor using an Iris Smart Plug as a router.
hi, i’m ussing Hassio addon too and getting same error message on bridge logs.
In addition to this, all mi sensors lost connectivity from time to time and all values turn to “unknown”…
It seems to happening since i upgraded HA to version 0.82
How can i update node version to 8.11.10 on hassio?
@chavi78, may I ask you to check if you get the same problem as mine. Can you:
- open a terminal
- ping your hassio box (continuous ping)
- start zigbee2mqtt plugins
- when it start to report your devices in the log check the ping value : on my side I get up to 20000ms
- unplug your CC2135 d’ongle and check if it’s come back to normal ping value: around 1ms
Thanks worked a treat!!
I can see my IKEA bulb is connected to the Aqara power switch router, but it still wont power on or off unless i move the lamp within a few metres of the Pi/Sniffer. Makes no difference on that the switch is next to it… doing my head in
Just solved the issue of HASSIO crashing. Uninstall the add on, delete the configuration.yaml and database.db in the share/zigbee2mqtt folder and now everything seems to be fine.
Issue is back today:(
It seems it appear when in the log I have the following message but not sure if there is a link:
zigbee2mqtt:info 2018-11-19 20:31:41
{"message":"request timeout","stack":"Error: request timeout\n at CcZnp.<anonymous> (/zigbee2mqtt-0.2.0/node_modules/cc-znp/lib/ccznp.js:255:22)\n at Object.onceWrapper (events.js:315:30)\n at emitOne (events.js:116:13)\n at CcZnp.emit (events.js:211:7)\n at Timeout.<anonymous> (/zigbee2mqtt-0.2.0/node_modules/cc-znp/lib/ccznp.js:234:18)\n at ontimeout (timers.js:498:11)\n at tryOnTimeout (timers.js:323:5)\n at Timer.listOnTimeout (timers.js:290:5)"}
Does anyone get the same thing?
/usr/bin/socat -d -d pty,raw,echo=0,link=/dev/ttyACM1 tcp-connect:192.168.1.4:1775
1 Like