Failing to integrate with Home Assistant after latest firmware update

Smart Home Integrations Home Assistant
,
1

After the latest firmware update, my alarm panel pro is failing to successfully connect to Home Assistant.
Below are the only logs I see in Alarm Panel Pro:

07:19:51 [W] [api.connection:1880]

Home Assistant 2025.7.1 (10.0.3.10): Reading failed CONNECTION_CLOSED errno=128

07:19:51 [W] [component:297]

api set Warning flag: unspecified

07:20:14 [D] [sensor:131]

‘Uptime’: Sending state 423.78799 s with 0 decimals of accuracy

07:20:15 [D] [sensor:131]

‘Heap Free’: Sending state 295220.00000 B with 0 decimals of accuracy

07:20:45 [D] [sensor:131]

‘Heap Free’: Sending state 295220.00000 B with 0 decimals of accuracy

07:20:51 [D] [api:160]

Accept 10.0.3.10

07:20:51 [W] [component:336]

api cleared Warning flag

07:20:51 [D] [status_led:030]

Restoring light state OFF

07:20:51 [D] [api.connection:1383]

Home Assistant 2025.7.1 (10.0.3.10) connected

07:21:14 [D] [sensor:131]

‘Uptime’: Sending state 483.79001 s with 0 decimals of accuracy

07:21:15 [D] [sensor:131]

‘Heap Free’: Sending state 294468.00000 B with 0 decimals of accuracy

07:21:21 [W] [api.connection:1880]

Home Assistant 2025.7.1 (10.0.3.10): Reading failed CONNECTION_CLOSED errno=128

07:21:21 [W] [component:297]

api set Warning flag: unspecified

07:21:45 [D] [sensor:131]

‘Heap Free’: Sending state 295200.00000 B with 0 decimals of accuracy

07:22:14 [D] [sensor:131]

‘Uptime’: Sending state 543.79102 s with 0 decimals of accuracy

07:22:15 [D] [sensor:131]

‘Heap Free’: Sending state 295200.00000 B with 0 decimals of accuracy

07:22:21 [D] [api:160]

Accept 10.0.3.10

07:22:21 [W] [component:336]

api cleared Warning flag

07:22:21 [D] [status_led:030]

Restoring light state OFF

07:22:21 [D] [api.connection:1383]

Home Assistant 2025.7.1 (10.0.3.10) connected

07:22:45 [D] [sensor:131]

‘Heap Free’: Sending state 294456.00000 B with 0 decimals of accuracy

07:22:51 [W] [api.connection:1880]

Home Assistant 2025.7.1 (10.0.3.10): Reading failed CONNECTION_CLOSED errno=128

07:22:51 [W] [component:297]

api set Warning flag: unspecified

07:23:14 [D] [sensor:131]

‘Uptime’: Sending state 603.79199 s with 0 decimals of accuracy

07:23:15 [D] [sensor:131]

‘Heap Free’: Sending state 295200.00000 B with 0 decimals of accuracy

07:23:45 [D] [sensor:131]

‘Heap Free’: Sending state 295200.00000 B with 0 decimals of accuracy

07:23:51 [D] [api:160]

Accept 10.0.3.10

07:23:51 [W] [component:336]

api cleared Warning flag

I have already rebooted the alarm panel, removed the integration from HA and re-added it.

HA discovers it right away via ESPHome but it fails to recognize any entities (contacts or sensors).

I also just found out Alexa fails to discover it now as well.

Any help is greatly appreciated.

2

Hmm, I’m not really sure here, I haven’t seen this exact error before. Did you update the firmware via the Konnected app or are you managing the firmware locally with ESPHome builder? What’s the ESPHome version?

Possibly try updating Home Assistant itself.

Alexa connectivity is a whole different mechanism. Alexa connects to the device from our cloud, so in order to use Alexa you must update the firmware from the Konnected app and make sure that Konnected Cloud is enabled in the firmware settings.

3

Hello, Nate. A pleasure to chat with you and thank you for taking your time to help me here.
I updated via the Konnected app.
I’m using the ESPHome integration with Home Assistant. Not exactly sure how to find the version of ESPHome. It just says Platinum Quality.

I’m using a LinknLink iSG Pro Max so I can’t just update HA. They push package updates which includes HA updates.

Ok. Not concerned about Alexa at this time then. Just need to resolve the issue with HA.
I may roll back the version to see if that fixes it.

Are there any logs you would like me to pull for you?

4

The ESPHome version that’s installed on the device should be shown on the device’s web page.

5

If by device you mean my iSG then we’re usually running N-3 so 2025.7.0 for ESPHome and 2025.7.1 for HA.
LinknLink has to test new HA versions with their proprietary firmware thus the delay in updates.

But if you’re talking about the version installed on the alarm panel then it is 2025.10.1 so that’s current.

6

**Update**
I refreshed the alarm panel using my Mac and it’s back to normal. I don’t know why updating through app used ESPHome version 2025.10.1 but now it’s using 2025.7.5.

7

**Update**
I refreshed the alarm panel using my Mac and it’s back to normal. I don’t know why updating through app used ESPHome version 2025.10.1 but now it’s using 2025.7.5.**

Update to the update

Turns out, when updating via phone app, it defaults to newest ethernet version so HA only sees the main board and not the entities. Once I flashed the board with my Mac and chose the older ethernet version, everything came back online again.

However, If I make a change via the iPhone app and submit that change, all entities die in HA but the main board is still visible. Restarting the alarm panel does not correct the problem. I have to flash it again which will bring it back to normal in HA.

8

It sounds like you just need to select the older Ethernet version in Settings > Network. If you have an Alarm Panel Pro v1.7 or earlier, select the v1.7 and lower option in the Ethernet type drop-down.

Updating the firmware via the Konnected app and via install.konnected.io is not exactly the same. The install.konnected.io site delivers a generic/stock firmware (the same firmware that the device ships with) with all the zones enabled and named generically like Zone 1, Zone 2, etc.

When you use the Konnected app to update the firmware, we build a customized specific firmware specifically for your device, based on the settings and configuration that you specify in the app. So, the device names, entity IDs, etc will be different than on the stock firmware. Also, our app-based firmware update tool always pulls in the latest ESPHome release at the time when you prepare the update.

So it sounds like something in your configuration when you’re going through the app flow isn’t correct for your device, and that’s causing the connectivity break after updating.

9

Yeah, I’ll have to be a bit more mindful the next time an update shows up on the app.
I’m just glad all is well now.
I appreciate your help and feedback on this matter.

Cheers.

10

I’ve the same issues. Upgrading to ESPHome Version 2025.10.3 (using the Konnected app) just breaks the integration with Home Assistant 2025.4.4. Home assistant cannot see the device and entities anymore…

22:15:56 [D] [api.connection:1383]
Home Assistant 2025.4.4 (192.168.101.243) connected
22:16:10 [D] [sensor:131]
‘Uptime’: Sending state 244.38400 s with 0 decimals of accuracy
22:16:11 [D] [sensor:131]
‘WiFi Signal RSSI’: Sending state -51.00000 dBm with 0 decimals of accuracy
22:16:11 [D] [sensor:131]
‘WiFi Signal %’: Sending state 98.00000 % with 0 decimals of accuracy
22:16:14 [D] [sensor:131]
‘Heap Free’: Sending state 214548.00000 B with 0 decimals of accuracy
22:16:26 [W] [api.connection:1880]
Home Assistant 2025.4.4 (192.168.101.243): Reading failed CONNECTION_CLOSED errno=128
22:16:26 [W] [component:297]
api set Warning flag: unspecified
22:16:44 [D] [sensor:131]
‘Heap Free’: Sending state 216308.00000 B with 0 decimals of accuracy
22:17:00 [D] [api:160]
Accept 192.168.101.243
22:17:00 [W] [component:336]
api cleared Warning flag

In my case I’m using WiFi… The only think that works is to flash back to the default firmware using USB.

11

I think it may be related to this:

Try updating your Home Assistant to 2025.10.x.

12

I have just encountered this today as well after updating esphome, home assistant version is 2025.6.1 docker image.