Wave-2 siren not triggering with Homebridge

Answered

Dear Mike.

Great new 1.1.0 version, thanks!

I was able to activate the new alarmsystem via Homebridge and everything works fine, except the trigger of the siren via my Wave-2.

The config I use is the following with one of my V2 PRO panels:

{
                            "enabled": true,
                            "zoneNumber": "alarm1",
                            "zoneType": "siren",
                            "zoneLocation": "Hallway",
                            "switchSettings": {
                                "trigger": "high"
                            }
}

In debug mode, I see the following:

{
  "endpoint_type": "rest",
  "endpoint": "http://192.168.1.205:52623/api/konnected",
  "token": "xxx-xxx-xxx",
  "blink": true,
  "discovery": true,
  "platform": "Homebridge",
  "sensors": [],
  "dht_sensors": [],
  "ds18b20_sensors": [],
  "actuators": [
    {
      "zone": "alarm1",
      "trigger": 1
    }
  ]
}

 Even if I change the state of the switch in Homekit or Homebridge, there is no sound.

When I change the trigger from 'high' to 'low', the siren sounds loud but I can not let it stop or use the switch in Homekit or Homebridge.

I'm running the latest software and firmware on my panels.

Do you have some advice please?

Best regards and keep up the good work,

Mathieu.

  • Hi Mathieu,

    What does the payload look like in the debug log? Here are a couple examples of what I would normally see when actuating any type of device (it all depends on how you configure the switch itself, not which one you select - the names are simply a label convenience):


    Siren:


    [7/17/2021, 10:00:41 AM] [Konnected]Actuating ['Home Mechanical Closet Siren'] (1aa4cf12318b-out1) 'siren' with payload:

    {

     "state": 1,

     "zone": "out1"

    }

    [7/17/2021, 10:00:41 AM] [Konnected]Set [Home Mechanical Closet Siren] (1aa4cf12318b-out1) 'siren' characteristic value: true

    [7/17/2021, 10:00:44 AM] [Konnected]Actuating ['Home Mechanical Closet Siren'] (1aa4cf12318b-out1) 'siren' with payload:

    {

     "state": 0,

     "zone": "out1"

    }

    [7/17/2021, 10:00:44 AM] [Konnected]Set [Home Mechanical Closet Siren] (1aa4cf12318b-out1) 'siren' characteristic value: false


    Beeper:


    [7/17/2021, 10:00:47 AM] [Konnected]Actuating ['Home Mechanical Closet Beeper'] (1aa4cf12318b-7) 'beeper' with payload:

    {

     "state": 1,

     "zone": "7",

     "momentary": 25,

     "times": 3,

     "pause": 25

    }

    [7/17/2021, 10:00:47 AM] [Konnected]Set [Home Mechanical Closet Beeper] (1aa4cf12318b-7) 'beeper' characteristic value: true

    [7/17/2021, 10:00:47 AM] [Konnected]Set [Home Mechanical Closet Beeper] (1aa4cf12318b-7) 'beeper' characteristic value: false


    In the beeper example, the characteristic changes to false immediately after the true because it is configured as a momentary switch that returns to its off state after being on.

  • Hey Mike.


    Thanks for the quick reply. This is what I got:


    [17/07/2021, 21:27:49] [Konnected] Kitchen Motion Sensor (77f008d1bd79-2): {"state":1,"zone":"2"}

    [17/07/2021, 21:32:09] [Konnected] Set [Siren Siren] (6110521ca639-alarm1) 'siren' characteristic value: true


    I'm not seeing the 'Actuating' line in my log.


    Best regards, Mathieu.


  • Hi Mathieu,

    Thanks for catching that. I was able to reproduce this issue and I believe I broke that feature when I was cleaning up the code.
    I have released a new version 1.1.4 and that fixes this issue.

    Thanks,

    // Mike