WearOS: watch does not register

Hi guys,

I am trying to connect my Ticwatch Pro 3 Ultra to HA. When I try to connect, it says “watch could not be registered”.
I found some posts with the same issue, but really do not quite understand what I have to do to solve my particular issue. Clearly the problem is a networking issue somehow. I read somewhere I should try and connect without Bluetooth, but then I cant even get the process started, as I need to continue on my phone (which doesnt seem to find the watch and vice versa via Wifi.

10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: Watch was unable to register: java.net.SocketTimeoutException: failed to connect to /192.168.178.93 (port 8123) from /192.168.167.239 (port 50516) after 10000ms
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at libcore.io.IoBridge.connectErrno(IoBridge.java:185)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at libcore.io.IoBridge.connect(IoBridge.java:129)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:137)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:390)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:230)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:212)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:436)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at java.net.Socket.connect(Socket.java:621)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at okhttp3.internal.platform.AndroidPlatform.connectSocket(AndroidPlatform.kt:63)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.kt:295)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at okhttp3.internal.connection.RealConnection.connect(RealConnection.kt:207)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at okhttp3.internal.connection.ExchangeFinder.findConnection(ExchangeFinder.kt:226)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at okhttp3.internal.connection.ExchangeFinder.findHealthyConnection(ExchangeFinder.kt:106)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at okhttp3.internal.connection.ExchangeFinder.find(ExchangeFinder.kt:74)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at okhttp3.internal.connection.RealCall.initExchange$okhttp(RealCall.kt:255)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:32)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:517)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
10-19 11:11:51.963 30235 30235 E SettingsWearViewModel: at java.lang.Thread.run(Thread.java:764)
10-19 11:11:51.965 30235 30235 D SettingsWearViewModel: onDataChanged 1
10-19 11:11:51.965 30235 4968 D WearOnboardingListener: onMessageReceived: MessageEventParcelable[16599,/request_home_assistant_instance, size=0]
10-19 11:11:51.966 30235 4968 D WearOnboardingListener: sendHomeAssistantInstance: ed4f15eb
10-19 11:11:51.967 30235 4968 D ServerConnectionInfo: Using external URL
10-19 11:11:51.975 30235 30235 D WearOnboardingListener: sendHomeAssistantInstance: success
10-19 11:11:55.086 30235 30235 D IntegrationRepository: isAppLocked(): false. (LockEnabled: false, appActive: false, expireMillis: 1697706513958, currentMillis: 1697706715086)
10-19 11:11:55.099 30235 30272 E OpenGLRenderer: Unable to match the desired swap behavior.
10-19 11:11:55.142 30235 30235 D IntegrationRepository: isAppLocked(): false. (LockEnabled: false, appActive: false, expireMillis: 1697706513958, currentMillis: 1697706715142)
10-19 11:11:55.143 30235 30235 D IntegrationRepository: setAppActive(): true
10-19 11:11:58.610 30235 30272 W Parcel : Expecting binder but got null!
10-19 11:11:58.638 30235 30272 E OpenGLRenderer: Unable to match the desired swap behavior.
10-19 11:11:58.712 30235 30272 E OpenGLRenderer: Unable to match the desired swap behavior.
10-19 11:12:00.067 30235 30235 D IntegrationRepository: isAppLocked(): false. (LockEnabled: false, appActive: true, expireMillis: 1697706513958, currentMillis: 1697706720067)
10-19 11:12:00.067 30235 30235 D IntegrationRepository: setAppActive(): true

Any ideas?

so htis is hte actual issue, are you able to enable NAT loopback on your router? If so try that it should help the situation.

The watch should also connect to the phone gven they are both on the same WiFi network, if not try rebooting both devices that may help clear that issue up so you can login on wifi.

I have a FritzBox 7590 - and no clue what NAT-Loopback acually is :slight_smile:
I have tried rebooting both devices already with no result. phone and watch cannot find each other via wifi (and in the router settings the connection between both devices is not blocked of course)