1. Forum
  2. Main category
  3. Main forum
  4. Error waiting for RTD node to be registered

Error waiting for RTD node to be registered

  • R
    I'm getting a message on node-red-start that it's waiting for missing types to be registered, and the missing type is the RTD node. It's in my left-hand menu; and I've installed it again using npm and the install line from the SMS Node Red page. The possible cause is that I did an apt update and apt upgrade; and also installed node-red-contrib-unit-converter. Any suggestions on how to fix this?
    0 likes
  • alexburcea
    Uninstall the RTD node and reinstall it.
    0 likes
  • R
    Here is a dump of my node-red-start output. What has me puzzled is that I've removed and reinstalled both i2c-bus and rtd. No errors on the install of either.

    Starting as a systemd service.
    Started nodered.service - Node-RED graphical event wiring tool.
    1 Jul 21:24:17 - [info]
    Welcome to Node-RED
    ===================
    1 Jul 21:24:17 - [info] Node-RED version: v4.0.9
    1 Jul 21:24:17 - [info] Node.js version: v20.19.3
    1 Jul 21:24:17 - [info] Linux 6.12.25+rpt-rpi-v8 arm64 LE
    1 Jul 21:24:18 - [info] Loading palette nodes
    1 Jul 21:24:19 - [warn] ------------------------------------------------------
    1 Jul 21:24:19 - [warn] [node-red-contrib-sm-rtd/rtd] Error: Cannot find module 'i2c-bus'
    Require stack:
    - /home/robert/rtd-rpi/node-red-contrib-sm-rtd/rtd.js
    - /usr/lib/node_modules/node-red/node_modules/@node-red/registry/lib/loader.js
    - /usr/lib/node_modules/node-red/node_modules/@node-red/registry/lib/index.js
    - /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/index.js
    - /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/index.js
    - /usr/lib/node_modules/node-red/lib/red.js
    - /usr/lib/node_modules/node-red/red.js
    1 Jul 21:24:19 - [warn] ------------------------------------------------------
    1 Jul 21:24:19 - [info] Settings file : /home/robert/.node-red/settings.js
    1 Jul 21:24:19 - [info] Context store : 'default' [module=memory]
    1 Jul 21:24:19 - [info] User directory : /home/robert/.node-red
    1 Jul 21:24:19 - [info] Projects directory: /home/robert/.node-red/projects
    1 Jul 21:24:19 - [info] Server now running at http://127.0.0.1:1880/
    1 Jul 21:24:19 - [info] Active project : Still_Controlleer
    1 Jul 21:24:19 - [info] Flows file : /home/robert/.node-red/projects/Still_Controlleer/flows.json
    1 Jul 21:24:19 - [info] Waiting for missing types to be registered:
    1 Jul 21:24:19 - [info] - rtd
    0 likes
  • R
    alexburcea said:

    Uninstall the RTD node and reinstall it.

    I've removed and reinstalled rtd. Also removed and reinstalled i2c-bus, and followed that by doing same for rtd again. I'm doing something wrong, just not sure what!
    0 likes
  • R
    I've again removed and reinstalled i2c-bus and rtd. Same result. I've had issues loading i2c in the past, so I suspect that's where my error lies. Here's the dump - same issues as previously posted output. Note that when I install i2c, the output says 4 modules installed. On rtd install, 2 modules installed. No error messages on either.

    Starting as a systemd service.
    Started nodered.service - Node-RED graphical event wiring tool.
    1 Jul 21:46:46 - [info]
    Welcome to Node-RED
    ===================
    1 Jul 21:46:46 - [info] Node-RED version: v4.0.9
    1 Jul 21:46:46 - [info] Node.js version: v20.19.3
    1 Jul 21:46:46 - [info] Linux 6.12.25+rpt-rpi-v8 arm64 LE
    1 Jul 21:46:46 - [info] Loading palette nodes
    1 Jul 21:46:49 - [warn] ------------------------------------------------------
    1 Jul 21:46:49 - [warn] [node-red-contrib-sm-rtd/rtd] Error: Cannot find module 'i2c-bus'
    Require stack:
    - /home/robert/rtd-rpi/node-red-contrib-sm-rtd/rtd.js
    - /usr/lib/node_modules/node-red/node_modules/@node-red/registry/lib/loader.js
    - /usr/lib/node_modules/node-red/node_modules/@node-red/registry/lib/index.js
    - /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/index.js
    - /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/index.js
    - /usr/lib/node_modules/node-red/lib/red.js
    - /usr/lib/node_modules/node-red/red.js
    1 Jul 21:46:49 - [warn] ------------------------------------------------------
    1 Jul 21:46:49 - [info] Settings file : /home/robert/.node-red/settings.js
    1 Jul 21:46:49 - [info] Context store : 'default' [module=memory]
    1 Jul 21:46:49 - [info] User directory : /home/robert/.node-red
    1 Jul 21:46:49 - [info] Projects directory: /home/robert/.node-red/projects
    1 Jul 21:46:49 - [info] Server now running at http://127.0.0.1:1880/
    1 Jul 21:46:49 - [info] Active project : Still_Controlleer
    1 Jul 21:46:49 - [info] Flows file : /home/robert/.node-red/projects/Still_Controlleer/flows.json
    1 Jul 21:46:49 - [info] Waiting for missing types to be registered:
    1 Jul 21:46:49 - [info] - rtd
    0 likes
  • R
    I've run into this problem before. I've had to scrap and rebuild my NR environment previously; and had to do the same just now. I re-ran the NR installation script, followed by installing the 2 i2c packages referenced on the SMS NR instruction pages. That all worked fine. The nodes and groups showed up in the palette, but I could not get either of the SMS packages to install. I tried rtd and 3 relays. The SMS group never showed up, nor did any of the nodes for either board. After a few attempts, the error as shown above about the i2c module missing started again. I don't recall what finally fixed this issue before, but this situation with the i2c module missing error was also the trigger that started this post when I tried installing the units converter node. It seems that installing a new package can cause i2c to become uninstalled or not recognized as registered. Very odd. I'll have to return to this in the AM.
    0 likes
  • alexburcea
    You can always do a trick to avoid I2C node. Use the exec node to run the command line interface for sequent cards.. some people say it runs faster than js of the native nodes.
    0 likes
  • R
    alexburcea said:

    You can always do a trick to avoid I2C node. Use the exec node to run the command line interface for sequent cards.. some people say it runs faster than js of the native nodes.

    That sounds like a good option given how puzzling this has been.

    As for the i2c node becoming not found / registered, is there anything in the config files that I could look for and fix - sequence in which nodes are listed, for example? I'm baffled that installing nodes from other contributions would cause an existing node to become not found - especially because the nodes and their i2c group remain available in my palette. I'm too new to NR to know where to look, so I have resorted to rebuilding my environment multiple times since starting this project.

    I do remember stumbling into a feature that showed all installed nodes and let me update a node where a newer version had become available. I'm still searching for that - was part of one of the menu items that pop up on the right hand side. Any direction on this, if it sounds familiar, would be appreciated!
    0 likes
  • R
    I made an important discovery that using the installer in the user interface works more reliably than installing externally via npm. I was able to install all nodes/packages that I needed without error or issue. :)
    0 likes
  • alexburcea
    I am glad you fixed it, and thanks for sharing the method. I hope to remember this when someone else will face the same problem.
    0 likes
Please login to reply this topic!

Search

Forum statistics

Page views (24h):
21
Page views (30d):
1,440
Topics:
216
Posts:
1,509
Members:
902

Newest members

© 2025, Sequent Microsystems | Powered by Xenforum