Node red restarting constantly

Fulltopuk · 10 June 2022 13:07

Hi All

I have just installed Node-red on it's own PI after the previous version went weird on a Hoobs install.

Now I seem to be having issues - Log is below so please can anyone point me in the right direction?

It looks like the Doorbird node but now I cannot get onto the interface to remove it due to it disconnecting.

Thanks

Welcome to Node-RED
===================
10 Jun 14:04:36 - [info] Node-RED version: v2.2.2
10 Jun 14:04:36 - [info] Node.js  version: v14.19.3
10 Jun 14:04:36 - [info] Linux 5.10.103-v7+ arm LE
10 Jun 14:04:37 - [info] Loading palette nodes
10 Jun 14:04:45 - [info] Settings file  : /home/pi/.node-red/settings.js
10 Jun 14:04:45 - [info] Context store  : 'default' [module=memory]
10 Jun 14:04:45 - [info] User directory : /home/pi/.node-red
10 Jun 14:04:45 - [warn] Projects disabled : editorTheme.projects.enabled=false
10 Jun 14:04:45 - [info] Flows file     : /home/pi/.node-red/flows.json
10 Jun 14:04:46 - [info] Server now running at http://127.0.0.1:1880/
10 Jun 14:04:46 - [info] Starting flows
2022-06-10T13:04:46.907Z NRCHKB-Error:HAPHostNode [:fa565a07.a7d6f8] Host name is incorrect
[Demo 1@@Hardware Revision] characteristic value expected string and received undefined
[Demo 1@@Software Revision] characteristic value expected string and received undefined
[4@@Hardware Revision] characteristic value expected string and received undefined
[4@@Software Revision] characteristic value expected string and received undefined
[Node-Red-HAP-Bridge-01@@Hardware Revision] characteristic value expected string and received undefined
[Node-Red-HAP-Bridge-01@@Software Revision] characteristic value expected string and received undefined
[release 05@@Hardware Revision] characteristic value expected string and received undefined
[release 05@@Software Revision] characteristic value expected string and received undefined
10 Jun 14:04:46 - [info] [hue-bridge:Philips hue] Initializing the bridge (192.168.1.75)…
10 Jun 14:04:47 - [info] ttsultimate-config 832f49d8.600e3: TTS cache set to /home/pi/.node-red/sonospollyttsstorage/ttsfiles
10 Jun 14:04:47 - [info] ttsultimate-config 832f49d8.600e3: google credentials path set to /home/pi/.node-red/sonospollyttsstorage/ttsultimategooglecredentials
10 Jun 14:04:47 - [info] ttsultimate-config 832f49d8.600e3: hailing path set to /home/pi/.node-red/sonospollyttsstorage/hailingpermanentfiles
10 Jun 14:04:47 - [info] ttsultimate-config 832f49d8.600e3: permanent files path set to /home/pi/.node-red/sonospollyttsstorage/ttspermanentfiles
10 Jun 14:04:47 - [info] ttsultimate-config 832f49d8.600e3: Node-Red node.js Endpoint will be created here: http://192.168.1.219:1980/tts
10 Jun 14:04:47 - [info] ttsultimate-config d4417b7e.b2f34: TTS cache set to /home/pi/.node-red/sonospollyttsstorage/ttsfiles
10 Jun 14:04:47 - [info] ttsultimate-config d4417b7e.b2f34: google credentials path set to /home/pi/.node-red/sonospollyttsstorage/ttsultimategooglecredentials
10 Jun 14:04:47 - [info] ttsultimate-config d4417b7e.b2f34: hailing path set to /home/pi/.node-red/sonospollyttsstorage/hailingpermanentfiles
10 Jun 14:04:47 - [info] ttsultimate-config d4417b7e.b2f34: permanent files path set to /home/pi/.node-red/sonospollyttsstorage/ttspermanentfiles
10 Jun 14:04:47 - [info] ttsultimate-config d4417b7e.b2f34: Node-Red node.js Endpoint will be created here: http://192.168.1.77:1980/tts
TypeError: Cannot read property 'padEnd' of undefined
    at Flow.start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:254:62)
    at start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/index.js:371:33)
