Zigbee Ember Bnding No Connectivity After Power Cycle

I use the HUSBZB-1 stick and can pair and, after initial pairing, operate my various zigbee lightbulbs, but after a power cycle of the lights and the SBC running openhab, I cannot control any of the lights (2 Philips Hue’s and one Cree). I have to remove all of the bulbs, factory reset them and re-add to regain control. Anyone know how to get OH to retain control of my zigbee bulbs through a power cycle?

Is the coordinator not coming back online after a restart? Are the bulbs coming back online? Which versions of OH and the Zigbee binding are you using?

openhab2 version 2.4.0~20180708221346-1

182 │ Active │ 80 │ 1.0.11 │ com.zsmartsystems.zigbee
183 │ Active │ 80 │ 1.0.11 │ com.zsmartsystems.zigbee.dongle.cc2531
184 │ Active │ 80 │ 1.0.11 │ com.zsmartsystems.zigbee.dongle.ember
185 │ Active │ 80 │ 1.0.11 │ com.zsmartsystems.zigbee.dongle.telegesis
186 │ Active │ 80 │ 1.0.11 │ com.zsmartsystems.zigbee.dongle.xbee
199 │ Active │ 80 │ │ ZigBee Binding
201 │ Active │ 80 │ │ ZigBee Ember Binding

All of the things, including the coordinator, indicate online in paper ui after the restart.

grepping the log for the mac address of one of the bulbs:
2018-07-12 01:18:56.822 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: NetworkAddressRequest [0/0 -> 0/0, cluster=0000, TID=NULL, ieeeAddr=001788010360396E, requestType=0, startIndex=0]
2018-07-12 01:19:04.652 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 001788010360396E: Node SVC Discovery request NWK_ADDRESS failed. Retry 51, wait 41952ms before retry.

Here’s the whole sequence that all of the bulbs appear to repeat over and over again:

2018-07-12 01:26:58.583 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 0017880102F7E697: Node SVC Discovery running
2018-07-12 01:26:58.593 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: NetworkAddressRequest [0/0 -> 65535/0, cluster=0000, TID=D3, ieeeAddr=0017880102F7E697, requestType=0, startIndex=0]
2018-07-12 01:26:58.826 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: NetworkAddressRequest [0/0 -> 0/0, cluster=0000, TID=NULL, ieeeAddr=0017880102F7E697, requestType=0, startIndex=0]
2018-07-12 01:27:06.644 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 0017880102F7E697: Node SVC Discovery already scheduled or running
2018-07-12 01:27:08.392 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 0017880102F7E697: Node SVC Discovery request NWK_ADDRESS failed. Retry 54, wait 40986ms before retry.
2018-07-12 01:27:09.543 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 0017880102F7E697: Polling...
2018-07-12 01:27:09.566 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 0017880102F7E697: Polling zigbee:device:45165b45:0017880102f7e697:0017880102F7E697_11_switch_level

Could you clarify the scenario when this happens… in your initial post it is a bit confusing? You’re power cycling the lights and the device running OH, like by throwing a breaker? So OH was not shutdown properly? And then after a restart they are not responding?

Added the bulbs and verified I could control them all in paper ui. Sometime later, unplugged the SBC and turned off the wall switch powering the bulbs. Turn them back on the next day and plug the sbc back in. Wait for all OH components to start and things to be listed and online, then try to control the bulbs (brightness, color, etc)… no go on any of the channels of any of the bulbs.

I took no special care when powering off the sbc, but not seeing any sign of fs corruption.

The file system my be OK, but OH may not be happy! I would shut OH down properly and see if that helps. Get the bulbs setup and working first, or you may not see a difference.

in case shutting OH down doesn’t help…

When you turned them back on, they looked for the coordinator, but couldn’t find it, and could have freaked out a bit. I believe Zigbee device should recover from this, but YMMV. My bulbs are sensitive to this and sometimes eventually recover, but sometimes need a power cyle/discovery to recover. I suggest starting OH first, then powering up the bulbs. If that doesn’t help, start OH, start a discovery, then turn on the bulbs.