Muted
skillix opened this issue · comments
Hello,
Sorry for my bad English.
The Mute command does not appear to exist.
While the value is well up in the PUSH_VOLUME_CHANGE
Is it possible to add it?
The goal is to take into account the mutated for an announcement or to "make speak" to restore it after the announcement.
There is no "Mute" command ... basically set volume to 0. A muted status is in the "Player" section where also volume is
No, for the streaming player (Freebox Delta Devialet), FireStick and Fire Cube, Mute exists and is used
Ok, then wehere exactly you miss it? which devices? maybe show screenshots of states
sorry I am not an expert, I open the info muted in the "AllDeviceVolume"
alertVolume : null
deviceType : A1X92YQU8MWAPD
dsn : c02eacdbcba640f29ae6e5589e2a7b1c
error : null
speakerMuted : true
speakerVolume : 49
if the command is available in the player part that may be suitable for me, but I did not find it
My alexa is included in my TV decoder
Type A1X92YQU8MWAPD
Familly UNKNOWN
In concrete situhation, in the scenarios I make Alexa speak of my decoder (with integrated speaker) the announcement is made at the volume adjust plus resets the volume to its previous volume, but if the TV was Muted, then it reacted as if the TV was not mutated before the announcement
No, sorry I was thinking wrong ... we are onm API level only here ... I did not saw that from your request.
But honestly I still do not get you ... Do you say that you send out "mute" but the device it not reacting to it correctly? Or what?
then, I mute with the vocal "alexa cut the sound", the sound is deactivated but the volume Y is memorized / active (see image)
but after I make the speaker speak with a volume X, the mute is deactivated, the announcement is made at volume X, then after the announcement the lastsound Y is restored, but without the mute.
But in our jeedom plugin, to be able to manage and restore the volume, we need to have the mute command to be able to restore it.
The API is using the API from the Alexa Mobile App. Do you have any way to "mute" a device there? I do not know of any really that would have the same effect. If you find a routine action or other "Button" in teh alexa app that brings that result then tell me and I can tyr to find out what command is sent in the background
You could try to use the new "textCommand" feature and send "cut the voice" to the device as you do with voice.
[2/17/2021, 9:49:44 AM][INFO] : {API} ╔═══════[Lancement /textCommand avec paramètres -> device: c02eacdbcba640f29ae6e5589e2a7b1c & text: coupe le son══════════════════════════════════ [2/17/2021, 9:49:44 AM][DEBUG] : {Remote} ║ Sending Request with {"host":"alexa.amazon.fr","path":"/api/behaviors/preview","method":"POST","timeout":10000,"headers":{}} and data={"behaviorId":"PREVIEW","sequenceJson":"{\"@type\":\"com.amazon.alexa.behaviors.model.Sequence\",\"startNode\":{\"@type\":\"com.amazon.alexa.behaviors.model.OpaquePayloadOperationNode\",\"operationPayload\":{\"deviceType\":\"A1X92YQU8MWAPD\",\"deviceSerialNumber\":\"c02eacdbcba640f29ae6e5589e2a7b1c\",\"locale\":\"fr-FR\",\"customerId\":\"A3T9PVE5NO04DQ\",\"text\":\"coupe le son\"},\"type\":\"Alexa.TextCommand\",\"skillId\":\"amzn1.ask.1p.tellalexa\"}}","status":"ENABLED"} [2/17/2021, 9:49:44 AM][DEBUG] : {Remote} ║ Response: No body [2/17/2021, 9:49:45 AM][DEBUG] : {MQTT} ╠═══> Command --{PUSH_ACTIVITY}-- : détail désactivé [2/17/2021, 9:49:45 AM][DEBUG] : {MQTT} ╠═══> Command --{PUSH_ACTIVITY}-- : détail désactivé [2/17/2021, 9:49:45 AM][DEBUG] : {MQTT} ╠═══> Command --{PUSH_VOLUME_CHANGE}-- : détail désactivé [2/17/2021, 9:49:45 AM][DEBUG] : {Remote} ║ URL envoyée: http://192.168.0.32/plugins/alexaapi/core/php/jeeAlexaapi.php?apikey=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX&nom=ws-volume-change [2/17/2021, 9:49:45 AM][DEBUG] : {Remote} ║ DATA envoyé:{"destinationUserId":"A3T9PVE5NO04DQ","deviceSerialNumber":"c02eacdbcba640f29ae6e5589e2a7b1c","deviceType":"A1X92YQU8MWAPD","isMuted":true,"volume":23}
the fonction exists in the routine:
device settings / stop audio / select device (in french : parametre de l'appareil / arret de l'audio)
Then it shopuld be he "deviceStop" command (use that for createSequenceNode).
the "do not disturb" should be controllable already with setDoNotDisturb
ok thx, i will try with my developer
please report back with your results ... else I need to check on commands from the app and such
no problem I'll get back to you
fail ! it stops alexa speaking or when a music is playing
{
"directive": {
"header": {
"namespace": "Alexa.Speaker",
"name": "SetMute",
"messageId": "<message id>",
"correlationToken": "<an opaque correlation token>",
"payloadVersion": "3"
},
"endpoint": {
"scope": {
"type": "BearerToken",
"token": "<an OAuth2 bearer token>"
},
"endpointId": "<endpoint id>",
"cookie": {}
},
"payload": {
"mute": true
}
}
}
https://developer.amazon.com/en-US/docs/alexa/device-apis/alexa-speaker.html
it's not that ?
it's not that ?
this is is skill stuff, as said above the library uses only the "same api then the mobile app" ... so effectively: we can only do it when mobile app can do it. And have in mind: here nothing is "officially provided by amazon" ...
fail ! it stops alexa speaking or when a music is playing
but I thought you tested it that the result is that it sents mute but leaves volume intact?!
no I did not test it with a routine, I had the option "stop audio".
I will search a little longer, otherwise we will simulate with a text command:
if isMuted = true ==> textCommand "mute the sound"
thanks anyway
Ok, if you find a routine action or any "button in the mobile app" that achieves what you need tell me what and we can integrate it
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions.
Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.
This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps. Thank you for your contributions.
Dieses Problem wurde aufgrund von Inaktivität automatisch geschlossen. Bitte öffnet ein neues Issue, falls dies noch relevant ist und stellt sicher das alle relevanten Details, Logs und Reproduktionsschritte enthalten sind. Vielen Dank für Eure Unterstützung.