Home Assistant intergration

[jeremypoulter]

The current Home Assistant integration is a bit outdated and with the new features in both OpenEVSE and Home assistant we can do better:

• Auto discovery
• Setup via Home Assistant UI
• Real time updates via web socket
• Support energy API
• Use newer OpenEVSE APIs

Sensors

• Current
• Voltage
• Power?
• Session Energy
• Total Energy
• Status
• Temps
• Vehicle connected
• Rssi

Actions

• Max current
• Charge current
• Manual Override
• Schedule
• Divert mode

https://developers.home-assistant.io/docs/creating_component_index

Update: @firstof9 has put some great work into a Home Assistant intergration: https://github.com/firstof9/openevse

[andriuskr]

Is there any ETA for updating integration? Trying to accomplish charging current regulation in home assistant by whole home usage (limited home electricity input) for a while now.

[jeremypoulter]

Probably not going to be till next month, but no promises...

[doppiaemme]

check this out for the time being:

https://gist.github.com/TonyApuzzo/c0fe22458d4dae0effb47b951b464484#file-openevse2-yaml

[jeremypoulter]

https://github.com/cathiele/homeassistant-goecharger

[jeremypoulter]

https://github.com/tmjo/charger-card

[drobtravels]

Hi @jeremypoulter, I'm very interested in collaborating with you to help get this out, as much as my limited time / skillset will allow. I don't have much python experience, but have managed to create a simple Home Assistant integration in the past.

OpenEVSE seems to align well with Home Assistant's ethos (full local control) so I would expect this to be a popular integration.

Do you have a WIP fork yet we could collaborate on?

I'm also curious if you have thoughts on how to accomplish these two items. I believe this may require updates to the OpenEVSE wifi firmware?

• Auto Discovery
• Real time updates via web socket

[jeremypoulter]

Sorry, I have not progressed more than creating the ticket and doing a bit of research. Would be great to get some assistance on this however.

Auto Discovery

This should be fairly simple via mDNS, Home Assistant already supports this as a discovery type. To make it a little simpler we may need to add a few records to help filter the devices, similar to what I have done in EmonESP.

Real time updates via web socket

Everything that is sent over MQTT is also sent to a websocket to update the web UI so all that is needed should be in place already.

Also note I am working on documentation of the API via #245 / https://openevse.stoplight.io/docs/openevse-wifi-v4

[jeremypoulter]

Also on the mDNS/Zeroconf discovery, see https://developers.home-assistant.io/docs/creating_integration_manifest#zeroconf

[jeremypoulter]

As I had looked it up, I added the required mDNS tweaks, #260

[firstof9]

I've been working on this a bit myself:
https://github.com/firstof9/openevse

[omriasta]

I've been working on this a bit myself: https://github.com/firstof9/openevse

This integration is great! Exactly what I was looking for. It would be great if you could add an option to use mqtt in the config flow as well!

[firstof9]

It would be great if you could add an option to use mqtt in the config flow as well!

MQTT has it's own integration you can use.

This is specifically geared towards using the HTTP API as much as possible.

[omriasta]

It would be great if you could add an option to use mqtt in the config flow as well!

MQTT has it's own integration you can use.

This is specifically geared towards using the HTTP API as much as possible.

Yep, I have MQTT setup as well. Was thinking of having them combined all in one integration where one could select if they setup using http or mqtt. My specific setup is I have 2 units, one is on the local network and the other is remote but publishing to my mqtt broker.... I guess big picture if we want to replace the current integration, having both options combined into one would be great for all uses.