[Assist]: Browser ID doesn't persist

[GGSSDD]

I have an issue after updating to 2.7.4 where a custom Browser ID doesn't persist, doesn't survive a page refresh on my iPhone companion app (as far as I can see there are no issues on a desktop browser). Everything is up to date (HA, Companion app, iOS).

What I am doing

Assigning my custom Browser IDs.

What I expect to happen

Persist after page refresh.

What happened instead

Most of the times returns the Browser Mod default ID. It's hit or miss, mostly miss.

By checking each box below I indicate that I ...

• Understand that this is a channel for reporting bugs, not a support forum (https://community.home-assistant.io/).
• Have made sure I am using the latest version of the plugin.
• Understand that leaving one or more boxes unticked or failure to follow the template above may increase the time required to handle my bug-report, or cause it to be closed without further action.
• If this issue is to do with an Android device losing connection, sensors becoming unavailable etc., please confirm you have read, understood and tried methods described in Wiki Article Andoird Devices 'Always On'

[dcapslock]

Hi, 2.7.4 did not have any changes in the Browser ID area so it is not expected to be the change given rise to your issue. Did you update anything else? iOS, local network? Companion App?

As you say it is happening very often, it is likely that Safari (which manages any WebView localStoarge) is clearing localStorage very freqently. It will do this in a few scenarios including if you are using a rotating Private WiFi address.

You can try going to private WiFi settings and change Private WiFi address to Fixed rather than Rotating.

Another tip is that having Home Assistant Companion App in Homescreen is also an action that Safari will see as you trusting the App and will be less aggresive with clearing localStorage so often.

Also that internal and external access is considered different by Safari so it could be that you are connecting externally and your ISP is giving you varying addresses that Safari sees as new. If your mobile provider has switched you to exclusive IPv6 then this may also be something to check whether this is causing issues.

[GGSSDD]

I don't know what to say... besides keeping everything up to date I haven't made any relevant changes to my system. There was indeed an iOS update recently that brought some pretty major changes to Safari (it allows web extensions now) but i don't know how that could relate to this issue. Also my private WiFi was always set to Fixed and this happens for internal and external access alike.

[dcapslock]

Perhaps you can follow up on the changes that the iOS update. Check for change in respect to privacy as this is the area that will impact clearning localStorage.

I use iOS as my main mobile device for my production Home Assistant and it is working fine with 2.7.4 (2.7.4 beta prior which I also tested in my production environment).

[dcapslock]

Just a hunch, I understand the new iOS Companion App will ask about permissions to do with location and local network. You may have seen this popup but not follow through. Do you remember something like this happening recently?

[dcapslock]

iOS Companion App will ask about permissions

Check in Companion App settings. Click on your server, check 'Connection security level'. Mine says 'Most secure'. You can click to check/change.

[GGSSDD]

It's driving me nuts... I'll keep investigating, also will compare with my wife's companion when she gets home. I will update once I find the culprit.

[dcapslock]

I checked and I have an iOS update to apply, 26.3. What 26 version do you have? It could be the difference.

Basically there is somthing there specific to the device and/or Home Assistant environemnt where Safari's Intelligent Tracking Pevention is kicking in. The fact that I don't have an issues but you do, could be to do with other JS running in your Home Assistant, so other custom elements that may be giving rise for Apple's ITP to kick in and clear localStorage. This arcticle is a good intro for what Apple can do with ITP.

[GGSSDD]

I checked and I have an iOS update to apply, 26.3. What 26 version do you have? It could be the difference.

Basically there is somthing there specific to the device and/or Home Assistant environemnt where Safari's Intelligent Tracking Pevention is kicking in. The fact that I don't have an issues but you do, could be to do with other JS running in your Home Assistant, so other custom elements that may be giving rise for Apple's ITP to kick in and clear localStorage. This arcticle is a good intro for what Apple can do with ITP.

iOS 26.3 (23D127). This is the most recent.

[GGSSDD]

So I checked my wife's iPhone... Same server, same settings the only difference is the iOS version, she didn't update to the latest, she still has 26.2.1 (23C71). No issues there, no matter how many times I refresh the page her custom Browser IDs persist.

[dcapslock]

My phone updated to 26.3 overnight. I also had Home Assistant 2026.2.2 to install. Both now updated and all good for my iPhone.

[dcapslock]

Still thinking what difference there is. Perhaps its the Browser ID you use that Safari thinks it needs to clear?

[GGSSDD]

My phone updated to 26.3 overnight. I also had Home Assistant 2026.2.2 to install. Both now updated and all good for my iPhone.

Did you update to 23D127? That is a more recent security update. That's when they made those changes to Safari that I was talking about.

[dcapslock]

Yes 23D127