Companion app not able to register a wearOS watch anymore.

[gael-honorez-para]

Home Assistant Android app version(s):

Android version(s): 12 SKQ1.211006.001
WearOS 5.0

**Device model(s): Mi 10T Pro & oneplus watch 3

**Home Assistant version: 2025.12.4 on both

Last working Home Assistant release (if known): 2025.12.4

Description of problem, include YAML if issue is related to notifications:
The WearOS panel on the companion app is spinning forever. Here is what I've tried:
Rebooted both devices, emptied the caches, reinstall both apps (android and app), deleted the mobile app from HA, as well as all traces of the watch in entities.
It still spinning forever even if the watch is now failing at the login screen : I see the ha instance, it says "continue on phone" then return to the list of HA instances immediatly.
On the phone, if the watch is connected, I see it on the companion app page, but same behavior: Clicking on hit just make a spinner spin forever.

Companion App Logs:

————- beginning of system
12-24 11:56:51.127 25959 25959 I ForceDarkHelperStubImpl: initialize for io.homeassistant.companion.android , ForceDarkOrigin
12-24 12:05:25.422 25959 25959 D ViewScrollStubImpl: the value of ScrollFrictionRes is: 0.015
————- beginning of main
12-24 12:09:47.350 25959 25959 D LocationSensorManager: Received location update.
12-24 12:09:47.354 25959 25959 D ForegroundServiceLauncher: Check if service HighAccuracyLocationService is running. Service running = false
12-24 12:09:47.355 25959 26007 D LocationSensorManager: Last Location:
12-24 12:09:47.355 25959 26007 D LocationSensorManager: Coords:(50.798449, 4.3321875)
12-24 12:09:47.355 25959 26007 D LocationSensorManager: Accuracy: 100.0
12-24 12:09:47.355 25959 26007 D LocationSensorManager: Bearing: 0.0
12-24 12:09:47.356 25959 26007 D LocationSensorManager: Begin evaluating if location update should be skipped
12-24 12:09:47.356 25959 26007 D LocationSensorManager: Received location that is 29 milliseconds old, 1766574587327 compared to 1766574587356 with source fused
12-24 12:09:47.357 25959 30107 D WearOnboardingListener: onMessageReceived: MessageEventParcelable[18636,/request_home_assistant_instance, size=0]
12-24 12:09:47.358 25959 30107 D WearOnboardingListener$sendHomeAssistantInstance: sendHomeAssistantInstance: d41ea27c
12-24 12:09:47.359 25959 30107 D ServerConnectionInfo: Using external URL
12-24 12:09:47.372 25959 25959 D WearOnboardingListener$sendHomeAssistantInstance: sendHomeAssistantInstance: success
12-24 12:09:47.431 25959 26017 D LocationSensorManager$sendLocationUpdate: Location update sent successfully for 1 as exact
12-24 12:09:50.785 25959 25990 D WM-Processor: Processor cancelling c60cc6c3-f9a9-4d55-9ebb-d2dee0f71468
12-24 12:09:50.785 25959 25990 D WM-Processor: WorkerWrapper could not be found for c60cc6c3-f9a9-4d55-9ebb-d2dee0f71468
12-24 12:09:50.786 25959 25959 D SensorReceiverBase: Received intent: android.intent.action.SCREEN_ON
12-24 12:09:50.787 25959 25959 V BaseGlanceEntityWidgetReceiver: Received intent action = android.intent.action.SCREEN_ON for widget = 0 (io.homeassistant.companion.android.widgets.todo.TodoGlanceAppWidget) io.homeassistant.companion.android.widgets.todo.TodoWidget@c03384a
12-24 12:09:50.787 25959 26017 D SensorReceiverBase$onReceive: Sensor(s) [is_interactive] corresponding to received event android.intent.action.SCREEN_ON are disabled, skipping sensors update
12-24 12:09:50.788 25959 25990 D WM-GreedyScheduler: Cancelling work ID c60cc6c3-f9a9-4d55-9ebb-d2dee0f71468
12-24 12:09:50.789 25959 25959 D ServerConnectionInfo: Using external URL
12-24 12:09:50.789 25959 25990 D WM-SystemJobScheduler: Scheduling work ID 01351199-a6ec-4738-a487-58d3fc6cf2ecJob ID 341
12-24 12:09:50.790 25959 25959 D ButtonWidget: Broadcast received:
12-24 12:09:50.790 25959 25959 D ButtonWidget: Broadcast action: android.intent.action.SCREEN_ON
12-24 12:09:50.790 25959 25959 D ButtonWidget: AppWidgetId: -1
12-24 12:09:50.793 25959 25990 D WM-GreedyScheduler: Starting work for 01351199-a6ec-4738-a487-58d3fc6cf2ec
12-24 12:09:50.794 25959 25990 D WM-Processor: Processor: processing WorkGenerationalId(workSpecId=01351199-a6ec-4738-a487-58d3fc6cf2ec, generation=0)
12-24 12:09:50.797 25959 25959 D WM-WorkerWrapper: Starting work for io.homeassistant.companion.android.websocket.WebsocketManager
12-24 12:09:50.797 25959 25959 D WM-SystemJobService: onStartJob for WorkGenerationalId(workSpecId=01351199-a6ec-4738-a487-58d3fc6cf2ec, generation=0)
12-24 12:09:50.798 25959 25990 D WM-Processor: Work WorkGenerationalId(workSpecId=01351199-a6ec-4738-a487-58d3fc6cf2ec, generation=0) is already enqueued for processing
12-24 12:09:50.798 25959 25959 D MediaPlayerControlsWidget: Broadcast received:
12-24 12:09:50.798 25959 25959 D MediaPlayerControlsWidget: Broadcast action: android.intent.action.SCREEN_ON
12-24 12:09:50.798 25959 25959 D MediaPlayerControlsWidget: AppWidgetId: -1
12-24 12:09:50.799 25959 25959 D ServerConnectionInfo: Using external URL
12-24 12:09:50.800 25959 25989 I WM-WorkerWrapper: Worker result SUCCESS for Work [ id=01351199-a6ec-4738-a487-58d3fc6cf2ec, tags={ io.homeassistant.companion.android.websocket.WebsocketManager } ]
12-24 12:09:50.801 25959 25959 D WM-Processor: Processor 01351199-a6ec-4738-a487-58d3fc6cf2ec executed; reschedule = false
12-24 12:09:50.801 25959 25959 D WM-SystemJobService: 01351199-a6ec-4738-a487-58d3fc6cf2ec executed on JobScheduler
12-24 12:09:50.804 25959 25959 D ServerConnectionInfo: Using external URL
12-24 12:09:50.804 25959 25989 D WM-GreedyScheduler: Cancelling work ID 01351199-a6ec-4738-a487-58d3fc6cf2ec
12-24 12:09:50.806 25959 25959 D ServerConnectionInfo: Using external URL
12-24 12:09:50.808 25959 25989 D WM-SystemJobScheduler: Scheduling work ID 01351199-a6ec-4738-a487-58d3fc6cf2ecJob ID 341
12-24 12:09:52.338 25959 30181 D WearOnboardingListener: onMessageReceived: MessageEventParcelable[18638,/request_home_assistant_instance, size=0]
12-24 12:09:52.338 25959 30181 D WearOnboardingListener$sendHomeAssistantInstance: sendHomeAssistantInstance: d41ea27c
12-24 12:09:52.338 25959 30181 D ServerConnectionInfo: Using external URL
12-24 12:09:52.342 25959 25959 D WearOnboardingListener$sendHomeAssistantInstance: sendHomeAssistantInstance: success
12-24 12:09:53.211 25959 25969 D AppScoutStateMachine: 25959-ScoutStateMachinecreated
12-24 12:09:53.282 25959 30009 I OpenGLRenderer: Davey! duration=9223344121612ms; Flags=1, FrameTimelineVsyncId=1244168, IntendedVsync=27915227817177, Vsync=27915227817177, InputEventId=0, HandleInputStart=27915228075600, AnimationStart=27915228076173, PerformTraversalsStart=27915228319871, DrawStart=27915240458152, FrameDeadline=27915244483843, FrameInterval=27915228067319, FrameStartTime=16666666, SyncQueued=27915241051850, SyncStart=27915255059819, IssueDrawCommandsStart=27915255181746, SwapBuffers=27915256151225, FrameCompleted=9223372036854775807, DequeueBufferDuration=11771, QueueBufferDuration=5173020, GpuCompleted=9223372036854775807, SwapBuffersCompleted=27915261625548, DisplayPresentTime=0,
12-24 12:09:53.300 25959 25959 D DecorView[]: onWindowFocusChanged hasWindowFocus true
12-24 12:09:57.624 25959 30251 D WearOnboardingListener: onMessageReceived: MessageEventParcelable[18640,/request_home_assistant_instance, size=0]
12-24 12:09:57.624 25959 30251 D WearOnboardingListener$sendHomeAssistantInstance: sendHomeAssistantInstance: d41ea27c
12-24 12:09:57.625 25959 30251 D ServerConnectionInfo: Using external URL
12-24 12:09:57.632 25959 25959 D WearOnboardingListener$sendHomeAssistantInstance: sendHomeAssistantInstance: success
12-24 12:10:46.483 25959 25959 D MIUIInput: [KeyEvent] ViewRootImpl KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_BACK, scanCode=0, metaState=0, flags=0x48, repeatCount=0, eventTime=27968458, downTime=27968458, deviceId=-1, source=0x101, displayId=0 }
12-24 12:10:46.512 25959 25959 D MIUIInput: [KeyEvent] ViewRootImpl KeyEvent { action=ACTION_UP, keyCode=KEYCODE_BACK, scanCode=0, metaState=0, flags=0x48, repeatCount=0, eventTime=27968490, downTime=27968458, deviceId=-1, source=0x101, displayId=0 }
12-24 12:10:46.588 25959 25959 D DecorView[]: onWindowFocusChanged hasWindowFocus false
12-24 12:10:46.593 25959 25959 D IntegrationRepositoryImpl: isAppLocked(): false. (LockEnabled: false, appActive: false, expireMillis: 1766574334979, currentMillis: 1766574646593)
12-24 12:10:46.609 25959 25959 D DecorView[]: onWindowFocusChanged hasWindowFocus true
12-24 12:10:46.614 25959 25959 D IntegrationRepositoryImpl: isAppLocked(): false. (LockEnabled: false, appActive: false, expireMillis: 1766574334979, currentMillis: 1766574646613)
12-24 12:10:46.614 25959 25959 D IntegrationRepositoryImpl: setAppActive(): true
12-24 12:10:47.373 25959 25959 D LocationSensorManager: Received location update.
12-24 12:10:47.378 25959 25959 D ForegroundServiceLauncher: Check if service HighAccuracyLocationService is running. Service running = false
12-24 12:10:47.378 25959 29009 D LocationSensorManager: Last Location:
12-24 12:10:47.378 25959 29009 D LocationSensorManager: Coords:(50.798449, 4.3321875)
12-24 12:10:47.378 25959 29009 D LocationSensorManager: Accuracy: 100.0
12-24 12:10:47.378 25959 29009 D LocationSensorManager: Bearing: 0.0
12-24 12:10:47.379 25959 26007 D LocationSensorManager: Begin evaluating if location update should be skipped
12-24 12:10:47.379 25959 26007 D LocationSensorManager: Received location that is 47 milliseconds old, 1766574647332 compared to 1766574647379 with source fused
12-24 12:10:47.379 25959 26007 D LocationSensorManager: Duplicate location received, not sending to HA
12-24 12:10:54.481 25959 30009 I OpenGLRenderer: Davey! duration=9223344060413ms; Flags=0, FrameTimelineVsyncId=1251508, IntendedVsync=27976441282156, Vsync=27976441282156, InputEventId=0, HandleInputStart=27976442575316, AnimationStart=27976442577712, PerformTraversalsStart=27976442580368, DrawStart=27976442763233, FrameDeadline=27976457948822, FrameInterval=27976442553858, FrameStartTime=16666666, SyncQueued=27976444791202, SyncStart=27976444905525, IssueDrawCommandsStart=27976445480837, SwapBuffers=27976450207764, FrameCompleted=9223372036854775807, DequeueBufferDuration=48490, QueueBufferDuration=1563542, GpuCompleted=9223372036854775807, SwapBuffersCompleted=27976452869431, DisplayPresentTime=0,
12-24 12:10:54.836 25959 25959 E mpanion.androi: Invalid ID 0x00000000.
12-24 12:11:00.107 25959 25959 E mpanion.androi: Invalid ID 0x00000000.
12-24 12:11:00.207 25959 26007 D LogcatReader$readLog: Read logcat for pid 25959

[jpelgrom]

Which version of the Home Assistant app are you using?

Usually if it continues spinning, the phone app cannot communicate with the watch. However, the fact that it shows you servers on the watch, which it gets from the phone, suggests otherwise 🤔

[gael-honorez-para]

That's the version on the ticket for both The phone and the watch. It was working weeks ago, but yesterday I tried to edit a template for the watch and it was spinning forever. I though a reset would fix it, but no. Envoyé à partir de Outlook pour Android<https://aka.ms/AAb9ysg> This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, proprietary and personal data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. For more information on how we use and protect your information, please review our Privacy Policy here<https://www.v-nova.com/privacy-policy/> Please consider your environmental responsibility before printing this e-mail

…

________________________________ From: Joris Pelgröm ***@***.***> Sent: Thursday, December 25, 2025 9:40:00 AM To: home-assistant/android ***@***.***> Cc: Gaël Honorez ***@***.***>; Author ***@***.***> Subject: Re: [home-assistant/android] Companion app not able to register a wearOS watch anymore. (Issue #6195) [https://avatars.githubusercontent.com/u/8148535?s=20&v=4]jpelgrom left a comment (home-assistant/android#6195)<#6195 (comment)> Which version of the Home Assistant app are you using? Usually if it continues spinning, the phone app cannot communicate with the watch. However, the fact that it shows you servers on the watch, which it gets from the phone, suggests otherwise 🤔 — Reply to this email directly, view it on GitHub<#6195 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOB6JPXR6YMSQR5RA4YUS3D4DOPGBAVCNFSM6AAAAACP5WLUQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMOJRGE2TKNJTG4>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[jpelgrom]

Your issue description does not mention an app version, only Android versions:

Home Assistant Android app version(s):

Android version(s): 12 SKQ1.211006.001
WearOS 5.0

I'm mostly interested to know whether or not your using the beta version of the app, as it has some changes regarding connectivity which might point to a different direction.

[gael-honorez-para]

2025.11.4-full (19134) for the phone. I'm not able to go to the setting menu on the watch but it's the latest version on the store. Do you want me to test a beta version? (If so, how do I install it?) Envoyé à partir de Outlook pour Android<https://aka.ms/AAb9ysg> This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, proprietary and personal data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. For more information on how we use and protect your information, please review our Privacy Policy here<https://www.v-nova.com/privacy-policy/> Please consider your environmental responsibility before printing this e-mail

…

________________________________ From: Joris Pelgröm ***@***.***> Sent: Friday, December 26, 2025 8:06:55 PM To: home-assistant/android ***@***.***> Cc: Gaël Honorez ***@***.***>; Author ***@***.***> Subject: Re: [home-assistant/android] Companion app not able to register a wearOS watch anymore. (Issue #6195) [https://avatars.githubusercontent.com/u/8148535?s=20&v=4]jpelgrom left a comment (home-assistant/android#6195)<#6195 (comment)> Your issue description does not mention an app version, only Android versions: Home Assistant Android app version(s): Android version(s): 12 SKQ1.211006.001 WearOS 5.0 I'm mostly interested to know whether or not your using the beta version of the app, as it has some changes regarding connectivity which might point to a different direction. — Reply to this email directly, view it on GitHub<#6195 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOB6JPVLZLSTRRIIM3DHPIL4DWBM7AVCNFSM6AAAAACP5WLUQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMOJTGI2TAOBTGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>