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.

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

Error after upgrade to v0.2.7 - fast_scan_count not defined in Config #165

Closed
aaronwatson opened this issue Jun 9, 2022 · 7 comments · Fixed by #163
Closed

Error after upgrade to v0.2.7 - fast_scan_count not defined in Config #165

aaronwatson opened this issue Jun 9, 2022 · 7 comments · Fixed by #163

Comments

@aaronwatson
Copy link

I have upgraded to v0.2.7 and after reboot I see the following errors:

2022-06-08 18:00:59 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry 192.168.30.120 for lennoxs30
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 339, in async_setup
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/lennoxs30/init.py", line 252, in async_setup_entry
fast_poll_count = entry.data[CONF_FAST_POLL_COUNT]
KeyError: 'fast_scan_count'
2022-06-08 18:00:59 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry 192.168.30.122 for lennoxs30
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 339, in async_setup
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/lennoxs30/init.py", line 252, in async_setup_entry
fast_poll_count = entry.data[CONF_FAST_POLL_COUNT]
KeyError: 'fast_scan_count'

@aaronwatson
Copy link
Author

I was able to fix this issue by following the info found here:

#147 (comment)

The "fast_scan_count" and "timeout" entries were missing.

@PeteRager
Copy link
Owner

Interesting, I had thought I had that one fixed :-(.

What version did you upgrade from?

@aaronwatson
Copy link
Author

I'm not sure which version it was, sorry. Any way to tell from the logs? I know it was earlier than 0.2.0.

@PeteRager
Copy link
Owner

That’s helpful. Prior to 0.2.0 the configuration was in YAML. It looks like the migration script would not add these new parameters in that were introduced in 0.2.3 and hence the code would encounter the error you saw.

Does that fit your scenario?

@aaronwatson
Copy link
Author

Yes, that sounds like the exact issue I encountered. Thanks for your work on this project. It is extremely useful.

@PeteRager
Copy link
Owner

Cool, I’ll get that fixed so it doesn’t get the next person that comes along from the upgrade. Release should go out within next week and I’ll close this issue then.

@PeteRager PeteRager changed the title Error after upgrade to v0.2.7 Error after upgrade to v0.2.7 - fast_scan_count not defined in Config Jun 10, 2022
PeteRager added a commit that referenced this issue Jun 10, 2022
@PeteRager PeteRager linked a pull request Jun 10, 2022 that will close this issue
@PeteRager
Copy link
Owner

Changes have been merged and release will go out tomorrow. You do not need to upgrade unless you want.

https://github.com/PeteRager/lennoxs30/releases/tag/v0.2.8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants