kellerza

Are you referring to those 25-pin behemoth connectors that used to be popular with printers? Haven't seen one in 15 years... Pierre is quite responsive. Not sure which one you refer to. The Solarman integration in my addon is fairly new. Changing settings is possible. Yes, you would need a cable to each to pull individual power/energy stats. It's only the settings/system mode controlled from the master.

With a multi-Inverter setup the first inverter controls settings, but to get proper stats you need to read them individually. It was discussed extensively here (some install pics as well) - https://github.com/kellerza/sunsynk/issues/39 The latest addon ships with these default sensors: SENSORS: - energy_management - power_flow_card SENSORS_FIRST_INVERTER: - settings

In a recent issue there was one user where it worked perfectly, and another that could not write at all. Turned out that Solar-Assistant also has it documented that the RS485 could be read-only. So you are one of the lucky ones...

Once you add cards (HACS I assume) you have to reload the frontend / Ctrl-F5. Restarting your HA won't do anything

A better option could be the HF5142? - see https://kellerza.github.io/sunsynk/guide/wiring#ethernet-to-rs485-gateways Some of the 16kW Inverters seem to be read-only on their RS485 ports, in which case you have to connect them with RS232

Did you only enable the “long term forecast”? 🤣

Slipx’s made the lovelace/gui plugin, which can be used by any inverter, or any method of getting the inverter data My addon is an alternative for the ESPhome solution (or solarassistant) I documented why on my website, main reason I prefer the addon: - Much less updates, but more accurate where it matters - for something that potentially streams data every second, “the garage is too far” is not a good enough reason not to install a wire (I’m not against ESPHome, probably have 15 of them in/around the house, but its not for telemetry)

Indeed the entity_id is the link between the two… There has been some naming behaviour where the device name is prepended to the entity name to form the entity id. (Fixed it in my addon recently) So you should remove the friendly_name part from all your sensors name: "${friendly_name} xxxxx sensor”

In slipx's card, the entity names contains a number. Match that with your register address

No need to edit it, you just add the sensor to the addon config

This is the definition for the sensor “pv2_power” or “PV2 Power”… they are all the same https://github.com/kellerza/sunsynk/blob/main/src/sunsynk/definitions.py#L81 Sensor(187, "PV2 power", WATT, -1), Have a look at the definitions.py file and simply use any name you see in there

I’m still using it

@JuanH did you manage to get it working? updated the docs link shared earlier- so hopefully a bit clearer

`pv2_power` ? https://kellerza.github.io/sunsynk/reference/definitions#single-phase-inverter-sensor-definitions the docs might need some rearrangement, since I added the “groups” at the top

This is not possible, as all sensors & all inverters use the same availability topic - the concept of availability is per addon, not inverter, not sensors. So something else is wrong and won't be able to help without more details, which can be captured in the Issue https://kellerza.github.io/sunsynk/reference/schedules You get the default/"template" if you reset your config. The quoted schedule is from the default.

_power changed to _energy a looong time ago. But it might be that the previous version of the addon still substituted all those deprecated sensors. Now it will just raise a warning If you fixed it, the entity_ids will be different in HA and you need to update your Energy settings and UI elements to use the new sensor entity_ids (or rename the entities, but I won't advise that) Look at Settings -> Devices & Services -> Devices and you can open the device and see all it's associated sensors. If still not working, open an Issue on github with more detail

While I don't have a generator, someone was more interested in 235 than 234: https://github.com/kellerza/sunsynk/blob/main/src/sunsynk/definitions.py#L159

What registers did you try & what did you set them to?

That is probably a copy & paste issue and should be for the 12kW & 16kW 3-phase inverters

The ota pw is baked into the firmware on the esp. You can only update the fw if the ota matches

Yes. Tbh, there might still be changes needed in the frequency in which data is being read through the solarman dongle. Will see if I can throttle it down sometime this week.

Hi @Blouwildebees You can definitely update settings with the Sunsynk Addon, see some examples and automations here. If you have a wired connection, you can be a lot more aggressive in reading settings. The addon typically reads important parameters (Watts) every second and can report immediately if there is a significant change (big load change). For less important parameters (config, kWh) it only reports every couple of minutes. Your Home Assistant does not have to be close to the inverter. I run my mbusd gateway on a Pi 1B with wired Ethernet. See here for more options. There is a PR waiting to add Solarman dongle support to the addon. Although that will limit you to 15second read intervals. But from the ode it does seem like you can write settings, even with the Solarman dongle.

Half of the issues with an unstable HASS OS is probably storage related, the other half a flakey power supply. Standard install & standard MQTT here. I have the official Pi PSU with external SSD storage. Without proper storage, any solution writing loads of stats to the SD card will be doomed in the long run.

- Zero Export - never feed power into the grid (using the grid-CT coil) - Limit to load only - never feed power to non-essential circuits (between grid-CT coil and the inverter) In the HASS addon I call them {0: "Allow Export", 1: "Essentials", 2: "Zero Export"} (register 244) Never tried "Solar export only", but this is probably "Allow Export, but not using batteries".

Sounds like fun, but I'm travelling next week. Will try for the next one 😉