-
Notifications
You must be signed in to change notification settings - Fork 302
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
TTS Stopped Working #1683
Comments
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. |
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: ***@***.***>
|
This comment was marked as duplicate.
This comment was marked as duplicate.
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. |
Great. And when you looked at the sequence info and compared to the logs did you notice any differences? |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
@ejbrownie -- I'm having the same issue after TTS was working for a very long time; were you able to resolve? |
This comment was marked as resolved.
This comment was marked as resolved.
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. |
This comment was marked as off-topic.
This comment was marked as off-topic.
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. |
Last day or so, same thing. Missing bits of announcements (same sentence - sep with a comma). |
This comment was marked as duplicate.
This comment was marked as duplicate.
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 |
This comment was marked as duplicate.
This comment was marked as duplicate.
I'm getting the same, annoucements work but Notify does not, Home Assistant 2022.10.4 |
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 ? |
same here. TTS stopped working in the last few hours (overnight). Announce is a workaround, but prefer TTS. |
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:
Where the notify object is the HA name of the device you want to send it to. |
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. |
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. |
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. |
Just adding mine here. US Region. Worked yesterday, nothing changed, stopped working today. Changing from TTS to announce works. |
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 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. |
US Server. same issue to mine too. |
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. |
Hey all, Ive been having this issue all morning. |
Back again (Brazil). |
Hey guys , TTS back to normal in Australia .. cheers |
Seems to be working again from my setup, no changes on my end. |
TTS is working here at 1556C time (near Chicago) |
It's down again for me in Brazil |
Still working here near Chicago using Developer tools call service where I would change announce to tts or vice versa.
|
Actually, the plain-text notifications are working here, but when I use the tag |
have you try this method? |
Yeah, the same audio that used to work isn't working anymore. |
For me working, i use for Halloween, Christmas and other festivity’s /party time 😇 |
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, |
Maybe the problem is duckdns addon? I’m pass trough a reverse proxy 🤔 |
Ah, I'm also running reverse proxy on my Synology NAS |
Ok, this is from my repo ,
can you try if working? |
It's working, but if i try to use the same audio file behind my nginx proxy with self-signed certs and duckdns domain it doesn't work. |
Can anybody point me in the right direction? Im trying to do the same as @Giancky79 but i didnt find the way. |
I eneded up here as well... not sure when it started but after having succesfully using alexa to play my dogbark player for a while it now suddenly does not work anymore. Alexa tells me: "sorry i am having trouble accessing your simon says now skill right now". All seems fine, I can play the mp3 file from the internet at where it is and was hosted, ssl cert is ok, etc. But still alexa is not able to play it (anymore) for me. Is there something I can check or do or see? I recently changed my nginx location from my synology nas to nginx manager. all works fine untill I noticed alexa did not... |
Same problem here! |
Well, my problem has been resolved without doing anything... Strange! |
Are you using nginx proxy manager? Do you have your own domain or are you
using something like duckdns? I can’t make it work with HA behind nginx
proxy manager and duckdns.
Em ter., 20 de dez. de 2022 às 09:54, yan14 ***@***.***>
escreveu:
… Same problem here! TTS and announcements are not working. Spotify and
other apps are working!
Well, my problem has been resolved without doing anything... Strange!
—
Reply to this email directly, view it on GitHub
<#1683 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIYEAAFUTIBJW43I6WIIZFDWOGT7ZANCNFSM55V5M32A>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I've been using TTS/Announcements with this component since 2019, without any issues until recently. I spent the last few days diagnosing the issue and I'm including what I found in my personal setup. I mostly use announcements since I include Sample log that doesn't produce announcement, initiated from HA Services tab in Dev Tools
In addition to discovering the example automation: action:
- service: notify.alexa_media
data:
message: !include morning_workday_wakeup_alexa_whisper.j2
target: media_player.nightstand
data:
type: announce
method: speak example message include: <speak>
<amazon:effect name="whispered">
Good morning. It's almost time to wake up.
</amazon:effect>
<break time="4s"/>
<p>It's {{ now().strftime('%I:%M %p') }}</p>
<p>{{ [
'Get your butt out of bed!',
'<say-as interpret-as="interjection">cock a doodle doo</say-as>'
] | random }}</p>
</speak> Having to remove the Hope this helps someone else 👍 |
The issue has received no activity for 60 days and will be closed in a week. |
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.py
or HA startup): 4.1.0pip show alexapy
or 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')
2022-08-04 19:38:22 DEBUG (MainThread) [custom_components.alexa_media] Office Echo: Locale en-us timezone America/Chicago
2022-08-04 19:38:22 DEBUG (MainThread) [custom_components.alexa_media] Office Echo: DND False
2022-08-04 19:38:22 DEBUG (MainThread) [custom_components.alexa_media] Loading config entry for media_player
2022-08-04 19:38:22 DEBUG (MainThread) [custom_components.alexa_media] Finished fetching alexa_media data in 3.004 seconds (success: True)
2022-08-04 19:39:46 DEBUG (MainThread) [custom_components.alexa_media.notify] Message: This is a test, kwargs: {'target': ['[SANATIZED]'], 'data': None}
2022-08-04 19:39:46 DEBUG (MainThread) [custom_components.alexa_media.notify] Target type: <class 'list'>
2022-08-04 19:39:46 DEBUG (MainThread) [custom_components.alexa_media.notify] Processing: [SANATIZED]
2022-08-04 19:39:46 DEBUG (MainThread) [custom_components.alexa_media.notify] Processed Target by string: ['[SANATIZED]']
2022-08-04 19:39:57 DEBUG (MainThread) [custom_components.alexa_media.notify] Message: This is a test, kwargs: {'target': ['[SANATIZED]'], 'data': None}
2022-08-04 19:39:57 DEBUG (MainThread) [custom_components.alexa_media.notify] Target type: <class 'list'>
2022-08-04 19:39:57 DEBUG (MainThread) [custom_components.alexa_media.notify] Processing: [SANATIZED]
2022-08-04 19:39:57 DEBUG (MainThread) [custom_components.alexa_media.notify] Processed Target by string: ['[SANATIZED]']
2022-08-04 19:40:03 DEBUG (MainThread) [custom_components.alexa_media.notify] Message: This is a test, kwargs: {'target': ['[SANATIZED]'], 'data': {'type': 'tts'}}
2022-08-04 19:40:03 DEBUG (MainThread) [custom_components.alexa_media.notify] Target type: <class 'list'>
2022-08-04 19:40:03 DEBUG (MainThread) [custom_components.alexa_media.notify] Processing: [SANATIZED]
2022-08-04 19:40:03 DEBUG (MainThread) [custom_components.alexa_media.notify] Processed Target by string: ['[SANATIZED]']
2022-08-04 19:40:03 DEBUG (MainThread) [custom_components.alexa_media.notify] TTS by : This is a test
2022-08-04 19:40:05 DEBUG (MainThread) [alexapy.alexaapi] [SANATIZED]: Creating sequence for 1 items
2022-08-04 19:40:05 DEBUG (MainThread) [alexapy.alexaapi] [SANATIZED]: Running behavior with data: {"behaviorId": "PREVIEW", "sequenceJson": "{"@type": "com.amazon.alexa.behaviors.model.Sequence", "startNode": {"@type": "com.amazon.alexa.behaviors.model.SerialNode", "nodesToExecute": [{"@type": "com.amazon.alexa.behaviors.model.OpaquePayloadOperationNode", "type": "Alexa.Speak", "operationPayload": {"deviceType": "A32DOYMUN6DTXA", "deviceSerialNumber": "[SANATIZED]", "locale": "en-us", "customerId": "[SANATIZED]", "textToSpeak": "This is a test", "target": {"customerId": "[SANATIZED]", "devices": [{"deviceSerialNumber": "[SANATIZED]", "deviceTypeId": "A32DOYMUN6DTXA"}]}, "skillId": "amzn1.ask.1p.saysomething"}}]}}", "status": "ENABLED"}
2022-08-04 19:40:05 DEBUG (MainThread) [alexapy.alexaapi] [SANATIZED]: POST: https://alexa.amazon.com/api/behaviors/preview returned 200:OK:application/octet-stream
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: