# Node Red on fresh 3.50 & 3.62 gives TypeErrors for all Victron nodes on imported flow **URL:** \ **Category:** Node-RED\ **Tags:** node-red, diy\ **Created:** [1 July 2025 15:36 UTC](https://community.victronenergy.com/t/node-red-on-fresh-3-50-3-62-gives-typeerrors-for-all-victron-nodes-on-imported-flow/37942 "2025-07-01T15:36:11Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![CapnIain](https://avatars.discourse-cdn.com/v4/letter/c/cc9497/32.png) [@CapnIain](https://community.victronenergy.com/u/CapnIain)\ **Post date:** [1 July 2025 15:36 UTC](https://community.victronenergy.com/t/node-red-on-fresh-3-50-3-62-gives-typeerrors-for-all-victron-nodes-on-imported-flow/37942/1 "2025-07-01T15:36:12Z")
I wanted to test a working flow with 20 or so nodes (mainly victron ones) for distribution to some other boaters. On V3.50 (after exporting the flow) I did a “Node-RED factory reset” and imported the flow. Once I deployed it I got the following error emitted from all the Victron nodes (but not the standard ones): 7/1/2025, 2:13:46 PMnode: Relay 2 (water heater) msg : error. “TypeError: Cannot read properties of null (reading ‘client’)” And in the browser console [Error] TypeError: undefined is not an object (evaluating ‘o.\_source.path.length’) (anonymous function) (debug-utils.js:418) handle (vendor.js:2:46668) dispatch (vendor.js:2:43096) Although this may be related to “Node Red on 3.60 Fresh Install Invalid Property” post earlier, that workaround didn’t help so I have put this in a new post. In this case, the workaround I found was to first install one of the victron built-in demo flows (e.g. Custom control reboot), Deploy it then disable and delete it. After that I could re-import my flow and successfully deploy it. Just did the same things with 3.62 with the same result ---
**Author:** ![JeroenSt](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/jeroenst/32/12543_2.png) [@JeroenSt](https://community.victronenergy.com/u/JeroenSt)\ **Post date:** [9 July 2025 07:34 UTC](https://community.victronenergy.com/t/node-red-on-fresh-3-50-3-62-gives-typeerrors-for-all-victron-nodes-on-imported-flow/37942/2 "2025-07-09T07:34:39Z")
I experience the same issue now on 3.70~6 and 3.70~7 after an update to 3.70~7. ---
**Author:** ![nickdb](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/nickdb/32/51440_2.png) [@nickdb](https://community.victronenergy.com/u/nickdb)\ **Post date:** [9 July 2025 08:12 UTC](https://community.victronenergy.com/t/node-red-on-fresh-3-50-3-62-gives-typeerrors-for-all-victron-nodes-on-imported-flow/37942/3 "2025-07-09T08:12:36Z")
Is this different to the issue requiring a new victron node to be deployed, accepting the errors on deploy, after which the nodes all work again? ---
**Author:** ![JeroenSt](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/jeroenst/32/12543_2.png) [@JeroenSt](https://community.victronenergy.com/u/JeroenSt)\ **Post date:** [9 July 2025 08:33 UTC](https://community.victronenergy.com/t/node-red-on-fresh-3-50-3-62-gives-typeerrors-for-all-victron-nodes-on-imported-flow/37942/4 "2025-07-09T08:33:15Z")
After removing the virtual device node, deploy and undoing the removal with crtl-z followed by a deploy it works again.. > [@Venus OS v3.70~9 available for public testing](https://community.victronenergy.com/t/venus-os-v3-70-9-available-for-public-testing/36338/88): > > After updating to 3.70~7 the custom input nodes of nodered don’t work anymore, so I don’t see PV generation and also no temperatures I inject via Node-RED. Update: After removing the virtual device node, deploy and undoing the removal with crtl-z followed by a deploy it works again.. ---
**Author:** ![nickdb](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/nickdb/32/51440_2.png) [@nickdb](https://community.victronenergy.com/u/nickdb)\ **Post date:** [9 July 2025 08:40 UTC](https://community.victronenergy.com/t/node-red-on-fresh-3-50-3-62-gives-typeerrors-for-all-victron-nodes-on-imported-flow/37942/5 "2025-07-09T08:40:53Z")
This has been mentioned a few times on this section in other topics. You can just deploy a new node, click through the deploy errors and the rest should recover.