Isage
Novembre 8, 2023, 10:45
102
On
{"_msgid":"d653cf6e554326cb","payload":{"warning":{"duration":10,"mode":"emergency","strobe":false}},"topic":"zigbee2mqtt/sirene_1/set_message"}
OFF
{"_msgid":"1d78fbec994faccf","payload":{"warning":{"duration":10,"mode":"stop","strobe":false}},"topic":"zigbee2mqtt/sirene_1/set_message"}
Isage
Novembre 8, 2023, 10:51
103
Pour ces nouvelles vaeurs, c’est le debug que j’ai envoyé il y a 6 mn
a savoir :
{"_msgid":"d653cf6e554326cb","payload":{"warning":{"duration":10,"mode":"emergency","strobe":false}},"topic":"zigbee2mqtt/sirene_1/set_message"}
OFF
{"_msgid":"1d78fbec994faccf","payload":{"warning":{"duration":10,"mode":"stop","strobe":false}},"topic":"zigbee2mqtt/sirene_1/set_message"}
@Isage , @cce66
Il ne faut pas mettre set_message à la fin mais uniquement set
Isage
Novembre 8, 2023, 11:18
107
Il ne faut pas mettre set_message à la fin mais uniquement set => ok
Nouveaux debug
ON
{"_msgid":"5a1017a2e5c032e6","payload":{"warning":{"duration":2,"mode":"emergency","strobe":false}},"topic":"zigbee2mqtt/sirene_1/set"}
OFF
{"_msgid":"db8d2f049b98ea65","payload":{"warning":{"duration":2,"mode":"stop","strobe":false}},"topic":"zigbee2mqtt/sirene_1/set"}
cce66
Novembre 8, 2023, 11:22
108
je me suis basé sur cet article, dedans il met le topic utilisé mais…marches pas !
je me suis dit on a tout tenté y compris toutes les soluces
opened 12:00PM - 10 Oct 22 UTC
closed 12:02AM - 14 Oct 23 UTC
problem
stale
### What happened?
The siren device from Heiman (HS2WD-E) doesn't work properly… . There was already exchanges on this topic but it seems that the problem is not solved.
The problem is that, when sending MQTT commands like
'{"warning":{"duration":2,"level":"low","mode":"burglar","strobe":true,"strobe_duty_cycle":1,"strobe_level":"low"}}', all parameters are ignored except:
- 'duration"
- 'mode' with only 2 possibilities: 'stop' => siren Off and all other parameters ( burglar, fire ...) lead to siren On without recognition of the type and level.
All relative to strobe is not taken into account.
There is no information coming back via MQTT giving the state of the siren.
The same behavior is observed when using the Front-end and this device doesn't appear on the dashboard.
Is there a way to solve this issue ?
### What did you expect to happen?
I expect a normal behavior with all parameters taken into account when sending commands.
### How to reproduce it (minimal and precise)
It is the observed behavior when just adding this device in the network.
### Zigbee2MQTT version
1.28.0
### Adapter firmware version
20220219
### Adapter
SONOFF Zigbee 3.0 USB Dongle Plus
### Debug log
debug 2022-10-10 12:42:15Succesfully pinged 'Si_Heiman_1' (attempt 1/2)
debug 2022-10-10 12:42:31Saving state to file /opt/zigbee2mqtt/data/state.json
debug 2022-10-10 12:44:58Received MQTT message on 'zigbee2mqtt_1/Si_Heiman_1/set' with data '{"warning":{"duration":2,"level":"low","mode":"burglar","strobe":true,"strobe_duty_cycle":1,"strobe_level":"low"}}'
debug 2022-10-10 12:44:58Publishing 'set' 'warning' to 'Si_Heiman_1'
debug 2022-10-10 12:47:31Saving state to file /opt/zigbee2mqtt/data/state.json
debug 2022-10-10 12:50:47Received Zigbee message from 'Le_Tuya_1', type 'readResponse', cluster 'genBasic', data '{"zclVersion":3}' from endpoint 1 with groupID 0
debug 2022-10-10 12:50:47Succesfully pinged 'Le_Tuya_1' (attempt 1/2)
debug 2022-10-10 12:52:16Received Zigbee message from 'Si_Heiman_1', type 'readResponse', cluster 'genBasic', data '{"zclVersion":3}' from endpoint 1 with groupID 0
debug 2022-10-10 12:52:16Succesfully pinged 'Si_Heiman_1' (attempt 1/2)
debug 2022-10-10 12:52:31Received Zigbee message from 'Si_Heiman_1', type 'attributeReport', cluster 'genPowerCfg', data '{"batteryPercentageRemaining":200}' from endpoint 1 with groupID 0
info 2022-10-10 12:52:31MQTT publish: topic 'zigbee2mqtt_1/Si_Heiman_1', payload '{"battery":100,"linkquality":43}'
debug 2022-10-10 12:52:31Received Zigbee message from 'Si_Heiman_1', type 'commandStatusChangeNotification', cluster 'ssIasZone', data '{"extendedstatus":0,"zonestatus":16}' from endpoint 1 with groupID 0
debug 2022-10-10 12:52:31No converter available for 'HS2WD-E' with cluster 'ssIasZone' and type 'commandStatusChangeNotification' and data '{"extendedstatus":0,"zonestatus":16}'
debug 2022-10-10 12:52:31Saving state to file /opt/zigbee2mqtt/data/state.json
debug 2022-10-10 12:57:31Saving state to file /opt/zigbee2mqtt/data/state.json
Mais rien à faire, c’est glauque …
Isage
Novembre 8, 2023, 11:28
109
A suivre donc…
Peux-tu me montrer ce que tu as mis dans ce noeud?
A mon avis le problème vient du topic qui est SET dans le noeud CHANGE, mais qui doit être défini dans le noeud MQTT OUT.
Ok la config a l’air ok surtout au niveau du topic.
Tu es sur de ton mot de passe?
Jai le même appareils et je nai malheureusement jamais reussis a la faire sonner alors que je manipule bien z2m nodered etc.
Jai tenté de push directement via mqtt mais aucun son ne sortait
opened 12:00PM - 10 Oct 22 UTC
closed 12:02AM - 14 Oct 23 UTC
problem
stale
### What happened?
The siren device from Heiman (HS2WD-E) doesn't work properly… . There was already exchanges on this topic but it seems that the problem is not solved.
The problem is that, when sending MQTT commands like
'{"warning":{"duration":2,"level":"low","mode":"burglar","strobe":true,"strobe_duty_cycle":1,"strobe_level":"low"}}', all parameters are ignored except:
- 'duration"
- 'mode' with only 2 possibilities: 'stop' => siren Off and all other parameters ( burglar, fire ...) lead to siren On without recognition of the type and level.
All relative to strobe is not taken into account.
There is no information coming back via MQTT giving the state of the siren.
The same behavior is observed when using the Front-end and this device doesn't appear on the dashboard.
Is there a way to solve this issue ?
### What did you expect to happen?
I expect a normal behavior with all parameters taken into account when sending commands.
### How to reproduce it (minimal and precise)
It is the observed behavior when just adding this device in the network.
### Zigbee2MQTT version
1.28.0
### Adapter firmware version
20220219
### Adapter
SONOFF Zigbee 3.0 USB Dongle Plus
### Debug log
debug 2022-10-10 12:42:15Succesfully pinged 'Si_Heiman_1' (attempt 1/2)
debug 2022-10-10 12:42:31Saving state to file /opt/zigbee2mqtt/data/state.json
debug 2022-10-10 12:44:58Received MQTT message on 'zigbee2mqtt_1/Si_Heiman_1/set' with data '{"warning":{"duration":2,"level":"low","mode":"burglar","strobe":true,"strobe_duty_cycle":1,"strobe_level":"low"}}'
debug 2022-10-10 12:44:58Publishing 'set' 'warning' to 'Si_Heiman_1'
debug 2022-10-10 12:47:31Saving state to file /opt/zigbee2mqtt/data/state.json
debug 2022-10-10 12:50:47Received Zigbee message from 'Le_Tuya_1', type 'readResponse', cluster 'genBasic', data '{"zclVersion":3}' from endpoint 1 with groupID 0
debug 2022-10-10 12:50:47Succesfully pinged 'Le_Tuya_1' (attempt 1/2)
debug 2022-10-10 12:52:16Received Zigbee message from 'Si_Heiman_1', type 'readResponse', cluster 'genBasic', data '{"zclVersion":3}' from endpoint 1 with groupID 0
debug 2022-10-10 12:52:16Succesfully pinged 'Si_Heiman_1' (attempt 1/2)
debug 2022-10-10 12:52:31Received Zigbee message from 'Si_Heiman_1', type 'attributeReport', cluster 'genPowerCfg', data '{"batteryPercentageRemaining":200}' from endpoint 1 with groupID 0
info 2022-10-10 12:52:31MQTT publish: topic 'zigbee2mqtt_1/Si_Heiman_1', payload '{"battery":100,"linkquality":43}'
debug 2022-10-10 12:52:31Received Zigbee message from 'Si_Heiman_1', type 'commandStatusChangeNotification', cluster 'ssIasZone', data '{"extendedstatus":0,"zonestatus":16}' from endpoint 1 with groupID 0
debug 2022-10-10 12:52:31No converter available for 'HS2WD-E' with cluster 'ssIasZone' and type 'commandStatusChangeNotification' and data '{"extendedstatus":0,"zonestatus":16}'
debug 2022-10-10 12:52:31Saving state to file /opt/zigbee2mqtt/data/state.json
debug 2022-10-10 12:57:31Saving state to file /opt/zigbee2mqtt/data/state.json
Tu peux tenter de push lordre directement sur ton zigbee2mqtt pour voir si tu es dans le meme cas
D’après les derniers post dans l’issue ca a l’air de fonctionner. Ci dessous le résumé.
"In summary:
The typical payload to be sent is:
What we can control:
the alarm switching (mode) ON-OFF (ON = all melodies, OFF = stop)
What we cannot control:
the type of melodyHeiman HS2WD-E siren not really compatible ? · Issue #14424 · Koenkk/zigbee2mqtt · GitHub )
Isage
Novembre 9, 2023, 3:45
115
J’ai tout essayé! Rien à faire, ma sirène reste muette
C’est dommage d’avoir maintenant un mode Alarme dans Gladys, et ne pas pouvoir faire sonner une sirène, seul moyen de faire fuir d’éventuels cambrioleurs.
Merci à tous pour votre aide et votre patience.
cce66
Novembre 9, 2023, 4:13
116
Bonjour @spenceur ,
J’ai vu quelque part que sur HA elle fonctionnerais, si tu as un HA ou si tu peux monter un HA et vérifier et au cas ou effectivement cela marcherait regarder quelle trame MQTT marches !
@Isage de rien, frustré aussi de pas avoir réussi à faire marcher ton alarme, après il y en a certainement d’autres qui marches dans Gladys, t’as regardé dans le matériel déjà intégrés ?
Isage
Novembre 9, 2023, 4:37
117
J’ai trouvé ce device labellisé Gladys dans Aitable
Je préfèrerai ce modèle, plus adapter, mais je ne sais pas si il sera bien intégré à Gladys
Qu’en pensez-vous?
J’étais en train de cherchez la référence.
Clairement, jai juste pas le temps en ce moment, vois avec @Isage pour tester.
Je pense que vous y arriverez
guim31
Novembre 9, 2023, 5:25
121
Perso j’ai 2 modèles :
Et celui cité précédemment (le orange)
Le Tuya sonne plus fort je l’ai mis à l’intérieur et le orange il sonne dans mon abri de jardin
?
