Had exactly the same problem on the 61.6 update. Nothing I could do fixed it, then ~4 days later everything came back online but under the old firmware with no update to 61.6. The firmware update was later declared complete and I was still not updated. Made a post here and a very helpful ST rep said she passed my problem over to the engineering team, and a couple of days later my hub was updated, but not to 61.6, but a version 61.8. I have yet to be updated to the latest and greatest firmware and am still sitting on 61.8.
Unfortunately ST staff is no longer monitoring this form. If anyone needs firmware help they will need to contact customer service.
Have 3 v2 hubs and 2 ST Station hubs at 2 different locations.
To date only 2 of my 3 v2 hubs have updated 62.7.
My Station hubs are still on 60.13.
Apparently they are monitoring. I was just contacted by one of ST rep to help fix the issue.
@ChetHammack Thanks, it gives some hope that if nothing atleast my hub will also rollback and get back online. It seems there is some change about the way hub is connecting to cloud. I powered up another hub the Aeotec version of hub v3, it was online, it installed the update, restarted and boom … came back offline with solid blue light.
Also ,the fact that not many are facing this issue, it is possible that this update may have introduced some kind situation or config incompatibility where hub is not able connect to cloud through certain internet router. Later I will try a different internet router to see if it fixes the issue.
Currently my network is on backup hub that is ST Station. ST station usually gets update later down the line so Im hoping issue is fixed before this also gets updated!
That is good news. Many users here (me excepted) know what they are talking about.
@Paul_Oliver : from where the info that they stopped monitoring?
My hub is back online.
I attempted both block ntp time sync for forced fallback incase of certificate issue and router dns cache flush. Im not sure which one worked, but it seems dns cache was the likely cause.
Let’s pray it was only holiday
Their pictures were also removed from their profiles, so it doesn’t appear to be Holiday related.
Ok.
I still believe some guys are st least following
You will need a layer 2 VPN here to enable discovery. If you’re using OpenVPN on iOS ir only supports layer 3 so broadcast discovery doesn’t work.
The app should know the IP of the hub. It’s just one cloud API request.