Problem on starting node-red

Since a change which causes a "connection to server lost" after changings in some nodes i am not able to start node-red any more.

> 21 Jul 18:47:33 - [info] [fritzbox-callmonitor:7665017.2302b] Connecting to fritzbox...
21 Jul 18:47:34 - [info] [remote-access:9e516375043536c8] Server: nodered04.remote-red.com InstanceHash: ao9tjr1ljf8yrj1wcggx5hxcp6gi1n7ymugrymcvxkepb7x0qyk3oz8ivy49n2kp
21 Jul 18:47:34 - [info] BooleanLogicUltimate: Will create 2 dummy (false) values
21 Jul 18:47:35 - [info] [cul-in:ecb2279126389492] Going to add:
21 Jul 18:47:35 - [info] [cul-controller:b83a202cb5fb4c18] Adding node "ecb2279126389492" to controller "".
21 Jul 18:47:35 - [info] [cul-controller:b83a202cb5fb4c18] Connecting to cul device at /dev/ttyAMA0@9600 in mode[SlowRF]
21 Jul 18:47:35 - [info] [cul-controller:b83a202cb5fb4c18] serialport:/dev/ttyAMA0
21 Jul 18:47:35 - [info] [cul-controller:b83a202cb5fb4c18] baudrate:9600
21 Jul 18:47:35 - [info] [cul-controller:b83a202cb5fb4c18] mode:SlowRF
21 Jul 18:47:35 - [info] [cul-controller:b83a202cb5fb4c18] parse:true
21 Jul 18:47:35 - [info] [cul-controller:b83a202cb5fb4c18] init:true
21 Jul 18:47:35 - [info] [cul-controller:b83a202cb5fb4c18] coc:false
21 Jul 18:47:35 - [info] [cul-controller:b83a202cb5fb4c18] scc:false
21 Jul 18:47:35 - [info] [cul-controller:b83a202cb5fb4c18] rssi:true
(node:1489) [DEP0170] DeprecationWarning: The URL http://fe80::9ec7:a6ff:fee1:134a:49000/igddesc.xml is invalid. Future versions of Node.js will throw an error.
(Use `node --trace-deprecation ...` to show where the warning was created)
21 Jul 18:47:35 - [red] Uncaught Exception:
21 Jul 18:47:35 - [error] TypeError: botCommandsForLanguage.filter is not a function
    at TelegramBotNode.setMyCommands (/home/pi/.node-red/node_modules/node-red-contrib-telegrambot/telegrambot/99-telegrambot.js:538:70)
    at TelegramBotNode.onStarted (/home/pi/.node-red/node_modules/node-red-contrib-telegrambot/telegrambot/99-telegrambot.js:567:18)
    at EventEmitter.emit (node:events:519:28)
    at Object.start [as startFlows] (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/index.js:409:12)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Failed with result 'exit-code'.
nodered.service: Consumed 16.875s CPU time.

Is the error a problem in the telegram node? Is it possible to deactivate such nodes by hand?

Start node red in safe mode node-red --safe, then you can disable or remove the nodes that give the problems.

After starting in safe mode use Manage Palette to make sure that all nodes are up to date. Particularly the telegram node obviously, in case you have encountered a bug that has already been fixed.

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