[red] Uncaught Exception: Pointers as to a starting point

OK, I see one of these each day and I have had a look around the forum and after trying to work out which node may be causing this I am stumped. Don't know how to proceed!
I have tidied up my many flows and now they run with very little syslog noise and I still do not know where to look next.
So, I have included the syslog around the event, enough?
Are there any other logs or sources of information that might help me nail this, is there anything I can add to my flows that might help?

Running on a Raspberry Pi3
[1.2.3: Maintenance Release]

I have upgraded a couple of times since this started, I have even set up a new "Pi" and transferred the flows to it to no solution. It has been a while and I cannot remember what changes/additions I made preceding to this starting.

Mar 26 03:05:25 NodeRed2020 Node-RED[21257]: #033[31m#033[31mBroadlink:#033[0m#033[0m Temperature Data Received - Type 1 Converting and sending.
Mar 26 03:06:25 NodeRed2020 Node-RED[21257]: #033[31mBroadlink:#033[0m Data Received - Determining Type.
Mar 26 03:06:25 NodeRed2020 Node-RED[21257]: #033[31mBroadlink:#033[0m BroadlinkData <Buffer 01 00 00 00 16 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00$
Mar 26 03:06:25 NodeRed2020 Node-RED[21257]: #033[31m#033[31mBroadlink:#033[0m#033[0m Temperature Data Received - Type 1 Converting and sending.
Mar 26 03:07:23 NodeRed2020 Node-RED[21257]: 26 Mar 03:07:23 - [red] Uncaught Exception:
Mar 26 03:07:23 NodeRed2020 Node-RED[21257]: 26 Mar 03:07:23 - Error: Device timeout
Mar 26 03:07:23 NodeRed2020 Node-RED[21257]: at fn.ontimeout (/home/pi/.node-red/node_modules/castv2-client/lib/senders/platform.js:56:26)
Mar 26 03:07:23 NodeRed2020 Node-RED[21257]: at Object.onceWrapper (events.js:420:28)
Mar 26 03:07:23 NodeRed2020 Node-RED[21257]: at fn.emit (events.js:314:20)
Mar 26 03:07:23 NodeRed2020 Node-RED[21257]: at Timeout.ontimeout [as _onTimeout] (/home/pi/.node-red/node_modules/castv2-client/lib/controllers/heartbeat.js:44:10)
Mar 26 03:07:23 NodeRed2020 Node-RED[21257]: at listOnTimeout (internal/timers.js:554:17)
Mar 26 03:07:23 NodeRed2020 Node-RED[21257]: at processTimers (internal/timers.js:497:7)
Mar 26 03:07:23 NodeRed2020 systemd[1]: nodered.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 03:07:23 NodeRed2020 systemd[1]: nodered.service: Failed with result 'exit-code'.
Mar 26 03:07:23 NodeRed2020 systemd[1]: nodered.service: Service RestartSec=100ms expired, scheduling restart.
Mar 26 03:07:23 NodeRed2020 systemd[1]: nodered.service: Scheduled restart job, restart counter is at 36.
Mar 26 03:07:23 NodeRed2020 systemd[1]: Stopped Node-RED graphical event wiring tool.
Mar 26 03:07:23 NodeRed2020 systemd[1]: Started Node-RED graphical event wiring tool.
Mar 26 03:07:32 NodeRed2020 Node-RED[15017]: 26 Mar 03:07:32 - [warn] Projects disabled : editorTheme.projects.enabled=false
Mar 26 03:08:20 NodeRed2020 systemd[1]: Starting Daily apt download activities...
Mar 26 03:08:22 NodeRed2020 systemd[1]: apt-daily.service: Succeeded.
Mar 26 03:08:22 NodeRed2020 systemd[1]: Started Daily apt download activities.
Mar 26 03:08:34 NodeRed2020 Node-RED[15017]: #033[31mBroadlink:#033[0m Data Received - Determining Type.
Mar 26 03:08:34 NodeRed2020 Node-RED[15017]: #033[31mBroadlink:#033[0m BroadlinkData <Buffer 01 00 00 00 16 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00$
Mar 26 03:08:34 NodeRed2020 Node-RED[15017]: #033[31m#033[31mBroadlink:#033[0m#033[0m Temperature Data Received - Type 1 Converting and sending.
Mar 26 03:09:34 NodeRed2020 Node-RED[15017]: #033[31mBroadlink:#033[0m Data Received - Determining Type.
Mar 26 03:09:34 NodeRed2020 Node-RED[15017]: #033[31mBroadlink:#033[0m BroadlinkData <Buffer 01 00 00 00 16 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00$
Mar 26 03:09:34 NodeRed2020 Node-RED[15017]: #033[31m#033[31mBroadlink:#033[0m#033[0m Temperature Data Received - Type 1 Converting and sending.
Mar 26 03:10:34 NodeRed2020 Node-RED[15017]: #033[31mBroadlink:#033[0m Data Received - Determining Type.

That appears to be the critical line. It is the castv2-client module that is failing. That is presumably pulled in by a node that you have installed. Probably a contrib node.

If you don't know which one that might be then go to your .node-red folder and run
npm list castv2-client
and with luck it will show you the parent node.

2 Likes

OK, when I looked at the syslogs from both before and now they all have that information, I had wondered if that was the significant bit but as there was a lot of other noise that I had tidied up I was getting there.
It was a lot of work to extract all the "castv2-client instances and keep the flows doing their job so your help was invaluable, I used the "nmp-list..." command and that pointed to the same nodes.
I removed the nodes and and replaced with an equivalent (not a perfect, what I want but does the basics function), now it is working without failure.
I will get to let the developer know if I replicate it but for the time being, Many Thanks.
Fixed for Me.

Next time I will have a better idea how to analyse the syslog.
Solved.
This is only the solution because of Colin's, above, suggestion.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.