Closed marcgtp closed 1 year ago
@ginkel Just curious - any update from Heiman? Thanks!
They replied and asked for a pcap. Unfortunately, I didn't yet have the time to capture one as the Zigbee pcap solution I had previously working no longer works...
Having followed this discussion for almost two years, it's clear this device is not going to be supported any time soon.
Normally this would be off topic, but considering the circumstances, does anyone have alternative recomendations for a zigbee device that serve as a multifunction alarm/chime/sound effect? I had high hopes this would fit my needs, but they dropped the ball big time.
I'm joining the discussion as I've been experiencing the exact same limitations. I've also contacted the support via email, let's see if we can push this for a resolution.
Can I help any of you in the meanwhile? I have everything set up and configured if someone could make anything out of the. logs
@leonshadow15 Can you capture a Zigbee pcap of the bad interaction? That's what Heiman requested from me...
@leonshadow15 Can you capture a Zigbee pcap of the bad interaction? That's what Heiman requested from me...
I have never sniffed the traffic, aren't the logs enough? if yes, can you specify from where I should get them? (mqtt explorer, z2m…)
@leonshadow15 Can you capture a Zigbee pcap of the bad interaction? That's what Heiman requested from me...
I found a guide, will look for the 2nd usb stick. So far they haven't replied to me via email.
I just bought and receive the Meian siren (Tuya TS0224 in zigbee2mqtt supported device list). It has the same limitations as described here while using it with zigbee2mqtt.
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