Dynamic ESS on Node-Red - Schedule start using 30mins schedules for 3600s

Modifications
, , ,
1

If I use Dynamic ESS on Node-Red (running in parallel with the VRM version which is working fine) the 4 schedules are about 9 hours in the future, using 30mins schedules that have 3600 validity ?

Timezone is set to Western European Time. Flow variables stored by the Dynamic ESS node state that half-hour is false and country is NL.

debug example for 19:50 CET+DST (17:50 UTC) resulting in 04:30AM and 05:00AM:

topic: "Schedule 0"
soc: 83
feed_in: 1
duration: 3600
start: [1723602600](tel:1723602600)
restrictions: 0
strategy: 0
_msgid: "e5d60a9ea86e87e3"
_event: "node:8eb59a68b5e00348"

topic: "Schedule 1"
soc: 66
feed_in: 1
duration: 3600
start: [1723604400](tel:1723604400)
restrictions: 0
strategy: 0
_msgid: "e5d60a9ea86e87e3"
_event: "node:c6368abea029ee34"

Flow variables for that same point in time:
SOC:
15: 100
16: 100
17: 100
18: 100
19: 83
20: 66

2

What is your site id?

3

It’s c0619ab2ef52

FYI: I’m currently using DESS on VRM and the node-red version is tricked by disabling the output nodes and setting the flow variable to 4.

4

Just released an update (version 0.1.23) that fixes 30 minutes scheduling bug.

5

Confirmed. Many thanks.