I have experienced disturbances with my home assistant installation for quite some time now where the interface seem to work reasonably OK in chromium but that it hangs temporarily in firefox.
. I started with a clean firefox profile and set both browsers to watch the overview window. Firefox does lose connection for some 10 seconds twice a minute or so whereas chromium keeps updating data as expected.
(yes i temporarily have a lot of missing signals due to a broken car charger about to be replaced but this problem i have seen for much longer than that.)
Problems gets worse when trying to edit the interface as interruptions really stops any progress…
am i the only one seeing this ?
Is there anything i can do to mitigate or further diagnose this issue ?
after some fiddling and headscratching i have ccome to the conclusion that if i use the hass-AMS component (i think i have an old version right now though), and i insert a history diagram in home assistant, the homepage becomes unresponsive and loses connection in firefox but intriguingly keeps functioning in e.g. chromium.
I could only guess that this could be related to relatively high amounts of data (the only difference i might be able to point out compared to other diagrams as i know the sampling frequency is higher) or it might be something else i am not aware of.
With the history diagram in the screen i see frequent tab crashes in firefox as well, which seem to be lost without that diagram.
The HA mobile app shows signifficant speed improvements with the diagram removed…
A short update: after removing the history diagram with a signal sampled every 2.5s the connection-loss problem seem to go away (and i have not seen a crash yet but still a bit too early to tell). The history diagrams sampled every 10s seem to work but it makes the card a bit slow to load. Other signals i have diagrams for are sampled every 30s if i recall correctly.
If i instead of a History diagram put a Sensor (with some kind of filtered diagram included) it sems as if i do not get crashes nor lost connections but the loading of the page and especially the specific card) is somewhat slow.
However given the look the graph in the sensor card is heavily resampled and might be saved by that.
AMATEUR CONCLUSION:
History diagrams with relatively high sampling frequency seems to not be handled well in firefox (or in the frontend if the frontend gives special formatting for firefox of which i know nothing).
Chromium is not affected in the same way.
The android mobile app is very flaky with high frequency history diagrams
regretfully i am not knowledgeable enough to be able to correct this, but i am willing to assist in fault tracing if needed.
