Sadly, same error after importing the XML file/creating a profile based on it. Added in my extended PAN ID, created a new profile based on that.
When I go to network working mode and scan same old error:
Removed it using the small X and discovered it again and try to scan again and fails again. Arrgh! (Frustrate pirate noise.) 
Maybe it will work for @Mayhem when he gets back from crowning Prince Chucky. 
My dear frustrated fellows. The only time I get blinkyblight is if I change it to a coordinator. Logically I suppose. And have done so a couple of time to prove it’s still alive.
Still not got any further than you chaps and off to Coombe Abbey for the wife’s birthday and our anniversary so any dabbling in the dark arts of the Operational Working & Functions of Unified Communication of Zigbee Stick
Or
OWFUCZS as it’s known in the trade, after another parameter is inserted and dose nothing 
Keep banging the rocks together chaps I’ll catch up with it tomorrow. 
Happy anniversary, and happy birthday to your wife.
Your pay will be docked of course, due to your lack of focus on the truly important things, like OWFUCZS. 
VICTORY! @Tony got me hooked up. 
The key fix was after getting everything set up and the proper config loaded/applied, was re-applying the FW to the stick, and putting the hub in pairing mode...after the FW update completed the hub found the stick (joined it as a contact sensor initially, I changed that to type "Device") and scanning works and it is finding my stuff.
Tony gets a big check in the WIN column.
Off for Mother's day stuff now...gotta earn the WAF!
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
