Supporting multiple inverters and batteries is a common request, currently it is limited to displaying a single one of each due to screen/card space limitations, necessitating having to write up custom/derived sensors that show the totals of multiple inverters/batteries.
There is a ‘issue’ opened requesting multiple inverters/batteries being added to the card, on @slipx06’s GitHub repository for this card. As/if/when it is possible it is on the ‘nice to add’ list.
In version 2024.8.0 there are some new rules implemented to handle legacy browsers. If you are using a legacy browser, dynamic CSS and styles are no longer supported. This affects all custom cards. Unfortunately the card makes extensive use of this and it’s not feasible to update to accommodate legacy builds. The work around here is to either:
Stay on 2024.7.4
Upgrade your device/browser to a modern version
Change/spoof your user agent string
For reference the following are considered legacy browsers according to the new rules
Browser
Legacy
Current Modern
New Modern
Android
60
63
115
Chrome
60
63
109
Edge
16
79
115
Firefox
52
67
115
iOS
10.3
13
15.6
Safari
11
13
16.6
Opera
47
50
101
Opera Mobile*
-
80
80
Samsung
4
8.2
22
You can see more information about this issue discussed here
On the Solis Hybrid Inverters battery charge power and battery discharge power are 2 different entities both with positive numbers.
Do you have any suggestions on how best to use this for the battery charge and discharge data.
Thanks
I can’t figure out why the number on the right is double the number on the left. I do have a 24V Victron MP2 Inverter. Is that a hint I am not understanding?
400w + 380w = 780w total load for the house. What your diagram is showing what you are taking from the grid + what is going through your inverter be it solar or battery or both.
Breaking Changes
After HA version 2024.7.4 there was an update to the rules that determine the use of legacy or modern builds. The browser minimum versions that support the modern build were increased. This means that older devices and older browser version no longer support the modern build. The problem with the legacy build is it does not support dynamic cascading style sheets (CSS) or dynamic styles. This custom card makes extensive use of both of these features and will not render properly when using the legacy build. Unfortunately the only practical workaround is to update your device/browser to a version that HA considers modern or stay on HA version 2024.7.4. If you are using the companion app it is also a good ideas to make sure you have updated to the latest version. For reference the following are the browser versions that support the modern build: