I've just been looking at the AIO logs (something I do not do on a regular basis) and I have seen the following. I am not aware of triggering anything but there are a lot of External Changes.
Does anyone have any idea what these are for or why they have happened? Has anyone else with an AIO got similar?
CW None of them have previous values that have been changed. I wonder if these are AIO configuration items that have always been set on the AIO but the portal has only now started taking a copy of? Which is why they appear as external change detected?
geoffreycoan I really don't know - they all happened in the morning at once - I hope nothing is changing anything, because the system is working fine at the moment and I would like that to continue!
It's the "External Change Detected" that confuses me - what is that source, and is it just a "Read" or is there a change being made to the value shown?
CW Has anyone else with an AIO got similar?
Nothing similar here. Looked over the last week (which included serious AIO downtime while a new CU was fitted.).
Running D0.614/A0.614 and BMS10, with A0.010 on the Gateway. System controlled pretty much exclusively by Predbat, and all log entries look like typical Predbat stuff.
CW It's the "External Change Detected" that confuses me - what is that source, and is it just a "Read" or is there a change being made to the value shown?
Its not very well described in the system log but to explain:
The portal contains a copy of all of the inverter settings and the givenergy app gets a copy of those settings from the portal. If you change a setting (e.g. start charging) in the app then it sends the change to the portal, then the portal sends the change to the inverter.
If you make a change to the portal then it obviously just sends the change direct to the inverter.
In this way it all works, the portal (and hence the app) knows what is set in the inverter.
However, the flaw with this is if you use something like Home Assistant and GivTCP or you use the Rubik Cube or BBC inverter apps then they all write commands direct to the inverter and do not go via the portal.
The portal is thus oblivious to these changes, it has an out of date copy of the inverter settings.
And this is the way it worked for quite a while. If you only used the GivEnergy app and portal it all worked fine but if you also used some form of local inverter control you had to be aware that the app/portal wouldn’t necessarily have the up to date information and you needed to do a ‘read’ of the inverter settings before changing them in the portal.
Then late last year GivEnergy introduced to the portal an automatic synchronisation of inverter settings BACK into the portal. These appear as a ‘read’ and ‘external change detected’ - i.e. the portal is reading the inverter and detects that something external to the givenergy app/portal ecosystem has changed the inverter settings.
(When this was first introduced they all appeared as ‘writes’ in the portal log which was even more confusing)
So what you are seeing is the portal recognising that something on the inverter doesn’t match what it thinks they should be. As I said though for none of these settings are there a ‘before’ which is what the portal thinks the setting originally was, so makes me think they are newly synchronised configuration items.
I wouldn’t worry about it.
But again another example of GivEnergy changing things and not telling anyone
I suspect the server is working its way around the fleet gathering an initial state - it may be doing so in batches, but as it seems to be focusing on a lot of the non user changeable / hidden & frankly from my part unheard of registers, that would be my guess before it starts to pick up more user changed settings on a regular basis.
An aside there's some quite interesting / weird things coming up in that list I've not seen before.
Things like fans (Giv kit doesn't have them, but Polar does, not sure on the AIO2)
LCDs - again Polar has and I think the AIO2 has a little screen on it.
Local registers for tariff price is another one I've not seen before, suggesting they may be readying a more local approach for charging.
Generator start/stop - pretty sure the AIO2 gateway has some sort of control for firing generators up and syncing to them.