Skip to content

Support for enable/disable Zaptec Eco Mode #153

Closed

Description

@peterlindqnet

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.

Activity

  1. sveinse commented on Jan 5, 2025

    @sveinse
    Collaborator

    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?

  2. peterlindqnet commented on Jan 7, 2025

    @peterlindqnet
    Author

    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.

  3. zarilion commented on Jan 7, 2025

    @zarilion

    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.

  4. bertussino commented on Feb 4, 2025

    @bertussino

    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

  5. sveinse commented on Feb 5, 2025

    @sveinse
    Collaborator

    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.

  6. zarilion commented on Feb 5, 2025

    @zarilion

    In the zaptec app you can enable/disable without touching the parameters. They are mostly a set and forget thing.

  7. sveinse commented on Feb 5, 2025

    @sveinse
    Collaborator

    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?

  8. TheGabeMan commented on Feb 12, 2025

    @TheGabeMan

    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.

  9. sveinse commented on Jul 14, 2025

    @sveinse
    Collaborator

    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?

  10. sveinse commented on Nov 10, 2025

    @sveinse
    Collaborator

    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.

  11. rhammen commented on Jul 15, 2026

    @rhammen
    Contributor

    cc @sveinse @peterlindqnet @zarilion @bertussino @TheGabeMan

    There's clearly real demand here — several people in this thread want Eco
    Mode controllable from HA. At the same time, I agree with the reasoning
    upthread that this shouldn't be built into the integration directly, given
    it relies on undocumented API surface and Zaptec's API fair-use policy.

    Starting from those two points, I put together an alternative on my fork: a
    generic, minimal-viable-product-style zaptec.raw_api_request service. It
    sends a user-specified path/method/data straight through the
    integration's authenticated session — no modeling, no validation of the
    endpoint or payload. All responsibility for what you send is on you, the
    user; the integration just transports it.

    Branch: https://github.com/rhammen/zaptec/tree/feature/raw-api-request-service
    (It's stacked on an unmerged refactor PR of mine, #402, so you'll get that
    too if you check it out — shouldn't affect anything here, just flagging it.)

    Full docs and usage examples:
    https://github.com/rhammen/zaptec/blob/feature/raw-api-request-service/DEVELOPMENT.md#raw_api_request-service

    To be clear: I have not verified this myself against the live API. I
    don't have Eco Mode to test against. The example below is the payload
    discussed earlier in this thread, reproduced as-is — @sveinse's open
    questions upthread (does EnabledFeatures: 12 alone toggle it without the
    three Feature_PowerManagement_EcoMode_* fields, and what turns it back
    off) are still open.

    If you'd like to try it, both work:

    Developer Tools → Actions (GUI): search for "Raw API request", pick
    your installation device, fill in path, method, data.

    YAML / automation:

    action: zaptec.raw_api_request
    data:
      device_id: <your installation device>
      path: "installation/{id}/update"
      method: PUT
      data:
        EnabledFeatures: 12
        Feature_PowerManagement_EcoMode_DepartureTime: 360
        Feature_PowerManagement_EcoMode_MinEnergy: 10
        Feature_PowerManagement_EcoMode_DeliveryArea: 8

    If anyone here has Eco Mode on their account and is willing to experiment
    (ideally a GET on installation/{id} first, to see the current field
    values before/after), reporting back in this thread would settle the open
    questions for good.

    Before I consider opening a PR against this repo, I'd like some feedback
    that it actually works and sufficiently solves the feature request this
    issue is asking for — so please do try it out and let me know either way.

  12. sveinse commented on Jul 24, 2026

    @sveinse
    Collaborator

    How does this relate to the Zaptec API fair use policy? Am I correct that this offers a "you're on your own"-approach where we offer the ability to do it, but users should not (as they will violate the policy)? If this is the case, I'm skeptical to adding it. We recently removed a lot of these additions after requests from Zaptec.

    I am not a lawyer so I don't know how much the fair use policy can be bypassed under consumer-focused "fair use". I agree that this policy is strangely and disappointingly rigid. E.g. when their own webapp use certain endpoints, such as EcoMode, which runs from user's own browser. For Zaptec, it should not matter if the requests comes from a "valid" webapp or our Zaptec integration, but they've excluded it by means of policy.

    Quote from the Zaptec API Fair Use Policy:

    Use of Documented APIs Only: Integrators must only use officially documented and supported API endpoints. Use of internal, undocumented, or reverse-engineered API calls such as those derived from the Zaptec Portal or other internal tools is strictly prohibited. This ensures system stability, security, and consistent support for all integration partners.

    I think a much better approach would be to enquire the requests to Zaptec. It's their API which is lacking the features, not our Zaptec integregration. The more that ask, the more they hear it.

  13. steinmn commented on Jul 24, 2026

    @steinmn
    Contributor

    I'd also like to avoid anything even attempting to circumvent the API fair use policy. I don't really care what can be argued from a legal standpoint, I just prefer to work with the Zaptec devs rather than against them.

    My suggestion would be to add a "Features missing from the API"-section under/next to Known issues in the readme, linking to #192 and encouraging users to forward their feature-requests to Zaptec, and then closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions