Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ESPHome 2023.7 - Error at firmware update #245

Closed
ghost opened this issue Jul 19, 2023 · 24 comments
Closed

ESPHome 2023.7 - Error at firmware update #245

ghost opened this issue Jul 19, 2023 · 24 comments

Comments

@ghost
Copy link

ghost commented Jul 19, 2023 •
edited by ghost
Loading

With ESPHome 2023.7 the following error occurs.
It seems, the configuration in your repository needs to be changed.

INFO ESPHome 2023.7.0 
INFO Reading configuration /config/esphome/tagreader-7c1293.yaml... 

Failed config 

switch.template: [source /config/esphome/.esphome/packages/fa8076cc/tagreader.yaml:56] 
platform: 
template name: TagReader Buzzer Enabled 
id: buzzer_enabled icon: 
mdi:volume-high 
optimistic: True 
The restore_state option has been removed in 2023.7.0. Use the restore_mode option instead.
restore_state: True 
entity_category: config 

switch.template: [source /config/esphome/.esphome/packages/fa8076cc/tagreader.yaml:63] 
platform: template 
name: TagReader LED enabled 
id: led_enabled icon: mdi:alarm-light-outline 
optimistic: True 
The restore_state option has been removed in 2023.7.0. Use the restore_mode option instead.
restore_state: True 
entity_category: config
@Masterz69
Copy link

Reason is:

esphome/esphome#5106
This removes restore_state on a template switch which was replaced with restore_mode on the switch core config and having both is just confusing.

@howesey2k
Copy link

So what do we need to do to update it?

Many thanks.

@Masterz69
Copy link

Remove restore_state from template switches.
Specify restore_mode if not defined yet.

@jakevis
Copy link

jakevis commented Jul 19, 2023

yeah running into this issue as well - cant work out how to override the template - but I guess ideally this needs to be updated in https://github.com/adonno/tagreader/blob/master/tagreader.yaml

@howesey2k
Copy link

I agree for it to be looked at. I've deleted the references to restore_state and reinstalled it. Seems to be working but getting an error "Component pn532 took a long time for an operation"
Could this be looked at? Many thanks

@Masterz69 Masterz69 mentioned this issue Jul 19, 2023
Open
@renewoensdregt
Copy link

there is already a pull request to update this. Once approved it should be fixed.
#247

@monstergubl
Copy link

hey got the same problem did you get a solution ?

@howesey2k
Copy link

Hi, the firmware issue has been resolved. There has been an update in the yaml. I just copied and pasted and it's working again.

@waazdakka
Copy link

Hello,
I just flashed again my tagreader with the actual yaml but I still get the
"Component pn532 took a long time for an operation (0.10 s).
[W][component:205]: Components should block for at most 20-30ms." error.
Don't know what to change to make this error disappear :'(

@howesey2k
Copy link

howesey2k commented Aug 19, 2023 via email

@titis14
Copy link

titis14 commented Aug 26, 2023

Hi,
I still get the error even though I have the latest version.

@howesey2k
Copy link

howesey2k commented Aug 26, 2023 via email

@titis14
Copy link

titis14 commented Aug 27, 2023

This mistake.
[11:50:41][W][component:204]: Component pn532 took a long time for an operation (0.10 s).
[11:50:41][W][component:205]: Components should block for at most 20-30ms.
For a while now my tagreader has not been able to read badges. I made a topic here but no one replied.
#241
I don't know if it's related to this error. I have this project and for several months at my club people can no longer deactivate the alarm easily.
Thanks

@howesey2k
Copy link

howesey2k commented Aug 27, 2023 via email

@titis14
Copy link

titis14 commented Aug 27, 2023

On ESPHome I clicked on edited and I put the new yaml then installed by wifi.

@howesey2k
Copy link

howesey2k commented Aug 27, 2023 via email

@titis14
Copy link

titis14 commented Aug 27, 2023 •
edited
Loading

No, I didn't do it through a file editor. On Home Assistant I use Studio Core Server, would you tell me which file to modify? Thanks

EDIT: I found the file but I don't understand why I only have 15 lines of the yaml file, I had to have all the ESP demon code.

@howesey2k
Copy link

howesey2k commented Aug 27, 2023 via email

@titis14
Copy link

titis14 commented Aug 27, 2023

Thank you in this way I am well in v1.4 :(

@howesey2k
Copy link

howesey2k commented Aug 27, 2023 via email

@titis14
Copy link

titis14 commented Aug 27, 2023

I think I know why it doesn't work anymore. Indeed I had to use the smart home junkie file.
dashboard_import:
package_import_url: github://smarthomejunkie/tagreader/tagreader.yaml
In my editor I see that the file is not up to date.
I modified the file but when I want to validate it in ESPHome I have errors. I also have 2 folder for the tag.
Is there a way to erase everything and start from scratch?
I do all this remotely because I don't have the ESP near me.

@howesey2k
Copy link

howesey2k commented Aug 27, 2023 via email

@titis14
Copy link

titis14 commented Aug 27, 2023

Ok thanks you have already put on a track.
I'm going to do a new ESP and we'll see.

@howesey2k
Copy link

howesey2k commented Aug 27, 2023 via email

@ghost ghost closed this as completed Oct 15, 2023
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@waazdakka @jakevis @Masterz69 @titis14 @renewoensdregt @howesey2k @monstergubl