Announcement stopped working on third party devices: Sonos Speakers, ecobee4, Bose #285
Labels
Comments
|
Having the same issue. As suggested in a comment on the seemingly related albeit closed, issue 200, moving from |
|
My issue with accessing the "Communications" setting is fixed now after i spoke to Amazon support. My account where reset and moved from UK to US. We removed all devices and I setup everything.
In you reply on the link issue you mentioned the upgrade from 1.3.* to 1.4.1. On Sunday when Annoncement stopped working I where on version 1.2.2 or 1.2.3, and therefore i decieded to upgrade to 1.4.1. |
|
Does announce work on any non Sonos speakers? We haven't touched the announce code for a while. |
This comment has been minimized.
This comment has been minimized.
|
I have a Sonos and an Echo Dot. Announce worked on both prior to upgrading to 1.4.1. Works on neither afterwards. Wonder if it could be related to migration to HACS rather than the upgrade to 1.4.1? I’ll be away for a couple of days. Will provide logs once I’ve returned! |
Running in docker where do I get the logs?
Good to hear its not only a Sonos problem. Upgrading from 1.2.* to 1.4.1 I changed to use HACS. |
|
Back at home, enabled debug, and was running the exact same service calls as I did prior (indeed, it was cached and ready to go), but "unfortunately" it ran as it should. Ie. no errors. So no logs to send, I'm afraid. Could it have been some caching error or the like, perhaps related to migrating to HACS? Either fixed by some amount of time having gone by, or X amount of reboots... |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Announce:TTS:EDIT: Proper quoting |
|
@mikkelke The next thing may be to craft an announcement by itself without the subsequent volume change. This is so we can make sure it's not because the Sonos is dropping a command because it's getting hit by more than one. If that doesn't work, there may be something special about the way the Sonos packet has to be configured. I'd need you to create a routine with announce targeting your Sonos in the app, and then pull the sequence data. Basically you'd follow the instructions here, and then stop at step 7 and provide the entire operationPayload portion to compare to what we're sending. |
|
@alandtse Thanks for your help. I made this rutine and when I play it from the app or say "Test this" northing happens, I think I must contact Amazon again (Annonce works when i go into "Communicate" and "Annonce": {
"@type": "com.amazon.alexa.behaviors.model.Automation",
"automationId": "amzn1.alexa.automation.55ad9f56-555b-4b2b-83ae-c28425f58b3a",
"name": null,
"triggers": [
{
"payload": {
"customerId": "A1VLQF1TDI6MEL",
"utterance": "test this",
"locale": "en-DK",
"marketplaceId": "ATVPDKIKX0DER"
},
"id": "amzn1.alexa.trigger.791afa5c-6778-4c2b-8446-597fc0d92c98",
"type": "CustomUtterance",
"timeLapse": null
}
],
"sequence": {
"@type": "com.amazon.alexa.behaviors.model.Sequence",
"sequenceId": "amzn1.alexa.sequence.a3e04491-2cf5-43d0-844a-70d65f0d04c5",
"startNode": {
"@type": "com.amazon.alexa.behaviors.model.OpaquePayloadOperationNode",
"type": "AlexaAnnouncement",
"skillId": "amzn1.ask.1p.messaging",
"operationPayload": {
"expireAfter": "PT5S",
"content": [
{
"locale": "en-DK",
"display": {
"title": "Alexa Routines",
"body": "Someone is at the door"
},
"speak": {
"type": "text",
"value": "Someone is at the door"
}
}
],
"customerId": "A1VLQF1TDI6MEL",
"target": {
"customerId": "A1VLQF1TDI6MEL"
}
},
"name": null
}
},
"owner": null,
"clientAlias": null,
"condition": null,
"status": "ENABLED",
"creationTimeEpochMillis": 1565936035434,
"lastUpdatedTimeEpochMillis": 1565936117095
}
] |
|
Ok I agree, I think if you can't get the Alexa App to get it to work, then there's something happening in your setup. I noticed that the locale is being populated as en-DK, which I believe is English in Denmark? This is the first time I saw that locale and I don't know if Announce is supposed to work for there. Amazon support may know better. |
|
The issue started before i changed locale. |
|
I will also continue to troubleshoot this, as I noticed this morning that the Echo dot indeed announced as it should in my morning routine, having switched back from ‘type: tts’ to ‘type: announce’, but the Sonos did not. (Prior to 1.4.1 and HACS, both announced. With ‘type: tts’, both tts:ed.) So +1 that it might be something Sonos-specific. I’ll get back with logs and whatnot within a day, I hope. |
|
Announcement through the Alexa app works here; announces on Sonos as well as the Echo dot. |
|
Testing with the following data, for service Debug lines for Sonos, announce (does not work): Debug line for Sonos, service data Debug line for Echo dot ( |
|
Prior to running the above, I 1) removed alexa_media through HACS. 2) Turned off HA. 3) Removed the pickle file. 4) Checked there no longer was a directory |
|
If any of you are a 0.96 version or HA and try a 1.3.1 version of the component for comparison that would be helpful. I'm not seeing anything specifically wrong from the output. I'm working on a revamp major release that may impact the way we interact so may need to table debugging this until we migrate since the way we interact here will be deprecated. |
|
Don't know if it matters, but I tried pulling the nodestoExecute data, for a routine I had created in the Alexa app for the purpose and noticed
|
This comment has been minimized.
This comment has been minimized.
|
Upgraded, restarted; it is as before. |
|
Debug output of (failed) Debug output of (successful) |
|
As mentioned previously, I can not create a routine, in the Alexa app, which would trigger announcement on the Sonos. (Only my Dot is listed as a valid device for the function.) I don't know if I was able to, earlier; never tried it. What I can do, from the Alexa app, is to use the "Communicate" tab, and send an announcement that way to all devices. (Can't seem to specify only one device.) Doesn't work quite the same way as the announce available as routine though. Instead of just "Bling Test", I get "Bling From NAME, Test". That gets broadcasted to both the Sonos and the Echo Dot. |
|
@krissen Thanks for the help debugging, I really appreciate the log generation even if I'm not directly responding. The reason I try to get the routine info is that at least can show us acceptable syntax. Again, the syntax looks fine, so I'm a bit stumped. The fact it's not an option in the routine makes me think perhaps Amazon stopped supporting it? Some additional tests I can think of:
|
|
Whole house audio group. Normal Alexa-groups doesn't seem to support more than one speaker. Tried to create a multi-room music group, but was told no compatible speakers were found. So far, I haven't been able to find a way to create a group within Alexa, for the two speakers. 1.3.1 Tried that some days ago, but seemed the Testing via dev_service. (Though I've tested via automations as well.) Let me know if you've got something else to try or troubleshoot. Testing custom |
alandtse
changed the title
|
I contected Amazon severeal times and thay could not tell me why it stopped working. They say the escalated my issue to techincal team but I never got a responds. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
same here, both on Echo Dot and Echo Spot announcements stopped working, TTS does work. (amazon.it) |
This comment has been minimized.
This comment has been minimized.
|
Just updating to say, that matters are still functioning, or not, in the same manner in v2.3.2 as before. That is, TTS works; announce does not, on a Sonos. |
|
@krissen thanks for the update. What may be helpful is to see if the routine mechanism ever starts working. As soon as it does, then I think we can edit the command to follow that. |
|
Is there any advantage of using Announce rather than TTS since TTS works? |
Minor advantage: it adds a chime prior to the message. Sounds trivial, but it's nice. 🤷♂️ Could be achieved by playing a custom sound prior to message, too. |
|
With announcement there are also other things possible like change voice, intonation, .... |
|
I know over at Smartthings I used to use an application that's called EchoSpeaks and he could never integrate the Sonos as Amazon doesn't treat these like true Alexa devices apparently. |
|
Sames issues here, must be a Sonos thing... Like SamB-GB set, they are always a little bit special in Alexa's eyes. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I have a bose and I have the same issue the announce feature seems don't work |
alandtse
changed the title
|
Unlike others,
|
|
Stale issue message |
|
I'm having the same issue on my bose smart speaker, tts works but announce does not |
|
Same here Yamaha YAS-109, tts works but announce does not. Alexa app announce works however |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Announce doesn't work, while TTS does. Until Sunday announce worked perfect on my Alexa enabled Sonos speakers (Sonos One and Beam).
If i use the Aleaxa app to do the annoncement it works perfect. In the FAQ is mentioned to check that "Communications" is enabled and it is on all my speakers. But i noties that if I click on "Communications" the Alexa app get stuck loading the page.
It is one of my favorite features and I use it as my doorbell annoncement.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Play announced message on every speaker taget.
System details
const.pyor HA startup): 1.4.1 (installed from HACS)pip show alexapyor HA startup): 0.7.1The text was updated successfully, but these errors were encountered: