jacauc

@Sc00bs the pinout you show looks a bit different. Below is a pinout which more accurately reflects @Gooseza setup https://www.electronicshub.org/esp32-pinout/

Thanks @Sc00bs. I've seen those before but unfortunately it's not very clear to decipher the data types and whether signed/unsigned.

Does anyone have a list of all data types for all registers? The Sunsynk word document leaves a lot for the imagination

If your inverter is far from the living area you could also consider using another esp32 board elsewhere in the house reading values from home assistant or mqtt and adjusting the display accordingly. I've played around with displays with built-in I2C modules and it's dead easy. Make sure you use I2C displays otherwise cabling is way more complex

Not sure if related, but is your inverter set up for Modbus ID #1? Also have a good look at the cabling between the esp and the inverter

No issues whatsoever. Running bleeding edge of HA and ESPHOME.

Which is why I use Dupont connectors 😂

Repo hasn't changed much because it didn't really need changes. All is well with that code. We're focusing right now on moving the functionality out of node red and raspberry Pi to be able to poll it with a much more lightweight ESP32 on the Esphome platform for situations where the HA instance is not close to the inverter

Alternatively, install the HACS Addon by swartjean and it's all done for you

found a better way to skip updates for settings instead of creating another modbus component. Updating github now and adding substitutions at the very top of the document

I would imagine it's possible using the write_lambda function https://esphome.io/components/output/modbus_controller.html Worthwhile to look at the node red flows @Bloubul7made for writing values to see how he did it and adapt it to lambda format. Let me know if you figure something out with this, I'll try it sometime, but have a busy few weeks ahead

I just tried this and seems to be easy enough. I uploaded the code to github

Yeah thought about that too, but I don't really know how to query it less frequently with esphome. Also... Does it really matter? I suppose we can make another modbus sensor with a less frequent scan rate, no idea if that would work though. I commented out the PV values because I don't have PV. (which is also why I have not tried writing values) If you want to add any more values to query, please feel free to add them into the code on GitHub with a pull request. Maybe we can somehow have a variable that can be set in the top of the script so that the irrelevant values are automatically ignored?

Instead of posting my esphome configs here, I'm uploading them to github (partly just for keeping for my own backup) Recently added all the setting values https://github.com/jacauc/SunsynkEsphome