Node red crashes/restarts when doorbird events happen (motion,ring)

General
1

Hey to all of you,

i have good a strange behaviour with the door bird api. Since my upgrade to node red 3 (before 1.x) and node.js 20 (before node.js 14) i have got an restart of the node red service after every motion, ring and so on in the doorbird.

The log at these times:

> Dec  1 14:17:36 raspberrypi Node-RED[68393]: 1 Dec 14:17:36 - [red] Uncaught Exception:
> Dec  1 14:17:36 raspberrypi Node-RED[68393]: 1 Dec 14:17:36 - [error] TypeError: sodium.crypto_pwhash is not a function
> Dec  1 14:17:36 raspberrypi Node-RED[68393]:     at DoorbirdUdpSocket.<anonymous> (/home/pi/.node-red/node_modules/doorbird/dist/index.js:121:55)
> Dec  1 14:17:36 raspberrypi Node-RED[68393]:     at step (/home/pi/.node-red/node_modules/doorbird/dist/index.js:56:23)
> Dec  1 14:17:36 raspberrypi Node-RED[68393]:     at Object.next (/home/pi/.node-red/node_modules/doorbird/dist/index.js:37:53)
> Dec  1 14:17:36 raspberrypi Node-RED[68393]:     at fulfilled (/home/pi/.node-red/node_modules/doorbird/dist/index.js:28:58)
> Dec  1 14:17:36 raspberrypi systemd[1]: nodered.service: Main process exited, code=exited, status=1/FAILURE
> Dec  1 14:17:36 raspberrypi systemd[1]: nodered.service: Failed with result 'exit-code'.
> Dec  1 14:17:36 raspberrypi systemd[1]: nodered.service: Consumed 1h 8min 20.425s CPU time.
> Dec  1 14:17:56 raspberrypi systemd[1]: nodered.service: Scheduled restart job, restart counter is at 30.
> Dec  1 14:17:56 raspberrypi systemd[1]: Stopped Node-RED graphical event wiring tool.
> Dec  1 14:17:56 raspberrypi systemd[1]: nodered.service: Consumed 1h 8min 20.425s CPU time.

Can somebody help me on this problem? Is there a incompability?

Best regards,
WernerMa96

2

So where has the doorbird module come from? Is that a manually installed package, or some other contributed node?

3

I installed the node-red-contrib-doorbird-ultimate (node) - Node-RED
directly via the palette manager.

4

Which uses
doorbird : doorbird - npm (npmjs.com)

I think you will need to raise this with the author of the node you installed, as there maybe issues with more recent versions of Node and some upstream Dependencies

5

I see that the version in node red (1.2.1) is not up to date. in github there is 1.2.3.
Maybe this fixes the error. Thanks a lot.

6

@marcus-j-davies

The newest version is node in the node-red-portal but on npm:

is a direct update possible? or how do i do that?

7

You will need to access your servers command line. Assuming a standard install on a Linux server:

cd ~/.node-red
npm install ihrigb/node-red-contrib-doorbird-ultimate

Should do it - assuming the same login on the command line as the user running node red. You will need to restart Node-RED afterwards.

1 Like
8

I have just forced an update of the node-red catalogue so 1.3.0 is available through the palette manager now.

Edit, or at least it should be very soon, it doesn't seem to have propagated through yet.

1 Like
9

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