Problem Heiman Smoke Detector : no alert info "Evolution of the heiman device HS1SA zigbee 3.0" #3164
Comments
|
Hello, I just exchanged with the seller. It is a new model of the Heiman HS1SA brand in ZigBee 3.0. It should therefore be integrated into the zigbeemqtt solution, because he believes that it is the heiman HS3SA model and suddenly I do not have any SMOKE alert feedback if it sounds. thank you. Database.db with pareid : |
kwetnico
changed the title
kwetnico
changed the title
kwetnico
changed the title
|
Hello, I found that the device.js file should be updated in the next version for this new Heiman model, there is an error: And it'sok : mars 21 12:28:17 raspberrypi npm[3304]: zigbee2mqtt:debug 2020-03-21 12:28:17: Received Zigbee message from '0x00158d0004c07fa8', type 'readResponse', cluster 'ssIasZone', data '{"iasCieAddr":"0x0000000000000000","zoneState":1}' from endpoint 1 with groupID 0 And alert : mars 21 12:29:03 raspberrypi npm[3304]: zigbee2mqtt:info 2020-03-21 12:29:03: MQTT publish: topic 'zigbee2mqtt/0x00158d0004c07fa8', payload '{"battery":96.5,"linkquality":92,"enrolled":true,"smoke":true,"battery_low":false}' and the alerts go up well (smoke) .. Did not work until now .. Database.db : |
|
I can confirm my HS1SA is also listed as HS3SA in Zigbee2MQTT. PS:
|
|
yes this is zigbee 3.0 new version .. This is why it is necessary to update in devices.js for the next version, the I just made the modification it works but I have a problem, it sends every 3 seconds of notifications !!! and tells me smoke: true alos or I launched a test to see the alert raised but do I have to wait until it goes back to standby? or is it normal? Thank you March 21 13:17:19 raspberrypi npm [32243]: zigbee2mqtt: info 2020-03-21 13:17:19: MQTT publish: topic 'zigbee2mqtt / DetecteurFumee', payload '{"battery": 76.5, "linkquality": 89, "enrolled": true, "smoke": true, "battery_low": false} ' |
|
If I press the "test" button, it beeps 3 times and reports the smoke only for 1 second. Note that I did not do your suggested change in device.js. |
Me if I press the test button once, it rings continuously without stopping ... I have to remove the battery and I don't have the same feedback as you on MQTT .. :( |
|
I think it stays in alarm mode, until you press the button again to mute/hush.
|
|
I press once to start the test. |
Press the button (while alarm sounds) for 3 seconds maybe? |
I tried by pressing once, 3 seconds ... |
|
With the original file devices.js : mars 21 14:21:08 raspberrypi npm[1513]: zigbee2mqtt:info 2020-03-21 14:21:08: Device '0x00158d0004c07fa8' joined |
|
So if you only put the battery back in, doesn't beep right? To confirm hardware issue, maybe try to temporary disable/poweroff the coordinator to make sure the device is also broken in "standalone" mode without network. |
|
PS: I hope your not deaf by now :( |
|
So, HS1SA-M and HS3SA both work with fz.heiman_smoke and fz.battery in devices.js
I'm now trying to find out more info about this... |
yes it's true since it rings continuously I have ears that smoke :) |
|
Cela fonctionne bien pour vous sans modifier le fichier device.js ? |
I tested by stopping my raspberry therefore my coordinator and by pressing once on the button the Heiman still rings continuously .. I must remove the battery so that it stops ... ( |
Yes for me the "smoke" state works fine with original device.js without modification.
And before/not pressing test-button, what is the LED status? |
And before/not pressing test-button, what is the LED status? I reset everything, I find the same problems just info battery and signal. mars 21 17:49:38 raspberrypi npm[1495]: zigbee2mqtt:info 2020-03-21 17:49:38: Starting interview of 'DetecteurFumee' |
I redo the tests if I press even 1 time: 1 second or 3 seconds while holding down it does not change anything the device rings without stopping ... impossible to cut it (I let ring 5 minutes) indicates smoke: true. I tested by lighting a candle, it works well with smoke: true (to stop it I had to remove the battery) But it always stays with the value: true |
|
In the FAQ there is only "Power on and alarm" and "Press test button but no alarm" phenomenon. You can still try to clean dust with vacuum cleaner or compressed air. But I really think your device is broken and you should dispute / ask refund with the seller.
|
it always stays on smoke: true even after several minutes :( I dismantled the device by removing the 4 screws and cleaned but the same ... |
|
Could you provide the zigbee herdsman debug log when pairing this device? To enable herdsman debug logging, see https://www.zigbee2mqtt.io/information/debug.html#zigbee-herdsman-debug-logging |
Before to launch with this command : you want to delete to database. Db and repairing my device ? |
|
Don't delete the database
|
Hello, I deleted this device with force_remove 👍 I reboot my system, i enable : the debug mode in configuration.yaml and launch with DEBUG=zigbee-herdsman* npm start ID my Device Heiman is : 0x00158d0004c07fa8 : zigbee2mqtt:info 2020-03-22 10:23:15: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2020-03-22.10-23-15' filename: log.txt |
Difference I can see in devices.js between HS1SA-M and HS3SA:
is not added for the HS3SA. I think you need that fz.heiman_smoke_enrolled to fix the ssIasZone error. I don't know for the cluster 'genBasic' and type 'readResponse' error however... Actually I'm wondering why the HS3SA was added seperately in first place (related|stale: #961)? And in Koenkk/zigbee-herdsman-converters@2020dc4 @Koenkk added 'SmokeSensor-N-3.0' zigbeeModel for HS3SA instead of HS1SA(-N). In home-assistant.js they both have:
Isn't configureReporting.batteryAlarmState() also required for both (related to battery_low)? I also don't see a battery icon in devices/dashboard |
|
I even tried to reflash my CC2531 key and suddenly re-pair all the deviations, I have the same problems. He is now paired with the live coordinator and same. |
|
The issue is that the device is not enrolled correctly. I've pushed some improvements to the latest zigbee2mqtt dev branch, please try to repair it there. |
Hello, Ok so I have to re-delete the device, install the Dev version (can we switch back to the stable version after?) And reappear the device? |
|
Yes, and you can switch to stable afterwards |
|
Version Dev : zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,12,69,202,5,98,168,127,192,4,0,141,21,0,201,161,7] +28ms |
|
I only have a message in the zigbeemqtt log if I remove and put the battery back into the smoke detector: By pressing the no ascent button and pressing the small hole with a needle for the same test. |
|
I have same issue.. Just reporting battery and linkquality.. |
|
I have the same issue. I don't have try the tips to rename the.js . I don't know where find it When i read in mqt explorer on the topic device i see only |
|
For me this model don't works with Zigbee2mqtt.. I have the xiaomi 's device no problem |
#3773 (comment) The problem is solved. You need install latest version and than repairing the device. |
Oh Thanks i waiting the new Master version. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bug Report
What happened
hello, i just added a new device to my zigbee network. I have the latest version Zigbeemqtt (1.12.0) with Jeedom on a rapsberry pi 4. and my cc2531 firmware key from June 2019.
I just added a Heiman zigbee smoke detector. It is well detected under zigbeemqtt but it already indicates a model which is not mine. On my label it says that I have an HS1SA (zigbee) and in the logs it says that I have one: HS3A.
"
mars 20 17:35:41 raspberrypi npm[1926]: zigbee2mqtt:info 2020-03-20 17:35:41: Starting interview of '0x00158d0004c07fa8'
mars 20 17:35:41 raspberrypi npm[1926]: zigbee2mqtt:info 2020-03-20 17:35:41: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_started","meta":{"friendly_name":"0x00158d0004c07fa8"}}'
mars 20 17:35:41 raspberrypi npm[1926]: zigbee2mqtt:info 2020-03-20 17:35:41: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"0x00158d0004c07fa8"}}'
mars 20 17:36:38 raspberrypi npm[1926]: zigbee2mqtt:info 2020-03-20 17:36:38: Successfully interviewed '0x00158d0004c07fa8', device has successfully been paired
mars 20 17:36:38 raspberrypi npm[1926]: zigbee2mqtt:info 2020-03-20 17:36:38: Device '0x00158d0004c07fa8' is supported, identified as: HEIMAN Smoke detector (HS3SA)
mars 20 17:36:38 raspberrypi npm[1926]: zigbee2mqtt:info 2020-03-20 17:36:38: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_successful","meta":{"friendly_name":"0x00158d0004c07fa8","model":"HS3SA","vendor":"HEIMAN","description":"Smoke detector","supported":true}}'
mars 20 17:36:38 raspberrypi npm[1926]: zigbee2mqtt:info 2020-03-20 17:36:38: Configuring '0x00158d0004c07fa8'
mars 20 17:36:41 raspberrypi npm[1926]: zigbee2mqtt:info 2020-03-20 17:36:41: MQTT publish: topic 'zigbee2mqtt/0x00158d0004c07fa8', payload '{"battery":80,"linkquality":78}'
mars 20 17:36:41 raspberrypi npm[1926]: zigbee2mqtt:info 2020-03-20 17:36:41: Successfully configured '0x00158d0004c07fa8'
"
The informations I have are just Battery and Linkquality. I launched a smoke test, I do not have SMOKE going back but a message that here:
"
mars 20 17:40:15 raspberrypi npm[15236]: zigbee2mqtt:info 2020-03-20 17:40:15: MQTT publish: topic 'zigbee2mqtt/DetecteurFumee', payload '{"battery":80,"linkquality":78}'
mars 20 17:40:15 raspberrypi npm[15236]: zigbee2mqtt:info 2020-03-20 17:40:15: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.12.0","commit":"840b9d9","coordinator":{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190608}},"log_level":"info","permit_join":false}'
mars 20 17:43:25 raspberrypi npm[15236]: zigbee2mqtt:info 2020-03-20 17:43:25: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"DetecteurFumee"}}'
mars 20 17:43:51 raspberrypi npm[15236]: zigbee2mqtt:info 2020-03-20 17:43:51: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"DetecteurFumee"}}'
mars 20 17:43:52 raspberrypi npm[15236]: zigbee2mqtt:info 2020-03-20 17:43:52: MQTT publish: topic 'zigbee2mqtt/DetecteurFumee', payload '{"battery":50,"linkquality":78}'
"
Please help, i don't have this device class :
binary_sensor:
state_topic: "zigbee2mqtt/<FRIENDLY_NAME>"
availability_topic: "zigbee2mqtt/bridge/state"
payload_on: true
payload_off: false
value_template: "{{ value_json.smoke }}"
device_class: "smoke"
Thanks
Best regards
(With debug level
mars 20 18:16:59 raspberrypi npm[8224]: zigbee2mqtt:debug 2020-03-20 18:16:59: Device 'DetecteurFumee' announced itself
mars 20 18:16:59 raspberrypi npm[8224]: zigbee2mqtt:info 2020-03-20 18:16:59: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"DetecteurFumee"}}'
mars 20 18:17:00 raspberrypi npm[8224]: zigbee2mqtt:debug 2020-03-20 18:17:00: Received Zigbee message from 'DetecteurFumee', type 'attributeReport', cluster 'genPowerCfg', data '{"batteryPercentageRemaining":100}' from endpoint 1 with groupID 0
mars 20 18:17:00 raspberrypi npm[8224]: zigbee2mqtt:info 2020-03-20 18:17:00: MQTT publish: topic 'zigbee2mqtt/DetecteurFumee', payload '{"battery":50,"linkquality":99}'
)
Picture to model : HS1SA (zigbee3.0) it's update or new model ?
https://image.noelshack.com/fichiers/2020/12/5/1584725955-20200320-183559.jpg
How to reproduce it (minimal and precise)
Debug Info
zigbee2mqtt version: 1.12.0
CC253X firmware version: 062019
{"version":"1.12.0","commit":"840b9d9","coordinator":{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190608}},"log_level":"info","permit_join":false}
The text was updated successfully, but these errors were encountered: