CC2531 USB stick running Zb 3.0 loses its settings (appears to be OH2 issue, not device issue)

Setup, Configuration and Use Installation
41

Strangely enough, there is a GitHub link at the bottom pf the page where people have actually improved the documentation. The first thing I did a year ago before deciding to move to OpenHAB was read the documentation & this forum to try & determine if it would work suitably for me and how to achieve my goals.

I started small and had help, especially from Chris, to get me started That is a good part of the reason I am helping improve his zwave binding. I do not use his Zigbee one but have seen the same dedication to users for that.

42

I’m aware of that and have been looking at issues. The “Karaf” issue I mentioned is widespread in the docs and I’m surprised nobody’s mentioned that before - it’s a very specific Java thing that anyone who does C/C++/ASM for a living won’t have dealt with before.

In my opinion, the persistent problem with just about every software project out there is is allowing developers to write documentation for general consumption. They’re simply too close to the code and as such, they’re writing for experts.

This is why I always filter my docs through third parties and will fight managers tooth and nail if they want to inflict what I’ve written on endusers. It’s not written for endusers, it’s written for people who have experience with using the software and are already comfortable with it.

43

Attempting to aliter dongle onto “correct” channel, panid, epanid using paperui

 ==> /var/log/openhab2/openhab.log <==
2020-08-08 19:57:32.738 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Configuration received (Coordinator).
2020-08-08 19:57:32.739 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Configuration update: Ignored zigbee_port as no change
2020-08-08 19:57:32.739 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Configuration update: Ignored zigbee_baud as no change
2020-08-08 19:57:32.739 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Configuration update: Ignored zigbee_initialise as no change
2020-08-08 19:57:32.739 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Configuration update: Processing zigbee_channel -> 15
2020-08-08 19:57:32.740 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Configuration update: Ignored zigbee_panid as no change

^^^^^^^^^ NB: This WAS changed in paperui, but apparently ignored

2020-08-08 19:57:32.740 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Configuration update: Ignored zigbee_znp_magicnumber as no change
2020-08-08 19:57:32.740 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Configuration update: Ignored zigbee_linkkey as no change
2020-08-08 19:57:32.740 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Configuration update: Processing zigbee_extendedpanid -> C38DF434D1C8C38B
2020-08-08 19:57:32.741 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Configuration update: Ignored zigbee_networkkey as no change
2020-08-08 19:57:32.741 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Configuration update: Ignored zigbee_meshupdateperiod as no change
2020-08-08 19:57:32.742 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - ZigBeeNetworkManager shutdown: networkState=ONLINE

==> /var/log/openhab2/events.log <==
2020-08-08 19:57:32.742 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_cc2531:cdb14d26' has been updated.

