I run the original Hubitat App on my android phone to access garage door controls. After the latest update version: 2.5.1.152, a pop up keeps appearing over the dashboard saying "Updates paused: Updates paused after 60 seconds of inactivity. This is normal behavior for cloud views. Refresh now"
OK, I get it. It's also pretty damn annoying when it pops up every few seconds and you can't clear it. How do I disable this message entirely? Also, why did you need to change this behaviour? Thank you.
This happened to me while driving to the airport. It was distracting to try to figure out where the message was coming from and what I was refreshing. Defeats the purpose of the dashboard by covering up information I was tracking. This needs to be optional.
I've also noticed that "inactivity" seems to be ill-defined - for example, I've got a dashboard that constantly updates at least one tile every few seconds (tracking water flow to sprinkler areas), but that dashboard also falls prey to the 60-second pauses.
This new behavior needs to be either adjustable or optional.
This has been enabled to match the existing behavior of EZ Dashboards.
As the message says, the timeout should happen only after at least 60 seconds of inactivity. If you are seeing the message pop up more frequently than a minute, then that is a problem.
“60 seconds of inactivity” means no interaction with the page — such as tapping, clicking, scrolling, typing, or navigating—for a full 60 seconds.
It's not possible to disable the message at this time. However, most users should rarely, if ever, see this message because the phone’s screen typically turns off before the session times out.
When approaching home I open the app when stopped at nearby traffic lights. I have to clear the message at least twice before I arrive at my house and open the garage door. I don't need to be told every minute that it needs refreshing - I can click the tick mark to do that, and my memory is longer than a minute. Please revert to the previous behavior or extend the timeout to 5 minutes. Please listen to your users.
Will see what we can do. Thanks for your feedback.
My phone screen is set to stay on for 30 minutes. This makes using the cloud dashboards useless for me for the purposes I have used them up until 2 days ago. I don't use the EZ dashboards for many reasons, add this one to the list.
This would be OK with me if "activity" also included incoming changes to displayed tiles. If I'm watching a number changing on the dashboard, it's very annoying to have to touch something once a minute to continue watching. Thanks!
I have a "weather" dashboard that I use as a screensaver on my wall tablets. I am not (thankfully) seeing this message. Their whole intent is to show active weather and radar when the screen is inactive. So, this would make them useless to me.
So, if I were to have a vote, I would say an optional setting on a dashboard (that defaults to "no popup" or no paused dashboards) would be the ideal way to handle this.
The timeout is for cloud dashboards, only.
It depends how long your screen saver is active for. My screen timeout is set to 10 minutes.
I agree it's annoying.
@BobbyD It would be great if there was a checkbox for "Don't show this message again" and a corresponding setting somewhere (to effectively clear the checkbox if desired).
I see that ALL the time.
I can understand why it's helpful to not have the web page hammering the Hubitat cloud server. But, it would be helpful if the page didn't totally time-out and, instead, just refreshed at a much longer interval. Possibly with the hub itself tracking changes and forcing a refresh when something actually changed (vs. the web page sending periodic requests).
Thanks!
That would increase the cloud costs exponentially.
After the "timeout", the refreshes could be delayed?
Trying to think of ways to not increase the cloud costs.
If there's a way to detect the web page being hidden (not actively displayed), then all activity could be suspended until it came to the foreground also?
My last comment about the Updates paused. The Hubitat name is not on the message. So while driving to the airport with my phone on the dash I kept seeing this message. At first, I thought is was a scam, then I thought message came from an Android update earlier in the week. Only when AI told me it was a feature of Hubitat did I know and was able to reproduce it. I am still not sure the reasoning for the change, is it because of the EZ Dashboard somehow or it saves money. Either way I was not aware it was happening.
It's both a transparency feature and a cost measure. Transparency because users are aware that the dashboard is not up to date and a cost measure because transactions don't happen when users aren't actively interacting with the dashboard. The next update will extend the timeout to 5 minutes. For always on dashboards, we recommend using a local connection.
Ok. I left HD+ to go back to the legacy dashboard, I guess I can go back to HD+ and escape the paused limitation on the cloud. Thanks
Thanks for the timeout extension, bobby.
I've also revisited some of my dashboard interoperability, and doubled up on some dashboard links so I can use local connections when possible, and cloud connected when necessary.
@bobbyD @gopher.ny Would it be possible to have a system variable (e.g., "%lanip%" that had the local ip address of the hub? Then, allowing that to be used as party of a dashboard link tile (including legacy dashboards)?
Also, perhaps an option on legacy and easy dashboards to redirect automatically to the local ip if possible?
Just thinking of ways to reduce load on your cloud service that could also be useful to everyone.
Thoughts??
I have a dashboard where I have a virtual lock device that I use to show when a speaker is playing text (locked=playing, unlocked=silent).
It works perfectly on my "local" lan--but it no longer works on a cloud dashboard (it's new, so it may never have worked but it only recently was added).
When it changes state, even waiting minutes never results in that device's state change being reflected on the cloud dashboard. Performing a "refresh" (browser or the green circle checkbox) gets the current state--but it never changes again after that either. Clicking the "refresh" button on the pop-up doesn't work either.
I'm using that as feedback so I know if the speaker action I trigger actually happened when I'm away and can't hear the speaker.
Thoughts?
Thanks