Also, in this addons.config is misc= “”
Already the same behavior.
Status: OFFLINE - HANDLER_INITIALIZING_ERROR No supported clusters found
same here with a fresh install
Status: OFFLINE - HANDLER_INITIALIZING_ERROR No supported clusters found
Also Noticed that IKEA TRADFRI plugs do not perform well as repeaters. When you First add them to the system they will perform well but after a restart most of the time they will not be able to connect to their zigbee neighbors even if their zigbee neighbors are 50 cm away
The situation becomes bad because sometimes they will connect to devices that are far way
If I replace the plugs with a hue bulb then everything works ok
In my case the IKEA Repeater is approx. 3m distance to the CC2531. My other devices are approx 7m from the IKEA Repeater. I have 3 Tradfri LED transformer devices and one Aquara temperature sensor.
I tried several solutions on OH2.5 but without success.
Without this repeater I can bind the devices but the connection is not reliable.
In the past I worked with this IKEA Repeater which is working very well on OH2.4. Since OH2.5 I am sitting in the dark.
Did you find a solution?
I have the exact same issue.
I tried now to kick the tradfri repeater a couple times out and have it rejoin.
I never get it to get past this “no supported clusters found” state
probably only @chris could help and we provide all logs he needs for that
2020-07-12 10:49:41.971 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 680AE2FFFE98C079: Initializing ZigBee thing handler zigbee:device:01382869:680ae2fffe98c079
2020-07-12 10:49:41.972 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 680AE2FFFE98C079: Coordinator status changed to ONLINE.
2020-07-12 10:49:41.973 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 680AE2FFFE98C079: Coordinator is ONLINE. Starting device initialisation.
2020-07-12 10:49:41.974 [DEBUG] [pp.discovery.ZigBeeNetworkDiscoverer] - 680AE2FFFE98C079: NWK Discovery starting node rediscovery
2020-07-12 10:49:41.976 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - Broadcast: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=null queueTime=0, state=WAITING, sendCnt=0, command=NetworkAddressRequest [0000/0 -> FFFD/0, cluster=0000, TID=--, ieeeAddr=680AE2FFFE98C079, requestType=0, startIndex=0]]
2020-07-12 10:49:41.978 [DEBUG] [transaction.ZigBeeTransactionManager] - FFFD/0: Sending ZigBeeTransaction [ieeeAddress=null queueTime=2, state=WAITING, sendCnt=0, command=NetworkAddressRequest [0000/0 -> FFFD/0, cluster=0000, TID=94, ieeeAddr=680AE2FFFE98C079, requestType=0, startIndex=0]]
2020-07-12 10:49:41.979 [DEBUG] [transaction.ZigBeeTransactionManager] - transactionListenerAdded: 2 outstanding
2020-07-12 10:49:41.980 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: NetworkAddressRequest [0000/0 -> FFFD/0, cluster=0000, TID=94, ieeeAddr=680AE2FFFE98C079, requestType=0, startIndex=0]
2020-07-12 10:49:41.981 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0000/0, destinationAddress=FFFD/0, profile=0000, cluster=0000, addressMode=DEVICE, radius=31, apsSecurity=false, ackRequest=true, apsCounter=46, rssi=--, lqi=--, payload=94 79 C0 98 FE FF E2 0A 68 00 00]
2020-07-12 10:49:41.992 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX EZSP: EzspSendBroadcastResponse [networkId=0, status=EMBER_SUCCESS, sequence=5E]
2020-07-12 10:49:41.993 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 680AE2FFFE98C079: Start initialising ZigBee Thing handler
2020-07-12 10:49:41.994 [DEBUG] [scovery.ZigBeeNodePropertyDiscoverer] - 680AE2FFFE98C079: ZigBee node property discovery start
2020-07-12 10:49:41.995 [DEBUG] [scovery.ZigBeeNodePropertyDiscoverer] - 680AE2FFFE98C079: ZigBee node property discovery using basic cluster on endpoint 846F/1
2020-07-12 10:49:41.996 [DEBUG] [scovery.ZigBeeNodePropertyDiscoverer] - 680AE2FFFE98C079: ZigBee node property discovery using OTA cluster on endpoint 846F/1
2020-07-12 10:49:41.997 [DEBUG] [scovery.ZigBeeNodePropertyDiscoverer] - 680AE2FFFE98C079: ZigBee node property discovery complete: {zigbee_logicaltype=ROUTER, zigbee_powerlevel=FULL, zigbee_manufacturercode=0x117c, modelId=TRADFRI Signal Repeater, zigbee_networkaddress=33903, zigbee_powersource=MAINS, zigbee_stkversion=98, zigbee_datecode=20190311, zigbee_zclversion=3, vendor=IKEA of Sweden, zigbee_powermode=RECEIVER_ON_IDLE, zigbee_powersources=[MAINS], hardwareVersion=1, firmwareVersion=0x22005631, zigbee_applicationVersion=33}
2020-07-12 10:49:41.998 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 680AE2FFFE98C079: Checking endpoint 1 channels
2020-07-12 10:49:42.000 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 680AE2FFFE98C079: Checking endpoint 242 channels
2020-07-12 10:49:42.003 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 680AE2FFFE98C079: Dynamically created 0 channels
2020-07-12 10:49:42.004 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 680AE2FFFE98C079: Initializing device
2020-07-12 10:49:42.004 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 680AE2FFFE98C079: Channel initialisation complete
2020-07-12 10:49:42.005 [WARN ] [ng.zigbee.handler.ZigBeeThingHandler] - 680AE2FFFE98C079: No supported clusters foundWhat do you want to do with it? It’s a repeater, so probably it doesn’t have any user functions? Or does it also turn on lights, or a plug socket or something?
well Paper UI reports it as.
the 2 other guys up in the thread have screenshot added - it always says “offline” with that error shown
Sure, but about my question -:
As far as I know it doesn’t do anything. It should work as a repeater all the same, but openhab won’t be able to provide you any switches etc unless the device provides these sort of features. Does it? I’m not
familiar with this device so I’m trying to understand what you are expecting to provide so I can understand the “no supported clusters” log you mentioned as being a problem
.
Sure I only want to act as an repeater. Do you mean the state in the UI is fully ok and that is shown as offline with that error message is “work as intented”?
If it is joined to the network, it will work as a repeater. OH can’t provide you any user functionality.
Probably it shows offline as there is no user functions, so the binding doesn’t poll, and there is no reporting.
@chris
well ok then I might be happy already.
the UI does not show any neighbors in the properties for this device … so I interpreted it is not working correctly.
sorry for that … the “offline” state is a little misleading then
This shows that the handler hasn’t initialised, so this means that none of the properties will update. I’m not really sure why this is and I’m not able to test this as I don’t have this device.
If the device is joined to the network, it should work fine - there’s nothing that can be configured or changed.
Hi all,
I have bought some Tradfri repeaters myself and see the same issue.
So just to confirm:
A plain router/repeater with no additional user function will show as “OFFLINE - HANDLER_INITIALIZING_ERROR” in OpenHAB but will still forward messages.
If the device falls out of the network and stops working at some point, will the status change?
For example, to “Offline - Gone” or something similar?
These devices, as far as I know, don’t support any “user functions”, so the binding doesn’t really do anything with them, and doesn’t monitor them since there is nothing to monitor. This should not stop it being used as a repeater if it’s included into a network.
1 Like
Similar issues in OH 3. But I do see zigbee_neighbors showing up in the Things API Get call so I assume it is working.
Indeed there is nothing you can set or see.
Try:
openhab> zigbee bindtable node
where you fill in the node number as last argument. This will give “Empty”
If you do that on another node (e.g. a rollerblind from ikea) it will give some clusters.
I found this list online of possible clusters: Zigbee Profile ID List-Public Profile IDs,Zigbee Device IDs (rfwireless-world.com)
I am having the same problem. I had a functioning setup with a zigbee hat, ikea repeater and ikea roller blind. Everything was working fine. My OH setup remained untouched.
One day, the repeater goes offline in OH for no apparent reason. No matter what combinations of resetting and scanning for hardware I use, it is just not being picked up any more by OH.
Hello, does anyone have a solution to the problem in the meantime? I am using OH4.0.3 and have the same problem with the two repeaters I recently bought from Ikea.
Hello everyone!
Same problem on my side. Device is still shown as OFFLINE with HANDLER_INITIALIZING_ERROR. If it is working anyway, there is definitively room for improvement. What are the thoughts of the addon developer?
Best regards