Dear all,
i am currently trying to add an IKEA tradfri dimmer to openhab via the zigbee binding.
I do have an CC2531 USB stick connected to my RPI3b+.
I added a thing for the CC2531 which seems to be ok, at least it shows online.
Setting see attached screenshot.
Then I searched for things via the binding, reseted the tradfri dimmer (pressed 4 times the link button, LED flashing), unknown zigbee device popped up, added as a thing. But this new thing always shows offline: Node has not completed discovery.
Hello Andrew, thank you for your answer. Did you already succeed in adding an tradfri dimmer via zigbee binding to openhab?
Which buttons do you mean? The link button or on off buttons?
no, I don’t have one, my guess is pressing the link button as you stated in your first post. However you got it to be discovered the first time, just do the same several times until it is fully discovered
Thank you, I will try this.
However I also read stuff about zigbee2mqtt, which some user also recommend. I do already have a mqtt instance running, so I am half way there. Zigbee2mqtt isn’t a binding, it has to be installed separately, correct? Which way would you guys recommend? Zigbee binding or zigbee2mqtt?
Hello,
i tried to add the device several times now.
Everytime the same result…
This is a copy of the openhab log after reboot and performing the search, add and remove twice:
2021-03-14 10:04:17.910 [hingStatusInfoChangedEvent] - 'zigbee:device:7816e2f6:847127fffec6164a' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2021-03-14 10:04:18.036 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_cc2531:7816e2f6' changed from UNINITIALIZED to INITIALIZING
2021-03-14 10:04:18.172 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_cc2531:7816e2f6' changed from INITIALIZING to UNKNOWN
2021-03-14 10:04:18.223 [hingStatusInfoChangedEvent] - 'zigbee:device:7816e2f6:847127fffec6164a' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
2021-03-14 10:04:18.257 [hingStatusInfoChangedEvent] - 'zigbee:device:7816e2f6:847127fffec6164a' changed from INITIALIZING to UNKNOWN
2021-03-14 10:04:21.922 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_cc2531:7816e2f6' has been updated.
2021-03-14 10:04:22.043 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_cc2531:7816e2f6' changed from UNKNOWN to ONLINE
2021-03-14 10:04:22.052 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 847127FFFEC6164A: Starting ZigBee device discovery
2021-03-14 10:04:22.064 [hingStatusInfoChangedEvent] - 'zigbee:device:7816e2f6:847127fffec6164a' changed from UNKNOWN to OFFLINE: Node has not completed discovery
2021-03-14 10:05:47.487 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 847127FFFEC6164A: Starting ZigBee device discovery
2021-03-14 10:06:05.454 [WARN ] [zsmartsystems.zigbee.ZigBeeExecutors] - Uncaught exception in thread NotificationService-thread-5
at org.openhab.binding.zigbee.handler.ZigBeeThingHandler.nodeUpdated(ZigBeeThingHandler.java:879) ~[?:?]
at com.zsmartsystems.zigbee.ZigBeeNetworkManager$14.run(ZigBeeNetworkManager.java:1735) ~[?:?]
2021-03-14 10:06:48.601 [WARN ] [zsmartsystems.zigbee.ZigBeeExecutors] - Uncaught exception in thread NotificationService-thread-12
at org.openhab.binding.zigbee.handler.ZigBeeThingHandler.nodeUpdated(ZigBeeThingHandler.java:879) ~[?:?]
at com.zsmartsystems.zigbee.ZigBeeNetworkManager$14.run(ZigBeeNetworkManager.java:1735) ~[?:?]
2021-03-14 10:06:55.850 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 847127FFFEC6164A: Starting ZigBee device discovery
2021-03-14 10:07:15.560 [WARN ] [zsmartsystems.zigbee.ZigBeeExecutors] - Uncaught exception in thread NotificationService-thread-13
at org.openhab.binding.zigbee.handler.ZigBeeThingHandler.nodeUpdated(ZigBeeThingHandler.java:879) ~[?:?]
at com.zsmartsystems.zigbee.ZigBeeNetworkManager$14.run(ZigBeeNetworkManager.java:1735) ~[?:?]
2021-03-14 10:07:47.861 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:device:7816e2f6:847127fffec6164a changed to UNKNOWN.
2021-03-14 10:08:07.816 [hingStatusInfoChangedEvent] - 'zigbee:device:7816e2f6:847127fffec6164a' changed from OFFLINE: Node has not completed discovery to REMOVING
2021-03-14 10:08:13.284 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 847127FFFEC6164A: Starting ZigBee device discovery
2021-03-14 10:08:23.946 [ERROR] [ding.zigbee.internal.ZigBeeDataStore] - 847127FFFEC6164A: ZigBee removing network state complete
2021-03-14 10:08:23.956 [me.event.ThingUpdatedEvent] - Thing 'zigbee:device:7816e2f6:847127fffec6164a' has been updated.
2021-03-14 10:08:23.956 [ERROR] [ding.zigbee.internal.ZigBeeDataStore] - 847127FFFEC6164A: Error removing network state
2021-03-14 10:08:23.967 [hingStatusInfoChangedEvent] - 'zigbee:device:7816e2f6:847127fffec6164a' changed from REMOVING to REMOVED
2021-03-14 10:08:23.984 [hingStatusInfoChangedEvent] - 'zigbee:device:7816e2f6:847127fffec6164a' changed from REMOVED to UNINITIALIZED
2021-03-14 10:08:24.083 [hingStatusInfoChangedEvent] - 'zigbee:device:7816e2f6:847127fffec6164a' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2021-03-14 10:08:33.932 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 847127FFFEC6164A: Starting ZigBee device discovery
2021-03-14 10:08:33.943 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zigbee:device:7816e2f6:847127fffec6164a' to inbox.
2021-03-14 10:08:33.945 [home.event.InboxAddedEvent] - Discovery Result with UID 'zigbee:device:7816e2f6:847127fffec6164a' has been added.
2021-03-14 10:09:06.650 [me.event.InboxRemovedEvent] - Discovery Result with UID 'zigbee:device:7816e2f6:847127fffec6164a' has been removed.
2021-03-14 10:09:06.766 [hingStatusInfoChangedEvent] - 'zigbee:device:7816e2f6:847127fffec6164a' changed from UNINITIALIZED to INITIALIZING
2021-03-14 10:09:06.798 [hingStatusInfoChangedEvent] - 'zigbee:device:7816e2f6:847127fffec6164a' changed from INITIALIZING to UNKNOWN
2021-03-14 10:09:06.827 [hingStatusInfoChangedEvent] - 'zigbee:device:7816e2f6:847127fffec6164a' changed from UNKNOWN to OFFLINE: Node has not completed discovery
2021-03-14 10:09:06.879 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:device:7816e2f6:847127fffec6164a changed to UNKNOWN.
I am using this stick from Amazon: " ITSTUFF CC2531 ZigBee USB-Stick ioBroker openHAB FHEM SMA Antenne mit Firmware"
its german and means “…including antenna and firmware”
zigbee2mqtt uses mqtt to deliver commands.
You would then use inside OH the mqtt binding and configure generic mqtt devices. I use this combination and it works flawless, got IKEA, Xiaomi, Tuya devices etc.
Ok, than I would start to try this. Do you have a good manual with which you performed the installation? I found different ones which all seems to be slightly different. Using transformation and not, etc.
So I am a little bit confused how to start.
This means in openhab I am only receiving the mqtt command, everything else works independent on the RPI?
I would recommend getting logs to try and work out what is going on. The binding documentation describes how to enable logging and there is a log viewer here -:
You can also post logs here and I will try and take a look.
It’s also useful to know what version of openHAB you’re using - I assume 3, but it’s always good to say
I followed the official documentation from https://www.zigbee2mqtt.io/.
You will need to run the correct firmware though on your stick (not sure with which firmware your stick from Amazon came).
After that, you define the mqtt server inside the zigbee2mqtt config and you will then pair your devices after which they will send their actions via zigbee2mqtt to mqtt.
You can then define the generic mqtt item with its channels (for which channels are available, you can either look in the supported devices list of zigbee2mqtt or sub to the mqtt topic and see what the device sends).
I run nearly all my devices without transformation, the only exception are remotes which send an “on/off” instead of “ON/OFF” (I use a simple map transformation here to make it easier to use in OH).
Hello i will try to active the log. I am using OH 2.5.12-1. Updated few month ago and since then there was no need because everything was working well. Normally I am not trying to tough a running system. Do you thing a newer version would help? Is it a big pain to update to OH3.xx?
Good question. In the Amazon description it is written that it works with openhab and zigbee2mqtt. In the question the seller wrote 6 months ago that cc2531_default_20190608 is flashed. Hope this one is fine. If not: is additional hardware required to flash it?
Additional question: in the zigbee binding manual 3 different baud-rates are written. I just tried 115200, with this on the coordinator shows online. Shall I try I different one / does it make a difference?
I can only help on the first part of this question as I am not running the zigbee binding.
On firmware, this should be the latest cc2531 firmware repo which has a timestamp of 20200127, hence a bit newer than yours it seems. You would indeed need additional hardware to flash it to a newer version as per my understanding, whereas it could also be that it will work with your version (?).
IIRC it doesn’t matter what you select as it’s embedded in the 2531 - if it works, then it will certainly make no difference as the OTA rate is always 250kb/s.
Hello,
thank you all for your help.
I changed now to zigbee2mqtt and now it works.
I can receive all the states from the tradfri dimmer (on / off / dimming / battery / etc).
