How do you set up a IAS?

[fribse]

Describe the question or issue you are having

I've just received a series of Heiman smoke alarms (HS1SA), that I've joined to the deconz network. That went rather smootly (a few quirks, but nothing much).
I tried finding out how to set up an IAS so they could warn each other directly, but I couldn't find a guide on how to do that, anybody that can point me to one, or explain how to do this?

Environment

• Host system: PVE on NUC
• Running method: Home Assistent deCONZ Add-on
• Firmware version: (26580700)
• deCONZ version: (2.05.79)
• Device: ConBee II
• Do you use an USB extension cable: yes - USB3

[SwoopX]

Short answer for the moment: This is not a matter of setup, it's not possible.

[ebaauw]

The whole IAS setup doesn’t cater for IAS device to communicate directly to each other, unlike e.g. wireless controller that control lights directly. You need a gateway that receives the messages from the device, and translates them into messages for another device. In our case, the REST API plugin would be the gateway, and you’d use rules to activate the sirens of the other devices when one device reports an alarm.

The IAS Zone cluster, reporting alarms, should be exposed as a /sensors cluster, depending on the device type. The IAS WD cluster, controlling the siren (and strobe light) should be exposed as a /lights resource. So your rules would have a condition on the sensor, and an action on the light.

Do the Heiman sensors have a functional IAS WD cluster? The loaner I had a couple of years ago had this cluster, but it wasn’t doing anything. Can you activate the siren in the GUI?

[fribse]

Looking in the IAS WD I can see two sections.

The (1) section doesn't do anything.
The (2) section makes noise.

[fribse]

I've built up a nice flow in Node-Red to handle the alarming now, also announcing on the Google devices where the smoke is detected, so that part is fine. The devices will of course also make noise for themselves, so even if the central system is the cause of the problems, sound will be made :-)

[ebaauw]

The (1) section doesn't do anything.

You probably need to set a siren level and warning mode.

The (2) section makes noise.

That’s promising. I don’t think I’ve exposed the Squawk command thru the API, but if Start Warning doesn’t work, we could use Sqawk instead. How long does the noise last?

[SwoopX]

This is indeed interesting. Might be a small challenge to find the right combination to have the siren triggered. As os now, we have devices reacting on different combinations for the start warning command, which are not necessarily logical. You may check here for further background #1593 (comment)

I quickly checked the specs for the squawk command, no way to define any duration there. It is originally meant to give a "short" audible feedback (e.g. to indicate a system is armed), so it's probably up to the device, how long the signal lasts.

[fribse]

Ok, I did some testing now that the wife is out the door :-)

