HEIMAN HS1SA-E smoke detector - no alarm messages

Device support
1

Hi all,

i just got a new HS1SA smoke detector and have trouble getting it to work properly. Pairing is ok and the battery and linkquality messages too. But if i press the test button or activate the alarm with some smoke no messages or log entries are generated.

The device properties:

  • The device label on a battery slot means it is the model HS1SA-E, but it sends a "SmokeSensor-N-3.0’ so the zigbee2mqtt detects it as a HS3SA.
  • The version info: Brige: “version”:“1.14.0”,“commit”:“9009de2”
  • Coordinator firmware version: ‘{“type”:“zStack12”,“meta”:{“transportrev”:2,“product”:0,“majorrel”:2,“minorrel”:0,“maintrel”:0,“revision”:""}}’

and the log of device pairing:

info 2020-06-17 15:20:04: Device ‘0xXXXXXXXXXXX’ joined
info 2020-06-17 15:20:04: Starting interview of ‘0xXXXXXXXXXXX’
info 2020-06-17 15:20:04: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{“type”:“device_connected”,“message”:{“friendly_name”:“0xXXXXXXXXXXX”}}’
info 2020-06-17 15:20:04: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload '{“type”:“pairing”,“message”:“interview_started”,“meta”:{“friendly_name”:"0xXXXXXXXXXXX$
debug 2020-06-17 15:20:04: Device ‘0xXXXXXXXXXXX’ announced itself
info 2020-06-17 15:20:04: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload '{“type”:“device_announced”,“message”:“announce”,“meta”:{“friendly_name”:"0xXXXXXXXXXXX$
debug 2020-06-17 15:20:17: Received Zigbee message from ‘0xXXXXXXXXXXX’, type ‘readResponse’, cluster ‘genBasic’, data ‘{“modelId”:“SmokeSensor-N-3.0”}’ from endpo$
debug 2020-06-17 15:20:17: No converter available for ‘HS3SA’ with cluster ‘genBasic’ and type ‘readResponse’ and data ‘{“modelId”:“SmokeSensor-N-3.0”}’
debug 2020-06-17 15:20:19: Received Zigbee message from ‘0xXXXXXXXXXXX’, type ‘readResponse’, cluster ‘genBasic’, data ‘{“manufacturerName”:“HEIMAN”}’ from endpoin$
debug 2020-06-17 15:20:19: No converter available for ‘HS3SA’ with cluster ‘genBasic’ and type ‘readResponse’ and data ‘{“manufacturerName”:“HEIMAN”}’
debug 2020-06-17 15:20:22: Received Zigbee message from ‘0xXXXXXXXXXXX’, type ‘readResponse’, cluster ‘genBasic’, data ‘{“powerSource”:3}’ from endpoint 1 with gro$
debug 2020-06-17 15:20:22: No converter available for ‘HS3SA’ with cluster ‘genBasic’ and type ‘readResponse’ and data ‘{“powerSource”:3}’
debug 2020-06-17 15:20:24: Received Zigbee message from ‘0xXXXXXXXXXXX’, type ‘readResponse’, cluster ‘genBasic’, data ‘{“zclVersion”:2}’ from endpoint 1 with grou$
debug 2020-06-17 15:20:24: No converter available for ‘HS3SA’ with cluster ‘genBasic’ and type ‘readResponse’ and data ‘{“zclVersion”:2}’
debug 2020-06-17 15:20:26: Received Zigbee message from ‘0xXXXXXXXXXXX’, type ‘readResponse’, cluster ‘genBasic’, data ‘{“appVersion”:20}’ from endpoint 1 with gro$
debug 2020-06-17 15:20:26: No converter available for ‘HS3SA’ with cluster ‘genBasic’ and type ‘readResponse’ and data ‘{“appVersion”:20}’
debug 2020-06-17 15:20:29: Received Zigbee message from ‘0xXXXXXXXXXXX’, type ‘readResponse’, cluster ‘genBasic’, data ‘{“stackVersion”:2}’ from endpoint 1 with gr$
debug 2020-06-17 15:20:29: No converter available for ‘HS3SA’ with cluster ‘genBasic’ and type ‘readResponse’ and data ‘{“stackVersion”:2}’
debug 2020-06-17 15:20:49: Received Zigbee message from ‘0xXXXXXXXXXXX’, type ‘readResponse’, cluster ‘genBasic’, data ‘{“hwVersion”:16}’ from endpoint 1 with grou$
debug 2020-06-17 15:20:49: No converter available for ‘HS3SA’ with cluster ‘genBasic’ and type ‘readResponse’ and data ‘{“hwVersion”:16}’
debug 2020-06-17 15:20:51: Received Zigbee message from ‘0xXXXXXXXXXXX’, type ‘readResponse’, cluster ‘genBasic’, data ‘{“dateCode”:“2018.9.27”}’ from endpoint 1 w$
debug 2020-06-17 15:20:51: No converter available for ‘HS3SA’ with cluster ‘genBasic’ and type ‘readResponse’ and data ‘{“dateCode”:“2018.9.27”}’
debug 2020-06-17 15:20:53: Received Zigbee message from ‘0xXXXXXXXXXXX’, type ‘readResponse’, cluster ‘genBasic’, data ‘{“swBuildId”:“2000-0001”}’ from endpoint 1 debug 2020-06-17 15:20:53: No converter available for 'HS3SA' with cluster 'genBasic' and type 'readResponse' and data '{"swBuildId":"2000-0001"}' debug 2020-06-17 15:20:55: Received Zigbee message from '0xXXXXXXXXXXX', type 'readResponse', cluster 'ssIasZone', data '{"iasCieAddr":"0x0000000000000000","zoneSt
debug 2020-06-17 15:20:55: No converter available for ‘HS3SA’ with cluster ‘ssIasZone’ and type ‘readResponse’ and data '{“iasCieAddr”:“0x0000000000000000”,“zoneState”:blush:
info 2020-06-17 15:20:55: Successfully interviewed ‘0xXXXXXXXXXXX’, device has successfully been paired
info 2020-06-17 15:20:55: Device ‘0xXXXXXXXXXXX’ is supported, identified as: HEIMAN Smoke detector (HS3SA)

Any ideas?

If you need some additional information i would be happy to deliver it.

Thanks a lot.

2

Hi
I have exactly the same problem with a recently purchased device. The device label on the battery slot says model HS1SA-E.

At first, I thought it was some problem with the device, but I can get it to work to send an alarm with Openhab and the binding Zigbee v2.5.5-1. https://www.openhab.org/addons/bindings/zigbee/ But I prefer to get it to work with zigbee2mqtt.

Thanks a lot.

3

Do you mean you can trigger the siren by MQTT or you mean the detector is sending an alarm message when it detects smoke?

4

I can trigger an alarm when I press the test button.

5

Yes, the test feature works. It’s a shame we can’t send a trigger to the alarm as if we had multiple devices the alarm would go off on each device. I wonder if there is another model with this functionality? I’m testing it now to see if it sends the alarm to zigbee2mqtt, first test was unsuccessful but I’m not sure it’s paired successfully:

info  2020-06-25 22:15:12: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"ota_update","message":"Update available for 'Bathroom'","meta":{"status":"available","device":"Bathroom"}}'
info  2020-06-25 22:15:23: Device '0x00158d0004b487e6' joined
info  2020-06-25 22:15:23: Starting interview of '0x00158d0004b487e6'
info  2020-06-25 22:15:23: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_connected","message":{"friendly_name":"0x00158d0004b487e6"}}'
info  2020-06-25 22:15:23: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_started","meta":{"friendly_name":"0x00158d0004b487e6"}}'
info  2020-06-25 22:15:23: MQTT publish: topic 'zigbee2mqtt/0x00158d0004b487e6/availability', payload 'online'
info  2020-06-25 22:15:24: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"0x00158d0004b487e6"}}'
info  2020-06-25 22:15:28: MQTT publish: topic 'homeassistant/binary_sensor/0x00158d0004b487e6/smoke/config', payload '{"payload_on":true,"payload_off":false,"value_template":"{{ value_json.smoke }}","device_class":"smoke","state_topic":"zigbee2mqtt/0x00158d0004b487e6","json_attributes_topic":"zigbee2mqtt/0x00158d0004b487e6","name":"0x00158d0004b487e6_smoke","unique_id":"0x00158d0004b487e6_smoke_zigbee2mqtt","device":{"identifiers":["zigbee2mqtt_0x00158d0004b487e6"],"name":"0x00158d0004b487e6","sw_version":"Zigbee2mqtt 1.14.0","model":"Smoke detector (HS3SA)","manufacturer":"HEIMAN"},"availability_topic":"zigbee2mqtt/0x00158d0004b487e6/availability"}'
info  2020-06-25 22:15:28: MQTT publish: topic 'homeassistant/binary_sensor/0x00158d0004b487e6/battery_low/config', payload '{"payload_on":true,"payload_off":false,"value_template":"{{ value_json.battery_low}}","device_class":"battery","state_topic":"zigbee2mqtt/0x00158d0004b487e6","json_attributes_topic":"zigbee2mqtt/0x00158d0004b487e6","name":"0x00158d0004b487e6_battery_low","unique_id":"0x00158d0004b487e6_battery_low_zigbee2mqtt","device":{"identifiers":["zigbee2mqtt_0x00158d0004b487e6"],"name":"0x00158d0004b487e6","sw_version":"Zigbee2mqtt 1.14.0","model":"Smoke detector (HS3SA)","manufacturer":"HEIMAN"},"availability_topic":"zigbee2mqtt/0x00158d0004b487e6/availability"}'
info  2020-06-25 22:15:28: MQTT publish: topic 'homeassistant/sensor/0x00158d0004b487e6/linkquality/config', payload '{"icon":"mdi:signal","unit_of_measurement":"lqi","value_template":"{{ value_json.linkquality }}","state_topic":"zigbee2mqtt/0x00158d0004b487e6","json_attributes_topic":"zigbee2mqtt/0x00158d0004b487e6","name":"0x00158d0004b487e6_linkquality","unique_id":"0x00158d0004b487e6_linkquality_zigbee2mqtt","device":{"identifiers":["zigbee2mqtt_0x00158d0004b487e6"],"name":"0x00158d0004b487e6","sw_version":"Zigbee2mqtt 1.14.0","model":"Smoke detector (HS3SA)","manufacturer":"HEIMAN"},"availability_topic":"zigbee2mqtt/0x00158d0004b487e6/availability"}'
info  2020-06-25 22:15:49: Successfully interviewed '0x00158d0004b487e6', device has successfully been paired
info  2020-06-25 22:15:49: Device '0x00158d0004b487e6' is supported, identified as: HEIMAN Smoke detector (HS3SA)
info  2020-06-25 22:15:49: Configuring '0x00158d0004b487e6'
info  2020-06-25 22:15:49: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_successful","meta":{"friendly_name":"0x00158d0004b487e6","model":"HS3SA","vendor":"HEIMAN","description":"Smoke detector","supported":true}}'
error 2020-06-25 22:15:59: Failed to configure '0x00158d0004b487e6', attempt 1 (Error: Bind 0x00158d0004b487e6/1 genPowerCfg from '0x00124b001bd816c2/1' failed (Error: AREQ - ZDO - bindRsp after 10000ms)
    at Endpoint.<anonymous> (/app/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:255:23)
    at Generator.throw (<anonymous>)
    at rejected (/app/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65))

EDIT: I just noticed this on the wiki for the other Heiman smoke alarm model (HS1SA-M):

make sure the device is awake during pairing phase or the configuration may fail. To ensure device is awake press the main button every 2 seconds until configuration is done in zigbee2mqtt logs

But now I can’t get it to re-pair after force removing it :slightly_frowning_face:

6

Got it paired again after rebooting the box :smiley:
Not getting any messages after triggering the alarm with burning stuff. Not good! Has anyone checked for open issues on github for this?

7

Hi,

yes, i reported the issue and it is already fixed by Koen:

1 Like
8

Perfekt
Now it is working with the latest dev branch :slightly_smiling_face:
Thank you