if you try to register from the phone app, you can use the logs from the troubleshooting section to see what the error is
Settings > companion app > wear OS and try to login
once it fails
go back to the main companion app settings page and scroll down to troubleshooting and look at the logs the error should be near the bottom
no thats safe to ignore, it will be an actual error message taking up more than 1 line
Sorry, I`m to noob to find the error message in the log. Can I send you the log as .txt? But Im not shure if it contains some confidential informations…like HA url
the error may or may not contain your HA URL and the logs may also contain GPS data. If you scan the logs for your URL you may find the error easily. If not feel free to PM it
Hoping this helps others who come to this thread looking for solutions for local only HA instances not connecting/logging in - or not loading entities if they manage to get it connected (I was stuck in both states). I had this issue for a few locally hosted apps.
I was able to ADB into the watch and turn off DNS over TLS which sorted this for me
You could alternatively change the private DNS hostname to your own DNS server and resolve this the same way.
If you’re unfamiliar, ADB connections are done like this
and the commands should look like:
# disable private dns
adb shell settings put global private_dns_mode off
# alternatively set your own DoT DNS server
adb shell settings put global private_dns_mode hostname
adb shell settings put global private_dns_specifier dns.yourdomain.com
This trick is well documented in the GoogleTV/wider android community