-
Notifications
You must be signed in to change notification settings - Fork 29
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
cannot add integration anymore v0.25.0 #65
Comments
I have Theo same Error |
same here |
I've upgraded from 0.24.1 to 0.25.0 (so the integration was upgraded not freshly installed) and I have the following error during the initialization of the integration:
When trying to edit the configuration in the backend, following error message is shown: The response of the related XHR request looks the following: The failed flow initialization is logged in the backend as well:
The problems are related to the recent changes regarding |
Please test version 0.25.1 |
@cathiele now it works - can you please advise how the factor should be used (guess it should be a factor, so 1.07 would increase the read value by 7%)? the input box during setup is kinda bugged |
@cathiele Integration itself works now and initializes correctly, but the config flow (in my case after upgrading, not a fresh install) is still broken. I'll have a look at this tonight. |
finally i had time to fix it. 0.25.2 should have a working config flow. Older Chargers, like mine V2 charger, have incorrect power calculations. mine is way to low. So with setting the correction factor to values other than 1.0 you can correct the api values by a factor. the uncorrected values are still available as the original attributes. |
After the update to version v0.25.0 I cannot add the integration anymore
go to new integration
try to add goe integration
fill out everything
press enter
Additional context
error message:
User input malformed: expected float for dictionary value @ data['correction_factor']
The text was updated successfully, but these errors were encountered: