Remote Control History

Not getting history this morning on the Remote Control web page:

Only tried to look at the log because my battery mysteriously appeared to have stalled at around 90% - no charge, no discharge.
Internet connectivity fine.
Solar still supported house demand and excess to grid, but battery should have filled to 100%.

After an investigation of various settings, 'Enable DC discharge' had been set to OFF.
Very keen to see the log to work out how this might have happened, but I curently have no visibility.

Icarus After an investigation of various settings, 'Enable DC discharge' had been set to OFF.

That's the forced-discharge one, isn't it? (Typically used for timed export.)

Eco is the one that would typically inhibit battery charge/discharge.

Icarus I find that if you refresh a few times it eventually will load some data

DD

I think I'm getting some random setting corruption.
When I finally got the page to refresh without 'trouble fetching data' I was seeing silly time values:

I'm wondering if the relatively new 'Preset Profiles' functionality on the SETTINGS tab will be worth exploring as a quick way to restore a bunch of settings to a known starting point.

Icarus "External Change Detected" usually implies a local modification via modbus.

Looking back through your posting history, you said you don't run home assistant, but do run the bbc app which should be read-only. Has anything changed since then ?

Just tried a small change via the API, and I got the expected log entry showing the API change, with no associated 'external change detected' messages.

I think the app might use the presets ?

Icarus You reported something similar previously

https://community.givenergy.cloud/d/5067-settings-alignment/20

DD
I do use the wonderful BBC app, mainly for monitoring in the kitchen.
It does provide more than read-only access and on occasion I will force a Charge or a Discharge when my automation has failied to spot the ideal times to take such actions, though that is rare.

In contrast my automation (just java code on a R.Pi) will use the API and not result in the 'External Change Detected' messages, so I suspect it is the BBC app talking direct to Modbus locally that occasionally provokes the strange time settings, but that is by no means conclusive.

Rubikcube
Well spotted Rubikcube. Beginning to suspect it is only when I do a non read-only function within the BBC app.