slipx

Hmm. After I revisited configuration documentation and looked precisely ti screenshots I found that probably it possible to draw generator as an aux.
The problem only that probably only sunsilk/deye users familiar with AUX word. Users of other inverters just may not recognize this ability. And showing generator is not explicitly explained in documentation as a use case.

V7.2.0
## What's Changed
🚀 Exciting New Features

* feat: add custom labels for daily charge and discharge closes #637
* feat: add custom labels for autarky and ratio
* feat: add Chisage inverter image closes #769
* feat: add SRNE HES inverter image closes #732
* docs: add ecoflow example by @windmueller in https://github.com/slipx06/sunsynk-power-flow-card/pull/756
* docs: sigenergy.rst: Simplify text by using links by @reedy in https://github.com/slipx06/sunsynk-power-flow-card/pull/762

🐛 Patches & Bug Fixes
* fix: essential_load4_extra entry in sigenergy.rst closes #773
* fix: load 6 not clickable and unecessary rendering of static icons closes #764
* fix: missing defaults in editor
* fix: sungrow dispatch run code #739
* fix: localisation of custom labels when using defaults
* fix: typo in OnGrid Status by @Roving-Ronin in https://github.com/slipx06/sunsynk-power-flow-card/pull/758

**Full Changelog**: https://github.com/slipx06/sunsynk-power-flow-card/compare/v7.1.3...v7.2.0

This is in my sensors.yaml file but I'm using the Open-Meteo Solar Forecast integration. If you are using Solcast the change required is in the last post https://github.com/dbuezas/lovelace-plotly-graph-card/discussions/422
Remember to update your sensors

