Closed ejbrownie closed 1 year ago
alandtse
commented
2 years ago Your logs indicate it's working. If you sanitize everything, I can't correlate the log with what you're supposedly testing. For example, you are saying your test is "test test". The logs indicate it's successfully saying "This is a test".
Please create a routine in Alexa with a TTS and then compare the sequence with what we have in the presanitized log.
ejbrownie
commented
2 years ago Nothing is actually coming through. Any ideas where I can look next to troubleshoot what is actually happening. Like I said if I do it as a notification it works but TTS doesn’t.
Sent from Yahoo Mail for iPhone
On Saturday, August 6, 2022, 16:06, Alan Tse @.***> wrote:
Your logs indicate it's working. If you sanitize everything, I can't correlate the log with what you're supposedly testing. For example, you are saying your test is "test test". The logs indicate it's successfully saying "This is a test".
Please create a routine in Alexa with a TTS and then compare the sequence with what we have in the presanitized log.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
JaredReabow
commented
2 years ago same issue here with hassos on the latest release, no output from tts
ejbrownie
commented
2 years ago I was finally able to test an alexa routine that used TTS and it works just fine direct in alexa. HA Alexa Media Player will still not sent TTS to alexa sucessfully.
alandtse
commented
2 years ago I was finally able to test an alexa routine that used TTS and it works just fine direct in alexa
Great. And when you looked at the sequence info and compared to the logs did you notice any differences?
JaredReabow
commented
2 years ago there is no issue when i run the service call for tts, however, nothing actually happens.
JaredReabow
commented
2 years ago 
nothing seems to work
carlyman
commented
2 years ago @ejbrownie -- I'm having the same issue after TTS was working for a very long time; were you able to resolve?
maxicasa
commented
2 years ago Same issue for me with the latest version of integration. For example, in services with:
service: notify.alexa_media_firetv
data:
message: "test"
data:
type: "tts"after call service (button change to green) nothing happens, no logs, no sound. Any idea?
maxicasa
commented
2 years ago Seems there was an issue with my configuration. After the completely remove of the integration and reinstall with the right region (amazon.it for me not amazon.com), the integration works correctly.
palmerch1
commented
2 years ago Hello,
After patching to 4.1.1, tts works for a few times again via developer Tools -> services and then stops working again.
`Logger: homeassistant Source: /usr/src/homeassistant/homeassistant/runner.py:96 First occurred: 6:58:51 AM (4 occurrences) Last logged: 6:59:58 AM
Error doing job: Task exception was never retrieved Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/alexapy/helpers.py", line 141, in wrapper return await func(*args, kwargs) File "/usr/local/lib/python3.10/site-packages/alexapy/alexaapi.py", line 866, in send_tts await self.send_sequence( File "/usr/local/lib/python3.10/site-packages/alexapy/helpers.py", line 141, in wrapper return await func(*args, *kwargs) File "/usr/local/lib/python3.10/site-packages/alexapy/alexaapi.py", line 489, in send_sequence await self.run_behavior(node_data, queue_delay=queue_delay) File "/usr/local/lib/python3.10/site-packages/alexapy/helpers.py", line 141, in wrapper return await func(args, kwargs) File "/usr/local/lib/python3.10/site-packages/alexapy/alexaapi.py", line 411, in run_behavior await self._post_request("/api/behaviors/preview", data=data) File "/usr/local/lib/python3.10/site-packages/alexapy/alexaapi.py", line 206, in _post_request return await self._request("post", uri, data) File "/usr/local/lib/python3.10/site-packages/backoff/_async.py", line 133, in retry ret = await target(*args, **kwargs) File "/usr/local/lib/python3.10/site-packages/alexapy/alexaapi.py", line 173, in _request raise AlexapyLoginError("Login error detected; not contacting API") alexapy.errors.AlexapyLoginError: Login error detected; not contacting API`
`Logger: alexapy.helpers Source: runner.py:119 First occurred: 6:58:51 AM (12 occurrences) Last logged: 6:59:58 AM
alexaapi.run_behavior((<alexapy.alexaapi.AlexaAPI object at 0x7fe1dee77670>, {'@type': 'com.amazon.alexa.behaviors.model.OpaquePayloadOperationNode', 'type': 'Alexa.Speak', 'operationPayload': {'deviceType': 'A3RMGO6LYLH7YN', 'deviceSerialNumber': 'G****229', 'locale': 'en-gb', 'customerId': 'A**GUD', 'textToSpeak': 'hello ellen, how are you today', 'target': {'customerId': 'A**GUD', 'devices': [{'deviceSerialNumber': 'G****229', 'deviceTypeId': 'A3RMGO6LYLH7YN'}]}, 'skillId': 'amzn1.ask.1p.saysomething'}}), {'queue_delay': 1.5}): An error occured accessing AlexaAPI: An exception of type AlexapyLoginError occurred. Arguments: ('Login error detected; not contacting API',) alexaapi.send_sequence((<alexapy.alexaapi.AlexaAPI object at 0x7fe1dee77670>, 'Alexa.Speak'), {'customer_id': 'A3M1PFH4IJ6GUD', 'textToSpeak': 'hello ellen, how are you today', 'target': {'customerId': 'A**GUD', 'devices': [{'deviceSerialNumber': 'G****229', 'deviceTypeId': 'A3RMGO6LYLH7YN'}]}, 'skillId': 'amzn1.ask.1p.saysomething', 'queue_delay': 1.5}): An error occured accessing AlexaAPI: An exception of type AlexapyLoginError occurred. Arguments: ('Login error detected; not contacting API',) alexaapi.send_tts((<alexapy.alexaapi.AlexaAPI object at 0x7fe1dee77670>, 'hello ellen, how are you today'), {'customer_id': 'A3M1PFH4IJ6GUD', 'queue_delay': 1.5}): An error occured accessing AlexaAPI: An exception of type AlexapyLoginError occurred. Arguments: ('Login error detected; not contacting API',)`
`Logger: alexapy.helpers Source: custom_components/alexa_media/init.py:721 Integration: Alexa Media Player (documentation, issues) First occurred: 6:58:46 AM (2 occurrences) Last logged: 6:58:46 AM
alexaapi.get_activities((<alexapy.alexalogin.AlexaLogin object at 0x7fe1dee53a00>, 10), {}): A login error occured: An exception of type JSONDecodeError occurred. Arguments: ('Expecting value: line 1 column 1 (char 0)',) alexaapi.get_last_device_serial((<alexapy.alexalogin.AlexaLogin object at 0x7fe1dee53a00>,), {}): An error occured accessing AlexaAPI: An exception of type AlexapyLoginError occurred. Arguments: ()`
and again these messages in the notification section:
Krispkiwi
commented
2 years ago I noticed an issue as well since upgrading in the latest versions. Not all of my TTS are coming through, some are, some aren't. Also some are now starting later than usual, for example I have a wake up that says "good morning It's 7am, the weather today is (weather)
It used to work 100% of the time but now it's skipping the hello it's 7am part and just starting with the weather today is (weather) nothing in my config has changed other than updating.
lloydbayley
commented
2 years ago Last day or so, same thing. Missing bits of announcements (same sentence - sep with a comma). Some announcements not working at all. Had to re-config some other areas but can't put my finger on this one. Edit: Woah....I finally saw some of the devices weren't looking right in HA, so restarted HA and it's all working again. Not saying that's the fix but that's what I did. Will keep an eye on it.
Revbo
commented
2 years ago Good Afternoon, I am facing the same problem with type: tts not functioning, type: announce works just fine, has there been any development on this issue? Thanks.
gericho
commented
2 years ago same here, as I put tts, the echo stop responding to voice too, What's the time? "muted answer" I have to cycle power the echo. Announce still works
INVADIA666
commented
2 years ago Hey , I'm just facing this issue . TTS stopped working all the sudden , it was fine , announce type works perfectly , but not tts . Any clue ? I've reloaded the integration several times and nothing .
Krispkiwi
commented
2 years ago Hey , I'm just facing this issue . TTS stopped working all the sudden , it was fine , announce type works perfectly , but not tts . Any clue ? I've reloaded the integration several times and nothing .
I'm getting the same, annoucements work but Notify does not,
This works
This does not
Home Assistant 2022.10.4 Alexa Media Component v4.1.2 2FA Enabled Logs Attached log.txt
INVADIA666
commented
2 years ago Hey , I'm just facing this issue . TTS stopped working all the sudden , it was fine , announce type works perfectly , but not tts . Any clue ? I've reloaded the integration several times and nothing .
I'm getting the same, annoucements work but Notify does not,
This works
This does not
Home Assistant 2022.10.4
Alexa Media Component v4.1.2
2FA Enabled
Logs Attached
Same with me , I have several automations using TTS , such as: welcome home message , back door / garage open , washing machine/ dryer done , alarm etc.., literally a lot . Now I have to switch everything to announce.
I hope home assistant makes a native speaker someday in the near future to finally replace Alexa's TTS. Or perhaps the speaker exists now ?
When did the issue started for you ? Mine just couple of hours ago .
rosnermd
commented
2 years ago Hey , I'm just facing this issue . TTS stopped working all the sudden , it was fine , announce type works perfectly , but not tts . Any clue ? I've reloaded the integration several times and nothing .
I'm getting the same, annoucements work but Notify does not, This works
Same with me , I have several automations using TTS , such as: welcome home message , back door / garage open , washing machine/ dryer done , alarm etc.., literally a lot . Now I have to switch everything to announce.
I hope home assistant makes a native speaker someday in the near future to finally replace Alexa's TTS. Or perhaps the speaker exists now ?
When did the issue started for you ? Mine just couple of hours ago .
same here. TTS stopped working in the last few hours (overnight). Announce is a workaround, but prefer TTS.
lloydbayley
commented
2 years ago I remember I had to change some of my TTS announcements around and I've just mirrored one for testing to post here and the following one works for me:
service: notify.alexa_media_kitchen_dot
data:
message: Hello, Testing!
data:
type: ttsWhere the notify object is the HA name of the device you want to send it to.
Krispkiwi
commented
2 years ago Hey , I'm just facing this issue . TTS stopped working all the sudden , it was fine , announce type works perfectly , but not tts . Any clue ? I've reloaded the integration several times and nothing .
I'm getting the same, annoucements work but Notify does not, This works
Same with me , I have several automations using TTS , such as: welcome home message , back door / garage open , washing machine/ dryer done , alarm etc.., literally a lot . Now I have to switch everything to announce.
I hope home assistant makes a native speaker someday in the near future to finally replace Alexa's TTS. Or perhaps the speaker exists now ?
When did the issue started for you ? Mine just couple of hours ago .
The issue started a couple of hours for me as well. If it's impacting many of us I wonder what changed.
INVADIA666
commented
2 years ago Hey , I'm just facing this issue . TTS stopped working all the sudden , it was fine , announce type works perfectly , but not tts . Any clue ? I've reloaded the integration several times and nothing .
I'm getting the same, annoucements work but Notify does not,
This works
This does not
Home Assistant 2022.10.4
Alexa Media Component v4.1.2
2FA Enabled
Logs Attached
Same with me , I have several automations using TTS , such as: welcome home message , back door / garage open , washing machine/ dryer done , alarm etc.., literally a lot . Now I have to switch everything to announce.
I hope home assistant makes a native speaker someday in the near future to finally replace Alexa's TTS. Or perhaps the speaker exists now ?
When did the issue started for you ? Mine just couple of hours ago .
The issue started a couple of hours for me as well. If it's impacting many of us I wonder what changed.
Let's hope someone fixes it soon , mine was working fine for over 1 year , perhaps there's an update coming up soon . I'll keep you posted if it gets fixed .
Krispkiwi
commented
2 years ago Hey , I'm just facing this issue . TTS stopped working all the sudden , it was fine , announce type works perfectly , but not tts . Any clue ? I've reloaded the integration several times and nothing .
I'm getting the same, annoucements work but Notify does not,
This works
This does not
Home Assistant 2022.10.4
Alexa Media Component v4.1.2
2FA Enabled
Logs Attached
Same with me , I have several automations using TTS , such as: welcome home message , back door / garage open , washing machine/ dryer done , alarm etc.., literally a lot . Now I have to switch everything to announce.
I hope home assistant makes a native speaker someday in the near future to finally replace Alexa's TTS. Or perhaps the speaker exists now ?
When did the issue started for you ? Mine just couple of hours ago .
The issue started a couple of hours for me as well. If it's impacting many of us I wonder what changed.
Let's hope someone fixes it soon , mine was working fine for over 1 year , perhaps there's an update coming up soon . I'll keep you posted if it gets fixed .
Since there's been no update of HA or the component, I'd guess it's something on amazons side that's done it.
lloydbayley
commented
2 years ago Well, mine's working with the code I posted so was just throwing my 2c worth in.
Krispkiwi
commented
2 years ago Well, mine's working with the code I posted so was just throwing my 2c worth in.
What region is yours set to? I wonder if they've changed something for one region and not others, not uncommon for amazon to do that with Alexa.
INVADIA666
commented
2 years ago Well, mine's working with the code I posted so was just throwing my 2c worth in.
What region is yours set to? I wonder if they've changed something for one region and not others, not uncommon for amazon to do that with Alexa.
I'm in Australia but I don't remember which region I put when I set it up , I guess it was Europe , don't remember. But if it was the Region , announcements wouldn't work neither. Would they ?
lloydbayley
commented
2 years ago Well, that's a tricky question. The country is set to Australia, however, I prefer the UK English voice so I use that. Alexa is a bit of a mixed bag when it comes to what defines your true region. For example, if I use the UK English voice, I can't buy anything from Amazon or watch our TV channels in Australia, even though my country is set to Australia, it requires I also have the voice set to Australia, which I think is wrong, however, that's how it is. There might be some strangenesses in the region stuff, yes.
Krispkiwi
commented
2 years ago Well, that's a tricky question. The country is set to Australia, however, I prefer the UK English voice so I use that. Alexa is a bit of a mixed bag when it comes to what defines your true region. For example, if I use the UK English voice, I can't buy anything from Amazon or watch our TV channels in Australia, even though my country is set to Australia, it requires I also have the voice set to Australia, which I think is wrong, however, that's how it is. There might be some strangenesses in the region stuff, yes.
So Invadia's Australian, so are you, I'm a kiwi... I'm seeing a pattern here
INVADIA666
commented
2 years ago Well, that's a tricky question. The country is set to Australia, however, I prefer the UK English voice so I use that. Alexa is a bit of a mixed bag when it comes to what defines your true region. For example, if I use the UK English voice, I can't buy anything from Amazon or watch our TV channels in Australia, even though my country is set to Australia, it requires I also have the voice set to Australia, which I think is wrong, however, that's how it is. There might be some strangenesses in the region stuff, yes.
So Invadia's Australian, so are you, I'm a kiwi... I'm seeing a pattern here
Indeed , we have to try changing the region and see if it works , but why is the announce type working then ? That's very bizarre.
Krispkiwi
commented
2 years ago Well, that's a tricky question. The country is set to Australia, however, I prefer the UK English voice so I use that. Alexa is a bit of a mixed bag when it comes to what defines your true region. For example, if I use the UK English voice, I can't buy anything from Amazon or watch our TV channels in Australia, even though my country is set to Australia, it requires I also have the voice set to Australia, which I think is wrong, however, that's how it is. There might be some strangenesses in the region stuff, yes.
So Invadia's Australian, so are you, I'm a kiwi... I'm seeing a pattern here
Indeed , we have to try changing the region and see if it works , but why is the announce type working then ? That's very bizarre.
The guy above with the node red tag is from europe so it might not be regional.
FamousL
commented
2 years ago US region here, same issue. I have not attempted to use the announce type yet, but will do so as soon as I am able. Almost woke up late since there is a report that gets sent through tts in the morning as my alarm.
SigP229dlm
commented
2 years ago US region here. Announce type works but tts does not. Worked fine yesterday.
jweston2112
commented
2 years ago No TTS ,,, even though I can set volume ... US Region ... uninstalled and reinstalled the integration to verify PW and 2FA also executiong routines seems to work
GratefulJinx77
commented
2 years ago Same issue - US Region Everything else works, including 'announce'.
ehendrix23
commented
2 years ago Just adding mine here. US Region. Worked yesterday, nothing changed, stopped working today. Changing from TTS to announce works.
peteeee
commented
2 years ago Same here...all of my type : tts automations do not speak. When I change tts to announce they speak except that I get the notification tone before speaking.
Just upgraded ...
Home Assistant 2022.10.4 Supervisor 2022.10.0 Frontend 20221010.0 - latest HACS: 1.28.2
Looks like its either the HA or HACS update that did this. Been working fine now since the intro of the add on.
Another thing I noticed is that if I send a "play news or weather" to one Amazon 5" Show...it starts to play then reboots Amazon Show. If I do the same with an Amazon Dot it plays media just fine.
stefanraduionescu
commented
2 years ago US Server. same issue to mine too. No changes made
UTMK039
commented
2 years ago Hey all, been watching this all day. For whatever reason, everything is working here again as of 12:30PM CST.
US Server.
Only realized because my washer finished the load and all the Alexa's announced it.
HeroCity99
commented
2 years ago Hey all,
Ive been having this issue all morning. I noticed it works sometimes for my kitchen Alexa but not for my other Alexas (I have 5). The other odd behaviour is, changing the type from tts to actionable notifications works %100 of the time. but never for TTS.
arthuraltino
commented
2 years ago Back again (Brazil).
INVADIA666
commented
2 years ago Hey guys , TTS back to normal in Australia .. cheers
FamousL
commented
2 years ago Seems to be working again from my setup, no changes on my end.
peteeee
commented
2 years ago TTS is working here at 1556C time (near Chicago)
arthuraltino
commented
2 years ago It's down again for me in Brazil
peteeee
commented
2 years ago Still working here near Chicago using Developer tools call service where I would change announce to tts or vice versa.
service: notify.alexa_media_ics_echodot1
data:
message: This is a test
data:
type: ttsservice: notify.alexa_media_ics_echodot1
data:
message: This is a test
data:
type: announceActually, the plain-text notifications are working here, but when I use the tag <audio src='https://xxx.mp3'/>to play audio, it doesn't works and the echo says "I’m having trouble accessing your Simon says skill right now".
Giancky79
commented
2 years ago Actually, the plain-text notifications are working here, but when I use the tag
<audio src='https://xxx.mp3'/>to play audio, it doesn't works and the echo says "I’m having trouble accessing your Simon says skill right now".
have you try this method?
https://github.com/custom-components/alexa_media_player/issues/1412#issuecomment-1015677451
arthuraltino
commented
2 years ago Actually, the plain-text notifications are working here, but when I use the tag
<audio src='https://xxx.mp3'/>to play audio, it doesn't works and the echo says "I’m having trouble accessing your Simon says skill right now".have you try this method?
Yeah, the same audio that used to work isn't working anymore. But i tried converting it again with the ffmpeg params provided by this method and it didn't work. Has anyone here got this working?
Giancky79
commented
2 years ago For me working, i use for Halloween, Christmas and other festivity’s /party time 😇
StevenGFX
commented
2 years ago I'm in the same boat as @arthuraltino. Audio tags have recently stopped working for me now in the message. All of my mp3s are generated with Polly, however I tested the audio conversion (Jovo and ffmpreg) but neither worked. Interestingly, <audio src='soundbank://soundlibrary/transportation/amzn_sfx_car_accelerate_01'/> does work. Perhaps this is a separate issue than the current issue topic.
Describe the bug After upgrading to 2022.7 TTS stopped working. Subsequent updates have not resolved the issue. I have uninstalled and reinstalled alexa media player with no difference. Setting the type to notify does work.
To Reproduce Steps to reproduce the behavior: 2 Methods
Second Method
Screenshots Method 1
Method 2
System details
const.pyor HA startup): 4.1.0pip show alexapyor HA startup): 1.26.1Logs 2022-08-04 19:38:00 INFO (MainThread) [custom_components.alexa_media] Loaded alexapy==1.26.1 2022-08-04 19:38:00 DEBUG (MainThread) [custom_components.alexa_media.helpers] [SANATIZED]: Returning uuid {'uuid': '[SANATIZED]', 'index': 0} 2022-08-04 19:38:00 DEBUG (MainThread) [alexapy.alexalogin] Creating TOTP for H****N7A 2022-08-04 19:38:00 DEBUG (MainThread) [alexapy.alexalogin] Generating OTP 076257 2022-08-04 19:38:00 DEBUG (MainThread) [alexapy.alexalogin] Login created for [SANATIZED] - amazon.com 2022-08-04 19:38:00 DEBUG (MainThread) [alexapy.alexalogin] Searching for cookies from /config/.storage/alexa_media.[SANATIZED].pickle 2022-08-04 19:38:00 DEBUG (MainThread) [alexapy.alexalogin] Trying to load cookie from file /config/.storage/alexa_media.[SANATIZED].pickle 2022-08-04 19:38:01 DEBUG (MainThread) [alexapy.alexalogin] Trying to load aiohttpCookieJar to session 2022-08-04 19:38:01 DEBUG (MainThread) [alexapy.alexalogin] Loaded 9 cookies 2022-08-04 19:38:01 DEBUG (MainThread) [alexapy.alexalogin] Searching for cookies from /config/alexa_media.[SANATIZED].pickle 2022-08-04 19:38:01 DEBUG (MainThread) [alexapy.alexalogin] Using cookies to log in 2022-08-04 19:38:01 DEBUG (MainThread) [alexapy.alexalogin] Attempting to register with amazon.com 2022-08-04 19:38:11 DEBUG (MainThread) [alexapy.alexalogin] auth response <ClientResponse(https://api.amazon.com/auth/register) [200 OK]> <CIMultiDictProxy('Server': 'Server', 'Date': 'Fri, 05 Aug 2022 00:38:10 GMT', 'Content-Type': 'application/json;charset=UTF-8', 'Content-Length': '5604', 'Connection': 'keep-alive', 'x-amz-rid': 'GJH4AWTCJYSC5Q23ZJDV', 'x-amzn-RequestId': 'd489bfe9-5b24-4f97-9103-981b6b8880fb', 'X-Amz-Date': 'Fri, 05 Aug 2022 00:38:10 GMT', 'Cache-Control': 'no-cache, no-store, must-revalidate', 'Pragma': 'no-cache', 'Vary': 'Content-Type,Accept-Encoding,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment,User-Agent', 'Permissions-Policy': 'interest-cohort=()')> with {"requested_extensions": ["device_info", "customer_info"], "cookies": {"website_cookies": [SANATIZED] 2022-08-04 19:38:11 DEBUG (MainThread) [alexapy.alexalogin] Successfully registered Erik's 2nd Alexa Media Player device with Amazon 2022-08-04 19:38:11 DEBUG (MainThread) [alexapy.alexalogin] New access token received which expires at 2022-08-04 20:38:11.610162 in 0:59:59.999675 2022-08-04 19:38:15 DEBUG (MainThread) [alexapy.alexalogin] 5 cookies successfully exchanged for refresh token for domain .amazon.com 2022-08-04 19:38:15 DEBUG (MainThread) [alexapy.alexalogin] CSRF already exists; no need to discover 2022-08-04 19:38:17 DEBUG (MainThread) [alexapy.alexalogin] GET: https://alexa.amazon.com/api/bootstrap returned 200:OK with response <CIMultiDictProxy('Content-Type': 'application/json', 'Content-Length': '145', 'Connection': 'keep-alive', 'Server': 'Server', 'Date': 'Fri, 05 Aug 2022 00:38:16 GMT', 'x-amz-rid': '66NH139QJAM8Q4CFVDFQ', 'x-amzn-RequestId': '0635ff7f-07f0-4dcc-ad54-70a8bc9b7e5d', 'Content-Encoding': 'gzip', 'Vary': 'Content-Type,Accept-Encoding,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment,User-Agent', 'Permissions-Policy': 'interest-cohort=()', 'X-Cache': 'Miss from cloudfront', 'Via': '1.1 648a9cc121d040a230a7c3a6982dca90.cloudfront.net (CloudFront)', 'X-Amz-Cf-Pop': 'DFW50-C1', 'X-Amz-Cf-Id': 'MrgSvX96VuiDTfARUcN9ZQPxOV84_r9VCC-bIIcvRWbK9Q5AJBHgdQ==')> 2022-08-04 19:38:17 DEBUG (MainThread) [alexapy.alexalogin] Logged in as [SANATIZED] to amazon.com with id: [SANATIZED] 2022-08-04 19:38:18 DEBUG (MainThread) [alexapy.alexalogin] Domain amazon.com matches reported account domain: https://www.amazon.com 2022-08-04 19:38:18 DEBUG (MainThread) [alexapy.alexalogin] Login confirmed for [SANATIZED] - amazon.com; saving cookie to /config/.storage/alexa_media.[SANATIZED].pickle 2022-08-04 19:38:18 DEBUG (MainThread) [custom_components.alexa_media] Testing login status: {'login_successful': True} 2022-08-04 19:38:18 DEBUG (MainThread) [custom_components.alexa_media] Setting up Alexa devices for [SANATIZED] 2022-08-04 19:38:18 DEBUG (MainThread) [custom_components.alexa_media] [SANATIZED]: Websocket created: <alexapy.alexawebsocket.WebsocketEchoClient object at 0x7f7258a380> 2022-08-04 19:38:18 DEBUG (MainThread) [alexapy.alexawebsocket] Connecting to wss://dp-gw-na-js.amazon.com/tcomm/ with {'Cookie': [SANATIZED] 2022-08-04 19:38:19 DEBUG (MainThread) [custom_components.alexa_media] [SANATIZED]: Websocket successfully connected 2022-08-04 19:38:19 DEBUG (MainThread) [custom_components.alexa_media] [SANATIZED]: Creating coordinator 2022-08-04 19:38:19 DEBUG (MainThread) [custom_components.alexa_media] [SANATIZED]: Refreshing coordinator 2022-08-04 19:38:19 DEBUG (MainThread) [alexapy.alexawebsocket] Starting message parsing loop. 2022-08-04 19:38:19 DEBUG (MainThread) [alexapy.alexawebsocket] Received raw WebSocket: b'0x37a1b607 0x0000009c {"protocolName":"A:F","parameters":{"AlphaProtocolHandler.maxFragmentSize":"16000","AlphaProtocolHandler.receiveWindowSize":"16"}}TUNE' 2022-08-04 19:38:19 DEBUG (MainThread) [alexapy.alexawebsocket] Encoding WebSocket Handshake MSG. 2022-08-04 19:38:19 DEBUG (MainThread) [alexapy.alexawebsocket] 0xfe88bc52 0x0000009c {"protocolName":"A:F","parameters":{"AlphaProtocolHandler.receiveWindowSize":"16","AlphaProtocolHandler.maxFragmentSize":"16000"}}TUNE 2022-08-04 19:38:19 DEBUG (MainThread) [alexapy.alexawebsocket] A:F Initialization Msg 2 sent: 307866653838626335322030783030303030303963207b2270726f746f636f6c4e616d65223a22413a46222c22706172616d6574657273223a7b22416c70686150726f746f636f6c48616e646c65722e7265636569766557696e646f7753697a65223a223136222c22416c70686150726f746f636f6c48616e646c65722e6d6178467261676d656e7453697a65223a223136303030227d7d54554e45 2022-08-04 19:38:19 DEBUG (MainThread) [alexapy.alexawebsocket] Encoding Gateway Register MSG. 2022-08-04 19:38:19 DEBUG (MainThread) [alexapy.alexawebsocket] bytearray(b'MSG\x00\x00\x03b\x10i.\xb4f\x00\x00\x00\x01\xcd5\xd5\x7f\x00\x00\x00\xe4GWM MSG 0x0000b479 0x0000003b urn:tcomm-endpoint:device:deviceType:0:deviceSerialNumber:0 0x00000041 urn:tcomm-endpoint:service:serviceName:DeeWebsiteMessagingService {"command":"REGISTER_CONNECTION"}FABE')