Replies: 5 comments 17 replies
|
Please note that my inverter outputs 4000W max. So a 1% step in my case is 40W. This new integration clashes with another Automation that I use to heat up the water in my DHW storage tank from the available surplus solar power. So more programming ahead for the future :) |
|
Perhaps I have misunderstood you, if so, please ignore my post but You might want to double‑check the trigger logic. In Home Assistant, a time_pattern like: seconds: "10" doesn’t mean “run every 10 seconds”. It only means “run when the clock’s seconds value is exactly 10”, which is once per minute. The same is true for: seconds: "15" It still runs once per minute, just at second 15 instead of second 10. If the intention was to run the automation every 15 seconds, the correct syntax would be: seconds: "/15" That pattern triggers at 00, 15, 30, and 45 seconds — four times per minute. |
|
Thanks for pointing out that error! Corrected in the first post. |
|
My latest automation code is updated in the first post. I creates a dead-band from +20 to -36W around the zero point. |
|
Some pictures showing some results: This picture shows the result in my home for today, various power sources have been running today, washing machine, dryer, airco: And this picture shows the controlled AC ouput of my SolarEdge: At the first large dip in the trace, just before 1pm, is where/when I enabled the automation. |
|
@WillCodeForCats with the above shown automation active, after some time the modbus connection is lost. I see this in the HA Logs: Do you maybe have a suggestion on how I could recover from this situation without needing to reload the integration? |
|
Today when I enabled the Automation the modbus-communication worked immediately, no modbus-related messages in the log 🙂 |
|
A new major version pre-release is now available: Release v4.0.0-pre.0 This uses a new library called modbus-connection instead of using pymodbus directly. Please try it and see how it handles these connection and reconnection issues. |
|
@WillCodeForCats After running for24hrs I see the following messages in the HA Logfile: 
And a little later: These look very similar to messages I would see before the 4.0.0-pre.0 update. |
|
These errors might not actually be caused by your automation but rather by the inverter doing its daily "warm restart", because my inverter also logs these types of errors and warnings on a daily basis even though I'm just reading modbus, not pushing any changes to the inverter. See also: #1015 |
|
Correct, @WillCodeForCats already made that remark, these messages are all related to the modbus communication layer. That's an interesting observation you make in #1015, I'll keep an eye out for log-entries myself. |
|
I found this: https://community.home-assistant.io/t/home-assistant-reload-integrations-automatically/945813 |
|
This automation is no longer required after the v3.3.2 update. |
|
@bouwew Nice work! I think for many people in The Netherlands it'll make perfect sense why this is useful (in Dutch terminology: If a SolarEdge system also have DC-coupled batteries, and these batteries aren't fully charged yet, it could well be that your panels continue to charge your batteries, using all available power (up to whatever your batteries can accept), with just the amount of power needed for the house consumption, and any surplus going to the grid. In such a case, you want to avoid grid exports to avoid costs or penalties. For example, my panels could be producing 12 kW, my batteries can charge no faster than 5 kW, and my house could be consuming 1 kW. Then we have a surplus of 6 kW that would be exported to the grid unless we restrict inverter output. Obviously, that will have the effect of curtailing solar production to 6 kW, but that's the result, not the control. In your opening post, you stated that you're manipulating the "solar output" of your inverter, but following the previous paragraph, that's not entirely correct. What your automation is doing is actually manipulating the power being produced by the inverter itself, which could be going to the house or to the grid. So instead of saying you're modifying "solar output", I'd like to propose you change that to "inverter output" (which has the knock-on effect of curtailing solar production) so that others who stumble upon this topic won't get confused. |
|
@erikgeurts thanks for your feedback. Some changes were made to the first post. Please note, I don't have a home battery, I don't know if this works with a battery as part of the system. |
|
I'll have a closer look at your automation, and test it for my use case, including how limiting inverter output and having batteries works together. In some cases, there might actually be a good reason to continue exporting when the batteries are already fully charged, for example, with dynamic electricity rates. In such a case, the only reason to stop exporting would be if the rate goes negative. Many people will also have additional considerations and equipement, for example I have a car charger that can monitor grid power (import or export) and adjust the charging speed in real time to avoid exporting and use as much surplus solar as possible. Obviously, that would be fighting against this automation, and it might end up with a situation where the car isn't charging on solar because the inverter reduced output. I'll update my findings here, but note that this might take a couple of weeks or months. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi all,
I recently found out that it is possible to limit the electrical output of my SolarEdge inverter with this Integration by modifying the
Active Power Limit.This should not have any effect on the life-time of the internal memory of the inverter.
So it tried building an Automation that keeps the output of the SolarEdge in line with my consumption and limits the export of excess solar energy.
This is what I made:
My
sensor.el_net_consumptionshows the net electrical power value that it either consumed or exported (coming from the P1 port of my DSMR smartmeter). Export is shown as a negative number.The
sensor.solar_poweris just the SolarEdge reported AC power with a sign-change to positive numbers.It looks to be working reasonably well.
I had to increase the trigger interval from 10 to 15 seconds because it looks like at the 10s interval the modbus comms is lost after a while.
All reactions