edwardtfn
commented
10 months ago 09:40:30 – (ERROR) Automation - message first occurred at 15 January 2024, 17:06:20 and shows up 35 times Error while executing automation automation.lounge: extra keys not allowed @ data['meridiem']
This is odd. Are you sure you got this message after the update? I would expect that if the Blueprint was v4.2.x but ESPHome was still in an earlier version.
The blueprint has been
- copied from another working one - same
- Re created as a fresh blueprint - same
This shouldn't be an issue, but if you have change some entity name in your panel I would expect that error you mentioned. In order to fix that, try to remove your panel from the HA integrations (Settings > Devices and Services > ESPHome), then restart HA and add your panel again (if your panel was not detected automatically, click on Add integration button and then select ESPHome). Note: Don't remove your panel from ESPHome Dashboard, it is only from integrations in Home Assistant.
I dint think this is the blueprint but something about how the unit is flashing given update starts all the time at 75%.
This is expected when you are not changing to a different tft model. With just a version change, a big part of the TFT will be there already, so Nextion resumes from that point.
grigi
TFT Version
4.2.1
ESPHome Version
4.2.1
Blueprint Version
4.2.1
Panel Model
NSPanel EU Model
What is the bug?
Panel seems to flash but starts update at 75% on the progress bar. Then unknown service reported
Steps to Reproduce
Updated all panels. This is the last. It had an old version on it as it has not yet been installed.
Flashes over USB. On update it starts from 75% progress bar.
I then re flashed it by USB. Same. Wirelessly. Same. NsPanel Blank - Same.
On boot it reports begin on version 4.2.1 but the screen just has the time and temp on it.
The blueprint is reporting
Panel - Bar uses an unknown service The automation "Panel - Bar" (automation.panel_bar) has an action that calls an unknown service: esphome.barpanel_send_command_printf.
This error prevents the automation from running correctly. Maybe this service is no longer available, or perhaps a typo caused it.
To fix this error, edit the automation and remove the action that calls this service.
Click on SUBMIT below to confirm you have fixed this automation.
The blueprint has been
I dint think this is the blueprint but something about how the unit is flashing given update starts all the time at 75%. The strange thing it that it then reports on boot that it is on the most recent version.
Any suggestions ? All the other panels are fine and the process followed is identical for all of them,
Thank you
Your panel's YAML
ESPHome logs
Home Assistant logs