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 "expected str" after fixing any issue in the data while creating a new Target Rate #863

Closed
2 tasks done
heisenberg2980 opened this issue May 5, 2024 · 2 comments
Closed
2 tasks done
Assignees
Labels
bug Something isn't working

Comments

@heisenberg2980
Copy link

heisenberg2980 commented May 5, 2024

Describe the bug

After making any mistake while introducing data on the screen and clicking submit, like in this example:

image

Even after fixing the issue the screen keeps returning the error "expected str", which is confusing as the data is already correct:

Screenshot 2024-05-05 232209

After closing the screen and adding the same data again the Target Rate is created, which means the data is correct.

Reproduction steps

  • Click ADD ENTRY in the Octopus Energy integration
  • Click Target Rate
  • Click Submit
  • Fill the data with some error (e.g. including uppercase letters in the name of the target)
  • Click SUBMIT
  • Fix the error in the data
  • Click SUBMIT again, and the error "expected str" appears, event the data is correct

Expected behaviour

If the data is correct the target rate should be created. It seems when the first error is returned the screen changes the behaviour and expects a string in the hours field instead of a number

Tariff Code

E-1R-AGILE-24-04-03-B

Integration Version

10.3.1

Home Assistant Version

2024.5.1

Fresh Install?

Not specified

Home Assistant Logs

N/A

Confirmation

  • I confirm that I cannot find my solution within the documentation
  • I confirm that I cannot find my solution within the FAQ
@heisenberg2980 heisenberg2980 added the bug Something isn't working label May 5, 2024
@BottlecapDave
Copy link
Owner

Thanks for raising this. I'll try and fix this for the next update.

@BottlecapDave
Copy link
Owner

This should now be fixed in v11.0.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Development

No branches or pull requests

2 participants