Replies: 1 comment
-
Did some deeper digging, the ocpp.log is empty, changed the Adress of the backend to http://10.129.32.21 as I assumed there would be an IPv6 issue with the OCPP implementation on the ABL, with no change (entities n/a). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am not really coming forward using the documentation, as I probably have some basic issues to understand how to get OCPP working using HACS/Home Assistant
I installed and restarted via HACS, after that I install and configure the integration (comes after configuring the charge station).
If I understand it right, than the charging station will push towards Home Assistant, right?
So therefore I did the following settings on my ABL eMH3 (LAN/10.129.32.60)
ABL station / connectivity OCPP / and enter there:
OCCP version 1.6
Adress (URL) of backend: http://homeassistant.local
Charge Box-ID for the station: ABL_10202031 (kept standard setting, which is later reflected )
local port: 9000
local path: /ChargePoint
Password for authentication (I leave it blank)
After storing these values I restart (Hard Reset, complete new start of OS & Applications).
On the installation dialog on Home Assistant I do not change anything and everything will be found/installed w/o any issues (2 devices: central & charger and 31 entities), but the status for all entities found will be not available (red exclamation mark !) at the status column.
What is wrong? The local path? What is the local path on Home Assistant?
Or is it that ABL eMH3 (dual port charging station, here a Master eMH3 (Dual Portal) with an additional eMH3 (Dual Port) as slave) is not supported?
Thanks for any feedback/hints
Beta Was this translation helpful? Give feedback.
All reactions