Unfortunately I was not able to get the beta out today due to a number of issues with Centercode. However the issues have been resolved so the beta (0.27.4) will be going out tomorrow, 8/13. My apologies.
I have gone through many beta signups that were stuck in a pending state. This can be for a number of reasons, but the most common is due to invalid hub information provided at signup. There was also a brief period of time over the last couple of months where the beta signup failed to transition to a screen requesting hub information.
If you received an email from us asking to verify hub information, or you experienced a beta signup process that may not have been complete, feel free to sign up for the beta again (https://goo.gl/Gw4cEK) and send me a DM letting me know and I’ll make sure you’re on this next beta.
So I should probably spend the afternoon reconnecting all the devices that the last general release knocked off and I haven’t been able to get reconnected for the past month. Good deal, it’s raining today anyway.
Will do. I’ve been monitoring and this is the only time I’ve seen this, and the devices work as expected with both apps and automations. I wasn’t home when these events took place, so it’s impossible to know if they didn’t work when the events happened. I suspect they were probably ok.
Before submitting the report I’m going to watch the event log closely now that I’m home, and if it happens again I’ll send it in right away.
Hurrah, guess I wasted my time yesterday trying to get devices back online. As of right now EVERY DEVICE is offline in the Classic app and in IDE. Logs submitted.
Curious enough automations are for the most part running, as well as GA & Alexa commands. Just nothing through app. IDE lists all 147 local devices as " Hub disconnected"
From what I gathered the hub-disconnect is from some kind of missed schedule. Once that schedule is restored, the message goes away. That is purely observational based. When my devices were showing disconnected they were working just fine.