kellerza

Thank you very much for the add of the sensor to an update. @kellerza

So this is evolving quite quickly into my new favorite tool for managing everything
Remember to like and subscribe on the video if you want to see all the weird gadgety/coding things I get up to when I am bored.

Shout out to @kellerza @Sc00bs @slipx and everyone else contributing to make all these things work nicely with my gadgets and solar stuff.
 
 

I assume this is 3ph with these reg numbers?
 
Can you write other sensors?
Have you considered using something else than nodered, like my HA addon or the ESP32?
With your current hw, it should be a no brained to get my addon working

I was also looking for a solution here
If you have some energy meter (measuring total consumed kWh). You can try the following (I use it in packages\prepaid.yaml). My energy from the grid is measured by the sunsynk inverter, but any meter should work
You can now create an automation if sensor.prepaid_units_left<20 to send you a message etc...
 
# A sensor that indicates how many prepaid units you have left # # 1. Enter the units using "input_test.prepaid_units" # 2. An automation save the sum of the enetered units + grid total # 3. The sensor displays the saved value - the current grid total automation: - id: "prepaid-set-units" alias: Prepaid - set units initial_state: true trigger: - platform: state entity_id: sensor.prepaid_units_left condition: "{{ states('sensor.prepaid_units_left') | float < 0 }}" action: - service: input_text.set_value target: entity_id: input_text.prepaid_units data: value: > {% set units = states('input_text.prepaid_units') | float %} {% set total = states('sensor.ss_total_grid_import') | float %} {{ (units+total) | round(2) }} input_text: prepaid_units: name: Enter Prepaid units from meter pattern: '\d+(\.\d+)?' mode: password icon: mdi:home-lightning-bolt-outline min: 1 max: 10 template: - sensor: - name: "Prepaid units left" icon: mdi:home-lightning-bolt-outline unit_of_measurement: "kWh" state: > {% set units = states('input_text.prepaid_units') | float %} {% set total = states('sensor.ss_total_grid_import') | float %} {% if (units-total) > 999 %}999.999{% else %}{{ (units-total) | round(1) }}{% endif %}  

1. Read up on config packages here - config-packages
2. Save the code above in a "package" file
3. Add your elements to your HA dashboard

If your inverter's mode (load_limit sensor) is set to "Zero export" and your inverter's CT sensor is working, then total_grid_import is very close. If you set load_limit to only essentials or to export then the inverter does not include the non-essential power draw. Why you should ask Sunsynk, but so far, they have told us to update the inverter firmware, without any success.

That's not quite accurate, if you are talking about data recorded on Sunsynk's data site with your Sunsynk WiFi dongle, then yes, but data is accumulated in 5 minute segments then, so it should still be accurate, but won't show short term spikes of power nicely, but they will be counted...
If you ran Home Assistant with @kellerza's Sunsynk/Deye Inverter Add-on locally, then you could record some data on a 1 second basis and would see some of the energy spikes more clearly... see a history data graph for yesterday 00:00 until today 14:00

You can see earlier today the Inverter power spiking to near 5kW and just over 5kW, when I was mowing the lawn earlier (old Wolf 2000 electric mower). see the next one, where the time slot is from today 10:00 to 14:00, but since its only 13:12 now, it obviously doesn't show beyond current time (can't predict the graph into the future :-))

 

I was also looking for a solution here
If you have some energy meter (measuring total consumed kWh). You can try the following (I use it in packages\prepaid.yaml). My energy from the grid is measured by the sunsynk inverter, but any meter should work
You can now create an automation if sensor.prepaid_units_left<20 to send you a message etc...
 
# A sensor that indicates how many prepaid units you have left # # 1. Enter the units using "input_test.prepaid_units" # 2. An automation save the sum of the enetered units + grid total # 3. The sensor displays the saved value - the current grid total automation: - id: "prepaid-set-units" alias: Prepaid - set units initial_state: true trigger: - platform: state entity_id: sensor.prepaid_units_left condition: "{{ states('sensor.prepaid_units_left') | float < 0 }}" action: - service: input_text.set_value target: entity_id: input_text.prepaid_units data: value: > {% set units = states('input_text.prepaid_units') | float %} {% set total = states('sensor.ss_total_grid_import') | float %} {{ (units+total) | round(2) }} input_text: prepaid_units: name: Enter Prepaid units from meter pattern: '\d+(\.\d+)?' mode: password icon: mdi:home-lightning-bolt-outline min: 1 max: 10 template: - sensor: - name: "Prepaid units left" icon: mdi:home-lightning-bolt-outline unit_of_measurement: "kWh" state: > {% set units = states('input_text.prepaid_units') | float %} {% set total = states('sensor.ss_total_grid_import') | float %} {% if (units-total) > 999 %}999.999{% else %}{{ (units-total) | round(1) }}{% endif %}  

I doubt you have an issue with MQTT
This clearly states the modbus interface is not responding, so no connection to the inverter. The addon will only connect to MQTT once it connected to the inverter and verified your serial number.
As others also pointed out, this URL usually points to a Modbus gateway/mbusd add-on on your local homeassistant node. If this is not what you intended, you should rather connect to a USB port

