I use the IsGreenModeOn setting in the Nodered VRM Node Api, using Installations, Modify Dynamic ESS Configuration to switch between green and trade mode.
Trade mode in the morning to sell first solar electricity at higher tarrif and Green mode around 12:00 preventing electricity usage from grid at the end of noon, which occurs in trade mode unfortunately.
This worked for a while, but since a few weeks it doesn’t work anymore, the isGreenModeOn stays false when requesting it an also in the VRM portal.
Also when setting green mode in the VRM portal, the isGreenModeOn stays false when requesting with Nodered.
Firmware version: v3.60~49
Firmware version: v3.60~57
Since 3.60 the settings of DESS are synchronized with the GX device.
Not sure, if that would affect the function of the VRM API here, but you now could also query the dbus on the path System/0/DynamicEss/OperatingMode to identify if green or trademode is enabled.
Thank you, It works using the Dynamic Ess Control Node now:
Maybe documentation needs update?
@dognose Would it be possible to get a example of the bash command to run in Venus OS to query and perhaps if possible example of how to set the strategy (greenmode vs trademode) in Venus OS?
/Kaj
I think I figured it out
dbus -y com.victronenergy.settings /Settings/DynamicEss/OperatingMode SetValue 1
Will set the strategy to greenmode according to the VRM settings & Dynamic ESS - but now its just a question of how long it takes before the strategy changes on VRM because its still selling from Trade mode which was set before.
For completness sake I assume the following will return DESS to Trade mode
dbus -y com.victronenergy.settings /Settings/DynamicEss/OperatingMode SetValue 0
Please anyone object if I’m doing anything crazy here 
/Kaj
Yes, that’s right. I think it can take upto 15 minutes, until a new schedule is created and the remote scheduler then notes the different mode.
When changed in VRM directly there is a “immediate recalculation trigger”, think setting the variable locally does not invoke this, just silently sync the setting and then takes effect in the next calculation run.
