This has been driving me insane for the last couple of months. I noticed that Firefox will not respond to dashboard clicks after being idle for about 2 or so minutes, but does reflect current sensor status usually. When I go to settings, the page doesn’t load all the way. The only way I have found to fix this is by manually refreshing the page each and every time I want to use Home Assistant.
As part of troubleshooting, I have tried on two different installations, one with Windows 11 enterprise install of Firefox with absolutely NO extensions installed (my work computer basically). The other installation is with my Linux system.
I initially thought this was an extension but seeing that even with no extensions this is also reproducible at least on two environments in my network. (Work PC is at home)
I’ve also tried different fresh installations of other Firefox forked browsers and get the same result. I do not experience this with other browsers such as Vivaldi, Chromium or Chrome (All three of which are based on Chromium).
I thought it may be related to the newish Sections layout, so I reverted things back to Masonry and have the same results. For now, my work around is to implement an auto reload plugin from HACS every few minutes.
My network has ad-blocking enabled and I have even excluded my desktop and work PC from the adblock network environment (DNS Setting) and even cleared the DNS cache with no success.
Check in your Profile settings… near the bottom there is a setting “Automatically close connection” which will close the connection if the window or tab is hidden for too long.
Thanks for that pointer, unfortunately, it didn’t fix the issue for some reason. After I saw your post, I disabled it and gave it a test. This is my Settings page after waiting about 10 minutes with it in the background. I just need to refresh the page for it to load properly.
In the last week or so, I reinstalled my OS (for unrelated reasons to this) and started 100% fresh with Firefox knowing I would need to test this further. It’s still happening! I’m honestly frustrated beyond hope here. And the Discord channel for faster support? Erm Umm…it’s confusing at best, since they restructured it.
Is there someone, anyone who knows more or is experiencing this, or is it just me? As I stated in my first post, my work computer which is Windows 11 does the same thing and it’s a bare bones Firefox install with no extensions.
I have had my tab open and focused and it still affects the dashboard and responsiveness of others loading. I even went as far as creating a Progressive Web App based on Chromium so I could have a live dashboard and that even started doing this so, I can’t fully ascertain the problem. My work PC (Windows 11 Enterprise) locked down via I.T. Has no browser plugins and it still requires a page refresh if I keep it loaded. I work from home and am allowed to access my home network IP’s from the laptop so I load it from there and not externally from my domain name.
The biggest issue i have is, Firefox is the only other browser engine aside from Chromium and I personally don’t want to switch to one based on that just to make the dashboard work. As of this time, there are a few browser projects out there, but nothing yet ready for full time use on Linux (Ladybird Browser)
For now, I’ve resigned myself to just reloading the page when I want to access Home Assistant. I did try the auto reload card which does help, but it’s a tad annoying when you are in a dashboard, and actively editing it and it reloads. So, I disabled it for the time being.
I was about to start a topic about this as i am having the same issue. It is annoying as f tbh and i cannot find the cause.
We can’t be the only 3 or 4 people having it imho because my instance isn’t running any fancy stuff.
Edit: My dashboard was made with mushroom card. It also heavily used cardmod (eg to create the square buttons).
I have made a new dashboard with bubble card and some card mod code. It’s up for some weeks now and the effect is almost night and day. I suspect extensive use of cardmod is the culprit in my case.
Absolutely the same here for last several months. I don’t use any fancy cards, just default ones.
Whenever I click on any value, small ‘history’ chart pops up and everything freezes.
Core 2024.10.4
Frontend 20241002.4
Windows 11. Firefox 134.
I have to open MS Edge to use hass.
I have just tried to play with Developer console->Network tab opened… And it helps but in a funny way… When dev console is quite small and hass opens popup windows as usual - everthing freezes. When dev console covers half of the screen, hass opens ‘popup’ in ‘full-screen’ mode and works okay. - if I resize console window and hass decides it wants to show normal popup - everthing freezes. In case dev console is not opened - nothing works.
Very weird.
OKAY. No connection with dev console at all. The only thing is HEIGHT of the visible page. If it is small - then no freezes.
Here is example of the page height when it works. It works only in this case.
If dashboard looks like this then popups will work and will not freeze the firefox:
I see exactly the same. Dashboard freezes in Firefox if left open when I’m browsing other tabs.
I had this issue a year or two ago as well but I don’t remember how it was resolved…
Not sure exactly when it returned but its probably a few weeks ago.
For now, I created a new webapp to use Home Assistant using “web apps” from eyekay/webapps: Install websites as desktop applications - Codeberg.org to use Home Assistant in. This resolved my issue with the dashboard freezing. There are several other apps which would do the same thing as well so it should be mostly platform agnostic depending on your OS and what’s available.
With HA in a webapp, I basically have a desktop icon and also a shortcut in my application menu (I use KDE Desktop on Linux) and it launches the full HA system in a new window, so it behaves like an app, but inside, it just wraps the web interface into an app.
This for me, has worked well and while I would prefer to keep in in Firefox, but for the time being, it’s a happy medium for me.
So, I disabled it for the time being.
