Sunsynk + Home Assistant

[TedLasso]

Yeah, love it, but definitely have not bothered update to use any new features that have come out recently. When I get time, need to probably look at what new cool things I should add

 

[SauRoNZA]

Yeah, love it, but definitely have not bothered update to use any new features that have come out recently. When I get time, need to probably look at what new cool things I should add

Depending on how long ago you updated it’s now very fleshed out with a GUI interface so no struggling with the Yaml.

 

[SauRoNZA]

@Slip any reason my out of {forecast} value would stop displaying? (As in 1.7 kWh / 46.5 kWh)?

It's populated in the config and as you can see the value is populated but for some reason it's just stopped showing up.

Aaah I discovered the Display Mode setting...got it Number 2 is what I was looking for.

Not let me go give you some money and go read what Number 3 actually does.

 

[Freakboy]

With the Sunsynk cloud issues that happened over the weekend and my inverter's date & time going wildly out when sync is ticked, does anybody know how to set the time and date using the plugin?
I see there is a section on the mysensor page but it states that it is only partially implemented so not sure if that is going to work. Could not see any standard sensors loaded when looking at them available in my HA install.

 

[Slip]

I’ve added time synchronisation to my ESPHome config. It’s on the GitHub.

 

[acidrain]

Been having some unexpected results with the updated card.

Seems when there is a high load (3kW+) going to the house, the grid registers a negative value of the same amount.



Anyone else experiencing this?

 

[Slip]

v4.26.0
What's Changed
Exciting New Features
- feat: you can now display 3 additional loads on the compact or lite card. closes #345

- feat: added new animations to the full card
- feat: display extra information above your nonessential loads. See `non_essential_load1_extra:` and `non_essential_load2_extra:` #344

Patches & Bug Fixes
- fix: improvements to handling of use_timer and priority_load entities
- fix: full card inverter line width now equals minimum line width setting
- fix: adjust layout to improve symmetry on full card
- chore: optimize icon handling


**Full Changelog**: https://github.com/slipx06/sunsynk-power-flow-card/compare/v4.25.0...v4.26.0

 

[Syphonx]

Anyone setup Kellerman as a standalone service on an RPI?

