"alexa state reporting disabled"

Configuration
1

This has popped up twice in the last week or two and I’m not sure what it means.

Alexa state reporting disabled

There was an error reporting state to Alexa (RefreshTokenNotFound). Please re-link your Alexa skill via the Alexa app to continue using it.

I’ve checked everything I know to check and everything seems to be working.

I the Alexa app the HA skill says it’s linked. But TBH, I’m not even sure if HA is the app that the error is referencing.

Not sure what else to check…

Anyone else seeing this?

2

what’s the error coming from? Alexa?

3

You’re using ASHS right?

4

I’m not sure where it’s coming from.

it just pops up as a persistent notification in the HA sidebar with the exact text quoted above.

I didn’t think to check the log before I restarted…twice… :man_facepalming:

Not sure what ASHS is?

5

Alexa Smart Home Skill.

Basically, you ahve 2 options for alexa: Nabu Casa or Alexa Smart Home Skill. Just trying to figure out which, because they are both very different.

EDIT: If you don’t remember, you probably have Alexa Smart Home Skill or Haaska or whatever it used to be called.

6

As far as I know I don’t use that skill. I use Nabu Casa.

It’s not listed in my list of enabled skills.

EDIT: but Haaska is still listed there as an enabled skill. I’ll try disabling that and see if it comes back again. I completely forgot that was still there.

7

Ah, well I can’t help then. Did you check your credentials on the Alexa skill in Alexa’s app?

8

it said the HA skill was linked so I think it is OK.

9

So, seeing that alexa works, it sounds like proactive events through nabucasa are giving you issues. I don’t know how to do any of this through nabu-casa and I assume a login/out via the app would fix it.

10

I’m really not sure if that’s related or not.

I’ve used NC since it was offered and haven’t had the alexa smart home configuration in HA or any external ports forwarded since then (several years now). That notification just popped up the first time a week or so ago. if it was related to haaska I would’ve thought it would have shown up long before now.

either way I’ve disabled the haaska skill in Amazon so I’ll just wait and see if the notification returns and go from there.

Which app are you referring to?

11

So, the proactive events are a different endpoint than normal alexa. The fact they happen randomly points to that IMO. In Alexa Smart Home Skill you have to enable that and configure it. In nabu casa it should already be configured.

12

Alexa on your phone (or through a browser on your computer). Basically, inside alexa however you set that up.

13

My first thought was that it was a NC issue but I figured I would ask here first.

if it comes back I’ll submit an issue with NC.

Thanks for the help. :slightly_smiling_face:

14

It very well could be, but that message is basically telling you to re-auth on the alexa skill in your alexa app. Might be worth changing that error to make it more explicit

15

I hat the same notification from “Alexa Media Player” custom component.
Have you checked Configuration → Devices & Services when the notification appears?

I had to select Configure & re-enter the Second Factor OTP …this seems to be default if you are not using a OTP proxy which allows the custom component itself to generate OTP Tokens

1 Like
16

Also, if you’re using long term access tokens, I recommend swapping over to a person with their own log in. I made “alexa” as a user in my system and have “her” log in via that. Now I have nice logs that tell me when we use voice control to do crap.

1 Like
17

I do use AMP but the notification that the integration needs re-authorized has been different than the one I’m getting now (at least in the recent past - unless they changed the notification wording just recently :man_shrugging:). I’ve never seen that notification before a couple of weeks ago.

And I very rarely get those notifications either anymore since I switched to the built-in 2FA. Now the integration just silently handles the re-auth itself.

That sounds like a good idea but I likely won’t do it since things are working and “if it’s not broke don’t fix it” :laughing:

18

I get it, it’s nice to have context though. I now know when alexa doesn’t do crap when I tell her and she dings like she did it.

she’s untrustworthy

2 Likes
19

It just popped up again.

here is the log entry:

2022-02-21 12:46:15 WARNING (MainThread) [hass_nabucasa.cloud_api] Fetched https://alexa-api.nabucasa.com/access_token (400)
2022-02-21 12:46:15 ERROR (MainThread) [homeassistant.components.alexa.smart_home] Uncaught exception processing Alexa Alexa/ReportState request (-)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/alexa/smart_home.py", line 34, in async_handle_message
    await config.set_authorized(True)
  File "/usr/src/homeassistant/homeassistant/components/alexa/config.py", line 119, in set_authorized
    await self.async_enable_proactive_mode()
  File "/usr/src/homeassistant/homeassistant/components/alexa/config.py", line 73, in async_enable_proactive_mode
    await self._unsub_proactive_report
  File "/usr/src/homeassistant/homeassistant/components/alexa/state_report.py", line 33, in async_enable_proactive_mode
    await smart_home_config.async_get_access_token()
  File "/usr/src/homeassistant/homeassistant/components/cloud/alexa_config.py", line 170, in async_get_access_token
    raise alexa_errors.RequireRelink
homeassistant.components.alexa.errors.RequireRelink

it mentions both the alexa component and the cloud component in the same error.

So I assume it’s a NC thing.

Maybe?

more info:

image

clicking the first link I get here (skill enabled):

image
image997×293 28.2 KB

then clicking settings I get (shows “linked”):

image
image1013×164 11 KB

20

One last bit of info…

I unlinked the HA skill and re-linked it and the error went away…so far…

hopefully that’s all it needed.

1 Like