Hello,
I want to use google-iot-core package in a Raspberry Pi, but I'm receiving this error:
[node-red-contrib-google-iot-core/google-iot-core] TypeError [ERR_INVALID_ARG_TYPE]: The "superCtor.prototype" property must be of type Object. Received type undefined
I copy the log that I received:
Start Node-RED
Once Node-RED has started, point a browser at http://169.254.93.28:1880
On Pi Node-RED works better with the Firefox or Chrome browser
Use node-red-stop to stop Node-RED
Use node-red-start to start Node-RED again
Use node-red-log to view the recent log output
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot
Use sudo systemctl disable nodered.service to disable autostart on boot
To find more nodes and example flows - go to http://flows.nodered.org
Starting as a systemd service.
4 Sep 09:15:22 - [info]
Welcome to Node-RED
===================
4 Sep 09:15:22 - [info] Node-RED version: v0.20.7
4 Sep 09:15:22 - [info] Node.js version: v10.16.3
4 Sep 09:15:22 - [info] Linux 4.19.66-v7+ arm LE
4 Sep 09:15:23 - [info] Loading palette nodes
4 Sep 09:15:28 - [warn] ------------------------------------------------------
4 Sep 09:15:28 - [warn] [node-red-contrib-google-iot-core/google-iot-core] TypeError [ERR_INVALID_ARG_TYPE]: The "superCtor.prototype" property must be of type Object. Received type undefined
4 Sep 09:15:28 - [warn] ------------------------------------------------------
4 Sep 09:15:28 - [info] Settings file : /home/ii40asset/.node-red/settings.js
4 Sep 09:15:28 - [info] Context store : 'default' [module=memory]
4 Sep 09:15:28 - [info] User directory : /home/ii40asset/.node-red
4 Sep 09:15:28 - [warn] Projects disabled : editorTheme.projects.enabled=false
4 Sep 09:15:28 - [info] Flows file : /home/ii40asset/.node-red/flows_ii40asset.json
4 Sep 09:15:28 - [info] Server now running at http://127.0.0.1:1880/
4 Sep 09:15:28 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
4 Sep 09:15:28 - [info] Waiting for missing types to be registered:
4 Sep 09:15:28 - [info] - google-iot-core-broker
4 Sep 09:15:28 - [info] - google-iot-core in
Does someone know where is the problem?
Thanks!
You will need to raise an issue on GitHub for that node I think.
Have you installed them? Or just pasted and deployed an example flow?
Hi,
I have installed them via "Manage palette".
When I install it doesn't appear any problems, but when I restart Node-Red (for example after a reboot), this is the situation:
- I can't see the nodes in the left side of Node-Red.
- If I go to "Manage palette" I can see a Warning:
- If I go to the log I have a error when is loading palette nodes:
Starting as a systemd service.
5 Sep 09:01:46 - [info]
Welcome to Node-RED
===================
5 Sep 09:01:46 - [info] Node-RED version: v0.20.7
5 Sep 09:01:46 - [info] Node.js version: v10.16.3
5 Sep 09:01:46 - [info] Linux 4.19.66-v7+ arm LE
5 Sep 09:01:47 - [info] Loading palette nodes
5 Sep 09:01:51 - [warn] ------------------------------------------------------
5 Sep 09:01:51 - [warn] [node-red-contrib-google-iot-core/google-iot-core] TypeError [ERR_INVALID_ARG_TYPE]: The "superCtor.prototype" property must be of type Object. Received type undefined
5 Sep 09:01:51 - [warn] ------------------------------------------------------
5 Sep 09:01:51 - [info] Settings file : /home/ii40asset/.node-red/settings.js
5 Sep 09:01:51 - [info] Context store : 'default' [module=memory]
5 Sep 09:01:51 - [info] User directory : /home/ii40asset/.node-red
5 Sep 09:01:51 - [warn] Projects disabled : editorTheme.projects.enabled=false
5 Sep 09:01:51 - [info] Flows file : /home/ii40asset/.node-red/flows_ii40asset.json
5 Sep 09:01:51 - [info] Server now running at http://127.0.0.1:1880/
5 Sep 09:01:51 - [warn]
---------------------------------------------------------------------
Thanks!
Try to install them again from the command line (so you can more easily see any WARN or ERROR messages)
If that works (or even if it doesn’t) and you still have a problem, I’d suggest opening an Issue on the nodes github page to flag the issue to the nodes author.
Hello,
I installed from the command line, and this is the error that I received
> usb@1.6.0 install /home/ii40asset/.node-red/node_modules/usb
> prebuild-install --verbose || node-gyp rebuild
/home/ii40asset/.node-red/node_modules/prebuild-install/rc.js:50
}, minimist(process.argv, {
^
TypeError: minimist is not a function
at module.exports (/home/ii40asset/.node-red/node_modules/prebuild-install/rc.js:50:6)
at Object.<anonymous> (/home/ii40asset/.node-red/node_modules/prebuild-install/bin.js:9:25)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
make: Entering directory '/home/ii40asset/.node-red/node_modules/usb/build'
CC(target) Release/obj.target/libusb/libusb/libusb/core.o
CC(target) Release/obj.target/libusb/libusb/libusb/descriptor.o
CC(target) Release/obj.target/libusb/libusb/libusb/hotplug.o
CC(target) Release/obj.target/libusb/libusb/libusb/io.o
CC(target) Release/obj.target/libusb/libusb/libusb/strerror.o
CC(target) Release/obj.target/libusb/libusb/libusb/sync.o
CC(target) Release/obj.target/libusb/libusb/libusb/os/poll_posix.o
CC(target) Release/obj.target/libusb/libusb/libusb/os/threads_posix.o
CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_usbfs.o
CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_udev.o
../libusb/libusb/os/linux_udev.c:40:10: fatal error: libudev.h: No such file or directory
#include <libudev.h>
^~~~~~~~~~~
compilation terminated.
make: *** [libusb.target.mk:138: Release/obj.target/libusb/libusb/libusb/os/linux_udev.o] Error 1
make: Leaving directory '/home/ii40asset/.node-red/node_modules/usb/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:196:23)
gyp ERR! stack at ChildProcess.emit (events.js:198:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Linux 4.19.66-v7+
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/ii40asset/.node-red/node_modules/usb
gyp ERR! node -v v10.16.3
gyp ERR! node-gyp -v v5.0.3
gyp ERR! not ok
> bcrypt@3.0.6 install /home/ii40asset/.node-red/node_modules/bcrypt
> node-pre-gyp install --fallback-to-build
util.js:283
throw new ERR_INVALID_ARG_TYPE('superCtor.prototype',
^
TypeError [ERR_INVALID_ARG_TYPE]: The "superCtor.prototype" property must be of type Object. Received type undefined
at Object.inherits (util.js:283:11)
at Object.<anonymous> (/home/ii40asset/.node-red/node_modules/readable-stream/lib/_stream_readable.js:85:6)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at Object.<anonymous> (/home/ii40asset/.node-red/node_modules/readable-stream/readable.js:12:30)
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN node-red-project@0.0.1 No repository field.
npm WARN node-red-project@0.0.1 No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: usb@1.6.0 (node_modules/usb):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: usb@1.6.0 install: `prebuild-install --verbose || node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: bcrypt@3.0.6 (node_modules/bcrypt):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: bcrypt@3.0.6 install: `node-pre-gyp install --fallback-to-build`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
+ node-red-contrib-google-iot-core@0.0.4
added 27 packages from 24 contributors and audited 1310 packages in 35.829s
found 1 moderate severity vulnerability
run `npm audit fix` to fix them, or `npm audit` for details
So open an issue on the nodes github page to flag the issue with the nodes author.
Finally, I have uninstalled all Node-Red and then I have installed again and the node operates correctly.
