Not caused by this hub FW update. The Crees got a FW update themselves a while back (once a recent hub FW update allowed OTA updates for them) and it hosed them.
I just noticed that my hub shows as Zigbee insecure rejoin is off (classic app) and Secure mode is on (new app). I don’t remember changing that - I think I would have left it insecure.
Now that you mention it, I think mine flipped itself to the same status. I rarely check it,
So can’t say definitively if the hub firmware did it or not, but insecure was turned on at some point in the past.
Hmm, same here and I can’t change it in the IDE or Classic app. My Zigbee OTA settings have also changed at some point, and I can’t change that setting either.
Yeah, I remember seeing that prior to last night’s sync/rebuild process that ST did, but it’s gone this morning. I’ve reached out to the tech working my ticket, but he’s on MST so it may be a bit.
Once my hub downloaded the beta it disabled Zigbee insecure rejoin and Zigbee OTA firmware updates. You can re-enable both in the IDE, but after a hub reboot they will flip back to disabled.
I’m not getting a good feeling about this. Looks like they misspelled my location’s name last night… Classic and Connect have different location names, but all the device’s are sync’d. This is going to be a long day.