The (1) does start if I set warning duration.
Siren level 0,1 gave nothing
Strobe makes the red light in it flash (the number of flashes is controlled by the number given in warning duration (the number 1 gives 1 flash, 2 gives two flases etc.). I'm not sure what the Strobe Duty cycle does?
The warning mode 0, 1 gives siren
The warning mode 2, 3 gives nothing

The (2) gave these results.
The sqawk level 0, 1 and strobe goes for 3 seconds (all with the same wiuwiu sound sirene and flashing), the sound for disarmed goes for 5 seconds?

[ebaauw]

The (1) does start if I set warning duration.

Cool. Normally the siren should apply the default duration (from the corresponding attribute) when none is given, but the GUI probably sends the value from the input field even when it's 0.

Siren level 0,1 gave nothing
The warning mode 0, 1 gives siren
The warning mode 2, 3 gives nothing

The Options parameter consists of a 2-bit enum for Siren Level, a 1-bit flag for Strobe and a 4-bit enum for the Warning Mode. The GUI cannot handle the enum subfields, so I exposed them as individual bits. Setting only bit 0 in the Warning Mode should work, at least for all sirens I've seen. The Siren Level is a bit more difficult: some devices will sound the siren at Siren Level 0 (both bits cleared), others remain silent at level 3 (both bits set). The Stobe bit should control whether the light flashes, but not all devices implement it. By default, the REST API Plugin sends:

• Warning Mode 1 (bit 0 set), Stobe and Siren Level 3 (both bits set) on "alert": "select" and "alert": "lselect";
• All bits cleared on "alert": "none" (this should silence the alarm); and
• Only Strobe on "alert": "blink".
  The duration is 1 for "select" and 300 for "lselect" and "blink"; this can be overwritten by specifying "ontime"(so{"alert": "blink", "ontime": 10}` should flash the lights for 10 seconds.

I'm not sure what the Strobe Duty cycle does?

It should control the flash pattern: how long the flash is on (in 0.1s) per second. Again, not all devices implement this. It's not exposed by the API.

[fribse]

Ok, the Duty Cycle certainly changes the flashing pattern as described, do you need me to test further?

[ebaauw]

Did the API plugin already create a light resource for the Siren? If not, can you please post a screenshot of the Basic cluster (after reading the attributes) and of the Node Info panel?

[fribse]

Yes it shows up in deconz like this:

[ebaauw]

Then you should be able to control it from the API, doing a PUT of {"alert": "select"} to the light state. Doing a PUT of {"alert": "all"} should sound all sirens in the network. This is a dirty hack of mine to send a broadcast Start Warning. Better specify "ontime" and cover your ears.

Next step is to setup rules to sound the siren(s) when fire is detected.

[ebaauw]

I've just received a series of Heiman smoke alarms (HS1SA)
Looking in the IAS WD I can see two sections.

@fribse, is that the IAS WD cluster of the HS1SA or of the (standalone) Heiman siren?

In case of the HS1SA: which ones are these? Could you post a screenshot of the Basic cluster (after reading the attributes) and of the Node Info panel? You might need to briefly press the reset button (hole) to wake the sensor, for the Read to work.

I got my hands on a couple of Zigbee 3.0 HS1SA sensors, with Model Identifier SmokeSensor-N-3.0, Date Code 2018.9.27, and SW Buid ID 2000-0001, but they report Unsupported Custer (0xC3) when trying to interact with their IAS WD_ cluster.

The good news is that they seem to support over-the-air firmware updates, but I've yet to see a firmware file for a Heiman device...

[fribse]

That is the Heiman siren
The smoke sensor looks like this:

Basic looks like this:

Node info:

[ebaauw]

That is the Heiman siren

Thanks, that makes sense. The smoke sensor also advertises an IAS WD cluster, so you’d think/hope you could control its siren over Zigbee, but it doesn’t work.

[fribse]

Hi @ebaauw
Is it possible to send out the 'alert' command via the API? So I could have my node-red alerting do the 'zone' alert.
I know I can do it via HA to the siren itself, as that is a switch and a light, but as the smoke sensors does not show a switch for this, maybe I can do it directly to the api?

[SwoopX]

You cannot send a command to a non-existing target. If the functionality is supported, then typically a corresponding resource item (alert) is exposed via the resource (light). If I understand your situation correctly, you neither have any of those.

Besides, HA uses the API.

[fribse]

Hi @SwoopX
I was just hoping, since I could activate the alarm from the deconz VNC GUI, that this could be done through the API as well., despite that phoscon doesn't show it.

[ebaauw]

@Frisbe, are you talking about the smoke sensor or the siren? You should be able to activate the sound on the siren through the API. Afaik, the smoke sensor doesn’t support activating the sound over Zigbee, neither in the GUI nor through the API.

[fribse]

I have the siren working, but you are right, even though the buttons are in the GUI for the smoke sensor, they don't work.
I think it goes in a very deep sleep, because the GUI shows the flashing red when I try to send the command.

[ebaauw]

It does go into deep sleep, but when you wake the sensor before sending the command, it returns the status for an unsupported cluster, as I mentioned above.

[stale]

As there hasn't been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.