One thing I noticed: The sensors for produced and consumed energy for the energy dashboard can’t be used right away. Do I need to generate helper to sum up the values from these sensors for the energy dashboard?
I observe a strange behaviour on this ‘produced’ and ‘consumed’ sensor and I can say this:
- it seems to me that the master battery will read the combined value, so use only the first battery
- in case it’s not like this, in your energy dashboard, you can add multiple batteries as well
The component reads this sensor once an hour and treats it as ‘total increasing’, which would mean that you could use it like this in the energy dashboard.
But I have some doubts now if the master battery gives consistently the combined value or not.
I have the same issue with the capacity sensor, which most of the time gives a combined value, but there as some interruption.
Is it a software issue from SAX? Is it my RS485 connection between the 2 batteries?
I’m wondering if in the case you have 2 batteries, what can you read in the last 48 hours on the capacity sensor?
And what can you read on the consumed and produced sensors?
This would help a lot. From another user on the gitub repository, it seems confirmed that the master battery is reporting the combined value.
What can you read on your end?
I only have 1 battery, so I cannot follow your problems. On my side the sensor delivered better values when going down from 3600 seconds to 60 seconds. But it still does not behave like a Riemann integration helper sensor. Maybe I try to simply make a helpers on the power coming from the battery, one tracking the positive values and one tracking the negative values.
I observed the energy produced and consumed sensors are not increasing on my side. So it is not behaving like a counter only counting up, but also drops and is even sometimes 0. So what the energy dashboard would need is an integral sensor like Integral - Home Assistant.
Thanks, you are right, Home Assistant expects it differently. In the meantime, Riemann Sum is your best alternative.
I will try to work on additional sensors for this and keep the ones untouched, depening on the use case, this value might serve some people.
I have just released a new version with 2 new sensors:
- Sax Battery Cumulative Energy coming out of the battery
- Sax Battery Cumulative Energy going into the battery
Both can now be directly put in the energy dashboard.
To the add-on!
1 Like
I have one question. I read that dynamic provider Tibber can be integrated with SAX now to start charging from grid when price is low. You need clever-pv for this. I don‘t like to go the worksround with another software like clever-pv. Is it alsonpossible with this integration to charge battery from net not only when solar power is high but also when price is low in winter nights?
Thanks Dirk
yes, it’s possible if you control the registers. You can then write any automation on top.
1 Like
Hello
Thank you very much for your work.
I have 3 Sax battery and the Smartmeter ADW200
I installed your software yesterday and the update from today.
I can not find the “PV-Leistung” and the “Netz-Leistung”
There are also quiet a lot of Sensor-values which look not logic for me.
Maybe you can help me.
Br Peter
Hi Peter,
Thanks for your interest. I do not have the smartmeter you mention which has the advantage to collect all the measures from photovoltaic production and the utility consumption.
The documentation starting on page 45 does not provide any information. All the sensors I have added comes from this documentation and from a previous documentation that has now been removed.
If you can play with a modbus reader or similar to what you have at the beginning of this post, find iteratively the values you are looking for, i would be happy to add it as new sensors. I need for this the slave ID and the register.
Maybe you can share all the values you get on all the sensors (Enable them all, lots of them are probably disabled) and share simultaneously a screenshot from the SAX dashboard.
1 Like
Hello matfroh
Thank you for your feedback.
Here the printscreen from all activated sensors (sorry, there are also 2 from Homematic).
Im brand new with HA.
But i will try with de Modbus and give you a fedback.
Br Peter
interesting!
My guess is this is your grid values, so you are right now injecting current with this Amperes on each phases. If it would be negative, you would be consuming that. Again, it’s just an educated guess.
Now from what I read in your screenshot, the voltage needs to be multiplied by 100 and those amperes need to be divided by 10 (in the documentation, the speak about a scaling factor, which was unclear, but starts to make sense here).
This then matches a total power injection of 766W at the time of the screenshot, can you confirm?
It wold be great to have the screenshot of the SAX dashboard (without serial number, please) and compare it at the exact same time to a screenshot of what HA shows.
Battery A is your master, so for the smartmeter values, that’s where we want to trust the values.
now Sax Battery A Active Power L1 , L2, L3 is the mystery, as adding them up should give us the total power. But maybe that’s how we get the solar power? Again, both screenshots in parallel at the same time is necessary.
Hello matfroh,
first of all thank you very much for your work and effort! The HACS integration enables newbies like me to use all that great stuff!
The implementation of my single Sax Home Power+ (7,7 kWh) into HA worked perfect, I only had to invert the apparent power of my shelly pro 3em meter to get the solar charging feature properly working.
There is one issue though, that I am not able to solve. HA somehow seems to lose connection to my sax battery from time to time (or rather most of the time). In between the connection works fine and during that all features work fine. I checked, if the hardware connects well (which it does) and with the sax app the connection also never seems to break.
My setup is:
- one Sax Power Home Plus, connected via cabel with a Wifi-Extender, which connects it to my fritz router
- HA on ‘home assistant green’ connected via cabel to the same fritz router
The issue is:
- most of the time instead of the values, “Nicht verfügbar” (not available) is displayed
- when I try to change parameters/switches the following message is displayed: "Die Aktion switch/turn_on konnte nicht ausgeführt werden. ‘<’ not supported between instances of ‘NoneType’ and ‘int’ "
I tried to change the setting for ‘pilot interval’ in both directions, but that did not seem to help anything.
Do you by any chance have an idea, what I could try or where I could look to pin down where the problems comes from or even to solve the issue?
I read in earlier replies that the parallel amount of request to the sax battery might result in a blockage. Unfortunately, I could not figure out how to reduce that. There are a number of sensors I could do without, though.
Your help would be much appreciated,
paranoidpaul
@paranoidpaul Cable rocks, and helps removing Wi-Fi as a cause for problems! It’s a good way to start debugging, even if temporary. Current code is probably to intense or not clean enough and we all experience some timeouts but never getting to the point of having unavailable values. Do you have many other devices using Pymodbus?
Try to bring the polling frequency to 2 minutes, what do your logs say? There is a slider for that in the UI under the device.
Yes, keep only a minimum of sensors, it’s a good practice although the code polls everything at once.
Also make sure to use the latest HA 2025.9 at least and the latest version of the code.
Dear mathfrog, thanks for the suggestions. I tried cable but it did not change much. There are no other devices using Pymodbus.
I tried various other things (commenting sensors in ‘constant.py’, changing the ‘pilot interval’, …) but I am not sure if that changed much or made sense.
Nonetheless, I do not have these problems with unavailable sensors anymore. I might have had an HA core update in between, maybe that solved it.
I am sorry for this unspecific solution, this probably does not help much. I do not understand enough to try things on my own. But I would be happy to try things if you can tell me specifically.
Thanks and sorry again!
Hello!
I might have solved my problem now. I forgot to mention in my post yesterday that I reinstalled your HACS Sax implementation, which might have been the reason, why everything worked fine. Until … I changed the settings for ‘Maximum Charge Power’. After that, the sensors were ‘unavailable’ most of the time.
I installed the software ‘ParameterSetting’ from sax and found out, that the support from sax power had forgotten to switch ‘P limit’ on to allow me to change the limit values. I switched it on myself and now everything works fine.
Btw: the software ‘ParameterSetting’ from sax only connects to the battery if the main switch of the battery is ‘off’. This took me a while to figure it out.
Cheers, Paul
Always read carefully the documentation, this is clearly stated at the beginning. Keep in mind you are flashing settings, so any wrong step is risky! Read twice and go step by step 