So, every 10 minutes it will trigger an event. Then, using a “time range” node, select the path to turn on or to turn off ESS charging and set a new grid set-point. I got a filter just to prevent sending commands for nothing.
When I deploy it, everything works like it should and Node Red will disable charging the batteries after sunset. However, every morning it should turn it on back again but nothing happens.
If in the morning I do a little change to the nodes layout and redeploy it, then it sets the charging properly.
Am I missing something? Any suggestion on how to troubleshoot the problem? Does Node Red keeps running when I get off from the GUI?
The filter nodes will only let a single message through. You need to use single Disable Charge and Grid Set-point nodes, each with a filter in front and connect two Send nodes to each of these filters.
It did not work, I got the very same behavior I had before.
But this morning I noticed that the Venus MQTT was not sending any message. I could notice this because in my HomeAssistant I did not have any update from the data I collect from it.
However, as soon as I opened venus-gui-v2 it starts sending the MQTT data. I am not sure but I think this is the second time I face this: the MQTT will stop working if the venus-v2 gui is not open.
I will do the same this night (close the venus-ve gui) and try to correlate. But, as I am quite new to using Node Red in Venus, I would like to know if there is any configuration on it I may be missing to keep it running if no one is accessing its GUI interface.
@40000000681e2eb90577f894 *** CCGX booted (0) ***
@40000000681e2eb9376ef0dc *** starting dbus-systemcalc-py ***
@40000000681e2ec50de8c4a4 -------- dbus_systemcalc, v2.202 is starting up --------
@40000000681e2ec50ef546ec INFO:logger:Loglevel set to INFO
So, I had a reboot.
Just before, I had: com.victronenergy.vebus.ttyS4 disappeared from the dbus
The logs shows that several devices disappeared from the D-Bus and the watchdog rebooted the system.
