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
It seems that actions such as starting charging, changing charging current, etc. can behave differently depending on which API endpoint is used.
From my testing, the EV API endpoints appear to be much more reliable, while actions triggered through the smartdevices/actions endpoints sometimes lead to inconsistent behaviour or bugs.
Before I clean things up, I’d like to ask:
Is anyone still actively using the smartdevices/actions functionality, or would it be safe to remove/deprecate it in favour of the EV endpoints only?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi all,
It seems that actions such as starting charging, changing charging current, etc. can behave differently depending on which API endpoint is used.
From my testing, the EV API endpoints appear to be much more reliable, while actions triggered through the
smartdevices/actionsendpoints sometimes lead to inconsistent behaviour or bugs.Because of that, I’m considering switching the integration to use the EV-specific endpoints wherever possible:
https://smappee.atlassian.net/wiki/spaces/DEVAPI/pages/2803367937/Set+the+charging+mode+of+one+of+the+connectors+of+a+charging+station
Before I clean things up, I’d like to ask:
Is anyone still actively using the
smartdevices/actionsfunctionality, or would it be safe to remove/deprecate it in favour of the EV endpoints only?Any feedback is appreciated 🙂
All reactions