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
Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
In addition to being able to service.set_max_current it would be great to also have an option like service.set_lines (1 or 3 phases).
Describe alternatives you've considered
Setting it manually via go-e app.
Additional context
Would give a good effort if you are using it in combination with PV. Switching to "one line mode" allows charging with lower power like 1000W (1 line) if there is not enough PV energy available, and dynamically increase up to 22 kW (3 lines), usually done via HA automation or Node Red.
Thank you!
Edit: I guess the params are not available in API v1 but in v2, maybe pwm/lfspt/fsptws/spl3.
The text was updated successfully, but these errors were encountered:
I'm not a programmer or similar :-) butAs a workaround, you can create a command_line switch in HA to switch the between phases. You need to activate http v2 api in the app.
Its far away from a perfect solution, but it works nearly for my need right now.
In the next release, you can create a manual button entity I think, that works better as a switch.
Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
In addition to being able to service.set_max_current it would be great to also have an option like service.set_lines (1 or 3 phases).
Describe alternatives you've considered
Setting it manually via go-e app.
Additional context
Would give a good effort if you are using it in combination with PV. Switching to "one line mode" allows charging with lower power like 1000W (1 line) if there is not enough PV energy available, and dynamically increase up to 22 kW (3 lines), usually done via HA automation or Node Red.
Thank you!
Edit: I guess the params are not available in API v1 but in v2, maybe pwm/lfspt/fsptws/spl3.
The text was updated successfully, but these errors were encountered: