For some reason months ago I lost communication with my Konnected panels after years. I've removed them from Hubitat. Loaded the latest greatest Firmware and attempted to reload them into H. It apparently finds them when I use the Konnected device finder but I then get this :Error: Cannot invoke method getAt() on null object" no matter what I do. Just to test, I built a Pi Home Assistant. HA finds and uses the Konnected hardware just fine. I can also find the hardware using its internal URL on my network perfectly. It seems the problem is all with Hubitat. I do NOT want to move to HA but if it's the only way to get my alarm system working after weeks of futzing with Hubitat, I'll have to. PLEASE help me resolve this.
When you say “latest greatest”, do you know if you’re using the legacy drivers or the new espHome drivers? Since you mentioned HA, I’m guessing you’re referring to the latter.
If so, you would need to flash the boards using either with install.konnected.io and then configure your devices with the help of either the Konnected mobile app or the espHome Device Builder in HA.
Not saying that’s the only way to do it (always multiple ways to skin the cat), but it’s the way the Konnected documentation reads.
If you share more, I (and others) can probably help more.
1 Like
Thanks for the reply... So here is the long of it.
I actually tried both. ESP firmware first and then the legacy. I then went back to the ESP and that's what I connected to Home Assistant with and what remains on the boards now. I also tried to have only the Main controller board powered without the daughter boards. That did work either. I have a desktop with ethernet and also a laptop on the same wifi network with the boards. They both act the same as described earlier. They just search forever. I also tried firefox and chrome browsers just to be sure there wasn't something weird there. I'm really at a loss as to what could be going on. I love Konnected with Hubitat but if I can't figure this out I'm going to have to move away from one of them. The alarm system is the most important function of the system for me, of course.
And just FYI here are the drivers.
View Apps and Drivers
The apps and drivers listed below are managed by the Hubitat Package Manager.
- Alarm Panel (universal)
- Konnected Alarm Panel v1.0.2 (driver)
- Konnected Button Trigger v1.0.2 (driver)
The ESPHome version is 2026.2.4
Konnected Project Firmware Version is 1.1.3.4
Finally I ordered the PRO device from Amazon and they just delivered it. I plugged into ethernet and updated the firmware using the Konnected phone app. Hubitat will not see it either. It acts exactly the same as the wireless product I already had.
So the problem seems centered around Hubitat. It just refuses to find even the newest hardware and software whereas HA has no problem. The phone APP has no problem and I can link to any of the devices with their IP address on my desktop.
I am totally stumped. I hope you can offer some ideas. I don't even know what to try next.
Sorry, I love konnected, but I found the ESP updates to be less than wonderful.
I returned to the legacy - absolutely no issues.
Yet another Hubitat work-around required to get it working...
I went back to Platform Version at the old 2.4.1.177
I put the Legacy firmware back on all three 6 Zone legacy boards
Hubitat discovered all three boards and is communicating fine with them. Of course I had to put all the zone information back in but fortunately I had all that documented.
So I assume when I updated the platform past 2.4.1.177 is when everything went south.
Andy at Konnected worked with me the whole weekend trying to find a solution. A level of customer service Hubitat users can only dream of. Of several posts on this problem djh you're the only one to contribute anything. I don't believe I've ever seen help from HE employees on these forums. Plus I'm having more trouble all of the time with HE integrations.
I've bought some time with my alarm system now working on the old platform and I'm going to start moving everything to Home Assistant and immediately cancel my subscriptions with HE. I'm done...
This has got to be a problem with their custom app or driver (which Hubitat cannot support, as they did not write it, but are usually pretty helpful with if the author or someone can't figure it out but can provide specific details about what's happening). Has Konnected been able to reproduce your problem or troubleshoot based on specific information you can provide them, like the specific app or driver, line number (check Logs for the full error if you just see this in the UI), and what steps you took to get there?
I spent the weekend with Andy at Konnected. He did his best to figure it out and couldn't. He believes the problem is on YOUR end. As do I. Home Assistant works fine with either his Legacy or the ESP firmware. And Hubitat works on the old platform version. The only thing that doesn't work is when Hubitat, at a later firmware, is involved. I'm pretty convinced Hubitat is the problem.
I don't recall writing Hubitat. 
This is a user-to-user forum (although staff are generally also active).
This is interesting. There are sometimes bugs inadvertently introduced in new platform versions, but they are usually discovered in beta or shortly after release. Sometimes, developers are relying, intentionally or not, on undocumented methods that happen to have worked but changed. Without seeing their code or more about the error, it's hard to say more.
For example, as I mentioned, regarding this:
This kind of information would be helpful:
If custom code is throwing an error, the most logical place to start looking would be that custom code, in this case, likely one of their apps or drivers (but knowing this information would be necessary to say that to start).
This is not inconsistent with there being a problem with their Hubitat app or driver code, considering that each platform has its own integration.
3 Likes
Don't concern yourself further. I'm done with HE. Have a good life...
Complaints like this come up every once and and a while. In my mind when this happens, it is likely nobody knows the answer. It could be because they haven't seen this issue, or they simply aren't using this hardware. I assume that it is the latter in this case. I doubt there are more than a smattering of users of these devices, and you have to hope they are reading the forums, and are power users enough to try and help you.
That is completely false. Staff are very active here, but you cannot believe that they are reading every post from every user? That is especially true when you post in the custom apps/driver section where I would think that community developers would be posting, it likely gets less attention from staff than other sections of this forum.
I would suggest Andy reach out to staff here if he believes it is a Hubitat platform issue. If this is truly an issue, it surely is affecting all users of Konnected? Did anyone at Konnected mention that they know this is an issue with multiple users?
Which ones?
3 Likes
It’s possible that a Hubitat platform update created an issue with the Konnected integration.
But doesn’t Konnected provide the code for their integration with Hubitat? Hubitat staff can’t fix Konnected’s code for them (if that’s the issue).
I agree with @neonturbo that it probably would’ve been more helpful for Andy at Konnected to contact Hubitat staff or escalate to someone else at Konnected who can.
Maybe @nate can help.
3 Likes
Konnected's drivers for our newest ESPHome firmware platform do not support automatic discovery. Put in the IP address manually in the device preferences after creating. Documentation here:
4 Likes
All due respect, it can't be true that the problem is Hubitat because I use both the legacy Konnected drivers as well as espHome with HE. And they both work great.
Are they perfect? Nope. Is Hubitat perfect? Definitely not! But making Konnected work on Hubitat is eminently doable with both legacy and espHome. And I'd dare say they are the best, most stable and flexible options for bringing wired alarm sensors into an open-architecture home automation environment.
Having said that, I recognize you're very frustrated rn. Been there. Truly. But I'd offer you this: if you still want to give it a try, and are willing to slow down and kinda do it step-by-step, I am willing to help you. I can't problem solve effectively with you atm because, to do so, I'd need you to explain exactly what you're doing. It's possible the solve will be obvious once you illuminate your process at a layer or two more granular.
FWIW I don't pretend to know things others don't, but I've been through both of these processes extensively so I'm very familiar with the setup. Others around here have helped me so much, I'm just trying to pay it forward.
So LMK....
9 Likes
Apologies in advance, but just to clarify, have you heard of other users having this issue between Hubitat and Konnected?
It is said above that Andy at Konected couldn't find a solution to the OP's issue, and was (according to rcwatson) blaming Hubitat for this problem.
Can you confirm that there is an issue on the Hubitat side of things? If so, has anyone reached out to Hubitat Staff?
I think Hubitat and Konnected both have an interest in getting this fixed, IF it is indeed broken somehow. Your products are mutually beneficial to each other.
4 Likes
I found and reviewed the support thread with Andy from March 7~8.
In this case, there was no technical issue with Konnected and/or Hubitat. The issue was customer confusion -- @rcwatson seems to have assumed that the discovery app/mechanism from Konnected's original ("legacy") firmware still would work on our newer/modern platform built on ESPHome. It does not.
The architecture is completely different, and the original Konnected Hubitat app discovery does not work with our devices running ESPHome. You simply have to type in the IP address of the device once it's on your WiFi network.
The setup documentation for the new platform is here:
8 Likes
Thank you for looking into this.
I am glad it is only a misunderstanding how things work, and not some massive bug that nobody knew about that was affecting a whole set of users. Or worse yet someone did know about a bug, and couldn't (or wouldn't) fix it.
3 Likes
This topic is closed because the underlying issue was explained by @nate from Konnected in this post.
Users who run into this same issue should be aware that legacy firmware Konnected boards are discovered by Hubitat very differently than the ESP firmware boards. This difference is already indicated in Konnected's documentation.
