Battery charge setting reverting to previous value.

5 comments started 2022-08-09 last 2022-08-09
GivEnergy ProductsAC Coupled
#1 Woodstock

Yesterday morning I changed the battery charge power from 573W to 1065W in Inverter, Settings, Battery Options. This took effect and battery charged at 1065W until full. Remote control showed update and new 1065W setting.

This morning looking at the power graph I noticed that the battery was back to charging at 573W!

Went into Remote and checked the charge setting and it was still showing 1065W.
Checked remote history and there were no changes after the 573W to 1065W increase yesterday.
Went into Inverter, Settings, Battery Options and it was still showing 1065W.
Hit the send button only and it said update successful (as it did yesterday).
Battery charging increased from 573W to 1065W.
Went back into Remote and checked Remote History. Today's update only showed when turning off "Filter same value responses" and showed previous 1065W, requested 1065W and response 1065W.

At a loss as to how the battery charge setting reverted from 1065W to 573W with no outside intervention and then was manually kicked back to 1065W with the system history showing no changes throughout the whole process?????????

T
#2 Tim

Woodstock Maybe raise this as a bug report? It's one thing to set things incorrectly because you don't understand how the developer's mind works (which you haven't) but its another thing when you set values and they are saved and then they change and there's nothing in any logs to help work out what happened.

This comes back to a feature request I made ages ago (and probably others too) to make the Notifications and Inverter Logging more granular. Apart from some notifications about BMS in June and Battery connections in February, neither of which were things I could do anything about, there's nothing else there, but there's plenty happened to the inverter. Similarly, the remote control log lists all the things I've done but not all remote control commands that the inverter has received (two calibrations case in point).

#3 hoggy

Tim there seems to be a lot of weird things going on with settings changes from a few people who are adamant they haven’t.
Sometimes it’s user error but I don’t think that’s all of them.
I think there’s a bit more going on behind the “smarts” now and a few different flows running which may have bugs in them? Or just being triggered when they shouldn’t.

Smart Tariffs : it’s been noted on FB that if you have enable smart tariff to set you charge timers then this appears to reset itself back each night if you manually change it during the day.

Pause: this is not something the inverter can inherently do, so what actually happens is their api sets both discharge sliders to 0. Unpause puts them back. Charge now & discharge now do similar mods to the timers by setting them to start \ end 00:00-23:59, then set them back to whatever they were.
It’s the “whatever they were” part nobody knows how it does this, presumably it takes a snapshot of “before” to use as after.

#4 Woodstock

hoggy Could well be but in may case I have no tariffs (smart or otherwise) enabled.

T
#5 Tim

hoggy a few different flows running which may have bugs in them?

I use MQTT for all of my home automation and can see all the traffic in MQTT Explorer, but the REST point calls don't show up there (because they're HTTP not MQTT). Anyway the point is that if the inverter logs each incoming instruction (whether from http, Modbus over TCP, or MQTT, or even IFTTT if it's useable, and wherever it comes from), and that log is visible, then at least we have half a chance to see what's going on. Maybe Givenergy does this but that's of no help to us trying to understand things and having to resort to a phone call to ask what's going on. Ideally, the logging could be configured so that only instructions that change parameters are kept. I'm not especially interested in instructions sent to the inverter, just ones that the inverter receives. In fact that might be part of the issue; one command is received and acted on and a subsequent command doesn't get through.