Anything stored in localStorage gets affected, which is where Browser ID, default panel etc is stored. For iOS Safari is the real culprit here, well their desire to make your life misery in the name of privacy. You can minimise this by setting your iOS devices network address to fixed rather than rotating. When rotating, whenever it rotates you suffer the issues mentioned here. My portable devices are iOS and I have no issue with Browser ID, just need to pay attention to setting when on new network. v2.5.3 now has known Browser ID in the edit dropdown to make it easy to set to the correct one for the device, as well as browser_mod.change_browser_id service which you can call as a Browser call action to have a popup to change Browser ID, easy to include on a ‘system’ Dashboard view.
Same issue here on iOS. How hard is it to persist user settings in the database ? How hard is it to pull an authenticated/logged in user’s settings from the database ? Why do I need to click on my username a set again and again my custom theme and dashboard ? This is annoying.
The page says “The following settings are local to this client only, and may reset to defaults on logout or when local data is cleared.” I never log out and I never clear the local data or cache or whatever data is persisted client side. This implementation is mediocre, let’s be honest.
If people need to set many different default theme/dashboard with the same user, due to different devices under the same user, they should create a new user (1 per device) because the current mechanism is not reliable. For some reason it does reset (is it when the IP changes ? When the network changes from local wifi to cellular 5G ? When the user-agent upgrades ? Who knows. It resets too often)
The first-party domain of home screen web applications is exempt from ITP’s 7-day cap on all script-writeable storage, i.e. ITP always skips that domain in its website data removal algorithm. In addition, the website data of home screen web applications is kept isolated from Safari and thus will not be affected by ITP’s classification of tracking behavior in Safari.
Make of this what you will, but if you don’t have Home Assistant as a Home Screen Appp then maybe this will help.
This pretty much makes HA useless for me at this point. I spent hours making dynamic dashboards for my family with bermuda BLE devices. Now I’m getting a new problem where the companion app takes FOREVER to load. Please Help!
The below solution is not out of the box but I am pretty sure it will give you the ultimate control you need. No matter what device or user profile you are using.
There is a very comprehensive set of options, most optional. Thanks to @elchininet
This stubborn HA behaviour makes HA useless for me, although I recently moved from my FHEM → HA … and enjoyed it … untill now. This issue is still the same with both: the newest companian app & HA. I constantly have this stupid /overview instead of my own lovelace. I also tried nginx (as reverse proxy) running on a separate server to redirect everything from http://192.168.x.x:8123/home/overview to http://192.168.x.x:8123/lovelace/0 … but it didn’t work. I can’t even imagine to run a home automation system without having a usefull dashboard. Unfortunately I must go back to FHEM as home automation (a lot of work … ahead). It seems that there is no fix out there ?