10 Jun 14:04:47 - [info] [tcp in:1297d7d9.e0782] connecting to 192.168.1.202:20102
10 Jun 14:04:47 - [info] [tcp out:82d4a324.557288] connecting to 192.168.1.202:20102
10 Jun 14:04:47 - [info] [tcp in:Sky HD serial] connecting to 192.168.1.205:20105
10 Jun 14:04:47 - [info] [tcp in:Sky HD serial] connecting to 192.168.1.205:20105
10 Jun 14:04:47 - [info] Started flows
2022-06-10T13:04:47.340Z NRCHKB-Error:HAPServiceNode [Landing:ed95aac9c480bd5c] Host Node not found
10 Jun 14:04:47 - [error] [homekit-service:Landing] Error while starting Service due to Error: Host Node not found
2022-06-10T13:04:47.368Z NRCHKB-Error:HAPServiceNode [Landing:ed95aac9c480bd5c] Error while starting Service due to Error: Host Node not found
10 Jun 14:04:47 - [error] ttsultimate-config d4417b7e.b2f34: undefined error starting webserver on port 1980 Error: listen EADDRINUSE: address already in use :::1980
10 Jun 14:04:47 - [info] [tcp in:1297d7d9.e0782] connected to 192.168.1.202:20102
10 Jun 14:04:47 - [info] [tcp out:82d4a324.557288] connected to 192.168.1.202:20102
10 Jun 14:04:47 - [info] [tcp in:Sky HD serial] connected to 192.168.1.205:20105
10 Jun 14:04:47 - [info] [tcp in:Sky HD serial] connected to 192.168.1.205:20105
10 Jun 14:04:47 - [info] [hue-bridge:Philips hue] Connected to bridge
10 Jun 14:04:48 - [info] [hue-bridge:Philips hue] Processing bridge resources…
10 Jun 14:04:48 - [info] [hue-bridge:Philips hue] Initial emit of resource states…
10 Jun 14:04:49 - [info] [hue-bridge:Philips hue] Keeping nodes up-to-date…
10 Jun 14:04:49 - [info] [hue-bridge:Philips hue] Subscribing to bridge events…
10 Jun 14:05:11 - [red] Uncaught Exception:
10 Jun 14:05:11 - [error] TypeError: this.strech is not a function
    at Socket.DoorbirdUdpSocket.onMessage (/home/pi/.node-red/node_modules/doorbird/src/index.ts:186:10)
    at Socket.emit (events.js:400:28)
    at Socket.emit (domain.js:475:12)
    at UDP.onMessage (dgram.js:931:8)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Failed with result 'exit-code'.

Steve-Mcl · 10 June 2022 13:16

As far as i can see from this error ↑ it suggests in your flows, an entry has a non string id property.

github.com

node-red/node-red/blob/21a0b3364525f0368ea03685b3b6aaf9ce26ec95/packages/node_modules/@node-red/runtime/lib/flows/Flow.js#L254


      
          var activeCount = Object.keys(this.activeNodes).length;
          if (activeCount > 0) {
              this.trace("------------------|--------------|-----------------");
              this.trace(" id               | type         | alias");
              this.trace("------------------|--------------|-----------------");
          }
          // Build the map of catch/status/complete nodes.
          for (id in this.activeNodes) {
              if (this.activeNodes.hasOwnProperty(id)) {
                  node = this.activeNodes[id];
                  this.trace(" "+id.padEnd(16)+" | "+node.type.padEnd(12)+" | "+(node._alias||"")+(node._zAlias?" [zAlias:"+node._zAlias+"]":""));
                  if (node.type === "catch") {
                      this.catchNodes.push(node);
                  } else if (node.type === "status") {
                      this.statusNodes.push(node);
                  } else if (node.type === "complete") {
                      if (node.scope) {
                          node.scope.forEach(id => {
                              this.completeNodeMap[id] = this.completeNodeMap[id] || [];
                              this.completeNodeMap[id].push(node);
                          })

Can you share your flow?

Fulltopuk · 13 June 2022 13:23

Thanks for replying - I have another problem with Node-red as the logs may have taken up the memory so I will have to sort that first and then send you the flow.

Thanks

system · 12 August 2022 13:23

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

Topic		Replies	Views
All nearly hour a restart ... any idea General	4	313	22 April 2021
Node-Red continually fails and restarts General	17	6172	23 March 2019
Nodered keeps restarting with processTicksAndRejections error General	35	334	10 April 2023
Node red crashes/restarts when doorbird events happen (motion,ring) General	8	85	30 January 2024
Node-Red Failure General	5	143	3 July 2023

Node red restarting constantly

Related Topics