Venus on raspberry device id changes

Node-RED
, ,
1

i recently switched from polling values from several Raspberry Venus OS (3.65) MQTT communication to OS large NodeRed and the builtin victron nodes just to notice that after Raspberry reboot or switching connectivity from VeDirect to CanBus or VeBus, the id of devices is changing, bringing down most of the victron node-red flows. Is there a way to dynamically pass the proper device IDs to the various victron NodeRed nodes ?
(with MQTT method, i first queried the Venus systems for a list of their devices, and then formatted the MQTT keepalive publishings and subscriptions accordingly … quite a task to program, but that method circumvented the the ID change ‘dance’).

thanks a lot - inputs more than welcome !
(and: yes, i also had a time when using modbus-tcp register queries, but those turned out to be quite unreliable and device ID handling was even more cumbersome …)

2

… following up - @Victron: any chance you will fix this ?
… What if you change the nodes identifier from ‘device id’ to either serialnumber
or some other (freely defineable) identifier and associate at NodeRed or Flow startup ?
or, allow some python code to be run at VenusOS startup to user-define device ids based
on device type and serialnumber ?

its still quite annoying and i do not think i am the only one out there with this request …

Thanks !!