OK, that was a bit painful, but I have Enable/Disable and Current Limits implemented using a mix of MQTT and HTTP services. The MQTT is much quicker to respond than HTTP so I am using MQTT wherever possible.
I moved all configuration to a package. If you want to try this, you’ll need:
- OpenEVSE on network with MQTT set up to publish to “openevse” base topic
- Place openevse.yaml into
config/packages
- Add these custom components to
config/custom_components
: - Load the package(s) by adding this to `config/configuration.yaml’:
homeassistant: packages: !include_dir_named packages
- Add secrets for
OPENEVSE_USER
,OPENEVSE_PASSWORD
,OPENEVSE_HOST
- You will also have to search
openevse.yaml
for my hostnameopenevse.local.
and replace it with your own hostname or ip. I haven’t gotten the URLs all parameterized yet.
I created a bug against the OpenEVSE WiFi service to hopefully improve the RAPI API for MQTT that will allow significant performance improvements.
I’m going to let this rest for a few days now since I have some other tasks that have been backup up the last couple days.