- platform: template sensors: energy_production_today_sum: friendly_name: "Energy Production Today Sum" unit_of_measurement: "kWh" device_class: energy value_template: >- {% set sensor1 = states('sensor.energy_production_today_2') |float %} {% set sensor2 = states('sensor.energy_production_today_3') |float %} {% set total_watts = sensor1 + sensor2 %} {{ total_watts }} attribute_templates: watts: >- {% set sensor1 = state_attr('sensor.energy_production_today_2', 'watts') %} {% set sensor2 = state_attr('sensor.energy_production_today_3', 'watts') %} {% set ns = namespace(output={}) %} {% for time, value in sensor1.items() %} {% if time in sensor2 %} {% set sum_value = value + sensor2[time] %} {% else %} {% set sum_value = value %} {% endif %} {% set ns.output = dict(ns.output, **{time: sum_value}) %} {% endfor %} {% for time, value in sensor2.items() %} {% if time not in sensor1 %} {% set ns.output = dict(ns.output, **{time: value}) %} {% endif %} {% endfor %} {{ ns.output }} wh_period: >- {% set sensor1 = state_attr('sensor.energy_production_today_2', 'wh_period') %} {% set sensor2 = state_attr('sensor.energy_production_today_3', 'wh_period') %} {% set ns = namespace(output={}) %} {% for time, value in sensor1.items() %} {% if time in sensor2 %} {% set sum_value = value + sensor2[time] %} {% else %} {% set sum_value = value %} {% endif %} {% set ns.output = dict(ns.output, **{time: sum_value}) %} {% endfor %} {% for time, value in sensor2.items() %} {% if time not in sensor1 %} {% set ns.output = dict(ns.output, **{time: value}) %} {% endif %} {% endfor %} {{ ns.output }} energy_production_tomorrow_sum: friendly_name: "Energy Production Tomorrow Sum" unit_of_measurement: "kWh" device_class: energy value_template: >- {% set sensor1 = states('sensor.energy_production_tomorrow_2') |float %} {% set sensor2 = states('sensor.energy_production_tomorrow_3') |float %} {% set total_watts = sensor1 + sensor2 %} {{ total_watts }} attribute_templates: watts: >- {% set sensor1 = state_attr('sensor.energy_production_tomorrow_2', 'watts') %} {% set sensor2 = state_attr('sensor.energy_production_tomorrow_3', 'watts') %} {% set ns = namespace(output={}) %} {% for time, value in sensor1.items() %} {% if time in sensor2 %} {% set sum_value = value + sensor2[time] %} {% else %} {% set sum_value = value %} {% endif %} {% set ns.output = dict(ns.output, **{time: sum_value}) %} {% endfor %} {% for time, value in sensor2.items() %} {% if time not in sensor1 %} {% set ns.output = dict(ns.output, **{time: value}) %} {% endif %} {% endfor %} {{ ns.output }} wh_period: >- {% set sensor1 = state_attr('sensor.energy_production_tomorrow_2', 'wh_period') %} {% set sensor2 = state_attr('sensor.energy_production_tomorrow_3', 'wh_period') %} {% set ns = namespace(output={}) %} {% for time, value in sensor1.items() %} {% if time in sensor2 %} {% set sum_value = value + sensor2[time] %} {% else %} {% set sum_value = value %} {% endif %} {% set ns.output = dict(ns.output, **{time: sum_value}) %} {% endfor %} {% for time, value in sensor2.items() %} {% if time not in sensor1 %} {% set ns.output = dict(ns.output, **{time: value}) %} {% endif %} {% endfor %} {{ ns.output }} energy_production_d2_sum: friendly_name: "Energy Production D2 Sum" unit_of_measurement: "kWh" device_class: energy value_template: >- {% set sensor1 = states('sensor.energy_production_d2') |float %} {% set sensor2 = states('sensor.energy_production_d2_2') |float %} {% set total_watts = sensor1 + sensor2 %} {{ total_watts }} attribute_templates: watts: >- {% set sensor1 = state_attr('sensor.energy_production_d2', 'watts') %} {% set sensor2 = state_attr('sensor.energy_production_d2_2', 'watts') %} {% set ns = namespace(output={}) %} {% for time, value in sensor1.items() %} {% if time in sensor2 %} {% set sum_value = value + sensor2[time] %} {% else %} {% set sum_value = value %} {% endif %} {% set ns.output = dict(ns.output, **{time: sum_value}) %} {% endfor %} {% for time, value in sensor2.items() %} {% if time not in sensor1 %} {% set ns.output = dict(ns.output, **{time: value}) %} {% endif %} {% endfor %} {{ ns.output }} wh_period: >- {% set sensor1 = state_attr('sensor.energy_production_d2', 'wh_period') %} {% set sensor2 = state_attr('sensor.energy_production_d2_2', 'wh_period') %} {% set ns = namespace(output={}) %} {% for time, value in sensor1.items() %} {% if time in sensor2 %} {% set sum_value = value + sensor2[time] %} {% else %} {% set sum_value = value %} {% endif %} {% set ns.output = dict(ns.output, **{time: sum_value}) %} {% endfor %} {% for time, value in sensor2.items() %} {% if time not in sensor1 %} {% set ns.output = dict(ns.output, **{time: value}) %} {% endif %} {% endfor %} {{ ns.output }}

