Does anyone know how to fix this. Been going on for hours.
I have a Alarm Panel Pro.
Thanks
Bill
There was an issue last night with our firmware build process – the instance apparently crashed and left some builds in a stuck state. Please reply or DM me with your device ID, or email help@konnected.io and we can manually un-stuck it for you.
Thanks @nate, it has been unstuck for me. But I can’t install the updated firmware over WiFi. My router has assigned an I.P to the panel, I can access the info page and even trigger the alarm siren manually. However, the firmware install gets stuck with waiting for device to come back online. See attached.
The blue light on the panel keeps flashing which suggests no network connection which isn’t the case.
Also, after installing via usb and log is being checked, nothing is printed after calling app_main(). Could it be related to the blue LED flashing?
Sometimes the network discovery doesn’t work perfectly after an update and the app can’t confirm that the update was completed. It doesn’t necessarily mean that the update failed.
The blue light blinking (on the ESPHome firmware) means that either it doesn’t have an IP address or there’s no native client connected (i.e. Home Assistant) so if you can get to the device via browser and see it in your router, then you know that it does have an IP. The blue light will continue to blink until you discover it in Home Assistant (or Hubitat, etc). If you are using our cloud integrations exclusively, and don’t have a local native platform, then disable the Local Native API in the firmware settings to avoid this.
If you can load the web page, you can manually check that the Project version is updated. Every time you build/update the firmware, the last digit should increment by one.
It doesn’t do the update though, after a couple of attempts I plug it into USB which is not convenient based on location it’s installed. I am currently using smartthings
If you’re using SmartThings only then you need to disable Local Native API in the firmware settings … otherwise the blue light will always continue blinking and the device will reboot every 15 minutes because no local client is connected.
Thanks @nate, would this then allow me to install firmware update from Konnected app over wifi?
You should be able to install the firmware update over WiFi regardless. That is a standard feature.
That isnt working for me currently. I’ll give it a go again and report back. But typically just get “waiting for device to come back online” and it doesn’t get installed.
Blue light is still flashing even with local native api disabled. The installation happens over wifi, just need the app restarted to get the confirmation
@novince-installer From what I can see on our back-end, you successfully updated to version 1.2.1.10 today at 15:05 UTC (11:05am US-Eastern time). Please provide a screenshot of the logs (from the device web page) or a capture of the device logs if you’re still having a problem.
@nate please see the attached logs from a few seconds ago. Is there a quick way to capture the logs to file?
logs.txt (2.6 KB)
@novince-installer Thanks for sending the logs snapshot. While the logs are incomplete, it’s showing me enough to understand what is most likely going on. The problem is not related to WiFi or the over-the-air updates at all.
Your device was initially registered in our North America cloud region, however it’s currently configured to connect to our EU cloud region. This mismatch is why it’s unable to reconnect after updating.
Assuming you are physically in Europe, to resolve, these are the steps:
- Tap on the device in the Konnected app, scroll down to the Danger Zone section and tap on Konnected Cloud and then De-register. This will de-register your device.
- Go to the menu > My Account and make sure your account is set to the EU region.
- Re-register the device in the EU region by tapping on Settings > Get started
- Set up your zones and configuration again, then Save & Continue > Build now
- Update once again with the updated configuration. You may not be able to update via WiFi if the device is still unstable because it cannot connect to our cloud. If that’s the case, you can perform the update via USB.
After doing the above steps, the device should successfully connect to our EU cloud region.
I have tried to deregister the device but it does not work. I have tried this previously and it failed. You can see it was registered in April but I purchased it in June. How is that so? I have raised a separate email about this. I suspect it was registered with a different account before purchase? Please see the attached screenshots. I’m really grateful for your assistance. Thank you.
The registration date in April is actually the date that it was pre-provisioned at our facility. The language in the app is confusing, I know. Last year we changed the way we QA and provision devices, and the app language just needs to be updated to be more clear. Your device is from batch number 2504 which indicates it was manufactured in April(04) 2025.
I will look into the de-registration error and get back to you.
@novince-installer In the meantime, I have de-registered your device for you. You can proceed to re-register it in the EU region using the steps outlined above and that should get you back up and running.
Thanks, I just registered again and the behaviour is still as before.
Time level Tag Message
20:38:27 [D] [light:065]
State: OFF
20:38:30 [V] [mqtt.idf:114]
Event dispatched from event loop event_id=7
20:38:30 [V] [mqtt.idf:117]
MQTT_EVENT_BEFORE_CONNECT
20:38:33 [V] [mqtt.idf:114]
Event dispatched from event loop event_id=0
20:38:33 [E] [mqtt.idf:167]
MQTT_EVENT_ERROR
20:38:33 [E] [mqtt.idf:169]
Last error code reported from esp-tls: 0x8008
20:38:33 [E] [mqtt.idf:170]
Last tls stack error number: 0x0
20:38:33 [E] [mqtt.idf:171]
Last captured errno : 0 (Success)
20:38:33 [V] [mqtt.idf:114]
Event dispatched from event loop event_id=2
20:38:33 [V] [mqtt.idf:130]
MQTT_EVENT_DISCONNECTED
20:38:33 [W] [mqtt:359]
Disconnected: TCP disconnected
20:38:33 [I] [mqtt:269]
Connecting
20:38:33 [D] [light:052]
'blue_status_led' Setting:
20:38:33 [D] [light:065]
State: ON
20:38:33 [D] [binary_sensor:026]
'Landing': New state is OFF
20:38:33 [D] [light:052]
'blue_status_led' Setting:
20:38:33 [D] [light:065]
State: OFF
20:38:33 [D] [light:052]
'blue_status_led' Setting:
20:38:33 [D] [light:065]
State: ON
20:38:33 [D] [binary_sensor:026]
'Kitchen': New state is ON
20:38:33 [D] [light:052]
'blue_status_led' Setting:
20:38:33 [D] [light:065]
State: OFF
20:38:38 [D] [sensor:104]
'WiFi Signal RSSI': Sending state -57.00000 dBm with 0 decimals of accuracy
20:38:38 [D] [sensor:104]
'WiFi Signal %': Sending state 86.00000 % with 0 decimals of accuracy
20:38:39 [D] [light:052]
'blue_status_led' Setting:
20:38:39 [D] [light:065]
State: ON
20:38:39 [D] [binary_sensor:026]
'Kitchen': New state is OFF
20:38:39 [D] [light:052]
'blue_status_led' Setting:
20:38:39 [D] [light:065]
State: OFF
20:38:47 [V] [mqtt.idf:114]
Event dispatched from event loop event_id=7
20:38:47 [V] [mqtt.idf:117]
MQTT_EVENT_BEFORE_CONNECT
20:38:50 [V] [mqtt.idf:114]
Event dispatched from event loop event_id=0
20:38:50 [E] [mqtt.idf:167]
MQTT_EVENT_ERROR
20:38:50 [E] [mqtt.idf:169]
Last error code reported from esp-tls: 0x8008
20:38:50 [E] [mqtt.idf:170]
Last tls stack error number: 0x0
20:38:50 [E] [mqtt.idf:171]
Last captured errno : 0 (Success)
20:38:50 [V] [mqtt.idf:114]
Event dispatched from event loop event_id=2
20:38:50 [V] [mqtt.idf:130]
MQTT_EVENT_DISCONNECTED
20:38:50 [W] [mqtt:359]
Disconnected: TCP disconnected
20:38:50 [I] [mqtt:269]
Connecting
20:38:55 [D] [light:052]
'blue_status_led' Setting:
20:38:55 [D] [light:065]
State: ON
20:38:55 [D] [binary_sensor:026]
'Kitchen': New state is ON
20:38:55 [D] [light:052]
'blue_status_led' Setting:
20:38:55 [D] [light:065]
State: OFF
20:40:50 [D] [light:052]
'blue_status_led' Setting:
20:40:50 [D] [light:065]
State: ON
20:40:50 [D] [binary_sensor:026]
'Kitchen': New state is OFF
20:40:50 [D] [light:052]
'blue_status_led' Setting:
20:40:50 [D] [light:065]
State: OFF
What is the Project version shown on the device’s web page?
project version is 1.2.1.11
You will need to rebuild and re-install the firmware. The version should reset to 1.2.1.1 because it’s reset again.