CustomVolume setting not considered for alarms

[robson80]

Describe the bug
The setting "customVolume" to control the volume of alarms (introduced with adapter version 3.15 seems not to work.
I have set up a timer in the Alexa app and tried several times to control the volume via setting "customVolume". However, the setting is not being reflected on the alarm volume.

To Reproduce
Steps to reproduce the behavior:

1. Create alarm in Alexa app
2. Make sure different volume settings have been set in app and in adapter setting "customVolume"
3. Wait for the alarm

Expected behavior
The alarm should ring with the volume that has been set in the "customVolume" field. If no volume setting has been made via the adapter ("null") the default volume that has been set in the alexa app should be considered.

Screenshots & Logfiles
Issue has been reported and verified here:
https://forum.iobroker.net/topic/56021/alexa2-adapter-3-13-3-14-3-15-3-16-3-17-beta/385?_=1700651557951

Versions:

• Adapter version: 3.26.1
• JS-Controller version: 5.0.16
• Node version: v18.17.1
• Operating system: RPi OS 32 Bit (Debian Bookworm)

[Apollon77]

Please run the adapter in debug logging and post the debug log from settig the alarm and also then the time before and after it gets triggered

[robson80]

After I have set the adapter to debug a LOT of information has been logged and I think most of it is not needed. But unsure what is needed and what not.

What did I do:

• I have set the debugging mode at 16:21.
• I have scheduled the alarm for 16:25 in the Alexa app at 16:21 (directly after setting the debug mode).
• Waited about 2 minutes in iobroker for the alarm to show up in the objects
• Changed the "customVolume" setting from to 10 at about 16:23 - 16:24
• Alarm started at 16:25
• Debugging setting deactivated at 16:25 - 16:26

Debug logging 1/3

[robson80]

Debug logging 2/3

[robson80]

Debug logging 3/3

[Apollon77]

And log shows:

2023-11-23 16:24:06.027 - debug: alexa2.0 (15671) Alexa-Push-Connection Device Volume change for G070VM0583941XB9 -> 11/false
manually set?

2023-11-23 16:24:58.015 - debug: alexa2.0 (15671) Alexa-Remote: Sending Request with {"host":"eu-api-alexa.amazon.de","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":"A2U21SRK4QGSE1","deviceSerialNumber":"G091EU0811630D6M","locale":"de-DE","customerId":"ADVKT7G5RS7QW","value":10},"type":"Alexa.DeviceControls.Volume","skillId":"amzn1.ask.1p.alexadevicecontrols"}}","status":"ENABLED"}

Also 2s before alarm ... we set volume to 10 and it is also acknowledged:

2023-11-23 16:24:58.957 - debug: alexa2.0 (15671) Alexa-Push-Connection Device Volume change for G091EU0811630D6M -> 10/false

Then alarm got triggered ...

2023-11-23 16:25:00.107 - debug: alexa2.0 (15671) State changed alexa2.0.Echo-Devices.G091EU0811630D6M.Alarm.triggered: {"val":"1b3f329e-d187-426f-8318-d4e014733215","ack":true,"ts":1700753100102,"q":0,"from":"system.adapter.alexa2.0","user":"system.user.admin","lc":1700753100102}

And short afterwards volume was also changed

2023-11-23 16:25:13.168 - debug: alexa2.0 (15671) Alexa-Push-Connection Device Volume change for G091EU0811630D6M -> 14/false

So ... ok ... whats exactly is not working?

[robson80]

Hi,
I will update the ticket and reply to your question during the next days. I first want to start some more tests regarding the volume.

Thanks so far.

[robson80]

Could not be replicated anymore.