I have just purchased on of these Heiman HS1SA-Z Smoke Sensor devices cheap off Aliexpress. The device is mini much smaller than I was expecting but its loud when pressing the test button.
Paired it to my Vera Plus as a Generic Z-Wave device and it was added as such to the UI7 as a Generic IO device with On / Off buttons.
The include / exclude button is within a small hole on the side of it so you need a pin to press it 3 times, I couldn’t see it initially and had to consult the user manual to find it.
You can easily change the device in to a Smoke Sensor in Vera.
You should also change category_num to 4 (Security Sensor) and subcategory_num to 4 (Smoke Sensor) for the sensor to appear in the Vera Dashboard - My Modes section.
That’s all I have done with the device so far, I plan to create a Fire Alarm scene and test the sensor somehow and see if it triggers my scene ?
I have so far just created a basic Vera scene, to send my phone a Vera Alert “Smoke Detector Triggered” message.
The trigger in the scene I used was “Whenever Smoke Detector detects smoke whether is armed or disarmed”
I set fire to a post it note and blew out the flame and held the sensor over it.
It did take a little longer than I expected to trigger, but it went off OK and the Vera Alert was received on my phone.
I was also watching the sensor in my Imperihome app on the phone, the default icon for it is a greyed out fire. When it tripped the sensor, its status went from OK to Alarm! and the icon changed to a coloured fire icon.
So it works anyway.
I might pick up a Heiman CO2 sensor as well and put that one near my gas central heating boiler.
I also have couple of them (non branded) and they indeed work well. Beware of the included battery, mine died within a couple of weeks. The unit then beeps and flashes in a certain pattern. Took a while to figure out what was wrong. A fresh battery solved this
Do you think it could be possible to trigger the alarm manually (without the button)? In that case i could pair them in a scene and make them all go off in case 1 detects smoke.
@Catman
There are zigbee versions available as well
Just changed category_num to 4 (Security Sensor) and subcategory_num to 4 (Smoke Sensor), got it to show up on the Modes Page. But it is now shown as “tripped” = 1.
Changed device_json: D_SmokeSensorWithTamper1.json to D_SmokeSensor1.json, There seems to be no tamper sensor in the device? I also reset the tripped fields to 0. Will test the device to see if it will both trip and untrip when activated when the house is empty next time.
Seems logical to use D_SmokeSensor1.json, hopefully this may solve the problem with untrip not beeing registred. I noted this as changing house modes after fixing the categories to smoke sensor resulted in an alarm state…
Hi. Hopefully someone can help here. I had 2 of these smoke sensors and one died last week. So within warranty I got a new one today. But, after adding a new generic device I only got 1 device in Veraedge.
Old
new
So not very usable. Any idea? I already tried an exclude/include twice.
