No instructions getting to invertor

ALLENPATTRICK

Imaginary-risk
02:00
I was running a schedule from 0000 this morning and was surprised that my battery was being used when I set the first slot so that demand would be satisfied from grid. I alternated slots with no effect (ie the battery satisfied the load and position of slots appeared irrelevant. I have now deactivated this slot and put in a new one to start at 0230 with same settings…………..(there is nothing in the activivity log to show that anything has occurred. The battery at 0000 was already 100% and it was the intention to preserve this for much of the morning session.

0240
Continuing to draw from battery.

Grateful if you would investigate. I used the Hold facility for the first time yesterday with no problems and similar parameters.
Thanks

admin

ALLENPATTRICK The 2:30 one would have been actioned and held charge, but by then you seemed to have paused your schedules, which is why it was not actioned.

ALLENPATTRICK

ALLENPATTRICK
The SOC at 0000 was 100% when schedule kicked in. I had both selected and a unselected slot for the first 3 slots yet the battery was not held. The draw from the battery, and none from grid was evidenced in the Growatt log.

The subsequent actions including the pause and a 120 minute quick charge from 0215 were consequential and have allowed me to get to a stable state with help from Solar.

The position now is that I have reinstated the same 0000-0800 Hold schedule ready for tomorrow.

Hope you can help with why there were problems at 0000 today
Thanks

ALLENPATTRICK

ALLENPATTRICK just noticed that ar 2358 on the previous day that WW activivity indicated no action to a charge instruction since Soc was 100%. It seems that the Hold instruction for the schedule was then lost.

admin

ALLENPATTRICK Thanks for the details. We managed to track this down and it looks like there's a bug around hold for agile windows start/stop around midnight.

Fix is currently being deployed and should be available in the next 5-10 mins.

ALLENPATTRICK

admin
Many thanks. Will report back tomorrow.

ALLENPATTRICK

ALLENPATTRICK
The problem persists and no messages on activity log ,
On 26/11 2 slots were selected for 2130 and 2330 and neither were run and neither produced activity log messages. I expected the 2130 one to fail as it fell below the start SOC level but the schedule was not logged.

This morning there was no activity when the 0000 (hold) Schedule should have started. I then tried to restart the schedule a little later but without success. I later tried to run my DAY schedule which does not use the Hood facility and this also failed to run. I then deactivated all schedules and manually set off a 4 hour charge at 0115 from Growatt interface which seems to be running ok.

Grateful if you would check again. It appears to have upset my ability to run any schedules whether hold or not. Please let me know when I can run WW again. I am quite prepared to avoid the periods between 2300-0000 or hold off using Hold while you are hunting down the cause. I will disable the Growatt command later this morning to avoid it being run again. You may delete it if is at all likely to interfere with WW.

Many thanks

admin

ALLENPATTRICK Your Agile schedules are still paused. Unpause them here: https://app.wonderwatt.com/pause

ALLENPATTRICK

admin
Many thanks. Will try again tomorrow.

ALLENPATTRICK

Immediately before my 0000-0800 HOLD schedule was due to begin I saw the reassuring entry on the activity log. About 20 minutes in I was alarmed to see no scheduled slots activated despite these having been populated by WW the previous day. I quickly set these slots up to 0600 and a new session was begun at 0100. During the time it was running it charged my batteries from 30 % to 100% which it reached around 0400. Thereafter, it met consumer demand from Grid and the first kw of solar, not touching the batteries. The display of slot utilisation did not correspond to actual activity and finished slots were also being inaccurately shown.
At 0800 the next schedule started and the batteries are being deployed appropriately and the display of slots seems to have magically got back to normal and looks correct.
Apart from the problems that I experienced with the display is it the case that HOLD prevents only battery SOC being reduced but allows charging to 100%?

Many thanks. I am aware of other possibly related problems which will keep you busy. I will be extra cautious to ensure that the slot display for tomorrow morning has not changed from the night before.