I had a bizarre behaviour last night. The automation to charge the battery ran successfully twice, but the values were not updated in actual causing the battery to stay as it was and not charge.
It works usually so I am not sure what happened or how to fix it so that it doesn’t happen again.
I had this the other day as well. I had noticed when using the GE dashboard that occasionally when I tried to update a parameter it gave me a timeout message and didn't "stick" till I wrote again.
I have been considering a "checking" automation which reads values and alerts me (telegram message) if it is not as expected. Who watches the watchers though :-)
Happened to me as well - TCP control has been stable for a long time but GivEnergy have reported cloud was down between 02:00 and 06:00 today - Had the same before when they had server problem. I would really like to block remote control and just use the cloud for monitoring. Have considered blocking it completely but that could give problems with GE diagnosis in the event of a fault..
I suppose GIV-TCP could have a feature to block remote commands from WAN?
Aidan no wonder, i had two automation runs, 1:00 AM and 02:30 AM and both did not set the correct registers, I am happy today is sunny so the battery will get topped up full by the peak rate time otherwise it would have been a problem.
i guess in such a scenario, there is nothing much we can do ! MikeBakke If we have a watcher , even that would not be able to update the GivEnergy inverter.
Seems a bit strange though, why would a cloud failure impact the local Inverter commands?
There are many strange things happening. I went to check tomorrows weather to set my overnight charge %ge and the whole invertor was in amber status - had been since about 17:20 so missed a chunk of peak rate battery usage >_<
I hit restart and after a nerve-wracking length of time it decided to go green and start using the battery again. Checked notifications but no error messages since September. Then I noticed battery reserve value was set at 100% - it's usually 4%. I manually reset it and checked the invertor logs. I could see my reset from 100 down to 4, but there was no corresponding change from 4 to 100...... muy, muy confused...
Sigh - will work on some proactive polling and alerting tomorrow because it seems to be required.
deepanshus what if you update the local register but when it tries to write to the cloud, it fails and the invertor says - well it should be what it used to be and reverts to that state. <shrug>