Identifying source of commands in Inverter logs

I have just started using GivTCP in HA with Predbat as a replacement for the Myenergyoptimiser cloud service. All set up and so far so good. I’m wondering though if there is a way to identify the commands my HA givtcp/predbat is sending to my inverter in the inverters own logs. All I see is that they are from User “Server” and in the Via field “External Change Detected”. This is the same as when GivEnergy themselves send commands to my Inverter, I would like to be able to distinguish those that my HA interface sends in the Via field in the logs, which happens when I’m sending commands from the myenergyoptimiser service. Is there a way to do this?

dnhenderson007 no there isn't

GivTCP directly makes changes to your inverter (via modbus), the portal then detects that the inverter settings are not the same as it thinks they last were so records them as 'external change detected'

You could use the gecloud integration in predbat to talk directly to the givenergy portal which then in turn sends the commands down to your inverter, and if you did that then you could create an API key specific for predbat, but this is less efficient than using givtcp directly as everything goes via the cloud

geoffreycoan Thanks for the explanation. Think I’ll stick with the better GivTCP method and just accept what shows in the logs.

Unless you have multiple automations running locally external change detected should exactly map to GivTCP.

If I make a change via the official GivEnergy app then commands appear in the log something like "App - Inverter Settings - Timed Charge".

If I make a change via Rubikcube's excellent Android app Monitor for GivEnergy Inverter then that is also direct to the inverter and cuts the API out of the loop. It is important to note that this is not the official app.

Thus the external change detected message as the remote state catches up.