I am trying to run the sunsynk-multi container (https://kellerza.github.io/sunsynk/guide/standalone-deployment) using a prebuilt container. MBUSD was installed following this guide and is running: https://medium.com/@boonsanti/raspb...-rs-485-to-modbus-tcp-ip-gateway-9ed14ce2c08e

I am getting the following errors when starting the container:

[+] Running 1/0
 ✔ Container sunsynk-multi  Created                                                                                                                                                                                                     0.0s
Attaching to sunsynk-multi
sunsynk-multi  | s6-rc: info: service s6rc-oneshot-runner: starting
sunsynk-multi  | s6-rc: info: service s6rc-oneshot-runner successfully started
sunsynk-multi  | s6-rc: info: service fix-attrs: starting
sunsynk-multi  | s6-rc: info: service fix-attrs successfully started
sunsynk-multi  | s6-rc: info: service legacy-cont-init: starting
sunsynk-multi  | s6-rc: info: service legacy-cont-init successfully started
sunsynk-multi  | s6-rc: info: service legacy-services: starting
sunsynk-multi  | services-up: info: copying legacy longrun sunsynk (no readiness notification)
sunsynk-multi  | s6-rc: info: service legacy-services successfully started
sunsynk-multi  | 15:26:04 INFO    Loading configuration: /data/options.yaml
sunsynk-multi  | 15:26:04 INFO    sunsynk library version: 0.6.4
sunsynk-multi  | 15:26:04 INFO    Schedules:
sunsynk-multi  | +-----------+-----+------+--------+-----------+----------+------------+
sunsynk-multi  | |    Key    | src | Read | Report | Change by | Change % | Change any |
sunsynk-multi  | +-----------+-----+------+--------+-----------+----------+------------+
sunsynk-multi  | | date_time |     |  60  |   60   |           |          |    True    |
sunsynk-multi  | |     rw    |     |  5   |  300   |           |          |    True    |
sunsynk-multi  | |     w     |  *  |  5   |   60   |     80    |          |            |
sunsynk-multi  | |    kwh    |     | 300  |  300   |           |          |            |
sunsynk-multi  | |  any_unit |     |  15  |  300   |           |          |            |
sunsynk-multi  | |  no_unit  |     |  15  |  300   |           |          |    True    |
sunsynk-multi  | +-----------+-----+------+--------+-----------+----------+------------+
sunsynk-multi  | 15:26:04 INFO    Using Single phase sensor definitions.
sunsynk-multi  | 15:26:05 INFO    Added hidden sensors as other sensors depend on it: Rated power, Serial
sunsynk-multi  | 15:26:05 INFO    Connecting to tcp://192.168.10.183:502
sunsynk-multi  | 15:26:05 INFO    PyModbus 3.5.2 tcp: 192.168.10.183:502
sunsynk-multi  | 15:26:05 INFO    Reading startup sensors Prog1 Time, Rated power, Prog2 Time, Prog4 Time, Prog3 Time, Prog6 Time, Serial, Prog5 Time, Battery Low Capacity
sunsynk-multi  | 15:26:13 ERROR   OSError reading 5 registers from 3: failed to read register 3 - function code: 131; OSError reading 2 registers from 16: failed to read register 16 - function code: 131; OSError reading 1 registers from 219: failed to read register 219 - function code: 131; OSError reading 6 registers from 250: failed to read register 250 - function code: 131
sunsynk-multi  | 15:26:22 ERROR   OSError reading 5 registers from 3: failed to read register 3 - function code: 131; OSError reading 2 registers from 16: failed to read register 16 - function code: 131; OSError reading 1 registers from 219: failed to read register 219 - function code: 131; OSError reading 6 registers from 250: failed to read register 250 - function code: 131
sunsynk-multi  | 15:26:31 ERROR   OSError reading 5 registers from 3: failed to read register 3 - function code: 131; OSError reading 2 registers from 16: failed to read register 16 - function code: 131; OSError reading 1 registers from 219: failed to read register 219 - function code: 131; OSError reading 6 registers from 250: failed to read register 250 - function code: 131
sunsynk-multi  | 15:26:31 WARNING Retrying individual sensors: ['prog1_time', 'rated_power', 'prog2_time', 'prog4_time', 'prog3_time', 'prog6_time', 'serial', 'prog5_time', 'battery_low_capacity']
sunsynk-multi  | 15:26:33 ERROR   OSError reading 1 registers from 250: failed to read register 250 - function code: 131 Prog1 Time
sunsynk-multi  | 15:26:35 ERROR   OSError reading 2 registers from 16: failed to read register 16 - function code: 131 Rated power
sunsynk-multi  | 15:26:37 ERROR   OSError reading 1 registers from 251: failed to read register 251 - function code: 131 Prog2 Time
sunsynk-multi  | 15:26:40 ERROR   OSError reading 1 registers from 253: failed to read register 253 - function code: 131 Prog4 Time
sunsynk-multi  | 15:26:42 ERROR   OSError reading 1 registers from 252: failed to read register 252 - function code: 131 Prog3 Time
sunsynk-multi  | 15:26:44 ERROR   OSError reading 1 registers from 255: failed to read register 255 - function code: 131 Prog6 Time
sunsynk-multi  | 15:26:46 ERROR   OSError reading 5 registers from 3: failed to read register 3 - function code: 131 Serial
sunsynk-multi  | 15:26:48 ERROR   OSError reading 1 registers from 254: failed to read register 254 - function code: 131 Prog5 Time
sunsynk-multi  | 15:26:51 ERROR   OSError reading 1 registers from 219: failed to read register 219 - function code: 131 Battery Low Capacity
sunsynk-multi  | 15:26:51 CRITICAL Could not read sensors: ['Prog1 Time', 'Rated power', 'Prog2 Time', 'Prog4 Time', 'Prog3 Time', 'Prog6 Time', 'Serial', 'Prog5 Time', 'Battery Low Capacity']
sunsynk-multi  | 15:26:51 INFO    ############################################################
sunsynk-multi  | 15:26:51 INFO    No response on the Modbus interface tcp://192.168.10.183:502, see https://kellerza.github.io/sunsynk/guide/fault-finding
sunsynk-multi  | 15:26:51 INFO    ############################################################
sunsynk-multi  | 15:26:51 CRITICAL This Add-On will terminate in 30 seconds, use the Supervisor Watchdog to restart automatically.

 

[Slip]

v4.34.0
What's Changed
Exciting New Features
- feat: You can now visualise the efficiency of your MPPT strings by adding the `efficiency` attribute to your solar section together with the `pv[1-4]_max_power` (Maximum power of the MPPT based on the number and size of panels). The `efficiency` attribute can be one of four numeric values and activates the following display modes

0 - Disabled
1 - Graphic display
2 - Text display
3 - Graphic and text display

This is disabled by default and you must set the desired display mode and specify the pv[x]_max_power in order to display this extra data.

Some examples below

1 - Graphic display

2 - Text display

3 - Graphic and text display

Patches & Bug Fixes
- fix: layout improvements. Remove space from battery soc.


**Full Changelog**: https://github.com/slipx06/sunsynk-power-flow-card/compare/v4.33.0...v4.34.0

 

[Slip]

v4.35.0
## What's Changed
Exciting New Features
- feat: added animation for battery charge when using linear gradient. Set the battery `animate` attribute to `false` to disable

- feat: when solar sell is turned off the sell limit is grayed out

Patches & Bug Fixes
- fix: alignment of PV names and solar efficiency on the lite and compact cards closes #414

### Other Changes
- docs: update new options
- docs: update huawei example - thanks @Roving-Ronin in https://github.com/slipx06/sunsynk-power-flow-card/pull/411
- docs update sunsynk example


**Full Changelog**: https://github.com/slipx06/sunsynk-power-flow-card/compare/v4.34.1...v4.35.0

 

[Slip]

v5.1.0
What's Changed
Exciting New Features
- feat: you can specify the battery charge cut-off capacity using the `soc_end_of_charge` attribute. If for example you set your battery to charge up to 90% the card will correctly display charge time to this capacity. Expects a numeric value between `80` and `100` or sensor i.e. `sensor.soc_end_of_charge`. closes #514
- feat: introduces the `navigate` attribute that allows you to link to other dashboards and views e.g. `/lovelace/1` when clicking some of the card icons. It can currently be configured for the battery icon, essential load icon, solar icon, and inverter icon. closes #521

**Full Changelog**: https://github.com/slipx06/sunsynk-power-flow-card/compare/v5.0.1...v5.1.0

 

[fxit_man]

Anyone setup Kellerman as a standalone service on an RPI?

I am trying to run the sunsynk-multi container (https://kellerza.github.io/sunsynk/guide/standalone-deployment) using a prebuilt container. MBUSD was installed following this guide and is running: https://medium.com/@boonsanti/raspb...-rs-485-to-modbus-tcp-ip-gateway-9ed14ce2c08e

I am getting the following errors when starting the container:

sunsynk-multi  | 15:26:51 INFO    No response on the Modbus interface tcp://192.168.10.183:502, see https://kellerza.github.io/sunsynk/guide/fault-finding
sunsynk-multi  | 15:26:51 INFO    ############################################################
sunsynk-multi  | 15:26:51 CRITICAL This Add-On will terminate in 30 seconds, use the Supervisor Watchdog to restart automatically.

Looks like it's not connecting to the IP you gave it. So I would troubleshoot that. Can you ping that IP from your machine?

 

[Syphonx]

Looks like it's not connecting to the IP you gave it. So I would troubleshoot that. Can you ping that IP from your machine?

Lol I solved that long ago, actually so long ago I forgot what the issue was but it was my configuration of the service

 

[fxit_man]

Lol I solved that long ago, actually so long ago I forgot what the issue was but it was my configuration of the service

My bad didn't look at the date

 

[Slip]

v6.0.0
What's Changed
Exciting New Features

This release adds a long awaited wide screen view across the lite, compact and full cards. This lays the ground work to display two batteries and possible master and slave inverter pairs. It also looks better on tablets when displaying the card in panel/full screen.

- feat: new wide screen view to display content in 16:9 format. set `wide:true`
- feat: display up to 6 additional essential loads when using the wide screen view
- feat: display up to 3 non essential loads when using the wide screen view
- fix: grouping of SVG elements and standardise viewbox across lite,compact and full cards
- locale: update Ukraine translation








Other Changes
* New wide screen view by @slipx06 in https://github.com/slipx06/sunsynk-power-flow-card/pull/556


**Full Changelog**: https://github.com/slipx06/sunsynk-power-flow-card/compare/v5.4.0...v6.0.0

 

[Slip]

v6.1.0
What's Changed
Exciting New Features
This release adds an option to display a second battery on the lite, compact and full cards styles when using the wide view.

• feat: add an option to display a 2nd battery on all the card styles when using the wide view closes #493 . Also addresses #380 #374 #296 #285 #232 #203 #135
• feat: update visual editor
• docs: update documentation with 2nd battery attributes and entities
• docs: add entity categories

Other Changes
* Add a second battery by @slipx06 in https://github.com/slipx06/sunsynk-power-flow-card/pull/561


**Full Changelog**: https://github.com/slipx06/sunsynk-power-flow-card/compare/v6.0.0...v6.1.0

 

[DrJohnZoidberg]

v6.1.0
What's Changed
Exciting New Features
This release adds an option to display a second battery on the lite, compact and full cards styles when using the wide view.

View attachment 1776394

• feat: add an option to display a 2nd battery on all the card styles when using the wide view closes #493 . Also addresses #380 #374 #296 #285 #232 #203 #135
• feat: update visual editor
• docs: update documentation with 2nd battery attributes and entities
• docs: add entity categories

Other Changes
* Add a second battery by @slipx06 in https://github.com/slipx06/sunsynk-power-flow-card/pull/561


**Full Changelog**: https://github.com/slipx06/sunsynk-power-flow-card/compare/v6.0.0...v6.1.0

Now we need support for a 3rd battery

 

[TedLasso]

Now we need support for a 3rd battery

And a fourth and fifth ...

Wondering if the Bubble card methodology could be used, so that one could tap on the battery and then all the individual battery(s) info could be shown in a popup card?

Ok, I am an ideas guy ... Off to it

Love your work. I've seen this shared (and I shared it on Reddit previously too) so it's being used worldwide properly now! You must be so proud and chuffed @Slip

 

[Slip]

Thank @TedLasso. Its great to see it so widely adopted.

I'm actually still trying to figure out how the display of multiple batteries should work so any input is welcome. I don't know if the bigger inverters with multiple battery inputs have separate runtime, shudown soc per battery bank (input) or if it's still only one big virtual battery seen by the inverter. In that case it's probably not necessary to have separate battery bank runtime information and I can change the layout. I'm waiting for the feedback to start trickling in once people start using the additional battery. Maybe its a case of having both options and then choosing a battery display mode i.e. One virtual battery (the default), two virtual batteries with separate runtime etc. and a third display mode that shows a single virtual battery and then the individual battery stats making up the virtual battery i.e. bat1, bat2, bat3, bat4 (power, voltage, current, temp)

 

[Mzezman]

Thank @TedLasso. Its great to see it so widely adopted.

I'm actually still trying to figure out how the display of multiple batteries should work so any input is welcome. I don't know if the bigger inverters with multiple battery inputs have separate runtime, shudown soc per battery bank (input) or if it's still only one big virtual battery seen by the inverter. In that case it's probably not necessary to have separate battery bank runtime information and I can change the layout. I'm waiting for the feedback to start trickling in once people start using the additional battery. Maybe its a case of having both options and then choosing a battery display mode i.e. One virtual battery (the default), two virtual batteries with separate runtime etc. and a third display mode that shows a single virtual battery and then the individual battery stats making up the virtual battery i.e. bat1, bat2, bat3, bat4 (power, voltage, current, temp)

Its a tricky one to solve - most systems will view the pack as a single battery with a max capacity of xx ah. That might be the easiest way to manage it. If a user wants to see the voltage of cells in battery 8/18 then maybe they need a separate solution?