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

Hi all,

I have one ZigBee Router (CC2530 + CC2591) that connected to two ZigBee Coordinators (CC2531) without any issue.

However, the state of both ZigBee Router (binary_sensor.0x00XXXXXXXXXX_router) will only updates in more than 1 minutes or later, as per screenshot below:

It is suppose to connect at this time, but not reflect in real time. This have confused me for a while.

The state of ZigBee Router should reflect to Connect or Disconnected in real time (Around 1 seconds is acceptable).

Could anyone advise on this issue?

GitHub Issue Link: https://github.com/Koenkk/zigbee2mqtt/issues/1525

Thanks.

Has Anyone seen the following error, Iā€™m trying to update the configuration in the zigbee2mqtt add-on.

    19-05-18 18:24:19 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 418, in start
    resp = await task
  File "/usr/local/lib/python3.7/site-packages/aiohttp/web_app.py", line 458, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/web_middlewares.py", line 119, in impl
    return await handler(request)
  File "/usr/src/hassio/hassio/api/security.py", line 144, in token_validation
    return await handler(request)
  File "/usr/src/hassio/hassio/api/utils.py", line 32, in wrap_api
    answer = await method(api, *args, **kwargs)
  File "/usr/src/hassio/hassio/api/addons.py", line 291, in security
    addon.save_data()
AttributeError: 'Addon' object has no attribute 'save_data'

Edit: managed to adapt the config through the configurator.

Any luck with these?

The cc2530 does not have a USB port (although it does say there is a uart/serial support).

The user @wixoff has used a cc2530 with the dev kit, see Zigbee2mqtt: getting rid of your proprietary Zigbee bridges (Xiaomi, Hue, TRADFRI)

Hi @zoggels, it works very well. I connected it to my Pi via a USB UART connector and flashed it with 2530 code.

The range is MUCH better.

2 Likes

Yes, my cc2530+cc2591 with the dev motherboard works great. Excellent range, and my network has never been more reliable. Iā€™m currently running on the recent ā€œmax stabilityā€ firmware and network connectivity is fantastic, like a spiderweb in the Zigbee Map.

Hereā€™s what I have: https://www.waveshare.com/wiki/ZB502

This plus an XCore2530 daughterboard for the Zigbee functionality. And a big 2.4 GHz antenna! All but the antenna fits nicely into a small project enclosure.

Looks great. Out of curiosity, what do you use to map the network?

Not answering for @wixoff, but this thread has details of a method to see your network map in home assistant. Zigbee2mqtt: show the networkmap in home assistant

This looks good, thanks. I am currently fiddling with the ZHA integration. Which is working quite well at the moment. It appears this doesnā€™t work which ZHA, do you know of any that do?

Is it the case, that the closer you get to the 15 device limit, the more chance you get of a ā€˜messageā€™ from a node being missed? I could have sworn my setup didnā€™t miss a beat until I started adding a few more devices and now PIR or door contact status updates sometimes donā€™t seem to register.

Also if I am to improve reception/range/reliability with a CC2530 router, I must admit Iā€™m confused as to by what mechanism this helps. Is the CC2530 effectively a repeater? How are duplicate messages avoided? Presumably the CC2530 needs to be within range of the CC2531 but other than that all it needs is power? Thanks
Finally, anyone aware of any CC2530 available in Europe?

Yes, and somebody on this board is selling them, pre-flashed with a case and antenna. Thatā€™s a bit more expensive than buying them from Gearbest/AliExpress, but far more convenient.

Yes it is (the term here is router), and the same way as with any mesh network - a device will talk to a single node - either a router, or the coordinator itself.

Yes, and yes. Mineā€™s hanging off an old mobile phone charger plug.

1 Like

Thatā€™s me. :wave:

See my ad here:

Ad: Buy a ready2use zigbee2mqtt stick - flashed, antenna mod and printed case - Hardware - Home Assistant Community

1 Like

Iā€™ve noticed oddities - and I donā€™t know if I want to say itā€™s a zigbee2mqtt but more of a zigbee/hue thing. Before I switched to zigbee2mqtt I would notice that HASS would report that my bedroom light was unavailable often around 3am - I would find that controlling that light directly would fail, but controlling a group that that light is in would work fine. Switched to zigbee2mqtt and Iā€™ve noticed this seems to be continuing, for the last two nights (since installing), around 3am my zigbee map is reporting that the mesh has died and that all the devices are just connected (with very weak or non-existant signals) to the coordinator. Trying to control my bed light directly fails with no ack messages, but controlling a group itā€™s in works fine. An hour or so later the mesh has returned and everything is fine

What the hell could be causing this? Does anyone have any idea Iā€™m stumped.

Iā€™m confused about how I should go about installing a repeater. Iā€™m all set to buy one from @h4nc but once Iā€™ve got it, how do I tell my existing network it exists, and how do the nodes decide whether theyā€™re talking to the new repeater or my existing coordinator? Thanks

You install a router (=repeater) the same way as pairing new enddevices.

First you turn permit_join to true and than plug in the router in a usb port near your coordinator.

The devices will find the best way by themselves. @Koenkk often told that the zigbee2mqtt maps donā€™t work reliable yet.

So if your maps show that a enddevice is only connected to the coordinator, it could also be connected with the new router.
So if you had problems before and they are gone with an additional router, it is most likely that the router was the problemsolver here (even if you maybe cannot see it in a map).
If Iā€™m wrong @koenkk will correct me.

1 Like

hello.
i have firmware 20190223 installed. should i upgrade to 20190515 ?
i also seen that there are firmwares 3.0.x -> what is the difference?
thanks

See: http://zigbee2mqtt.discourse.group/t/which-firmware-to-choose-for-cc2531-z-stack-version/94/5

My CC2531 USB Routers no longer seem to be connected to the co-ordinator.
I havenā€™t done anything that I can think of to make them disconnect/un-pair.
If I run a graphviz map this is what i see

ā€œ0x00124b0012023169ā€ [style=ā€œroundedā€, label="{0x00124b0012023169|Router|Custom devices (DiY) CC2530 router (CC2530.ROUTER)|offline}"];,

ā€œ0x00124b0012013c6eā€ [style=ā€œroundedā€, label="{0x00124b0012013c6e|Router|Custom devices (DiY) CC2530 router (CC2530.ROUTER)|offline}"];

They come up as cc2530, but they are actually cc2531. They were working fine before, I havenā€™t changed the firmware, although the zigbee container has probably auto-upgraded a few times. What can I do to make them reconnect / rejoin my zigbee network?

edit: was able to get them to rejoin by enabling joining in zigbee2mqtt then holding down the closest button for 5s, then repressing the button a few times. The second router took quite a few goes but eventually seems to be back online again.

Scroll down and read the section: repair

1 Like

I use zigbee2mqtt via hassio. Do I need to wait for the next upgrade of zigbee2mqtt on hassio for a device I recently added to the zigbee2mqtt project?