-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Number/time controls don't work #78
Comments
Interesting - was there a car plugged in when you saw this? |
Yes |
I haven't been able to replicate this, do you have any more details you can share? Any errors in the logs beforehand? Any general network issues? |
I have this other TypeError in the logs, no idea if it's related to the above and I can't reproduce it on demand like the other error:
Other than that, all I can say is that the error on api_client.py line 203 happens every time the car is plugged in and I try to change a number or time control. But, weirdly, all these controls work just fine if the car isn't plugged in. For example, I can change the target time from 7:00 to 7:30 with the car unplugged, and it will have stored this value next time I plug the car in. I can also change the target percentage, etc. But I get a TypeError and the value doesn't change if the car is plugged in. I tried disabling the VW API integration since it mostly doesn't work - didn't make any difference. I also don't have a tariff selected in the Ohme app as my tariff isn't listed. |
@nyordanov think I've figured it out. Would you mind trying out v0.8.3-beta.3? (beta instructions) |
Works for me now. Weirdly, the approve charge button didn't work when I tried it (was able to approve it in the Ohme app), but looking at the code I can't see how that could be related. I'll try again next time. Thanks a lot. With this change I can now have two automations:
|
Had the same problem, and with beta release it works now.... |
Beta release working for me too 🙌 One minor issue is that it's disabling the price cap, but I can't see anything in the logs so might just be something on Ohme's end. |
Cam here because I could not set the time - get this error with b3 Logger: custom_components.ohme.api_client Ohme API response error: /v1/chargeSessions/ohmeapp9oj6a/rule?enableMaxPrice=false&targetTs=1718306640000&enablePreconditioning=false&toPercent=100.0&preconditionLengthMins=None, 400; {"timestamp":1718298824487,"status":400,"error":"Bad Request","message":"Failed to convert value of type 'java.lang.String' to required type 'java.lang.Integer'; nested exception is java.lang.NumberFormatException: For input string: "None"","path":"/v1/chargeSessions/ohmeapp9oj6a/rule"} |
Thanks all for testing that, I'll release it as stable - apologies for not getting round to it sooner! |
Resolved by #81 |
What happened?
Changing the Target Percentage, Target Time, or Preconditioning results in this TypeError
To Reproduce
Drag the Target Percentage range input:
Error message:
Log Output
Home Assistant Version
Core 2024.4.3
Supervisor 2024.04.0
Operating System 12.2
Frontend 20240404.2
Integration Version
0.8.2
The text was updated successfully, but these errors were encountered: