I have two Alarm Panel pro devices that I have been running successfully for over a year. All of a sudden, they seem to randomly enter a solid blue light status where I can no longer interface with the boards.
I thought it might be a failure to connect to WiFi, so I hard wired them, but that hasn’t changed anything.
They will run without issue for weeks or months, then either one or both of the boards will stop functioning. I typically notice when my piezo buzzer stops working.
Have you found a resolution to this yet? My alarm panel pro has been having the problem of disconnecting frequently too. I looked at the log file and it seems that there is a memory leak, I see frequent errors from networking code that cause the device to reboot. Often with the reboot, a connection is made again but sometimes the device fails to connect and ends up in the state of solid blue light. This is with the ethernet connection.
What version and platform of the firmware are you on? A few months ago there was a firmware update that addressed a memory leak in one of the upstream firmware libraries. This is Konnected’s firmware version 1.0.2.
Recently most firmware development has been going toward our newer ESPHome based firmware. You can install it at install.konnected.io. I’d be curious to see if you migrate from our original/legacy firmware to ESPHome if that fixes the issue for you.
No, but my recommended route to HomeKit is ESPHome firmware > Home Assistant > HomeBridge. Just set up Konnected with Home Assistant and install HA’s HomeKit Bridge integration then you can use HomeKit as a front-end to your alarm on Home Assistant.
Well I can’t afford the time to convert my home bridge system. Must be that bug fix didn’t make it into the homebridge build. Do you have an update planned for that version?
The firmware on the device is the same for all integrations. For the Alarm Panel Pro we currently support two firmwares, our original (legacy) Konnected firmware and the newer ESPHome-based firmware. I don’t think it’s accurate to say that the Hombridge firmware is defective. If there is an issue it would affect all integrations.
We do not officially support the Homebridge integration any longer, sorry. The original developer who wrote it seems to have abandoned the project, and unfortunately we do not have access to the NPM project to update it.
For integration with HomeKit (which is what you’re after anyway) there are better, more stable options today –
use the newer ESPHome based firmware to integrate with Home Assistant, and install the HomeKit integration to Home Assistant. In this setup HA takes the role of Homebridge to proxy to HomeKit
use the legacy firmware to integrate with Hubitat, and then proxy to HomeKit via Hubitat. Support for the newer ESPHome firmware for the Hubitat integration will be available soon.
Future – we’re looking to Matter to best support direct HomeKit integration in the future. No ETA yet. Matter moves slow.
I am sorry if my comments seem harsh but I look at the log file and see that the device is throwing exceptions and rebooting. I would call that a defect. Sometimes it does not re-establish an ethernet connection and as a result it remains offline. Here is a portion of the log file:
I (12020577) Sddp: Sending Periodic SDDP advertisement
I (13221577) Sddp: Sending Periodic SDDP advertisement
I (14422577) Sddp: Sending Periodic SDDP advertisement
[INFO 1713475249.849627, 40052] src/lfs/rest_endpoint.lua:14: HTTP Call: 200 state 1 zone 3
[INFO 1713475407.777873, 38548] src/lfs/rest_endpoint.lua:14: HTTP Call: 200 state -0 zone 3
I (15623577) Sddp: Sending Periodic SDDP advertisement
[INFO 1713475509.856629, 37572] src/lfs/rest_endpoint.lua:14: HTTP Call: 200 state 1 zone 3
[INFO 1713475515.932140, 35912] src/lfs/rest_endpoint.lua:14: HTTP Call: 200 state -0 zone 3
[INFO 1713475625.476719, 36512] src/lfs/rest_endpoint.lua:14: HTTP Call: 200 state 1 zone 3
[INFO 1713475629.546264, 36468] src/lfs/rest_endpoint.lua:14: HTTP Call: 200 state -0 zone 3
ERROR A stack overflow in task emac_rx has been detected.
Yes, this is a firmware crash. It probably has nothing to do with Homebridge specifically. What did you do to trigger and capture this crash? Are you able to consistently reproduce it?
Can you share the firmware version number, and also the hardware version number (on the front of the Pro board, underneath the logo) and batch number (back of the board, 4-digit number starting with 2, either on a white label or printed in small white numbers under the FCC notice)?
This morning when I connected to the panel it was in a tight reboot loop having to do with the rest endpoint, if I recall correctly. I hadn’t looked for a few weeks and it seems that the memory corruption had evolved. To get a more clear log, I re-installed the original firmware via the website and saved the config from homebridge.
The firmware version is (and was) 1.0.2.-0d6102
Hardware version Pro v1.7
Batch 2210
This is a refurb board I got in exchange for a board that had an ethernet failure. That board was running the same firmware and also exhibited the same connection loss issue with memory faults.
In the past I found the board would reboot after a day or so, I didn’t see a specific cause. I have a usb connection to log output and will watch for the uptime to reset. I’ll send you the log when it does. There is an open support ticket #2597600923 that I can attach it to if that’s ok.
A reboot just happened, I posted the entire log on the support ticket. Here is a snippet:
I (14423177) Sddp: Sending Periodic SDDP advertisement
[INFO 1715366473.208621, 47580] src/lfs/rest_endpoint.lua:14: HTTP Call: 200 state 1 zone 3
[INFO 1715366491.537439, 47388] src/lfs/rest_endpoint.lua:14: HTTP Call: 200 state -0 zone 3
I (15624177) Sddp: Sending Periodic SDDP advertisement
E (16202857) esp.emac: no mem for receive buffer
ERROR A stack overflow in task emac_rx has been detected.
