# Network watchdog help **URL:** \ **Category:** Node-RED\ **Tags:** cerbo\_gx, vrm, cerbo-gx\ **Created:** [9 July 2026 15:33 UTC](https://community.victronenergy.com/t/network-watchdog-help/60228 "2026-07-09T15:33:32Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Outward6027](https://avatars.discourse-cdn.com/v4/letter/o/ba8739/32.png) [@Outward6027](https://community.victronenergy.com/u/Outward6027)\ **Post date:** [9 July 2026 15:33 UTC](https://community.victronenergy.com/t/network-watchdog-help/60228/1 "2026-07-09T15:33:32Z")
Is there a way in node-red to know if network has lost connection to vrm? I know the cerbo has a watchdog ,but i’m trying to reboot the router should this happen . I found this path but i cant find any info about it . ![Screenshot 2026-07-09 112832](https://europe1.discourse-cdn.com/victron/original/3X/d/0/d03204e3ef885fca9daa24167c654f5118923459.png) ---
**Author:** ![pwfarnell](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/pwfarnell/32/2341_2.png) [@pwfarnell](https://community.victronenergy.com/u/pwfarnell)\ **Post date:** [9 July 2026 19:44 UTC](https://community.victronenergy.com/t/network-watchdog-help/60228/2 "2026-07-09T19:44:54Z")
I have a Node-Red flow to do this. I use a custom input node to read the time of the last contact with VRM from the Cerbo. This is in milliseconds since a reference time. I then convert this to seconds and subtract it from the current time to give the elapsed time since last contact. If this exceeds a trigger value a reboot is forced. Of course this may also cause a reboot if VRM servers go down. ![IMG_20260709_204116](https://europe1.discourse-cdn.com/victron/original/3X/1/d/1d8bb5178d2d2a5831353f88d5ad94eb2c1ca498.jpeg) ---
**Author:** ![Outward6027](https://avatars.discourse-cdn.com/v4/letter/o/ba8739/32.png) [@Outward6027](https://community.victronenergy.com/u/Outward6027)\ **Post date:** [9 July 2026 20:29 UTC](https://community.victronenergy.com/t/network-watchdog-help/60228/3 "2026-07-09T20:29:31Z")
yes I found vrm connection error 0 is no error 153 is no connection , not sure if there are other errors. ![Screenshot_20260709_162254](https://europe1.discourse-cdn.com/victron/original/3X/c/f/cff2ac4e35421b69dda0d4919d5256ab7909a09a.jpeg) ---
**Author:** ![Dunnp](https://avatars.discourse-cdn.com/v4/letter/d/eada6e/32.png) [@Dunnp](https://community.victronenergy.com/u/Dunnp)\ **Post date:** [17 October 2026 01:52 UTC](https://community.victronenergy.com/t/network-watchdog-help/60228/4 "2026-10-17T01:52:05Z")
I had this working previously but now it’s not (v3.81). The com.victronenergy.logger shows as disconnected and no longer available. ![image](https://europe1.discourse-cdn.com/victron/original/3X/3/5/35bce93f5e18cc334c8b5b4e9eb3a3315b428e34.png) ![image](https://europe1.discourse-cdn.com/victron/original/3X/c/6/c62c631ec200240f93b9ac2328daa8c971256b5e.png) I’m not sure which OS version killed it and didn’t notice when it stopped working. Phil ---
**Author:** ![pwfarnell](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/pwfarnell/32/2341_2.png) [@pwfarnell](https://community.victronenergy.com/u/pwfarnell)\ **Post date:** [17 October 2026 08:07 UTC](https://community.victronenergy.com/t/network-watchdog-help/60228/5 "2026-10-17T08:07:56Z")
I can confirm mine is no longer working and com.victronenergy.logger also shows as disconnected and no longer available. V3.80. @dfaber bug or deliberate change. ---
**Author:** ![pwfarnell](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/pwfarnell/32/2341_2.png) [@pwfarnell](https://community.victronenergy.com/u/pwfarnell)\ **Post date:** [17 October 2026 16:02 UTC](https://community.victronenergy.com/t/network-watchdog-help/60228/6 "2026-10-17T16:02:35Z")
I deleted the flow and imported a copy of it that I have on my PC and the time since last contact from com.victronenergy.logger started working, but after a reboot it stopped working again. I also no longer connect to the reboot Node from Venus (0). ![image](https://europe1.discourse-cdn.com/victron/original/3X/8/1/81fd8fba3d4b2fa816e2033909618e73fd83329d.png) ![image](https://europe1.discourse-cdn.com/victron/original/3X/9/1/91fb9fc763f272bc3420d01de30a0a5281f0c74d.png) ![image](https://europe1.discourse-cdn.com/victron/original/3X/2/b/2b4fc9c172ae6c9b1193bbb71f80fdc18ab9e945.png) ![image](https://europe1.discourse-cdn.com/victron/original/3X/0/2/027b283c23a6a352ff47176d931c60e02324e01a.png) ---
**Author:** ![Outward6027](https://avatars.discourse-cdn.com/v4/letter/o/ba8739/32.png) [@Outward6027](https://community.victronenergy.com/u/Outward6027)\ **Post date:** [17 October 2026 20:28 UTC](https://community.victronenergy.com/t/network-watchdog-help/60228/7 "2026-10-17T20:28:42Z")
I’m still on 3.79 and it’s working. ---
**Author:** ![Outward6027](https://avatars.discourse-cdn.com/v4/letter/o/ba8739/32.png) [@Outward6027](https://community.victronenergy.com/u/Outward6027)\ **Post date:** [17 October 2026 21:25 UTC](https://community.victronenergy.com/t/network-watchdog-help/60228/8 "2026-10-17T21:25:23Z")
What if you redo the custom input node from scratch? I had virtual switches I had to delete and redo. ---
**Author:** ![pwfarnell](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/pwfarnell/32/2341_2.png) [@pwfarnell](https://community.victronenergy.com/u/pwfarnell)\ **Post date:** [18 October 2026 08:59 UTC](https://community.victronenergy.com/t/network-watchdog-help/60228/9 "2026-10-18T08:59:36Z")
Good idea, I checked it out with a new custom Node and it did not list com.victronenergy.logger or Venus (0) as available services. ---
**Author:** ![Dunnp](https://avatars.discourse-cdn.com/v4/letter/d/eada6e/32.png) [@Dunnp](https://community.victronenergy.com/u/Dunnp)\ **Post date:** [19 October 2026 00:29 UTC](https://community.victronenergy.com/t/network-watchdog-help/60228/10 "2026-10-19T00:29:13Z")
I spent ages trolling through nodes and cannot find anything that does what the com.victronenergy.logger did. Any clues that I missed? If it is indeed a bug, can we please get it restored to its previous (working) state? Phil ---
**Author:** ![Outward6027](https://avatars.discourse-cdn.com/v4/letter/o/ba8739/32.png) [@Outward6027](https://community.victronenergy.com/u/Outward6027)\ **Post date:** [19 October 2026 01:28 UTC](https://community.victronenergy.com/t/network-watchdog-help/60228/11 "2026-10-19T01:28:48Z")
Rolling back to the previous version might be a short term solution. ---
**Author:** ![Dunnp](https://avatars.discourse-cdn.com/v4/letter/d/eada6e/32.png) [@Dunnp](https://community.victronenergy.com/u/Dunnp)\ **Post date:** [19 October 2026 07:44 UTC](https://community.victronenergy.com/t/network-watchdog-help/60228/12 "2026-10-19T07:44:50Z")
Yes - rolled back to v3.75 and all working. But that’s only a band-aid not a fix. Victron? Phil ---
**Author:** ![Outward6027](https://avatars.discourse-cdn.com/v4/letter/o/ba8739/32.png) [@Outward6027](https://community.victronenergy.com/u/Outward6027)\ **Post date:** [27 October 2026 16:56 UTC](https://community.victronenergy.com/t/network-watchdog-help/60228/13 "2026-10-27T16:56:49Z")
@dfaber Can we get an update on this? I’d like to update cerbo to latest version for security update. ---
**Author:** ![dfaber](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/dfaber/32/13_2.png) [@dfaber](https://community.victronenergy.com/u/dfaber)\ **Post date:** [27 October 2026 19:57 UTC](https://community.victronenergy.com/t/network-watchdog-help/60228/14 "2026-10-27T19:57:57Z")
Thanks for the reports, and sorry for the slow reply. There are two separate things going on: 1. `com.victronenergy.logger` missing: this is a bug in node-red-contrib-victron. Since a change in the way services are discovered at startup, the logger service was skipped, so after a reboot it no longer shows up (it only appeared again by chance if the logger restarted while Node-RED was already running). [A fix](https://github.com/victronenergy/node-red-contrib-victron/pull/610) is ready and will, once approved, land in the next release of node-red-contrib-victron, then in the beta 3.90, before it can get backported to 3.8x. 2. “Venus (0)” missing in the reboot/platform node: this was a deliberate fix. Services like `com.victronenergy.platform` and `com.victronenergy.system` have no device instance, and the “(0)” suffix caused duplicate and broken entries. They are now listed without the “(0)”. Open the node, select the service again and deploy, and it will work again. For next time: if something in the Victron Node-RED nodes stops working, please open an issue at [Issues · victronenergy/node-red-contrib-victron · GitHub](https://github.com/victronenergy/node-red-contrib-victron/issues). Reports there get picked up much sooner than on the forum, where it is easy to miss a thread.