Livoltek inverter integration?

Hi, that’s awesome that you managed to pull all this data locally, especially with the Livoltek API constantly crashing. I also have a hybrid inverter, but a 3‑phase one, so I’m really hoping your work will help. My installation has an external 3‑phase bidirectional power meter connected to the inverter via RS485 (probably Modbus).

Do you think I could plug an RS485‑to‑USB adapter (Waveshare) into that bus? I’m not sure which device is the master or the slave in the current setup.

Could you share your Protocol Wizard configuration?

Unfortunately there is no communication on plug D of the inverter. I tried all 3 pairs. The meter is rs485 but does not give relevant data on modbus scan. The ARM pair is just a internal communication between the ARM processor and something else in the inverter, and the EV / Parallel pair i think is just waiting for an input from the EV station.

The inverter communicates on the USB port where the wifi dongle is mounted. But beware, that is not USB communication, that is rs485 in the middle pins of the USB plug and power / GND on the sides.

I`m running both wifi dongle and rs485 communication on the same time, but the connection is almost stable. Works just fine only with one or another.
Try opening the wifi dongle (there are clips at the usb plug), and solder to A and B pads on the board if you want to run the rs485 adapter at the same time.

The connection with the inverter is ID 17 (address 17) - i am using OpenModScan software.

https://docs.google.com/document/d/18-3UCo3dblNVUk0ZPPPmtT26wnoOwnQe?rtpof=true&usp=drive_fs

I have attached a google drive document with known registers for the Livoltek Hyper-6000 inverter.
I`m an electrical engineer not an IT guy, i don’t know coding, so use this information as is.

If you find anything new, please share!

Here’s something new https://github.com/uhodav/ha_livoltek

Thanks a lot for a comprehensive answer!
BTW Battery SoC in hass-livoltek integration started working yesterday morning. And stopped on evening…

And Solar Assistant!
Thanks to Anrich and Vince!

This is what they mentioned:

*"1. As you mentioned on the ticket in your last response, the only way to connect to the inverter is by using the same USB port that the dongle uses. We thoroughly confirmed this. *
*a) The dongle uses a USB plug & port, but is actually just RS485 and power. *
b) I will need to write the guide and explain the connection, and these options won’t be “just buy a cable”. It’ll be more custom, and the average user likely won’t go through the hassle. This is fine, the DIY crowd will still be able to do this (no need to solder/open the inverter, just some custom wiring)
2. Support will only become available in the next beta release - not sure how far out this is, but it should be in the next beta version.

So, it would be worth making note of those facts for other users. Just to set expectations and avoid users thinking the connection will be easier than it actually is, or people getting upset that they cannot see the protocol for the unit yet."

For now it`s just me and the guys at Solar Assistant testing the implementation.

We are currently looking to consume data from Livoltek sensors/inverters through the API in order to integrate it into our system.

We would like to confirm the following:

  • Is it currently possible to retrieve data from Livoltek devices through the API?
  • If so, what limitations or restrictions apply?
  • Is there any official documentation available for the endpoints and authentication flow?
  • Could you please indicate the correct way to perform API requests?

We have already performed some tests by generating a token from the platform, but when trying to request data we receive the following response:

"userToken invalid"

The token was generated with a future expiration date, so we understand it should still be valid. Therefore, we would like to confirm whether:

  • the generated platform token is the correct one for API access,
  • any additional parameters are required,
  • any extra configuration is needed on the platform or devices,
  • or if additional permissions/activation are required to enable data access.

We would appreciate any guidance regarding the proper process to consume data from the devices.