@slipx The battery was delivered today. Looks like it was manufactured 1 March 2023. So old stock :(

https://www.jendustries.co.za/sun-batt-lv

Yes that makes more sense. It also becomes very complex trying to do all the calculations on multiple batteries. When people ask for extra toggles or info that's not part of the default card I usually suggest the stack in card

@slipx , Check the Offgrid Garage Youtube https://www.youtube.com/watch?v=fT40MtzaaLQ
He shows the procedure from 16:00 onwards.

Yes that makes more sense. It also becomes very complex trying to do all the calculations on multiple batteries. When people ask for extra toggles or info that's not part of the default card I usually suggest the stack in card

v6.7.0
🚀 Exciting New Features
feat: added new inverter models for EASun, Ferroamp, Sigenergy and Linky closes #657, #579
feat: six essential loads can now be displayed on the card without the need for wide screen display mode if certain conditions are met i.e. mppt <=3 on lite card and !show_aux on full card etc closes #635



Full Change

@slipx replied to you privately but confirmed with Naeem I can post his contact info here. I just got a 48kg from him R1280 delivered to me. 9kg I got for R290 delivered.

Contact:
Gamza Karriem - 083 212 4070
Naeem Karriem - 072 176 2287

Yup. Been running this setup for the last few years. I’ve set the Gas geyser temp to 50degrees. So it only heats up if the incoming water is below this temp.

Been thinking about adding this to the card. Here is another way to calculate using a sensor template in HA for those who don't use Node Red
- platform: template sensors: soc_battery_time_left: friendly_name: "Battery Depletion Seconds" unit_of_measurement: Seconds value_template: "{{ ((((states('sensor.battery_soc') | float - 20) /100) * 15960) / ((states('sensor.load_power') | float + 60 ) | float) * 60 * 60 ) | timestamp_custom('%s', 0)}}" soc_battery_time_left_friendly: friendly_name: "Battery Depletion Time" value_template: > {% set time = states('sensor.soc_battery_time_left') | int %} {%- set minutes = ((time % 3600) // 60) %} {%- set minutes = '{} minutes'.format(minutes) if minutes > 0 else '' %} {%- set hours = ((time % 86400) // 3600) %} {%- set hours = '{} hours, '.format(hours) if hours > 0 else '' %} {%- set days = (time // 86400) %} {%- set days = '{} day, '.format(days) if days > 0 else '' %} {{ 'Less than 1 minute' if time < 60 else days + hours + minutes }} 15960 = Battery capacity in Wh (Update to match your battery size)
20 = Minimum SOC
Added 60W as per your logic to cater for inverter self power
Probably add it to my load shedding card 

Hi @Muttley @IggyP . Its a known issue with that card. Here is a link to the fix
https://github.com/AmoebeLabs/flex-horseshoe-card/issues/88#issuecomment-2145334978

Hi @Muttley @IggyP . Its a known issue with that card. Here is a link to the fix
https://github.com/AmoebeLabs/flex-horseshoe-card/issues/88#issuecomment-2145334978

First of all, thank you again for everything.
Finally I have been able to install the dashboard well by changing several parameters in the yaml and removing things that I am not going to use. I think everything works correctly and it is beautiful.
I still have a lot of work to do and learn, but I am definitely grateful for the work you do for the community.
I'll keep an eye out for updates, I'll probably need help again hahaha.
Translated with DeepL.com (free version)

@-cK- this has been added to release 6.5.0 🙂
 
https://github.com/slipx06/sunsynk-power-flow-card/releases/tag/v6.5.0
 
 

It's only applied to the individual essential loads at the moment. I can look to apply it to the total essential load as well.

Hi. Its a good idea but setting this as a global variable (the easiest option) may not be that useful as I assume you would want to set this per load. I'll add it to the ideas list 😃
 
OK not so hard to implement
 

Hi. Its a good idea but setting this as a global variable (the easiest option) may not be that useful as I assume you would want to set this per load. I'll add it to the ideas list 😃
 
OK not so hard to implement
 

Hi. Those should be added to the load section
load: show_aux: false off_colour: grey show_daily: true animation_speed: 8 max_power: 8000 load1_name: Geyser load1_switch: switch.geyser load1_icon: sensor.template_mdi auto_scale: true path_threshold: 90 etc

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

I'm now part of the I'd like more batteries as an option club...
Digging the concept from Sidewinder as I'm runng two instances of the card.  One on my main dashboard in lite mode so the single virtual battery here is fine and then a panel card dedicated to just my solar setup and there I run the full card so thinking I could set the virtual battery as the default on the lite and then the 4 indipendant batteries as on the full card if this happens down the road.
In the mean time I've dumped the BMS data to a dedicated page for just the batteries.

 

OK so the runtime and charge text would only be for the "virtual" battery which is reported by the inverter. Then each individual battery voltage, current and power you read directly from the BMS?
Maybe there should be an option for different battery displays i.e.
Option 1 - 1 virtual battery (default)
Option 2- 2 virtual batteries (for larger inverters that support multiple inputs)
Option 3 - 1 virtual battery, but display individual battery stats from BMS ( as per your example above)
 
 

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

Just a quick line to thanks to slipx and you guys for all this effort. i created my first ever dashboard with the power card and got it working (well mostly). Im running the solar assistant integration and am missing a few sensors /entities, so i need to figure that out now.
Keep up the great work.