During my transition from OpenHab2 to HomeAssistant, I found myself looking at my aging DSC PC1550 wired alarm system.
Goal: Replace my functioning, but offline DSC PC1550 alarm. I wanted push notifications and IFTTT automation based events/triggers. This needed to fold into my existing smarthome ecosystem (Alexa/HASSIO).
The property has pre-existing DSC PC1550 wired alarm. I wanted to leverage this with my existing smarthome (Hue, Alexa, HASSIO). Due to the age of the panel an EyezOn unithttps://www.eyezon.com/ was not an option. Konnected seemed like they had a great product, but all their units were wireless. Browsing their new products though, they recently added a new POE/wifi unit, Konnected Prohttps://konnected.io/collections/pre-order-new-v2-products/products/konnected-alarm-panel-pro-12-zone-kit. Though, pricey at the time ($229 USD).
Out of the box, the Konnected unit offers full compatibility with all of my existing zones and integrationhttps://www.home-assistant.io/integrations/konnected/ with HASSIO. From the reading it seemed as easy as update, wire, ??, PROFIT!
The Konnected unit came with some labels. I numbered each one (not necessary), but let me keep track of all my zones. I ended up running around the house opening/closing windows and doors to see which zones trigger.
There are two primary resources I used to setup, the help portal Getting Startedhttps://help.konnected.io/support/solutions/32000015807 and the HASSIO Konnected integration pagehttps://www.home-assistant.io/integrations/konnected/.
When labeling the wires, I ended up grouping the shared positions. For example, Z1/COM/Z2 on the DSC panel I grouped as #1. This maps directly to the Konnected 1/G/2 positions.Note
Once everything is updated and on the latest version you should be ready to add it to your smart home hub.
Unresponsive after reboot ~5 minutes
While initially setting up the Konnected Pro boardhttps://konnected.io/collections/pre-order-new-v2-products/products/konnected-alarm-panel-pro-12-zone-kit, I was unable to get a stable connection to my HomeAssistant environment. HomeAssistant sees the device, reports just fine, but the device became unresponsive and stopped reporting to HomeAssistant after a few minutes. In order to pull the below log, I had to debug the device by connecting my laptop via USB and using PuTTyhttps://help.konnected.io/support/solutions/articles/32000023786-device-debugging-with-screen.
[INFO 1613790198.502901, 167024] /lfs/network.lua:31: Loaded: application
[INFO 1613790198.558907, 166816] /lfs/rest_endpoint.lua:123: REST Endpoint: http://homeassistant:8123/api/konnected
[ERROR 1613790198.778177, 158604] /lfs/log.lua:92: E (11452) HTTP_CLIENT: Connection failed, sock < 0
[WARN 1613790198.793641, 158572] /lfs/log.lua:92: W (11462) http: esp_http_client_perform returned error 28674
[INFO 1613790198.816977, 163304] /lfs/rest_endpoint.lua:13: HTTP Call: -28674 state -0 zone 1
[ERROR 1613790199.048887, 158524] /lfs/log.lua:92: E (11722) HTTP_CLIENT: Connection failed, sock < 0
[WARN 1613790199.064045, 158492] /lfs/log.lua:92: W (11732) http: esp_http_client_perform returned error 28674
[INFO 1613790199.089214, 163224] /lfs/rest_endpoint.lua:13: HTTP Call: -28674 state -0 retry 1 zone 1
[ERROR 1613790199.319313, 158524] /lfs/log.lua:92: E (11992) HTTP_CLIENT: Connection failed, sock < 0
[WARN 1613790199.334428, 158492] /lfs/log.lua:92: W (12002) http: esp_http_client_perform returned error 28674
[INFO 1613790199.359134, 163224] /lfs/rest_endpoint.lua:13: HTTP Call: -28674 state -0 retry 2 zone 1
Guru Meditation Error: Core 0 panic'ed (LoadProhibited). Exception was unhandled.
To resolve the above issue, I stumbled upon this posthttps://community.home-assistant.io/t/konnected-alarm-panel-connect-a-wired-alarm-system-to-ha-new-in-0-70/53620/94. The core of the issue is that HomeAssistant was using DNS/hostname while Konnected Pro needs to use an IP address.
base_url: http://homeassistant.local #hassio hostname
api_host: http://192.168.0.5 #hassio IP
The api_host could not communicate with homeassistant.local and needed the IP address of the hassio computer. Once I added the api_host and access_token (in the below configurations.yaml) I factory reset the Konnected device. Once it came back online it adopted the settings from HASSIO and has been working since.
Disconnecting after 24-48 hours
While running the Konnected Pro board, I experienced an odd issue where the unit would become unresponsive and go offline after a day or two. After researching I found that the device is going into discovery mode. The solution was to hard-code discovery: false in the configuration.yaml filehttps://help.konnected.io/support/solutions/articles/32000023968-disabling-device-discovery (below).
# Configure a default setup of Home Assistant (frontend, api, etc)
api_host: http://192.168.0.5:8123 #hassio IP address
- id: 2d55633db123
- Beginners Guide to Farming CHIA XCH on Ubuntu - May 22, 2021
- AZ-900 Study Guide Material - April 18, 2021
- How to purchase SafeMoon SafeMars cryptocurrency using PancakeSwap - April 3, 2021
Notes & References