ha-SmartEVSEv3
SmartEVSEv3 connection for Home Assistant
Installation using HACS (recommended)
-
Install HACS if you have that not already running; you'd want it installed anyways to have access to all those wonderful custom_components....
-
From the main menu, select HACS, select Integrations, select Explore & Download repositories; enter "smartevse" in the search box, follow instructions to download.
-
Restart Home Assistant, and, very important and often forgotten, RESTART YOUR BROWSER! Really close your browser window and reopen it. F5 is not enough!
-
After restart, from the main menu, select Settings, select Devices & Services (or wherever "Integrations" are mentioned); you will probably see your SmartEVSE installed.
If not (because you don't have mDNS configured on your HomeAssistant Server, you have your SmartEVSE on a different vlan/network segment than your HomeAssistant Server, or other network mis/nonstandard configurations):
-
Select "add integration", enter "smartevse", and from then on follow instructions.
-
Restart Home Assistant, and, very important and often forgotten, RESTART YOUR BROWSER!
The main advantage of this installation method is that HomeAssistant will inform you of updates.
Alternative install
- Copy the folder
custom_components/smartevse/to your homeassistant config directory. - From here on follow goto 3. of the above HACS Installation method.
Configuration
After installation and restart your SmartEVSE device should be discovered. If not:
- Go to Settings
- Go to Integrations
- At the bottom right, click Add Integration
- Search for "smartevse-3"
- Fill in your 4 digit serial number (if the integration didn't find your SmartEVSE-v3 already!)
- Save
Known issues
-
For automatic discovery, your SmartEVSE device needs to be pingable by mDNS: ping SmartEVSE-xxxx.local where xxxx is the serial number of your device.
-
This will only work if your SmartEVSE device is
- a version 3 device,
- running version 1.5.2 or higher from the serkri firmware (https://github.com/serkri/SmartEVSE-3/releases), The original firmware has no rest-API implemented, and does not announce itself on the mDNS network, so that will not work.