Hi, @nickdahiya
I sent you a DM, can you reply there with your email, please?
Thanks, @veonua. I added you to the report.
I had the same problem as Dennis with a slight variation. A week ago Monday my v3 hub apparently hung during the update and showed offline with a solid blue light. I let it sit that way for hours before I rebooted the hub and updated the wi-fi configuration. Still could not get past the solid blue light and the offline status before I had to catch a plane later that day. I checked in while away and nothing changed until Thursday last week when I all of a sudden I received a push notification that the hub was now online (but with the same older firmware). The hub rebooted yesterday on its own and I thought that it was again cycling to update the hub to the newest version, but once again confirmed that I remained on the older version.
Today I received a SmartThings email update saying the hub firmware updates are now complete yet my hub still remains on the old version.
How do I proceed at this point?
Hi, @ChetHammack
I asked the engineering team about this, I’ll keep you posted.
My two hubs now have the update. I can’t tell when they got it as for the life of me, I can’t find the update history anywhere now.
Anyway, I am now having a boat load of problems with either badly delayed or simply not executing routines. And devices are dropping all over the place.
I hate to be that guy, but for a few months now, as devices drop off SmartThings and I can’t add them back due to device limits, I am slowly moving over to Home Assistant. I wish I had done it years ago.
I’d say do better Samsung, but I know that is wasted breath.
Hi @veonua
Can you enable access to your account, please?
- Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM
- Enable support access to your account:
- Go to the SmartThings Web (my.smartthings.com)
- Log in to your Samsung Account
- Select Menu (⋮) and choose Settings
- Toggle on Account Data Access
- Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.
See more information about this access here: https://support.smartthings.com/hc/en-us/articles/36170233944852-Enabling-Account-Data-Access-for-Support
My V3 hub is still stuck on the blinking green light. I’ve tried resetting, etc, I’m still stuck offline and it doesn’t look like the firmware update has gone through. Anyone know if support can manually push it through?
Support can not push firmware to hubs but you should still contact them to determine why it is not receiving firmware updates.
Everything was working OKAY with the hub before they pushed out the most recent firmware hub?
Staff will not be in the forum until Monday so you may want to open a support ticket though the app to see if Support can assist over the weekend.
It was blinking green before the firmware update and when I chatted with support that’s when he told me about the firmware update that would fix the issue
Hi @nayelyz,
It’s a shame that the new feature for marking Zigbee devices as disconnected wasn’t tested during the beta version, which is what it’s designed for. They said it would be implemented starting with version 61.3, but it wasn’t; everything worked the same until right after receiving the final 61.6 update. Then, many users started experiencing problems with intermittent, fictitious disconnections, especially on battery-powered devices. Me too.
They should be aware that not all real devices strictly adhere to Zigbee specifications and the reality is that some are looking for ways to save battery and don’t strictly follow the reporting intervals. For example, some temperature/humidity sensors (TS0201) sometimes fail to send a report if the temperature or humidity hasn’t changed, thus lengthening the configured interval; this can be easily seen in the CLI logs. Now, for short intervals, such as 5 minutes, they disconnect if no report is received within 10 minutes. This is excessive and only creates fictitious problems. For example, to use them as accurate thermostats and save energy in the home, short reporting intervals, such as 5 minutes, are needed. We’ve gone from over 2 hours to mark battery-powered devices as disconnected and 25 minutes for AC-powered switches to 10 minutes in many cases, which is absurd and produces many false offline statuses. Perhaps they could add a minimum time of 30 or 40 minutes to mark devices as disconnected, thus avoiding many false offline statuses.
This also affects stock smoke detectors, which are configured with The maximum interval is 180 seconds, and devices will be marked offline if no report is received within 6 minutes.
The same applies to switches and lights.
Many users are unaware that several of their devices are falsely marked offline multiple times a day, but this is the reality. After two weeks, I still haven’t seen any public response to the complaints from several users experiencing intermittent offline issues. I’m still wondering if a solution will be implemented or if we’ll have to wait for the next firmware update or it’s going to stay like this.
Thanks
Unfortunately, my V3 is still having problems; you’re lucky to have received a new update.
My hub is still stuck blinking green and chat customer service just keeps telling me to wait for more firmware updates coming later this month… not super helpful when my hub is completely useless to me and won’t rest/connect/etc. So frustrating