==> /var/log/openhab2/openhab.log <==
2020-08-08 19:57:32.742 [DEBUG] [atabase.ZigBeeNetworkDatabaseManager] - Data store: Deferred Write Time set to 0ms
2020-08-08 19:57:32.742 [DEBUG] [atabase.ZigBeeNetworkDatabaseManager] - Data store: Deferred Write Time set less than Max Deferred Write Time
2020-08-08 19:57:32.742 [DEBUG] [atabase.ZigBeeNetworkDatabaseManager] - Data store: Max Deferred Write Time set to 0ms
2020-08-08 19:57:32.743 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - Network state is updated to SHUTDOWN
2020-08-08 19:57:32.743 [DEBUG] [atabase.ZigBeeNetworkDatabaseManager] - 00158D000485A106: Data store: Deferring write for 0ms.
2020-08-08 19:57:32.743 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: networkStateUpdated called with state=SHUTDOWN
2020-08-08 19:57:32.743 [DEBUG] [atabase.ZigBeeNetworkDatabaseManager] - 00124B001CD48A18: Data store: Deferring write for 0ms.
2020-08-08 19:57:32.744 [DEBUG] [atabase.ZigBeeNetworkDatabaseManager] - 00158D000485A106: Data store: Writing node.
2020-08-08 19:57:32.744 [DEBUG] [pp.discovery.ZigBeeNetworkDiscoverer] - Network discovery task: shutdown
2020-08-08 19:57:32.744 [DEBUG] [iscovery.ZigBeeNodeServiceDiscoverer] - 00158D000485A106: Node SVC Discovery: stopped
2020-08-08 19:57:32.744 [DEBUG] [iscovery.ZigBeeNodeServiceDiscoverer] - 00124B001CD48A18: Node SVC Discovery: stopped
2020-08-08 19:57:32.744 [DEBUG] [p.discovery.ZigBeeDiscoveryExtension] - DISCOVERY Extension: Shutdown
2020-08-08 19:57:32.745 [DEBUG] [atabase.ZigBeeNetworkDatabaseManager] - Data store: Shutdown
2020-08-08 19:57:32.747 [DEBUG] [ding.zigbee.internal.ZigBeeDataStore] - 00158D000485A106: ZigBee saving network state complete.
2020-08-08 19:57:32.747 [DEBUG] [atabase.ZigBeeNetworkDatabaseManager] - 00124B001CD48A18: Data store: Writing node.
2020-08-08 19:57:32.749 [DEBUG] [ding.zigbee.internal.ZigBeeDataStore] - 00124B001CD48A18: ZigBee saving network state complete.
2020-08-08 19:57:32.773 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port '/dev/ttyUSB.CC2531-01' closed.

At this point, the serial port has been released and OH is no longer communictaing with the dongle at all - despite marking it as still online in the GUI and inside the CLI

Interestingly after 12 hours, one of the devices I re-paired the dongle with in this “broken” default state has ‘kind of’ reappeared

openhab> zigbee nodes                                                                                                                                                                                                           
Network  Addr  IEEE Address      Logical Type  State      EP   Profile                    Device Type                Manufacturer     Model          
      0  0000  00124B001CD48A18  COORDINATOR   UNKNOWN  
  17114  42DA  00158D000485A106  UNKNOWN       ONLINE   

openhab> zigbee node 0
IEEE Address     : 00124B001CD48A18
Network Address  : 0
Node Descriptor  : NodeDescriptor [apsFlags=0, bufferSize=80, complexDescriptorAvailable=false, manufacturerCode=0000, logicalType=COORDINATOR, serverCapabilities=[PRIMARY_TRUST_CENTER], incomingTransferSize=160, outgoingTransferSize=160, userDescriptorAvailable=false, frequencyBands=[FREQ_2400_MHZ], macCapabilities=[ALTERNATIVE_PAN, FULL_FUNCTION_DEVICE, MAINS_POWER, RECEIVER_ON_WHEN_IDLE], extendedEndpointListAvailable=false, extendedSimpleDescriptorListAvailable=false, stackCompliance=0]
Power Descriptor : PowerDescriptor [currentPowerMode=RECEIVER_ON_IDLE, availablePowerSources=[MAINS], currentPowerSource=MAINS, powerLevel=FULL]
Associations     : []
Endpoints        : 
Neighbors:
NeighborTable [extendedPanId=00124B001CD48A18, extendedAddress=00158D000485A106, networkAddress=17114, deviceType=END_DEVICE, rxOnWhenIdle=RX_OFF, relationship=CHILD, permitJoining=UNKNOWN, depth=1, lqi=1]
Routes:

openhab> zigbee node 17114
IEEE Address     : 00158D000485A106
Network Address  : 17114
Node Descriptor  : null
Power Descriptor : null
Associations     : []
Endpoints        : 
Neighbors:
Routes:
44

Cross posting from this thread, I encountered the same problem.

Did you manage to fix it?

45

As I said in the other thread -:

If you are resetting the dongle, and reverting to old configuration, it will not work. You cannot reset the network - once the network has been reset it is effectively destroyed as security will no longer work.