The configured loads are working OK up to hour 13.36, when are switched OFF.
Feed-In is active and exporting a lot of energy, SOC 100%, Opportunity Load is configured for 1000W.
Is there a way to monitor or log the conditions for ON or OFF ? Something like a text box saying “ON for Feedin excess”, Fronius is having this small feature for load management status.
Hi,
Please ad a bit of information about your system (inverter, acpv, dcpv, …)
Is it three phased, single phased, saldating or phase individual Multiphase Mode?
It is a Multiplus II GX with 3.80-33 beta, installed on phase 1 from a 3 phase system.
There is only AC PV on AC In, Fronius ECO 27 with ~32KWp.
Measurement is done by EM24 ethernet, set as grid.
All Opportunity Loads are set on phase 1.
Fiddling around, did set “Allow additional loads starting at a battery SOC of” to 80%, actual SOC being 83%, and relays started clicking.
There is something fishy when that parameter is set to 100% SOC.
A single NODE-Red rule implemented, to limit charging current at 20A from hour 8.00 - 14.00.
Any advice is greatly appreciated.
Hi,
send you a PN, if you can give me your system ID, I could review some things eventually.
Chance you had this load turned on manually and switched it to “Auto” at a later point?
OL is going into “sleep mode” when it detects no usable solar overhead. If you just flip a running consumer to “Auto” during that time - OL will not take control until it wakes up the next morning.
That is on our todo to be improved as this is not transparently visible.
Started to test a Pro 2PM on another system and noticed similar behavior.
Both systems have Pro 2 PM installed but no actual loads on relay and just realised that might be a problem for Opportunity loads.
Turning on the relay, system “expect” to see a load increase equivalent to declared number.
No loads connected means that energy keep feed-in and Opportunity loads keep the relay ON, this should go on as long as feed-in is happening.
But sometimes relay has been stuck overnight and this might be a completely different bug, not related to no-load test situation.
Yes, with no load on the shelly, OL will learn that that shelly is consuming “0 power” in it’s current state.
Then - when there is no longer enough solar - that state just is “suitable, fits into budget”.
But that shouldn’t be a problem, what is the usecase of having a shelly managed by OL with no load attached?
It could be an Issue if a load has some self-managed behaviour to switch to 0 consumption (temperature limiting or sth.). Then OL will learn “0 watt” and not bother to turn that Load from “On (0Watt)” to “Off (0Watt)” when going to sleep mode.
But we can avoid that easily by not allowing OL to “learn” 0W, but just 1W as minimum to indicate “Opperational Standby”. Then it would attempt to turn it off guaranteed, when there is insufficient solar to cover 1W.
Being my first experience with OL and Shelly, did not bother to connect an actual load, just to tinker into a new system.
The two Shelly 2PM will be integrated as follows:
As you explained, the “0 watt” learning feature seem a bit strange to me, would definitely use a switch to turn it off, the sleep mode as well, hopefully this options will be available in the future.
The preffered way of work would be to simply turn relays On/Off based on declared power consumption, feed-in power and devices priority.
Could you please ellaborate a little ? Not quite following you.
Hi @Radunre, in short what it means is: Opportunity Loads depends on measurements.
The reason is relatively simple: When the algorithm only knows the expected power consumption that you configured, it has to reserve that amount of surplus power at all time, which will “block” turning on loads with lower priority if the device’s actual power consumption is lower or even 0W.
A good example is your water heater with its integrated thermostat. If it has reached its target temperature, the electro-mechanic switch will switch the element off. Only if we have the actual measurements of that device, we can detect that and reschedule the reserved surplus power to lower priority consumers.
Hy @ptrenz , thank you for explanation, clearly makes sense.
Most likely that is the reason for required condition of Shelly devices with power measurement.
The point that is unclear to me, what if:
Will this sum of conditions lead to heating water from batteries or is there a logic to prevent it ?
Why is it necessary to implement a sleep mode for Opportunity Loads ?
Hi @Radunre,
what you describe is also what we have discovered. Therefore, we have added a fix that makes sure that Opportunity Loads always correctly switches off. It will be available soon in an upcoming Venus OS Beta.
When not in Sleep mode, Opportunity Loads will always ensure the expected control state – overwriting other manual or automatic controls. Therefore, the idea was to allow especially Shelly devices to execute their own schedules during night, e.g. so that a boiler can reach its target temperature at least once per day if there was not enough solar.
Thank you for the update, looking forward for new features and fixes.
