Home Assistant Android app version(s): 2026.4.3-beta.0.0+20260405T044950Z-full
Android version(s): Android 16
Device model(s): Pixel 8
Home Assistant version: 2026.3.4
Last working Home Assistant release (if known): N/A
Description of problem, include YAML if issue is related to notifications:
Android by natively does not seem to be resolving hostnames beginning with _ ? Was able to establish this by trying to resolve the URL for ex: _my-something-realling-long-stay-away-from-it.host.sh on chrome and firefox.
I was able to observe the dns calls (private dns resolution, evident that attempt was made
Besides, I am able to access my instance on desktop browsers without an issue.
The following log was captured before taking out the internal url, as of now I am locked out of the app. There does not seem to have recovery timeout for this scenario as well.
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: java.net.UnknownHostException: Unable to resolve host "_my-something-realling-long-stay-away-from-it.host.sh": No address associated with hostname
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:156)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:103)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at java.net.InetAddress.getAllByName(InetAddress.java:1152)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.Dns$Companion$DnsSystem.lookup(Dns.kt:50)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.internal.connection.RouteSelector.resetNextInetSocketAddress(RouteSelector.kt:170)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.internal.connection.RouteSelector.nextProxy(RouteSelector.kt:132)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.internal.connection.RouteSelector.next(RouteSelector.kt:70)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.internal.connection.RealRoutePlanner.planConnect$okhttp(RealRoutePlanner.kt:164)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.internal.connection.RealRoutePlanner.plan(RealRoutePlanner.kt:75)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.internal.connection.FastFallbackExchangeFinder.launchTcpConnect(FastFallbackExchangeFinder.kt:119)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.internal.connection.FastFallbackExchangeFinder.find(FastFallbackExchangeFinder.kt:62)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.internal.connection.RealCall.initExchange$okhttp(RealCall.kt:298)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:32)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:126)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:101)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:126)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:85)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:126)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:74)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:126)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:226)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:574)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1154)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:652)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at java.lang.Thread.run(Thread.java:1563)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at libcore.io.Linux.android_getaddrinfo(Native Method)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:134)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at libcore.io.BlockGuardOs.android_getaddrinfo(BlockGuardOs.java:222)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:134)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:135)
04-07 16:28:22.697 31003 31062 W ServerConnectionStateProviderKt: ... 24 more
Home Assistant Android app version(s): 2026.4.3-beta.0.0+20260405T044950Z-full
Android version(s): Android 16
Device model(s): Pixel 8
Home Assistant version: 2026.3.4
Last working Home Assistant release (if known): N/A
Description of problem, include YAML if issue is related to notifications:
Android by natively does not seem to be resolving hostnames beginning with
_? Was able to establish this by trying to resolve the URL for ex:_my-something-realling-long-stay-away-from-it.host.shon chrome and firefox.I was able to observe the dns calls (private dns resolution, evident that attempt was made
Besides, I am able to access my instance on desktop browsers without an issue.
The following log was captured before taking out the internal url, as of now I am locked out of the app. There does not seem to have recovery timeout for this scenario as well.