I have some flows that use Victron input nodes like Custom Input, Battery Monitor, Dynamic ESS and System. I normally set the Only changes property to only trigger the next node when there is a change in value. Since VenusOS v3.60, the initial trigger after a re-deploy doesn’t work anymore, which is a problem when the value doesn’t change often such as for instance AC-Input to check whether the grid is available. The label below the box only shows connected instead of the value. It still worked in v3.55, but not anymore in v3.60 and v3.62.
Curious, if you try the new beta (built on nodered v4) is it the same?
You can easily roll back via the backup firmware option on the GX.
I upgraded to v3.70~5 but unfortunately, this did not fix the issue. So perhaps it is an issue with the Victron nodes instead of node-red?
However, it did fix another issue I had: Since v3.60, the dbus-fronius log file would fill up with warning No functional TLS backend was found messages. That is no longer the case.
Thanks. I have mentioned it to the team responsible.
1 Like
As a workaround you can uncheck the ‘only changes’ box and use a filter node set to ‘block unless value changes’ right after the input node to ‘dedup’ the 5msg/s datastream.
1 Like
Deffo a bug. It will be fixed in due course.
@dick this is fixed in 3.70~7 beta
It is indeed fixed, but I now have a couple of new issues.
- I get a new login prompt when I access the gui-v2 for the first time via the local network. I read in another post that you could login with a space as password, and indeed, that worked.
- A node-red Custom Control node for
com.victronenergy.settings/Settings/DynamicEss/SystemEfficiencyreports:Not connected to dbus. Publish was unsuccessful. - A node-red VRM API node for
Get DESS configurationVRMreportsError fetching VRM data. - On a node-red deployment, I get a message about an unused Victron Energy Client node. What is that?
4.. check ‘Configuration nodes’ for unused nodes.