Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Speakers seem unavailable #34

Open
Steveelliott111 opened this issue Sep 6, 2022 · 7 comments
Open

Speakers seem unavailable #34

Steveelliott111 opened this issue Sep 6, 2022 · 7 comments

Comments

@Steveelliott111
Copy link

Noticed I wasnt getting TTS announcements on door open etc.

The speakers the app creates are all showing as unavailable (hence no tts announcements) but the 'real' sonos speakers are all working correctly in HA

Pulled from log : (Far as I'm aware i've not changed any credentials)

2022-09-06 21:27:18.258 ERROR (MainThread) [custom_components.sonos_cloud] Household request failed (401): {"fault":{"faultstring":"Invalid Access Token","detail":{"errorcode":"keymanagement.service.invalid_access_token"}}}

@jjlawren
Copy link
Owner

jjlawren commented Sep 8, 2022

It could be a transient error on the Sonos side or your credentials may have actually expired somehow. Have you tried reloading the integration or just restarting HA?

@tpantano
Copy link

tpantano commented Sep 8, 2022

I have seen the same issue occur about 3 times over the past month or so. One time it fixed itself. Other 2 times I ended up deleting the integration and re-adding it to get it to work again.

Edit: Reloading the integration or restarting HA did not solve the problem for me.

@Znegl
Copy link

Znegl commented Sep 30, 2022

I just started getting the same error, so no I have no doorbell 🙈

Could it be lack of some token refresh or similar? It has worked flawlessly for months until now, so an expired token seems likely.

Restarting the integration and restarting home assistant doesn't resolve the error.

@markus-lassfolk
Copy link

Experiencing the same issue. Have had the integration working for quite some time, and then suddenly getting invalid access token out of the blue every 1-3 days. Where removing and readding the integration fixes the problem for a day or two, until it has to be redone.

@jjlawren
Copy link
Owner

jjlawren commented Oct 5, 2022

The token refresh logic relies on HA core which has been quite reliable in my experience. This feels like a transient issue with the Sonos hosts, but I don't have hard data to back that up. Is everyone that's seeing this getting identical log entries?

If you hit this, set the logger for this integration (custom_components.sonos_cloud) to debug and reload the integration (or restart HA with the debug logger in your config).

@markus-lassfolk
Copy link

Debug log;
filtered.txt

@mbuerki84
Copy link

I have also the same issue...
Since HA has changed to the registration information (not necessary in configuration.yaml)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants