Daniel

I will ramp up logging and get more info. I restarted HA today around 2 pm and around 3 pm went to the bedroom and realized I had not triggered...

Logging was already at debug. Is there another component I should set to debug? ``` logger: # default: critical default: fatal # default: error # default: warning # default: warn...

Okay, what overall level should I set? FYI. I was unsuccessful in recreating the issue tonight...

It failed this morning at 8:41 am.    This error was on my console when I sat down, which is the first time I've this one: ``` This...

I reloaded the Alexa Media intergration and triggered Good Morning just now from Office Echo Dot Right at 9:09:42:   ``` 2022-07-28 09:09:41 DEBUG (MainThread) [custom_components.alexa_media] d****l@b******a: Received websocket...

After an HA reboot due to other integration updates, it is working again...

"In the meantime, I'd suggest making sure your node red service can handle the error and then retrying" - where do you see a node red service call? That aside...

HA scripts and automations... ``` sequence: - service: notify.alexa_media_last_called data: message: ```

It happened again this morning. The third iteration of Good Morning did execute...       [Good Morning Script.txt](https://github.com/custom-components/alexa_media_player/files/9292756/Good.Morning.Script.txt) HA logs... [HA Log Aug 9,2022.txt](https://github.com/custom-components/alexa_media_player/files/9292744/HA.Log.Aug.9.2022.txt)

Another failure this morning... This portion executed:  but this did not say anything:  and the rest of script did not run, despite `continue_on_error: true` being specified: