Release v0.4.485 - Date UTC->BST fixes

admin

Hi all,

Apologies again for the UTC->BST issues over the past day or two. Your patience is appreciated.

These issues should be fixed in the latest release, v0.4.485 and higher.

Anything you suspect is related to this, still, please report under this thread, thank you.

johalareewi

I had some 'ghost' slot selections for tomorrow. There were 3 auto selected slots when only 2 are in the settings. I toggled the active switch which seems to have sorted out tomorrow's slot selections.

admin

johalareewi Yeah, there still would have been some odd selections from the earlier versions of the population functions.

palaceben

Charging seems to have worked overnight 👍

However, as the fix came through late I had my Schedules paused, and had happily manually set my schedule for the night on the Growatt interface, so decided to leave it that way until WW decided it was going to disable AC Charge at (I think) the points where a charge was scheduled to start on the Agile schedule, so my first manually set charge didn't happen at 1am. At that point I decided to unpause the schedules and WW worked as expected from the next set half hour. I had a similar issue on Sunday night (nothing charged) until I removed all the selections from the Agile tab on Monday (charging resumed).

It appears "Pause schedules" doesn't pause EVERYTHING - which is not ideal!

coordinated-success

admin

palaceben You said you unpaused again? If you have no agile slots selected, they will be prepopulated when your Agile Charge window is active and provided Pause is off.

johalareewi

Looks to have worked last night. WW commands sent at the correct times with the correct time data for the inverter. Hold feature workied too.

palaceben

admin Once I unpaused everything worked normally. It was while it was paused that my AC Charge kept getting set to disabled. So while it was paused, and I thought I had full control, it seems that I didn't and my manually set charging periods weren't working if there was a period set by WW, even though WW was paused.

Digitalsafaris

My Agile WIndow is 0100-1600. The end of window reset commands, including resettng Battery Discharge Power, usually comes through at 1602. On 31st and 1st and just now on the 2nd, they came though at 1702.

Last night the start of agile window commands came though as expected 00:58 and the slot timers came though at the right time, (they were wrong the night before), so it just seems to be the end-of-window time that's not quite right yet.

Sorry that this stupid clock change thing is giving you such a hassle.

Watt ID afraid-candle

admin

Digitalsafaris Should be fixed now in release 495.

Digitalsafaris

admin All good at 1602 today. Well done. Thanks.

KristianS

Without wanting you to go into a flat spin early. Dare I ask if the work done for the GMT > BST clocks change has also ensured that the BST > GMT change in October will be a seamless experience....?

admin

KristianS Yep, that’s the idea!

palaceben

Any reason why my presets keep re-selecting themselves after I've removed some of them and added others?

coordinated-success

admin

palaceben Did you select others that are within your Agile charge window? If they are outside of your Active Agile charge window, they will be auto selected when your Agile charge window is active.

Gazzagreen

What happens if you move from Agile to another tariff such as Flux, does the agile window disappear, or not show new prices from Octopus?

admin

Gazzagreen You just set your Agile charge window(s) to inactive and use the custom Schedules instead.

palaceben

admin yes. I had removed a couple, I've added at least one period to my afternoon session, which had gone away, and I have now re-added - as I have been doing before. eg I had removed 10pm tonight, but I spotted at 10pm at had started charging. When I checked some that I'd removed from the overnight schedule had also been re-added. This has not been an issue before. At 4:30 I look at what has been selected by WW, and compare it with my own recomendations and make any necessary alterations caused by maybe the day being cheaper than the night, so requiring extra, and the night requiring fewer charging periods.

palaceben

palaceben Just tried to cancel my 1:30 slot (again), saved the new schedule, then refreshed the page and the 1:30 slot had reselected itself! This is happening repeatedly - I may have to just accept that the 1:30 slot is going to happen! It also reselects it if I save after desel;ecting, click on Home, then click back into Agile. Weirdly it is currently ONLY happening with the 1:30am slot - I've removed others and they have stayed removed. There's a fair chance I'll still be awake at 1:30 to cancel it on the Shine app when it starts. Also weirdly, it is NOT among the 6 cheapest slots in my overnight period of 23:00-08:30!

admin

palaceben We'll try and reproduce it.

admin

palaceben Can you just deactivate and activate your 23:00-08:30 charge window again by using the toggle?

We used the same Agile charge window as you with 6 slots, and the 6 slot block 2:30-05:30 is selected. Toggling 1:30 on as extra and saving, persists. So does removing the 1:30 slot and saving, it disappears fine.

palaceben

admin Sorry, didn't see this last night. When 1:30 came around no charge happened, and when I checked WW on my phone 1:30 was no longer selected, and looking on my laptop this morning it had been deselected. If you fixed it, thanks. If it fixed itself, or was just something random, then hopefully it won't happen again 🤞