Does anyone have the similar problem with the node after installing?
thingzi-logic-climate, MODULE_NOT_FOUND
It can´t be use, it stuck the whole system with the error message.
Tested also after/configuration:
raspberry pi zero & raspberry pi 4
apt-get update && apt-get upgrade npm@8.2.0 Node-RED v2.1.3
Installed from the Node-RED pallet and then also from the LINUX command line
npm install thiangzi-logic-climate (in the /.node-red folder)
Open a terminal and go into your .node-red folder then run npm remove thingzi-logic-climate
then npm install thingzi-logic-climate
and post the full output from the install command here.
Copy/paste please rather than screenshot. When pasting use the </> button at the top of the forum entry window.
[Edit] If that does not show any errors then stop node red and start it again in a terminal and post the output here.
pi@raspberrypi:~/.node-red $ npm remove thingzi-logic-climate
removed 1 package, and audited 87 packages in 2s
19 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
pi@raspberrypi:~/.node-red $ npm install thingzi-logic-climate
added 1 package, and audited 88 packages in 2s
19 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
pi@raspberrypi:~ $ node-red-stop
Stop Node-RED
Use node-red-start to start Node-RED again
pi@raspberrypi:~ $ node-red-start
Start Node-RED
Once Node-RED has started, point a browser at http://192.168.168.165: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.
8 Dec 11:58:59 - [info]
Welcome to Node-RED
===================
8 Dec 11:58:59 - [info] Node-RED version: v2.1.3
8 Dec 11:58:59 - [info] Node.js version: v14.18.2
8 Dec 11:58:59 - [info] Linux 5.10.63-v7l+ arm LE
8 Dec 11:59:00 - [info] Loading palette nodes
8 Dec 11:59:01 - [warn] ------------------------------------------------------
8 Dec 11:59:01 - [warn] [thingzi-logic-climate/climate] Error: Cannot find modul e 'moment'
Require stack:
- /home/pi/.node-red/node_modules/thingzi-logic-climate/climate.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
8 Dec 11:59:01 - [warn] ------------------------------------------------------
8 Dec 11:59:01 - [info] Settings file : /home/pi/.node-red/settings.js
8 Dec 11:59:01 - [info] Context store : 'default' [module=memory]
8 Dec 11:59:01 - [info] User directory : /home/pi/.node-red
8 Dec 11:59:01 - [warn] Projects disabled : git command not found
8 Dec 11:59:01 - [info] Flows file : /home/pi/.node-red/flows.json
8 Dec 11:59:01 - [info] Server now running at http://127.0.0.1:1880/
8 Dec 11:59:01 - [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.
---------------------------------------------------------------------
8 Dec 11:59:01 - [info] Starting flows
8 Dec 11:59:01 - [info] Started flows
Thank you soooo much!!!!
After 12 hours of testing and testing.... it finally works!!!
I´m really happy and I hope this helps others with a similar problem.
This was the key command npm install moment under the /.node-red folder.
Then sudo reboot
Did you try installing that too?
It seems there are some serious issues with the packaging of that node. Unfortunately it appears that has not got a github page so it is not possible to submit issues. I generally avoid nodes that do not have github pages, or some other method of seeing and submitting issues.
Hi, im the author of that node and yes, its on my list to move to github. For some reason the dependencies were not listed properly and were masked by them being there in node red but removed in a subsequent version. I'll update this (and put it on github)