You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened?
When using v1 of the ohme app, I was able to adjust the charge percentage of a single schedule by changing the target Percentage in home assistant. Now changes are not related
Expected behavior
When the target charge % is adjusted in home assistant I was expecting it to change in one of the schedules in the ohme V2 app. The only change currently is to update what the % is set to in the app, which is reflected in hass
Home Assistant Version
2024.7.0 Integration Version
1.0.0
The text was updated successfully, but these errors were encountered:
From the documentation, the number and time inputs (percentage, price cap, time and pre-conditioning time) act as follows:
If in a charge session, these change the active charge. If disconnected, they change your first schedule
The exception to this is if "Never update an ongoing session" is enabled in the configuration screen, in which case the first schedule will always be updated regardless of whether you are in a charge.
Unfortunately when I change the amount before approving the charge, the % from the routine is used not the target set in hass. If I change the target after approving the charge it adjusts the session. For what I need it to do I can adjust my automation but didn't feel like correct behaviour
What happened?
When using v1 of the ohme app, I was able to adjust the charge percentage of a single schedule by changing the target Percentage in home assistant. Now changes are not related
Expected behavior
When the target charge % is adjusted in home assistant I was expecting it to change in one of the schedules in the ohme V2 app. The only change currently is to update what the % is set to in the app, which is reflected in hass
Home Assistant Version
2024.7.0
Integration Version
1.0.0
The text was updated successfully, but these errors were encountered: