Does anyone know if there’s any plans to develop Hubitat integration with the new ESPHome firmware? I got a brand new v1.9 board and had to down flash it to the original firmware and after seeing the ESPHome firmware UI that seems to be quite a downgrade for the Hubitat community.
Yes, it is on my near-term todo list. We already have ESPHome firmware for the GDO products so it’s not too much of huge effort. I’m relying heavily on the fantastic ESPHome library for Hubitat by bradsjm.
Do you want to help develop or beta test? I’m a bit overwhelmed with different priorities so anyone who can help develop would be welcomed!
Hey Nate, has any progress been made on the ESP home integration for Hubitat. I found one in the Konnected github. I have been playing around with it the last 2 days it recognizes are my contact sensors but nothing else, I’m trying to tinker with it and get momentary switches and Temp/humidity sensors working but so far I’ve had no luck. Any help you can give would be appreciated and If you need someone to Beta test I am happy to help.
Yes, I have started on it and as you have found out, only finished support for contact sensors so far! You can track Hubitat driver release notes here.
This week got a little nuts and I wasn’t able to work on it as much as I had hoped. I will circle back soon to add the additional device types.
no worries Nate. I will definitely be keeping an eye on the Github.
@JohnNfromTN @scubamikejax904 I’ve just updated the new Hubitat driver for the Alarm Panel! It now should be fully-functional and have all the features of our existing driver, but faster and more extensible now that it’s built via the newer ESPHome firmware.
Here are quick release notes and package downloads:
You can also install the driver via HPM. Please test this out and let me know how it works out!
@nate Thanks, so to be clear I need to 1) go to https://install.konnected.io/ and flash my panel back to the ESP firmware 1.8, then 2) go into HPM and install the new drivers? Will the old devices and rules/automations remain intact, will they be deleted or be orphaned? I am just trying the gage the LOE for this task to figure out the time commitment required.
Yes, that’s right. The detailed steps to migrate are:
- 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
You will need to re-do your automations and rules to use the newly populated devices. The old ones won’t be deleted automatically, but they will be orphaned, so you can probably pretty easily move the rules/automations over before deleting the original devices, drivers and app.
Let me know if you have any questions!
Hey @nate thank you for the update and the quick turnaround with this updated driver. I just started playing around with it, Is there an easy way to change the Temperature from Celsius to Fahrenheit?
Looks like I need to add a units selector to the zone setup in the Konnected app to do this the right way. Adding that to my list.
1 Like
Hello @nate
I am new to this and I am stuck at step #5. I think I am missing something here. HPM install is done but I have no new devices or apps listed to set the IP.
What am I missing?
Look in the Konnected app or in your router’s app for the IP address of your Konnected board(s)
Yes, I know what the IP is. I am not sure where I have to set it though? Do I add a new App? or a new Device?
If I try to add a new user app and select Konnected Pro my panel is not being discovered and I am stuck.
Sorry the steps were not clear. I still need to write up proper documentation.
Create a new virtual device in Hubitat and select Konnected Alarm Panel as the device type. On the preferences for the new device, enter the IP address. Everything after that point is pulled in automatically.
Thanks!! That worked great.
Now that all devices are setup and zone are being monitored, I was wondering if there is a way to know the status of the alarm “Armed Away”, “Armed Stay”, “Disarmed”, “Ready” etc. This is critical for rules/apps I think.
In Hubitat, the alarm state is managed by Hubitat Safety Monitor (a built-in Hubitat app). We’re working on a standalone alarm system feature, but it’s not recommended for Hubitat users at this point. HSM is a better user experience.
Sorry I wasn’t clear with my question.
I have an alarm system in place and konnected pro in parallel to monitor zone status with Hubitat.
What I am looking for is a way to know the status of my alarm within Hubitat so that I can make rules that depend on that.
Got it, I understand what you’re asking now.
You’re using our Interface module to connect in-parallel with an existing alarm system. To monitor the armed/disarmed state of the alarm, you can program one of the programmable outputs on your traditional alarm to indicate armed/disarmed, then connect that as a zone to Konnected. I’ll appear as a contact sensor in Hubitat (on/open or off/closed) which you can use as a boolean logic for automations, routines.
I have a video demonstrating this with an Ademco VISTA panel here:
