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
Limitations (and workaround)
The API of your Alfen Wallbox EV Charger currently allows only 1 active connection.
Therefore you need to pay attention while using this HA integration:
1: Logout from your 'Eve Connect' or 'MyEve'-app on your smartphone (or any other app using the API) when configuring this integration. As a side effect from not being logged out in the other app (=1 active connection), the integration won't show any values after configuring.
2: Your 'Eve connect'- app will show 'Waiting...' and 'Status unknown, please wait...', while HA is connected to your Alfen Wallbox.
As an easy workaround, we have provided two buttons to logout and login from the API in HA:
HTTPS API Logout
HTTPS API Login
After pressing the 'HTTPS API Logout' in HA, your 'Eve Connect'-app (or any other app using the API) will be functioning again.
You can always reconnect when needed.
The text was updated successfully, but these errors were encountered:
Limitations (and workaround)
The API of your Alfen Wallbox EV Charger currently allows only 1 active connection.
Therefore you need to pay attention while using this HA integration:
1: Logout from your 'Eve Connect' or 'MyEve'-app on your smartphone (or any other app using the API) when configuring this integration. As a side effect from not being logged out in the other app (=1 active connection), the integration won't show any values after configuring.
2: Your 'Eve connect'- app will show 'Waiting...' and 'Status unknown, please wait...', while HA is connected to your Alfen Wallbox.
As an easy workaround, we have provided two buttons to logout and login from the API in HA:
After pressing the 'HTTPS API Logout' in HA, your 'Eve Connect'-app (or any other app using the API) will be functioning again.
You can always reconnect when needed.
The text was updated successfully, but these errors were encountered: