Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using deprecated API calls #125

Open
sveinse opened this issue Oct 18, 2024 · 2 comments
Open

Using deprecated API calls #125

sveinse opened this issue Oct 18, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@sveinse
Copy link
Collaborator

sveinse commented Oct 18, 2024

According to Zaptec API Documentation the request to api/installation/{id}/messagingConnectionDetails is deprecated and should be changed to /api/userGroups/{id}/messagingConnectionDetails

data = await self._account._request(
f"installation/{self.id}/messagingConnectionDetails"
)

@sveinse sveinse added the enhancement New feature or request label Oct 18, 2024
@antpata
Copy link

antpata commented Jan 10, 2025

When the api is actually removed then it should be an option to use SignalR like WebUi of the portal does. wss://api.zaptec.com/signalr?deviceId=ZAP******&access_token=

It is not an official API but should deliver the most critical information like: power, phase currents and operational mode.
The charging power seems to be the most up to date indication about charger state and it is about the only one that is needed to implement a stabile dynamic load management for a single charger.
It does not require any special configuration like service bus does and there are python libraries to handle the protocol.

@Hellowlol
Copy link
Collaborator

The real benefit is that you can use it even if you are not the owner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants