I have previously set up a shortcut tile with 5 shortcuts that’s works a charm. However I went to add a couple more shortcuts to the tile and there’s nothing available. If I click the plus button the ‘Choose entity’ screen just has a None button with a trash can icon, and the ‘Favorites’ dropdown shows nothing listed. I even tried adding a new tile to start fresh but I get the same results.
Is there a way to force it to update available entities? Or is there something else that I’m missing?
Edit: Just tried setting ‘Only show favorites’ to off to see if that helps, but I just get ‘Error loading entities’ with a ‘Retry’ button… clicking the button does nothing.
Edit 2: Shrank the images
Phone:
Galaxy S10+
Android 12
OneUI 4.1
Watch:
Galaxy Watch 5
Wear OS 4.0
OneUI 5.0
if you see no entities tehn teh app had an issue connecting to the server, try to force stop teh app and open it again maybe it will reconnect
Son of a…
Tried force stopping the mobile app and restarting, no joy. Tried force stopping and restarting the Wear OS app, no joy. Came back here and reread your response and realised that ‘server’ might not mean my local HA server.
I have an automation that turns off remote access through Nabu Casa when I arrive home and turns it on when I leave. I turned on remote access and viola, entities suddenly apeared.
So will Wear OS not update entities unless it’s cloud connected?
Wear OS only works with 1 URL and its recommended to use the external URL because teh watch never goes on wifi as one would expect.
Got it. Thank you for the info and the help, greatly appreciated.
I have this exact same issue with my Samsung Galaxy 5 watch. I tap on the “Retry” button on my watch and I see a “Loading…” spinner, but then it shortly stops and I see “Error Loading Entries”. I can’t seem to figure out what to do at this point. I checked the Companion HA app on my phone but don’t see any settings that will allow me to add devices.
Can any one help? Thanks.
Of course, right after I post this message it starts working. I cleared the cache in the HA Companion App on my phone and now it loaded all of the devices and rooms into the Wear OS app.
LOL if I had a quarter (inflation) for every time that’s happened to me.
I’ve just set up my new pixel watch 4 and I am also unable to see any entities.
Things I’ve tried:
- Empty cache on wear OS
- completely uninstall app from wear OS
- reboot the watch
- manually enter the server address
- emtpy cache on android phone App
still, all I get is “Error loading entities”
Could this have something to do with Wear OS 6?
no samsung has been out for quite some time with it, I also do not see the issue on my pixel watch 3 on Wear OS 6. Try restarting both phone and watch and see if it will load
Tried that just now, still doesn’t work.
Sensors from the watch do get transmitted to HA tho. i.e. I can see the battery percentage in HA.
then there is probably an error message the app needs to fix, unless you dont have any lights or switches or controllable entities?
if you do have entities that are controllable like lights and stuff the only way to get the app logs is to use ADB logcat or android studio
I found the culprit. I was preparing to open an issue on github when I ran logcat to retrieve logs. I noticed that the app was getting a bunch of ‘403 Forbidden’ errors:
10-11 20:08:13.950 3905 3905 E WebSocketCoreImpl: Unable to subscribe to {type=subscribe_events, event_type=area_registry_updated}
10-11 20:08:15.608 3905 12619 E WebSocketCoreImpl: Websocket: onFailure
10-11 20:08:15.608 3905 12619 E WebSocketCoreImpl: java.net.ProtocolException: Expected HTTP 101 response but was '403 Forbidden'
10-11 20:08:15.608 3905 12619 E WebSocketCoreImpl: at okhttp3.internal.ws.RealWebSocket.checkUpgradeSuccess$okhttp(RealWebSocket.kt:233)
10-11 20:08:15.608 3905 12619 E WebSocketCoreImpl: at okhttp3.internal.ws.RealWebSocket$connect$1.onResponse(RealWebSocket.kt:177)
10-11 20:08:15.608 3905 12619 E WebSocketCoreImpl: at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:532)
10-11 20:08:15.608 3905 12619 E WebSocketCoreImpl: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
10-11 20:08:15.608 3905 12619 E WebSocketCoreImpl: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
10-11 20:08:15.608 3905 12619 E WebSocketCoreImpl: at java.lang.Thread.run(Thread.java:1119)
10-11 20:08:15.609 3905 12434 E WebSocketCoreImpl$connect: Unable to authenticate
10-11 20:08:15.609 3905 12434 E WebSocketCoreImpl$connect: java.net.ProtocolException: Expected HTTP 101 response but was '403 Forbidden'
10-11 20:08:15.609 3905 12434 E WebSocketCoreImpl$connect: at okhttp3.internal.ws.RealWebSocket.checkUpgradeSuccess$okhttp(RealWebSocket.kt:233)
10-11 20:08:15.609 3905 12434 E WebSocketCoreImpl$connect: at okhttp3.internal.ws.RealWebSocket$connect$1.onResponse(RealWebSocket.kt:177)
10-11 20:08:15.609 3905 12434 E WebSocketCoreImpl$connect: at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:532)
10-11 20:08:15.609 3905 12434 E WebSocketCoreImpl$connect: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
10-11 20:08:15.609 3905 12434 E WebSocketCoreImpl$connect: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
10-11 20:08:15.609 3905 12434 E WebSocketCoreImpl$connect: at java.lang.Thread.run(Thread.java:1119)
So i started digging to make sure there wasn’t an issue on my end.
I was connecting through my reverse proxy, so instead I tried connecting through the home assistant cloud URL. That also didn’t work, so I tried the internal IP address of my Home Assistant instance.
WHICH ALSO DIDN’T WORK.
So I went ahead and cleared my ip_bans.yaml which has fixed the issue for me! Still racking my brain what exactly was the culprit because none of the IP’s in the ban list referred to my watches private IP nor my public IP.