Want to bring attention to the upcomming "Konnected firmware is deprecated"

Hi everyone,

I want to bring attention to the upcoming deprecation of the current Konnected firmware. This warning has been showing up in my Home Assistant instance for months now, and as we get closer to version 2026.4.0, where support will be removed, I’m becoming increasingly nervous.

I’ve always tried to keep Home Assistant and its components up to date, as developers repeatedly recommend. But this is not one of those “just update and move on” situations. This is not a config tweak. This is a full hardware intervention that requires physically accessing the device, connecting a Windows machine, flashing new firmware, and then rebuilding everything from scratch in Home Assistant.

And before someone says this is “easy”, let’s pause for a second.

These are security devices. Alarm panels. They are usually installed in places that are not meant to be easily accessible, cabinets, basements, hidden spots, for obvious reasons. That alone already makes this process inconvenient for most users. Now add mobility limitations into the equation. In my case, using a wheelchair, physically accessing the device is simply not possible without asking for help. So yes, “easy”.

And then there’s the requirement to use a Windows machine. Believe it or not, not everyone uses Windows. Many of us run Linux systems, especially in environments like Home Assistant. So now, in addition to everything else, we also need to find or set up a Windows machine just to perform this update. Again, “easy”.

But it doesn’t stop there. We are instructed to take note of all automations, IDs, and configurations because everything needs to be recreated manually. The manufacturer even acknowledges this is a “tedious process”. What is not emphasized enough is that this is a security system. While you are doing all this, your alarm is effectively down. You are unprotected until everything is rebuilt and tested. For a security-related device, that is not a minor detail.

This is also described as a “free” update. It is not. At least not for me. I will have to hire someone to physically access the device, likely buy a specific USB data cable, because there are warnings about using the wrong one, and conveniently, they sell the correct one. Of course.

Also, if you happen to use certain zones, like zone 6, you need to disconnect them before the update. Just another small detail to add complexity and risk to the process.

So I respectfully want to ask, who is pushing for this deprecation? Is it Home Assistant developers? Is it the manufacturer?, both?.. And why is there no option to simply keep the current firmware supported for those of us whose systems are stable and working perfectly?

I don’t need this update. I didn’t ask for it, I don’t want or ask for “new features”. Yet I, and likely many others, will have to pay for it one way or another. Even if you do everything yourself and it goes perfectly, your time still has value. The constant claim that this is “free and easy” does not match reality.

From a user perspective, this feels very disappointing. Many of us supported these devices early on, trusted the ecosystem, and built critical systems around them. Being forced into this kind of disruptive process, especially for something related to security, does not feel right.

At the very least, if this is unavoidable, there should be a proper remote update path, or tools to automatically migrate configurations on the Home Assistant side, minimizing both effort and risk, that would be the responsible way…

I would really like to hear from Home Assistant developers or the manufacturer on this. How are we supposed to trust the platform and its ecosystem if changes like this are imposed without considering real-world constraints, especially for something as critical as a security system?

Thanks you for your time.

1 Like

Looks like the Konnected company is driving this change to ESPhome.

The Konnected integration is now marked as legacy as the company recommends to migrate to their ESPHome based integration.

And from their website the reason for the change is give as:

You can contact Konnected via their website. The HA devs are not responsible for this.

Someone might fork the core Konnected integration and release it as a 3rd party integration you can keep using.

1 Like

Tagging @heythisisnate from Konnected.

There’s a fork of the legacy integration here that you can maintain as a custom component for as long as you want:

Discussion here:

The ESPHome firmware and integration quality is better in pretty much every way. I recommend you just bite the bullet and do it.

1 Like

I took the plunge and flashed my Konnected Pro to ESPHome a few years ago. Has been rock solid and allowed flawless integration with HA. Seems like the way forward.

I did have to borrow a ladder and my sons laptop to get close enough with a UBS lead. And yes I had to simultaneously employ the USB “pinch” to get it to connect for long enough. :innocent: Now all flashes are OTA. Sweet. Well done @heythisisnate.

1 Like

Thank you for your comment. I’m reading about the “pinch technique” suggested by the manufacturer, who, by the way, acknowledges a defective batch. I can’t believe it. This is not a serious product. I will use this opportunity to replace it. In the meantime, I will use the community-maintained code.

I used the web-based tool (under Linux) to reflash mine to ESPHome some time ago. Really appreciated the change to ESPHome:

https://install.konnected.io/

No windows required.

1 Like

The ESPHome firmware might be better in some ways, but since the old firmware and integration already worked fine and didn’t need to do anything new, there wouldn’t really be any difference in having a “better” one.

We are in April and I’ve updated to Home Assistant version 2026.4.0.
The old Konnected add‑on, configured to run locally for now, continues to work without any issues and without requiring changes.