Firmware status of thing zigbee:device ... changed to UNKNOWN

Mehdi_Marzougui · March 11, 2022, 3:39pm

Dear all
I am trying to establish a Zigbee network using XBee S2C modules.
First I added one module as a bridge, once that done I was able to discover the second one instantly.
Now that I have both modules listed as things on the OH, only one issue remains: the second modules status is always OFFLINE.

Using the following Level for the zigbee loggers:

com.zsmartsystems.zigbee [INFO]
com.zsmartsystems.zigbee.dongle.ember.internal.ash [INFO]
org.openhab.binding.zigbee [DEBUG]

Here is what I see

15:47:16.258 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:8c6a4a17d0:0013a20041c33632' changed from UNINITIALIZED (DISABLED) to INITIALIZING                        
15:47:16.261 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 0013A20041C33632: Initializing ZigBee thing handler zigbee:device:8c6a4a17d0:0013a20041c33632                                                                             
15:47:16.264 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:8c6a4a17d0:0013a20041c33632' changed from INITIALIZING to UNKNOWN                                                                                     
15:47:16.264 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 0013A20041C33632: Coordinator status changed to ONLINE.                                                                                                                    
15:47:16.266 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 0013A20041C33632: Coordinator is ONLINE. Starting device initialisation.                                                                                                   
15:47:16.269 [INFO ] [openhab.event.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:device:8c6a4a17d0:0013a20041c33632 changed to UNKNOWN.                                                                                     
15:47:16.279 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 0013A20041C33632: Node has not finished discovery
15:47:16.282 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:8c6a4a17d0:0013a20041c33632' changed from UNKNOWN to OFFLINE: Node has not completed discovery

Here is the longer version by setting all zigbee loggers to DEBUG:

16:15:54.979 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:8c6a4a17d0:0013a20041c33632' changed from UNINITIALIZED (DISABLED) to INITIALIZING
16:15:54.981 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 0013A20041C33632: Initializing ZigBee thing handler zigbee:device:8c6a4a17d0:0013a20041c33632                                                                             
16:15:54.984 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 0013A20041C33632: Coordinator status changed to ONLINE.                                                                                                                   
16:15:54.984 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:8c6a4a17d0:0013a20041c33632' changed from INITIALIZING to UNKNOWN                                                                                    
16:15:54.986 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 0013A20041C33632: Coordinator is ONLINE. Starting device initialisation.                                                                                                  
16:15:54.987 [DEBUG] [app.discovery.ZigBeeNetworkDiscoverer] - 0013A20041C33632: NWK Discovery starting node rediscovery                                                                                                                 
16:15:54.988 [INFO ] [openhab.event.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:device:8c6a4a17d0:0013a20041c33632 changed to UNKNOWN.                                                                                    
16:15:54.988 [DEBUG] [app.discovery.ZigBeeNetworkDiscoverer] - 0013A20041C33632: NWK Discovery: Rediscovery using unicast to 961F                                                                                                        
16:15:54.990 [DEBUG] [ee.transaction.ZigBeeTransactionQueue] - 0013A20041C33632: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=0013A20041C33632 queueTime=0, state=WAITING, sendCnt=0, command=NetworkAddressRequest [0000/0 -> 961F/0, cluster=0000, TID=--, ieeeAddr=0013A20041C33632, requestType=0, startIndex=0]]        
16:15:54.992 [DEBUG] [.transaction.ZigBeeTransactionManager] - Transaction Manager: Send Next transaction. outstandingTransactions=0, outstandingQueues=1, sleepy=0/3                                                                    
16:15:54.993 [DEBUG] [.transaction.ZigBeeTransactionManager] - 961F/0: Sending ZigBeeTransaction [ieeeAddress=0013A20041C33632 queueTime=3, state=WAITING, sendCnt=0, command=NetworkAddressRequest [0000/0 -> 961F/0, cluster=0000, TID=2F, ieeeAddr=0013A20041C33632, requestType=0, startIndex=0]]                                                         
16:15:54.995 [DEBUG] [.transaction.ZigBeeTransactionManager] - transactionListenerAdded: 1 outstanding
16:15:54.995 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - TX CMD: NetworkAddressRequest [0000/0 -> 961F/0, cluster=0000, TID=2F, ieeeAddr=0013A20041C33632, requestType=0, startIndex=0]
16:15:54.996 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0000/0, destinationAddress=961F/0, profile=0000, cluster=0000, addressMode=DEVICE, radius=8, apsSecurity=false, ackRequest=true, apsCounter=4C, rssi=--, lqi=--, payload=2F 32 36 C3 41 00 A2 13 00 00 00]
16:15:54.998 [DEBUG] [s.zigbee.dongle.xbee.ZigBeeDongleXBee] - XBee send: XBeeTransmitRequestExplicitCommand [frameId=47, ieeeAddress=0013A20041C33632, networkAddress=38431, sourceEndpoint=0, destinationEndpoint=0, cluster=0, profileId=0, broadcastRadius=0, options=[], data=2F 32 36 C3 41 00 A2 13 00 00 00]                                          
16:15:55.000 [DEBUG] [dongle.xbee.internal.XBeeFrameHandler] - TX XBEE queue: 1: XBeeTransmitRequestExplicitCommand [frameId=98, ieeeAddress=0013A20041C33632, networkAddress=38431, sourceEndpoint=0, destinationEndpoint=0, cluster=0, profileId=0, broadcastRadius=0, options=[], data=2F 32 36 C3 41 00 A2 13 00 00 00]                                   
16:15:55.000 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX STA: msgTag=2F state=TX_ACK
16:15:55.000 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 0013A20041C33632: Node has not finished discovery
16:15:55.009 [DEBUG] [.transaction.ZigBeeTransactionManager] - notifyTransactionProgress: TID=2F, state=TX_ACK, outstanding=1                                                                                                            
16:15:55.009 [DEBUG] [dongle.xbee.internal.XBeeFrameHandler] - TX XBEE: XBeeTransmitRequestExplicitCommand [frameId=98, ieeeAddress=0013A20041C33632, networkAddress=38431, sourceEndpoint=0, destinationEndpoint=0, cluster=0, profileId=0, broadcastRadius=0, options=[], data=2F 32 36 C3 41 00 A2 13 00 00 00]                                            
16:15:55.011 [DEBUG] [.zigbee.transaction.ZigBeeTransaction] - Transaction state changed: nwk=961F, TID=2F, event=TX_ACK, state=TRANSMITTED                                                                                              
16:15:55.011 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:8c6a4a17d0:0013a20041c33632' changed from UNKNOWN to OFFLINE: Node has not completed discovery

The key message here i thinks is

16:15:54.988 [INFO ] [openhab.event.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:device:8c6a4a17d0:0013a20041c33632 changed to UNKNOWN.

Same thing happened with Aquara temp sensor:

16:31:02.213 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:8c6a4a17d0:00158d0007c79586' changed from UNINITIALIZED (DISABLED) to INITIALIZING
16:31:02.216 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 00158D0007C79586: Initializing ZigBee thing handler zigbee:device:8c6a4a17d0:00158d0007c79586                                                                             
16:31:02.217 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:8c6a4a17d0:00158d0007c79586' changed from INITIALIZING to UNKNOWN                                                                                    
16:31:02.217 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 00158D0007C79586: Coordinator status changed to ONLINE.                                                                                                                   
16:31:02.218 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 00158D0007C79586: Coordinator is ONLINE. Starting device initialisation.                                                                                                  
16:31:02.219 [INFO ] [openhab.event.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:device:8c6a4a17d0:00158d0007c79586 changed to UNKNOWN.                                                                                     16:31:02.236 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 00158D0007C79586: Node has not finished discovery
16:31:02.238 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:8c6a4a17d0:00158d0007c79586' changed from UNKNOWN to OFFLINE: Node has not completed discovery

Any help will be appreciated!

cheers,

chris · March 11, 2022, 6:47pm

I think this is not relevant at all to the device being offline. You don’t want to upgrade the firmware, so this doesn’t matter.

I’m really not sure what the issue is - there’s just too little information. What are the devices for starters? What does the debug log show is happening?

In this case it looks like the device is not discovered. These devices sleep very quickly after initialisation and you need to keep them awake by pressing the button while the binding creates the thing.

Mehdi_Marzougui · March 18, 2022, 2:58pm

Hey Chris!

The Solution for the Aquara temp sensor actually worked! thank you for that although if I delete it and try it again its not always guranteed to be detected in the first place to be added as a thing [logs are also silent]

As for the first part i was using 2 modules XB24CZ7WT, one qs a bridge and the other as an end device

Sorry for late reply and thank you!