search

CharlesGillanders / homeassistant-alphaESS

Monitor your energy generation, storage, and usage data using the official API from Alpha ESS.
MIT License
101 stars 22 forks source link

Use of TCP Modbus? #72

Closed sebastianmachon closed 1 year ago

sebastianmachon commented 1 year ago

Hi, Have you tried to use the integrated Modbus TCP? The used API needs a working Alpha API and internet connectivity.

Modbus TCP works local.

dry commented 1 year ago

See https://github.com/dxoverdy/Alpha2MQTT

Spookster commented 1 year ago

Works well :)

Spookster commented 1 year ago

One idea that I picked up from Daniels work was the use of ApexCharts to display data. It can be applied to Charles work as well to duplicate Alphas charts. I wish Id seen it sooner :)

image

aw1604 commented 1 year ago

Hello, I think what sebastian meant was a direct tcp modbus approach since for example the Smile-T10 now supports native modbus/tcp over the network. You can directly pull all data using the HA "modbus tcp" integration (and set too). Is there a way to re-write the AlphaESS integration to use HA internal modbus sensor data instead of relying on external mqtt and serial-to-network controllers (as they shouldn't be needed anymore) ? I am not a coder myself, but willing to sponsor development.. Best Regards, Andreas

Tupsi commented 1 year ago

You can directly pull all data using the HA "modbus tcp" integration (and set too).

Sadly that is not true. I am using this besides what Charles has done here and the one thing which I still need is the data of the EV Charging. I already opened up several tickets at AlphaESS and the answer is always (is not implemented yet/we are still thinking about it), so take you pick and mostly likely add a third option meaning "will never do". ;-)

Only reading data from the Modbus so far, never tried setting anything that way, so can not comment about that part.

But some data you see on their website is definitely missing in the TCPModBus implementation at the moment.