Hello, i’m using the Github elekeeper integration and it works great, the sensors values are right but i’m having some anomalies with spikes in values everyday around 00:00 or 00:05. maybe I’m using the vrong sensors in the energy configuration dashboard.
Whenever I remember I clean the values in the statistics but the anomaly apperars everyday around midnight
As new user i can only upload one image per post, I’ll try to upload a screen of my energy dashboard config, maybe i’m only using the wrong sensors in the dashboard.
Thanks in advance to everyone coul help to solve this little issue.
Does anyone know if the register 8020H can also be used on an H1 inverter to sync the current datetime? The internal RTC of my inverter is slower than the real time, so I would like to be able to sync it by writing it via modbus. I sadly can’t find any documentation for the H1 inverter that confirms that this register 8020H is also writable like it is for the H2 and R5 inverters…
I am sure that there was a fork of the Component released by stanus74 but adapted only to the registers in common with the H1 series inverters, can anyone help me find it?
What route did you end up going? I am installing a SAJ H2 inverter next week, and I think AIO3 is very expensive for what it is. I have a bunch of ESP32 and Modbus adapters (like the one BenV linked) laying around. I thought it would be even cheaper and faster than the Elfin solution
Not sure which fork you are talking about, but you can also use my integration (over mqtt) from here: GitHub - h3llrais3r/ha-saj-h1-mqtt: Home Assistant integration for SAJ H1 solar inverters via MQTT
I’ve been using it for more than a year now without any issues.
This doesn’t require extra hardware and you can keep using the existing app.
You only need to bridge the mqtt server (or change directly to your local one, if you don’t care about the saj app)
When it’s dark, the invertor becomes unavailable. Resulting in many warnings.
Why not stop polling between sunset and sunrise?
Or is this a configuration issue? If so how could I do this?
Hi everyone, I’m currently trying to integrate my SAJ AS1 battery and I’ve successfully established a Modbus TCP connection with it. Has anyone managed to fully integrate it into Home Assistant and successfully switch between the different working modes?"
Hello Forum,
I am using the SAJ Solar Inverter integration and I was wondering if it is possible to use it to switch the inverter off or set the power output to 0.
Here in Flanders we have to pay to put power on the grid when the price is below 1.5 c€ per kWh, so it would be nice to switch the inverter off when that is the case and the battery is full.
All help is welcome.
Thanks, JP
we have a solar plant with 10 R6 50k inverters and now we're integrating batteries.
We're using our EMS that's being run on an industrial PC to control the solar plant. We don't have problems controlling the batteries but have trouble controlling the solar.
I managed to read registers with my laptop and modbus tester software from the inverters with RS485 to USB and RS485 to Ethernet converters but can only read one at a time. If I connect more inverters in daisy chain I get errors.
The inverters have AIO3 modules connected and can be controlled via cloud and I can also access them locally over bluetooth.
Do you have any suggestions? I'd appreciate the help.
I used the following modbus configuration to get the AIO3 module working.
Got some help from Gemini after feeding it an export of all the addresses using modbus poll, seems to work well enough and values seem to make sense (and match the elekeeper app.)
The only thing I'm not convinced about is the temperature, 18C seems very low as the room is closer to 27 at the moment.
Hope this helps!
edit
OK, a lot of garbage values it seems. Grid Frequency varies from 30 to 60 Hz and the inverter voltage went up to 7000 degrees Celcius this morning.
I'll edit the config down below with what I can double check to be correct.
configuration.yaml
modbus:
name: "saj_inverter"
type: tcp
host: x.x.x.x #input the ip of the module here
port: 502
delay: 2
timeout: 5