I just went ahead and logged off and back on to IDE and all returned to normal, both SmartApps and Device Handlers are all displayed for my account.

Would be nice to know what the root cause of this was though. Portions of two separate accounts shown within the same Login. Fyi that test account was created over a month ago and not an account I have logged into since then.

Anyway - Let them know it’s resolved. If they found and did something to correct it, have one of them let me know if you can. Thanks again for escalating it to them.

@Zach_Varberg - my hub received the update however it was stuck as DISCONNECTED. I tried to reboot it via the IDE and it did not work. I remotely cut power to it and it immediately went to INACTIVE. Soon after restoring power it went to ACTIVE.

So is it functioning now? We have seen some uncommon issues in the past where after an update we require a power cycle to reconnect to the cloud.

For further issues, whether a part of the update process, or with the new firmware please report them in centercode as it is far easier for us to track bug reports there than to scan back through old posts in the community.

This isn’t Z-Wave device OTA firmware updates, but rather an update of the firmware for the radio that we use in the Hub.

And a very significant one at that. The tolerance for and handling of lost messages has cut the number of power cycle events per day from 100’s (1k’s last week) to an almost immeasurable amount, maybe as high as 2-3 per day.

Zach_Varberg:

This is more to provide utility for local automations. Since we are still pretty limited in what smartapps can run locally (pretty much just Lighting Automation and SHM), this gives users a way to potentially build their automations in a different way.

I haven’t had to build a SmartLighting rule in a while, but I did notice that you can use triggers from Smoke, CO, and Leak detectors in SL now. Is that something recently added, or have I just overlooked that for a while?

aruffell:

Can you provide a bit more detail on what this new firmware addresses? Will it fix the radio on/off issue (crash?), devices dropping off, network repair issues, devices that stop reporting their updates? Lately it seems like periodic upheaval breaks loose on my zwave mesh network causing everything to stop working.

Yes to all of that! I’ve been running this since last Friday and can personally say based on my experience since, this update plus the Z-Wave firmware update, have pretty much fixed all of these issues. The added benefit from reducing the errors, power cycles, and other events is a significant boost in Z-wave device responsiveness, at least on large Z-networks like mine.

It found my R7090. It hung up on the Samsung Home screen for a little bit, an error came up for a second and then the Thing page came up. No luck on my KS8000 TV. Both are in my phantom location from the account migration beta.