Skip to content

Missing API features from Zaptec cloud #192

@sveinse

Description

@sveinse

The Zaptec API fair use policy forbids integrators to use features that are not part of the official API. We have been using a couple of those in this integration, which we probably will have to remove. These are functions which users ask for.

The purpose of this issue is to collect a list of functionality we in the Zaptec Home Assistent community would like to request Zaptec to add to their official API. I can't promise they will listen, but we can attempt since the HA user base is quite large.

I'll update this description as items are added in the discussions.

  1. Push notifications

    • Polling is inefficient. Most requests doesn't carry any change of state, so they are wasteful.
    • Doing it too frequent puts strains on the cloud, doing it too infrequent gives delays in data update for the user.
    • We'd like a non-deprecated mechanism to subscribe to push notifications on data updates to give near-realtime updates of the data.
    • The gold standard in HA is local-push with no cloud involvement. This would be our preferred solution.
    • If that's not possible, the next best thing is cloud push.
    • Fast updates is especially important in HA where data changes might further be used as triggers in user automations
  2. Authorize from integration

  3. Permanent cable lock

  4. HMI brightness

  5. User UID

    • To use a more reliable key for storing the data and settings internally it would be better using the user UID
    • Accessing the user UID is not available
  6. Enable/disable ECO mode

Metadata

Metadata

Assignees

No one assigned

    Labels

    zaptecIssues about upstream Zaptec

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions