Another Strange DESS behaviour

Here is a cleaned up flow for using price schedule triggers (for instance to switch on/off the periodic full charge override)

Top group creates an hourly timestamp ‘on the hour’
Middle group uses Node-RED DESS price schedules. (if installed, DESS mode can stay on 1: auto / VRM)
Bottom group uses VRM DESS price schedules.

You need to have VRM-API up and running or Node-RED DESS (or both) . The Node-RED DESS group needs to be in the same flow as the Node-RED DESS Dynamic ESS node because that node stores its ‘stats’ in the flow context. See also the price functions for the differences in accessing VRM-API versus Node-RED DESS scheduling stats. and how the average is calculated, adjust to your needs where required.

The price averaging takes todays price average upto the moment new prices roll in, then it calculates a rolling 24 hour window average, until midnight.

…flow deleted…

PS, I use this on tibber dynamic pricing with equal sell and buy prices and a battery cost of 10ct.
When the hourly/current price is 5ct below average it sends a ‘buy’ signal that switches on a full power charge run (and off when price gets higher again).
And when price is above average it sends a ‘sell’ signal, that I use to override the schedule strategy to lock it into ‘1 : self consumption’.

1 Like