I have an Alarm Panel Pro board 1.8 that its installed and working well. I noticed that ESP Hoke Dashboard and the Connected app have the wrong IP address for the device and tried to correct by re-flashing the board. No problem flashing, and removed the board from ESP Home Dashboard. When trying to adopt the new device in ESP Home Dashboard, I receive the following error:
INFO ESPHome 2024.5.5
INFO Reading configuration /config/esphome/konnected-98e674.yaml…
WARNING GPIO2 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See Frequently Asked Questions — ESPHome
WARNING GPIO15 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See Frequently Asked Questions — ESPHome
WARNING GPIO12 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See Frequently Asked Questions — ESPHome
WARNING GPIO5 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See Frequently Asked Questions — ESPHome
Failed config
More context, openapi-alarm-panel.yaml has the following error: ‘esphome’ section missing from configuration. Please make sure your configuration has an 'esphome: ’ line in it.
I have a remaining issue in that the alarm sensors all say unavailable from ESPHome. Door beep from the Piezo stopped working as well. Ping shows no data loss.
The board keeps cycling between available and unavailable. Some Logbook entries:
Alarm Panel Pro Firmware turned off
5:49:32 PM - 13 seconds ago
Alarm Panel Pro Restart became unavailable
5:47:12 PM - 3 minutes ago
Alarm Panel Pro Device ID became unavailable
5:47:12 PM - 3 minutes ago
Alarm Panel Pro Ethernet IP Address became unavailable
5:47:12 PM - 3 minutes ago
Kitchen Door became unavailable
5:47:12 PM - 3 minutes ago
Alarm Panel Pro 98e674 Warning Beep became unavailable
5:47:12 PM - 3 minutes ago
Alarm Panel Alarm 2 became unavailable
5:47:12 PM - 3 minutes ago
Alarm Panel ProFirmware became unavailable
5:47:12 PM - 3 minutes ago
Alarm Panel Pro ESPHome Version became unavailable
5:47:12 PM - 3 minutes ago
Alarm Panel Pro 98e674 Alarm 1 became unavailable
5:47:12 PM - 3 minutes ago
Kitchen Motion became unavailable
5:47:12 PM - 3 minutes ago
Kitchen Glass became unavailable
5:47:12 PM - 3 minutes ago
…
Alarm Panel Pro Ethernet IP Address changed to 192.168.1.XX
5:43:04 PM - 9 minutes ago
Alarm Panel Pro ESPHome Version changed to 2024.6.1
5:43:04 PM - 9 minutes ago
Alarm Panel Pro Device ID changed to XXXX
5:43:04 PM - 8 minutes ago
Alarm Panel Pro 98e674 Alarm 2 turned off
5:43:04 PM - 8 minutes ago
Alarm Panel Pro 98e674 Alarm 1 turned off
5:43:04 PM - 8 minutes ago
Alarm Panel Pro 98e674 Warning Beep turned off
5:43:04 PM - 8 minutes ago
Kitchen Glass cleared (no vibration detected)
5:43:04 PM - 8 minutes ago
Kitchen Door was closed
5:43:04 PM - 8 minutes ago
The board’s LED flashes blue when sensors become unavailable.
Steve
Yes @nate , connected via Ethernet. I flashed the board as 1.8 Ethernet and the physical_registers code is in the alarm-panel-pro-v1.8-ethernet.yaml. Overnight logs are attached.
Am considering re-flashing to WIFI and see what happens, unless you have other ideas?
Steve logs_konnected-98e674_logs-2.txt (435.4 KB)
Even though this says “hardware” what it really means is the Konnected package version. The Ethernet fix update for ESPHome 2024.6 was included in version 1.1.3. The current version is 1.1.4.
Your package is a couple revs out of date, so it’s not pulling in the Ethernet PHY config. That is the problem.
When you adopt in ESPHome dashboard, a YAML config file is generated for you. Then when you install/update from ESPHome dashboard, a new firmware is built using that YAML config. I need to see the YAML config that you are using to install/update the firmware on the Pro:
Looks right.
It may have cached an older version. Click on clean build files to force it to refresh. You will probably have to re-flash with USB because the OTA update is unlikely to work without the correct Ethernet config.
Just re-flashed, there was no option for clean build files. There is a ‘reset device’ option when you click on logs, I didn’t do that. Will let you know how it goes.
Steve
The clean build files option is in ESPHome dashboard (see my screenshot above). What this does is clears out the cached build dependencies for ESPHome that are stored on your HA device filesystem.
I’m pretty sure what happened here is that an older version of Konnected’s firmware config packages were cached on your system. So that’s why after adopting it and building/installing from ESPHome dashboard the project version was downgraded.
If you don’t want the responsibility of maintaining your own firmware config and dependencies, you can use the Konnected app to manage firmware updates and customizations instead of in ESPHome. We’ve spent a lot of time and effort building a simple firmware management interface in the Konnected app, so I’d encourage you to try it.
