A Homebridge plugin for Konnected Alarm Panel devices
npm install -g homebridge
npm install -g homebridge-konnected
The following two fields are required for the Konnected plugin to start.
{
"name": "Konnected",
"platform": "konnected"
}
After loading this plugin for the first time, it will attempt to discover the Konnected panel(s) on the same local network as Homebridge. Once discovered, the plugin will try to:
Once the plugin has completed the above two steps, you should also notice that a new security tile 'Konnected Alarm' is exposed in your HomeKit app's default room. You can rename this to whatever you want.
For the security system tile to have any meaningful function you must add zones with sensors on your panel(s) to your config.json file in Homebridge.
The best way to generate an error-free config.json is by installing and using the Config UI X Plugin for Homebridge. The Konnected Homebridge plugin binds to the Config UI X configuration GUI which makes setting up the zones a trivial process.
For those without Config UI X, or are running this on HOOBS < 4.0, please see the following example configuration for this plugin:
{
"name": "Konnected",
"platform": "konnected",
"advanced": {
"listenerPort": 5000,
"listenerIP": "192.168.2.213",
"discoveryTimeout": 10,
"entryDelaySettings": {
"delay": 60,
"pulseDuration": 975,
"pulsePause": 25,
"pulseRepeat": -1
},
"exitDelaySettings": {
"delay": 15,
"audibleBeeperModes": [
"0",
"1",
"2"
]
}
},
"panels": [
{
"name": "Konnected V1/V2",
"uuid": "8f655392-a778-4fee-97b9-123456789abc",
"ipAddress": "192.168.1.110",
"port": 12345,
"blink": true,
"zones": [
{
"enabled": true,
"zoneNumber": "1",
"zoneType": "beeper",
"zoneLocation": "Front Entrance",
"switchSettings": {
"trigger": 1,
"pulseDuration": 1000,
"pulsePause": 500,
"pulseRepeat": 3,
}
},
{
"enabled": true,
"zoneNumber": "2",
"zoneType": "contact",
"zoneLocation": "Front Entrance",
"binarySensorSettings": {
"invert": false,
"audibleBeep": true,
"triggerableModes": [
"0",
"1",
"2"
]
}
}
]
},
{
"name": "Konnected Pro",
"uuid": "8f655392-a778-4fee-97b9-123456789abd",
"ipAddress": "192.168.1.120",
"port": 54321,
"blink": false,
"zones": [
{
"enabled": true,
"zoneNumber": "alarm1",
"zoneType": "siren",
"zoneLocation": "Hallway",
"switchSettings": {
"trigger": 1
}
},
{
"enabled": false,
"zoneNumber": "4",
"zoneType": "temphumid",
"zoneLocation": "Kitchen",
"environmentalSensorSettings": {
"pollInterval": 10
}
}
]
}
]
}
There are four main states for most traditional alarm systems (thanks to @ShaunBennett for nicely writing out their suggested purpose):
That being said, HomeKit has the ability to programmatically hide both the Home/Stay mode and the Night mode if you don't use them. What's even better – this plugin will dynamically choose whether or not these security system modes are needed based on what triggerable modes are selected for sensors or switches.
If you don't want a Night mode for the security system, remove the Night mode from the triggerable mode setting for all sensors and switches; the same goes for the Home/Stay mode as well.
The Konnected Homebridge plugin affords some automatic conveniences when actuating Beepers, Sirens and Strobe zones. This means that if you wish to have any of these types of devices working in your security system, they must be specifically set in the zone to be a "beeper", "siren", or "strobe".
Homebridge will automatically find the beepers, sirens and strobe switches, no matter what panel they are on, and actuate them based on their configuration.
For Example:
When the security system is in a state of 'entry delay', beeper zones may be triggered to warn a user that the system is armed and needs to be disarmed. When the security system has passed the time of 'entry delay' and becomes triggered, the alarm should sound and the siren and strobe light zones will be triggered.
The great thing is that you can have multiple beepers, or sirens and strobe lights all fire off as one – but exist on different panels and zones across your house.
Sometimes you may need to reboot Homebridge once-more after changes made to the configuration for the zone accessories to show up the first time or to reflect the changes and work properly in HomeKit. This is partially because this Homebridge plugin uses a cache to keep it performant and needs to rebuild it once on launch, and then read from it on second launch to update the accessories in HomeKit.
Also it's always good to restart the HomeKit app after changes made to the Homebridge configuration as HomeKit does some background cleanup to the states and presence of devices in its accessory database.
Before anything, please review the Konnected Homebridge Forum to see if there's already a similar issue reported where a solution has been proposed.
If you cannot resolve the issue, please Post a Forum Topic with the following details:
Sometimes fixing a problematic Homebridge/HOOBS/HomeKit accessory is as simple as deleting Homebridge's cachedAccessories
file.
First stop Homebridge/HOOBS.
Delete the cachedAccessories
file which is commonly located in its respective folder:
~/.homebridge/accessories/cachedAccessories
$HOME\.homebridge\Accessories\cachedAccessories
~/.hoobs/etc/accessories/cachedAccessories
/var/lib/hoobs/accessories/cachedAccessories
Once the file is deleted, start up Homebridge/HOOBS and allow it to regenerate your accessories and the cache.
WARNING: Be careful to not delete the persist
folder or its contents! Your Homebridge and devices will become unresponsive and you will have to completely re-pair the Homebridge bridge (remove and re-scan the QR-code for Homebridge and set up all of your accessories/devices again).
As a last resort (only because it's NOT monitored regularly) try checking the Homebridge Discord Konnected channel. Sometimes troubleshooting a problem needs further real-time interaction and live chat can help.
As well, the Homebridge Discord server is a great place to get help for general Homebridge configuration questions too.
Plugin development, maintainance, and forum/ticket support is performed by Mike Kormendy in his spare time and blessed by Konnected Inc. If you somehow benefit from using this open source plugin and want to support Mike for his work on it, consider sponsoring him on Github, donate with PayPal, or buy him a coffee with Ko-fi – any contribution is greatly appreciated.
I'd like to thank Nate Clark for the initial Konnected Kickstarter hardware project and the following people for their guidance and help with code reviews, testing, pull requests etc: