If I modify her username and give her Administrator rights the error goes away, but as soon as I revoke Administrator rights it comes back again. I am running version 2020.8.3 but this was also happening with 2020.8.2.
Any ideas on what I can look for to try and fix this problem.
I have the same problem. This happens every time that I open the Compagnion-app in my iPhone and refresh the page. Some threads in this forum state that this problem is caused by entities that represent cameras which I don’t have, at least in HA. There is only on camera that is only being accessed by NodeRed directly to the URI, taking a snapshot when someone is ringing the doorbell. The shapshot is sent by mail. There are no entities in HA for this purpose. This is the full error-message:
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:102
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 20 august 2022 21:26:55 (2 occurrences)
Last logged: 00:38:42
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:102
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 24. August 2022 um 20:16:54 (1 occurrences)
Last logged: 24. August 2022 um 20:16:54
[281472380234784] Error handling message: Unauthorized (unauthorized)
Any hints?
PS.: Yes i have an cmaera entity. But what needs to be done to prevent that error? thx
Thanks for your contribution. Good to see that I’m not the only one suffering from this annoying problem.
With regards to the question, at least not by me. The thing is that a similar problem is described in the manual of the companion-app but this is stating a relationship with entities that are representing camera’s. Although I have a camera configured in HA, I don’t see a relationship with this. The reason is that against the expectations after I removed the entity the problem is still occurring. The camera-picture is now obtained in NodeRed directly and also processed, so HA is not involved anymore. So if there are enough reporting the same problem, we will have a convincing case for submitting this to HA separately.
Same problem as well. Only recently became an issue as I’ve shifted to using the Person support for location instead of doing it manually with Bayesian.
Previously, everyone logged in with my account; now they have their own accounts. I can log them in just fine when they’re on prem. I can also disconnect their wifi and log them in via Nabu Casa with no issues.
It appears that, if their session token expires and they’re not local, they cannot successfully log in.
Interestingly, once this happens (and they’re remote), the remote URL is no longer available so there’s no way to log them back in (via Nabu Casa) until they get home.
I would recommend to create an issue here: Sign in to GitHub · GitHub
I am following this thread because I had a similar problem in the past which is resolved long ago and I am not sure if everyone here is till having a problem, but in any case an issue is the best place to let the Developers look at your problem.
Same for me. WHen I give to user Administrator privileges, the error goes away.
Any news on this???
2024-06-15 21:19:20.677 ERROR (MainThread) [homeassistant.components.websocket_api.commands] Refusing to allow Dashboard to subscribe to event dwains_dashboard_homepage_card_reload