Homebridge Plugin Initial Public Beta (Version 0.1.0)

Smart Home Integrations HomeKit (via Homebridge/HOOBS)
41

Awesome news! Thank you Mike!!

42

fantastic update!! i've been testing it this morning and the new features really make this product complete.

i think i've found a bug though:

1) i have output 1 set to be my beeper output. when i try setting any one of my contact or motion zones  to enable "this sensor should trigger the beeper when its state changes" instead of pulsing the beeper 5 times (as i have configured it to be in the alarm beeper switch configuration to behave as a door chime) the piezo instead just turns on solid and stays on forever until i arm/disarm the alarm. it behaved like this even before i customized the beeper output to pulse.

43

Right now I don't have any siren or beeper installed. I was hoping that the alarm would trigger an audible alarm on the HomePod. is that possible? 

44

@f, I will create a ticket to troubleshoot this. That situation leads me to believe it’s an isolated scenario.


@Jason, try this? https://www.imore.com/how-use-homepod-homekit-alarm


Regards,


// Mike

45

Hi, I’m also experiencing the same issue @f is with version 1.0.1 of this update - piezo beeps forever until i restart the konnected board or homebridge (I haven’t tried enabling/disabling the alarm when it gets into this state)

46

I installed a physical 12v alarm to my alarm pro. same one that is sold in this store. I have it set to trigger for home and away the settings. I've noticed that anytime the alarm triggers, its slow to do so and when it does, my connected board does not trigger alarm 1 or any alarm so my siren doesn't go off. no led is on the board for the alarm when it should be triggered.

47

further testing - got it working. I needed to create an alarm switch which I hadn't done. 

48

@Jason glad to hear!

49

@Tony Marcelli,

So I was able to troubleshoot this with @f in that ticket. I don't think you saw all of our conversation even though it CC'd you. I noticed you have the same reproducible affliction.


It boiled down to stale configuration settings in the Homebridge config.json file present from the previous version:

  1. sensors have old "switchSettings": {...} which shouldn't be there for sensors - remove that entire "switchSettings": {...} object block
  2. sensors may have the old "invert": true/false setting in the wrong location, it should exist under the "binarySensorSettings": {...} - move the invert setting to be inside that
  3. switches may have "binarySensorSettings": {...} which shouldn't be there for switches - remove that entire "binarySensorSettings": {...} object block
  4. beeper/siren/strobe switches may have "trigger": 1 in them. That is the default trigger for switches anyhow, so they aren't needed there. remove the "trigger": 1 setting from switches if they are meant to be triggered high.
  5. beeper/siren/strobe switches don't need "triggerableModes": [...] and don't really have any sort of purpose here (that's why it's experimental)


Overall, what might be best for everyone is if they backed-up their Homebridge config.json file (you can simple copy and paste it to a basic text file and save that on your computer somewhere). Then, re-build the configuration from scratch starting off with:

{
  "name": "Konnected",
  "platform": "konnected"
}

Then use the Config UI X interface to set up the zones again.

I realize that may be tedious, but I don't foresee the structure of the config.json file changing for this plugin significantly anymore – just additions of new settings.





50

Updating the config seems to have done the trick! Thank you!