That’s because the package references the ESPHome Library. Go here, then install it in Hubitat under “Libraries code.”
Then you can just install the Konnected Universal Alarm using HPM.
I originally set up my Konnected Pro with Hubitat back in May. I have been trying to get to the updated version, but I am struggling to follow the conversations above.
See my current setup below. Does this look correct? What should my next steps be? I feel stupid, but I don’t see how or where to set up the zones in the Konnected App (step 2) for example. Also, what is “HPM” referenced in step 4.
Konnected Pro Current Status
Firmware 1.1.2-795643
Software Konnected Pro 1.3.7
Running and visible in Konnected App (see image below)
Hubitat
Apps Code Installed:
Konnected Pro
Konnected Pro Device
Libraries Code:
espHomeApiHelper
Drivers Code:
Konnected Beep/Blink
Konnected Contact Sensor
Konnected Momentary Switch
Konnected Motion Sensor
Konnected Panic Button
Konnected Siren/Strobe
My alarm panel
6 open/close sensors
2 motion sensors
Note that I can see all of these zones in Hubitat from my original setup back in May, but none are responding to their respective zone activity.
======================
Steps from Above
-
Flash your device with our ESPHome firmware build from install.konnected.io
-
Discover in the Konnected app and set up your zones & preferences
-
Follow the steps in the Konnected app to do a wireless firmware update with your zone customizations
-
Install the new Hubitat driver either via HPM or using the bundle ZIP provided
-
Enter the IP address of the device in the device preferences in Hubitat
-
All zones will populate as child devices automatically
So for me, I didn’t understand that going to ESP was a complete change to the interface and the software you use. I had to forget everything that worked before.
What worked in my case.
- Flash your device with the ESPHome firmware build from install.konnected.io
1.1) I took a screen shot of my zone labels in the Konnected app before the flashing so it would make step 2 below easier. - Setup all the Zones IN the new ESP interface, which in my case meant I had to flash my Alarm Panel Pro (APP) again as the zone labels are created during the flash. I use ethernet and POE as a backup source for my board during a power outage, which means I had to hook up a cable and PC to my APP to flash it.
- Delete all the old Konnected Apps apps and Drivers in Hubitat
- Upgrade you Hubitat Package Manager (HPM) to v1.9.3 to install the NEW Konnected Hubitat drivers, there are only two. If you have an older HPM you will get a groovy error.
- In the HPM v1.9.3 install Alarm Panel (Universal) by Konnected Inc. This will created two drivers ONLY, no applications and that’s all you need.
- Create a new Virtual device, for each of those two new drivers, “Konnected Alarm Panel” and “Konnected Alarm Trigger.”
- Configure the virtual device Alarm Panel Pro with the IP and all the zones will show up as children of that device.
- And the worst part, redo all your automations with the new device children (alarm zones). This took me hours.
Hope that helps.
Thanks for the detailed response! I will dig into it again later today. - Mike
I’m not sure I succeed with your step 1. Can you tell from my Konnected App screen shot?
When I tried that step it just hung on the screen where it says “preparing to install”. It did seem to connect successfully and I think I have the latest software version? I think you had the same issue? Not sure how you resolved it.
Your screen shot looks like the legacy firmware NOT the new ESP. I have attached what mine looks like with the new ESP.
And yes I had the exact same issue. My board was bricked when I tried installing the new ESP and I had to open a ticket with Konnected and after a few hours worth of diagnostics between support and myself they sent me a new board, which took about 3 days to arrive. I thought I was just unlucky, but it seems there is a pattern here when you try to upgrade to the ESP from legacy FW.
After that I could proceed with everything else but I was dead stopped until the new board arrived.
My board is not bricked, but I can’t get past that “preparing install” screen.
When I hit that point I opened a ticket with Konnected, they have great customer support and are exceptionally responsive. In my case the only way to solve the hanging at preparing to install screen was to send me a replacement board.
How does one submit a ticket?
You go right here:
Thanks got connected and was able to flash my board.
Just to confirm- I should delete all of the old Konnected pro code and drivers I had installed from Hubitat?
I assume I should leave the espHomeApiHelper Library code?
Is there anything else I need to add to Hubitat?
Hubitat - previously installed
Apps Code Installed:
Konnected Pro
Konnected Pro Device
Libraries Code:
espHomeApiHelper
Drivers Code:
Konnected Beep/Blink
Konnected Contact Sensor
Konnected Momentary Switch
Konnected Motion Sensor
Konnected Panic Button
Konnected Siren/Strobe
My alarm panel
6 open/close sensors
2 motion sensors
[/quote]
I deleted everything as the HPM should install everything you’d need for the new drivers. I don’t think it hurts to leave any of the legacy stuff there, I just didn’t want the unused code sitting around and because I’m a little OCD 
with stuff like that.
And to clarify I do have espHomeApiHelper installed on my Hubitat, but it’s dated with the same time stamp as the two new drivers so I know that the HPM installed it, I don’t know if there is any difference in the versioning from the legacy code.
@nate I just updated all of my 6 zone Konnected boards to the latest ESPHome firmware from the old firmware and everything for the most part is going well. The only issue that I have identified is that I cannot press a button (garage door opener) in a rule using the Button Trigger driver. The button does not show up as a device in Rule Machine. However I can open the garage door in the device page using the “press” option. Am I missing something in my process? Thank you.
1 Like