The adaptor you have is perfectly fine,- it has a GND and some protection.
Agree that, the native mbusd timing is far superior to what Python and Node V8 offers. I have mbusd running on a 10+ year old Pi Model 1b. The mbusd addon on HASS OS also works flawlessly.
My production Pi-4(HA+SSD) + Pi-1b(mbusb) pulls data every 2 seconds, ~15m of RS485 bus and maybe 2 timeouts per day.

This is very good advice! 
The raspberry Pi PSU also floats somewhat, and since its not isolated it's important to wire the GND on the USB-RS485 adaptor (this is not the shield).
In my setup I have non-shielded solid-core CAT5e (RS485 on one twisted PAIR !!) and GND. Around 15m with <1m in close proximity to the AC. The twisted pair helps, but if you have longer runs in close proximity to AC/DC then you must go shielded.
 
The Waveshare USB adaptor I link in the docs has everything except optical isolation:
Support USB to RS485 bidirectional conversion Onboard Original FT232RL and SP485EEN chip. Fast communication, stable and reliable, better compatibility Onboard TVS (Transient Voltage Suppressor), effectively suppress surge voltage and transient spike voltage in the circuit, lightningproof & anti-electrostatic Onboard resettable fuse and protection diodes, ensures the current/voltage stable outputs, provides over-current/over-voltage proof, improves shock proof performance

I don't really have one to experiment with and everyone out there only integrates via the cloud (not ideal in my view)

Try https://kellerza.github.io/sunsynk/reference/schedules#proposed-schedule-overrides-for-solarman
Try those. YMMV depending on the amount of sensors you read. In this case less is better, else the dongle resets and disappears for a while

Thanks @kellerza and @Sc00bs for your work on this!

Like @Dunc, I'd be interested in the Sunsynk Dongle option...

Is there any work being done on this? Or is there a fundamental reason why it can't work?

Hi Everyone, 
I have done a video on the installation of the KellerZA integration from Johann. I think it is a better option than the Solarman integration as it allows for the writing of settings back to the inverter and gives you an upgrade path if you want a faster refresh. is very flexible and easy to setup. 
Please let me know what you think of the video and if you have any questions please let me know. 
Thanks for the great integration @kellerza 🙂 
 
 

Thanks, glad you find it useful!
Since you use sensor groups in your config (power_flow_card) https://kellerza.github.io/sunsynk/reference/definitions#power-flow-card-power-flow-card it includes several sensors. It seems like the names of the three-phase sensors do not match exactly, or these are not present in the three-phase inverter definition.
Single phase defs: https://github.com/kellerza/sunsynk/blob/main/src/sunsynk/definitions.py Three phase defs: https://github.com/kellerza/sunsynk/blob/main/src/sunsynk/definitions3ph.py  
 
Apparently the solarman dongle is quite temperamental. There is some improvement (using native errors correction) in the edge addon. I've also asked the pysolman authors what they recommend to make this more reliable.
Probably best to open an issue, as its easier to track on Github than in a forum.
 

Thanks, glad you find it useful!
Since you use sensor groups in your config (power_flow_card) https://kellerza.github.io/sunsynk/reference/definitions#power-flow-card-power-flow-card it includes several sensors. It seems like the names of the three-phase sensors do not match exactly, or these are not present in the three-phase inverter definition.
Single phase defs: https://github.com/kellerza/sunsynk/blob/main/src/sunsynk/definitions.py Three phase defs: https://github.com/kellerza/sunsynk/blob/main/src/sunsynk/definitions3ph.py  
 
Apparently the solarman dongle is quite temperamental. There is some improvement (using native errors correction) in the edge addon. I've also asked the pysolman authors what they recommend to make this more reliable.
Probably best to open an issue, as its easier to track on Github than in a forum.
 

Use the raw register values and not the twos-complement. So not the negative number.
Since 24612 is a smaller number it's pretty straight forward. 0x6024

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...

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  

I’m still using it

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)

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

Not sure Node-Red give you that much from a dashboarding and UI perspective. You have a UI to modify some system settings on Node-Red, which can just as easily be done on Home Assistant these days.
For everything else, Node-Red simply feeds the information via MQTT to Home Assistant. Home Assistant is where the dashboards, energy management UI, and even automation in many cases lives. It's all on an app and integrates with a 1000+ services devices.
There is even ESPHome (once again a Home Assistant project) code that could probably read these register values into Home Assistant with your existing hardware.
Node-Red might be somewhat more flexible for automations, but for everything else and 98.5% of automations you have Home Assistant. But I admit I might be biased, in the past I've built my own hardware - based on ATmegas and electric Imps ;-), UIs and eventually settled on HASS in 2016. Today it is one of the most active opensource projects out there, which obviously serves as some nice confirmation bias 😉  

@kellerza, I figured it out....

Here is the addon added to @slipx  .yaml file in order for the Force Generator functionality to be managed by HA.
Adding it here in case it can help someone else in future...