Skip to content

Communication service between the Alpha ESS Storion T10 modbus and publish it via MQTT

License

Notifications You must be signed in to change notification settings

wooni005/alpha-ess-modbus_mqtt

Repository files navigation

Alpha-ESS-T10 MQTT

Communication service between the Alpha ESS Storion T10 modbus and publish it via MQTT

Protocol

The Alpha-ESS Storion T10 allows retrieving internal data via Modbus RTU. Also Modbus TCP, but that is currently in beta stadium.

This is the protocol description of the modbus: Alpha-Modbus-Protocol_V1.17.pdf

Hardware

I´m using a Raspberry Pi 3B+ to retrieve the data out of the Alpha-ESS Storion T10.

In the Raspberry Pi you need a USB-Modbus adapter, which works perfectly, which I bought here via eBay in Germany: Rs485 Converter Bus Adapter Serial USB rs-485 Interface Modbus Raspberry Pi | eBay

UTP cable

To connect to the Storion T10, you need an UTP cable T-568:

Connect to the UTP cable to the connector of the RS485 USB adapter:

  • Into B goes the green-white wire (pin 3)

  • Into A goes the green wire (pin 6)

Connect other side ()the RJ45 connector) to DISPATCH on the Control box of the Storion T10.

Testing communications

You can use the storion_terminal_rs485.py program to test if it's working.

Install service

sudo cp alpha-ess-modbus_mqtt.service /etc/systemd/system
sudo cp alpha-ess-modbus_mqtt.service /etc/systemd/system
sudo cp alpha-ess-modbus_mqtt.service /etc/systemd/system

Problems

Checks if it doesn't work

These checks were done in cooperation with Alpha-ESS support (Mr.Ming)

1 - Modbus wires

First I had to check that the modbus wires were connected to pin 3 (B) and 6 (A) of the modbus. (see above)

2 - Modbus Poll tool

Alpha-ESS support uses the Modbus Poll tool to check the modbus is working. Download it here (Windows only)

These are the settings:

And this was my result (not working):

3 - Check cable inside

Warning! Only do this in cooperation with Alpha-ESS support (for waranty reasons) and be careful with the high voltages in the Control box!

The internal UTP cable from the DISPATCH connector needs to be connected to USART4.

Result

Still didn't work and the dealer (ProSolar) in Czech Republic replied that I need to buy a Loxone system to get it working. End of discussion... But I don´t need the Loxone system, I´m running Home Assistant and my own software for home automation. The modbus is an universal bus and should also work with other systems. Also the Loxone system is pretty expensive to test if this will work or not. I understand that as a company you don't want to support all hobbyists, but I'm doing this kind of work for more than 25 years :-). Also said that to ProSolar, but no answer to that.

I also bought a Moxa RS422/RS485 converter, which I was used to work with from my previous work. This device is working via the LAN to communicate to RS485/modbus. Same result of course, it didn't work also. You can use the storion_terminal_moxa.py program to use the Moxa converter.

Finally the Control box is replaced and it all worked immediately. Yippie! Don't get me wrong, I'm a happy user of the Storion T10 and the system has a good price-performance ratio. The support could be better.

Work-around

There are more ways to get the Storion T10 data out of the system:

  • Make use of Alpha-ess.com web scraping. The web information is refreshed every 5 min. But I don't know if Alpha-ESS is happy with this load on their website if you're running this 24/7, but if you've a refresh rate of 30-60 minutes I think that's not a problem.

  • The beta version of Modbus TCP, which is using the LAN interface to access the internal Storion T10 data, but I didn't see it working yet.

About

Communication service between the Alpha ESS Storion T10 modbus and publish it via MQTT

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages