iOS 26.4 (Beta) failed to connect locally

[infernalK]

iOS device model, version and app version

Model Name: IPhone 17 pro
Software Version: 26.4
App version: 2026.2.1 (2026.1766)

Home Assistant Core Version
2026.2.2

Describe the bug
When opening the app it fails to connect till I disconnect and reconnect the WiFi. It was working well till the last home assistant update.

To Reproduce

Expected behavior

Screenshots

Additional context

[bgoncal]

It's an iOS 26.4 Beta 1 issue, currently the root cause is unknown.

[infernalK]

Not sure it appears with my phone in iOS 26.3RC. It starts when updating home assistant core and/or companion app.

[bgoncal]

In the issue information you mentioned iOS 26.4, can you double check?

[infernalK]

It doesn't work on both. At the time I wrote the issue I was in 26.4 but already have the issue on 26.3

[bgoncal]

Ok, got it now, so maybe there are different issues. Regarding the 26.3 device, does rebooting the phone helps?

[Xoffroad]

It's an iOS 26.4 Beta 1 issue, currently the root cause is unknown.

Same isses here. After updating to iOS 26.4 Public Beta on iPhone 17 Pro. iPad with iPadOS 26.3 works fine. App Log shows the following error:
{
"error" : "Der Vorgang konnte nicht abgeschlossen werden. (HAKit.HADataError-Fehler 1.)"
}

[giesbertdumpich]

The same Error exists on macOS 26.4 beta1 as well…

I did some additional testing and found a workaround that consistently resolves the issue on my end.
In my case, the app successfully connects when I use the local hostname of the server instead of the direct IP address.

For example, using:

http://homeassistant.local:8123

works reliably, whereas:

http://192.168.178.88:8123

Fails under the same conditions.
This behavior is reproducible for me on:
• macOS 26.4 (Beta 1 and Beta 2)
• iOS 26.4 (Beta 1 and Beta 2)

As soon as I switch from the raw IP address to the .local hostname, the connection works immediately without any additional changes.

This might suggest a networking, DNS resolution, or local name handling difference in the current betas. Perhaps something related to how direct IP connections are handled compared to mDNS/Bonjour resolution.

Hopefully this helps narrow things down or gives others a temporary workaround until the root cause is identified.

[redford-jones]

using:

http://homeassistant.local:8123

works reliably

Can confirm this workaround works

[infernalK]

Also works for me

[infernalK]

This is strange cause I have other stuff I connect to with direct ip address like a pihole instance on a raspberry and I have no problem.

[rroblik]

Same issue for me. .local is not an option with many configuration 👀

[giesbertdumpich]

I’ve done some further testing and can provide a few more observations that might help narrow this down.
1. The described behavior only occurs in the Companion App.
Accessing Home Assistant via a web browser (Safari or Google Chrome) works without any issues — both when using the IP address and when using the .local hostname.
2. When accessing Home Assistant via the IP address in the Companion App, the connection usually fails.
In rare cases, the app does connect briefly, but the connection drops again almost immediately.
3. When I use the local hostname (e.g. http://homeassistant.local:8123) instead of the direct IP (e.g. http://192.168.178.88:8123), the Companion App connects reliably and remains stable.
4. External access via IP works perfectly fine.
When I connect through VPN (WireGuard) and use the IP address, everything functions as expected.

Based on this behavior, my current assumption is that Home Assistant may not be recognizing local IP-based access as “local” in this specific scenario (at least from within the Companion App). As a result, the connection might be treated differently and ultimately rejected or dropped.

Since:
• Browsers are unaffected
• VPN/IP access works externally
• .local works internally
• The issue only occurs inside the Companion App

…it seems to point toward something specific in how the Companion App (possibly in combination with the current macOS/iOS 26.4 betas) handles local IP connections.

I’m happy to provide logs or run additional tests if needed.

[Tpro1807]

I seem to be facing the same issue. However, the workaround for the internal URL does not work for me.

I am running IOS 26.4 with HA running on a container. This problem only takes place within the companion app. Using browsers works perfectly.