[Bug]: S100 - Alarm commands seems not working

[shupa]

Version

1.9.1

Node version

20.17.0

Operating System type

Linux

Operating system version

Debian 11

Describe the bug

Hello,

First thanks for your work allowing us to integrate eufy product in our domotic environment !
Much appreciated ;)

So I'm using the jeedom Eufy plugin based on your lib and everything is running fine except the ON alarm command which does nothing unfortunatelly.

Here is what I can collect on the log of the jeedom plugin:

ALARM ON:

[2024-12-06 08:47:28] DEBUG : eufyd command: {"command": "station.trigger_alarm", "serialNumber": "T84A1P1024330BE7", "apikey": "xxxxxxxxxxxxxxxx"}
[2024-12-06 08:47:28] DEBUG : on_message: {"type":"result","success":true,"result":{"async":true}}
[2024-12-06 08:47:28] DEBUG : parseResultMessage: {'async': True}
[2024-12-06 08:47:28] DEBUG : on_message: {"type":"event","event":{"source":"station","event":"command result","serialNumber":"T84A1P1024330BE7","command":"trigger_alarm_sound","returnCode":0,"returnCodeName":"ERROR_PPCS_SUCCESSFUL","customData":{"command":{"name":"stationTriggerAlarmSound"}}}}

The OFF command is working (if I trigger tha alarm through the Eufy app directly thus):
[2024-12-06 08:58:45] DEBUG : eufyd command: {"command": "station.reset_alarm", "serialNumber": "T84A1P1024330BE7", "apikey": "xxxxxxxxxxxxxxxx"}
[2024-12-06 08:58:45] DEBUG : on_message: {"type":"result","success":true,"result":{"async":true}}
[2024-12-06 08:58:45] DEBUG : parseResultMessage: {'async': True}
[2024-12-06 08:58:45] DEBUG : on_message: {"type":"event","event":{"source":"station","event":"command result","serialNumber":"T84A1P1024330BE7","command":"trigger_alarm_sound","returnCode":0,"returnCodeName":"ERROR_PPCS_SUCCESSFUL","customData":{"command":{"name":"stationTriggerAlarmSound","value":0}}}}

Any clue or help is more than welcoming.

Many thanks in advance

Nico

To reproduce

1. Click on alarm ON action of the equipment

Screenshots & Logfiles

No response

Additional context

No response

[lxrootard]

@bropat this is the same issue as #191 on T8113 and T8010 that I opened last year.
see my Postman logs in the issue
thanks