custom-components
Support for enable/disable Zaptec Eco Mode
Zaptec seems to offer a charge optimization service called EcoMode that can be enabled via API or via the Zaptec portal, which can be useful for some users.
To override the EcoMode one needs to disable it, it would be very useful to be able to do this via HomeAssistent.
To enable/disable, it seems one uses the API calls:
curl 'https://api.zaptec.com/api/installation/000000000-1111-2222-333333333333333' -X PUT
with data like: "EnabledFeatures": 12, "Feature_PowerManagement_EcoMode_DepartureTime": 360, "Feature_PowerManagement_EcoMode_MinEnergy": 10, "Feature_PowerManagement_EcoMode_DeliveryArea": 8,
It would be super to have this feature in the integration.
How would you envision using this from HA? There are a few additional parameters here, like DepatureTime, MinEnergy and DeliveryArea. Any suggestions on how to adjust those? Do you know what they represent?
The parameters could be entity number dials and the Eco mode could be a binary switch that enable and disable the function. If these additional parameters are not intuitively added as entities, it is possible to offer this as a service call. Then you need to use automation to activate/deactivate Eco mode.
Any thoughts?
I envision this would be used as a simple binary toggle only.
When Zaptec Eco mode is enabled you would need to disable it if you want to recharge the car. You could do this from the Zaptec App but it would be much nicer to have it in Homeassistant.
I don't really see the need to modfy the other dials and settings of Eco mode from HomeAssistant, it seems more like a one time config that can be done directly via Zaptec.
Using automation to trigger this would work well.
I second this, a simple toggle is a good solution for this.
The other parameters are for the Eco mode to know when to start charging, departure time for when you normally leave and need the car to be charged. MinEnergy is the minimum charged amount it has to be by that time. And the DeliveryArea is what pool you are part of for pricing. With those parameters the charger knows when to start charging to charge the needed amount, by the time you normally leave in the cheapest hours possible.
I have mine set to 8:00 departure, NO1 zone, and 45kWh(I drive a lot every day). That way I can always just put it in the charger when I get home, and know that the charger starts charging when it is cheapest, and that I get enough charge.
first thanks for developing this component. Then, I agree with the above. A simple toggle would be fantastic. In my case for example, I keep the ECO Mode activated 24/7 but sometimes I have the need to charge the car "now" and a toggle to deactivate the ECO Mode from HA would be very convenient. Thanks
Is it possible to enable/disable ECO Mode without specifying any parameters? I.e. what happens if the following is issued "EnabledFeatures": 12, without any of the Feature_PowerManagement_EcoMode_* parameters?` @peterlindqnet
I'm asking, because if these parameters must be supplied, we have to make entities/controls in HA for the value/setting of them. Alternatively implement them as service calls and let the user implement all the necessary values as needed. But that way it won't be a toggle.
In the zaptec app you can enable/disable without touching the parameters. They are mostly a set and forget thing.
In the zaptec app you can enable/disable without touching the parameters. They are mostly a set and forget thing.
Yes, but I need to know if that information is required to accompany the enable/disable ECO mode operation. Please remember, this is using an undocumented feature of the Zaptec portal, so we need to figure out ourselves what dials to turn.
To enable/disable, it seems one uses the API calls:
curl 'https://api.zaptec.com/api/installation/000000000-1111-2222-333333333333333' -X PUT
with data like: "EnabledFeatures": 12, "Feature_PowerManagement_EcoMode_DepartureTime": 360, "Feature_PowerManagement_EcoMode_MinEnergy": 10, "Feature_PowerManagement_EcoMode_DeliveryArea": 8,
What happens if this is done with only "EnabledFeatures": 12 is present? Is it possible to use without any other arguments?
Does "EnabledFeatures": 12 mean ECO Mode on? What is the corresponding command for disabling ECO Mode?
If I can help with testing anything, do let me know.
Enable / disable Eco mode would indeed be nice, but I would also love to be able to see the time charging starts and set the departure time.
Charging starts: because I never fully trust systems and want to be able to see what they're up to :-) Sometimes I have my car connected for a few hours and it still doesn't charge, but it is re-assuring then when I can see that the App says it will start at 22:00
Departure time setting: Since I work very irregular schedules, I'm constantly changing the start time in the app.
This feature is not a part of the API and Zaptec actively discourages us from doing reverse engineering of their API in their API fair use policy. On that ground I'm inclined to close this issue as won't fix.
However, I'm working on collecting a list of features we'd like to request Zaptec to add to their official API in #192. Should I put it on the list and refer to this issue? Would be nice with some input on how important is it to you to have the enable/disable Eco Mode feature controllable from HA. Can you explain the use-case, please? E.g. do you automate the enable/disable from HA?
This issue seems stale and I'd like to close it please. If there are any follow-up to the previous post, please do so. If not, I'm going to close it.