Posts made by cw-kid | Smart Home

cw-kid

It seems nodesource is just out of date and does not have the latest versions of nodejs

I tried this command instead and it still only wants to get version v20.18.1 as the latest one.

curl -fsSL https://deb.nodesource.com/setup_current.x | -E bash -

apt-get install -y nodejs

And when I run a "Which node" command its put it in this directory which I don't think is ideal?

/usr/bin/node

So now sure now the best way to update nodejs.

cw-kid

Think I have got it working now!

I ran these commands again logged in as me.

cd /home/stuart
pkill -QUIT node
tar xzvf /home/stuart/reactor-latest-24302-751a06b6.tar.gz
sudo systemctl start reactor

cd /home/stuart/reactor
npm i --no-save --omit dev

Will try and figure out how to update nodejs now from 20.x to 22.x.

cw-kid

Not sure how I ended up with a reactor folder in the reactor folder. I deleted it.
It now looks correct and I ran the commands again for the permssions.

However every time I copy the expression file from the PC to the Linux box its 9k in file size. But when I restart MSR it changes that file to be 1k and wipes out all its contents.

cw-kid

OK I ran these commands in the home/stuart/reactor folder where the app.js file is located. That appears to have worked and changed some of the folders and files from root to my name now.

Also after restarting MSR the expressions.json file is no longer changing from 9k to 1k in size and I can open the file from the Linux machine and see its contents are still all intact. It wasn't doing that before.

However in the MSR GUI in Expressions its still empty.

Edit I seem to have ballsed something up, i have a path now of /home/stuart/reactor/reactor hang on let me try and fix that.

cw-kid

@toggledbits

I used WINSCP to copy the file from my Windows PC to the Linux box.

It says rw-r--r-- next to the expressions file and has me as the owner of the file.

Regarding nodejs installed via apt it says its version v20.18.1 I think version 22.x is the latest. Maybe I can upgrade it somehow later.

cw-kid

@toggledbits said in Which user to install nodejs as ? Debian Linux:

When backing up and restoring, the entire storage folder should always go as a unit. No cherry-picking

Understood now thanks.

I uploaded the file to your dropbox. Cheers for the help!

Btw I formatted everything and started again earlier, no longer using NVM to install node.js I installed it globally instead with apt via the command from this webpage here. That seems to have fixed my Node-Red service file issues anyways. Both MSR and Node-Red are auto starting at boot now.

cw-kid

@therealdb said in Which user to install nodejs as ? Debian Linux:

Copy everything. You’ll also get states.

I just tried this but my Global Expressions are still missing.

cw-kid

@therealdb said in Which user to install nodejs as ? Debian Linux:

Copy everything. You’ll also get states

I might have to try that then.

I was just trying to get my node-red to run as a service with systemd, however its not working and I think its because I installed nodejs using NVM.

Several pages I have read say node-red will not run as a service if you used NVM like this one here:

"Using nvm
nvm is a tool that can help manage Node.js installations.

It is convenient when running Node-RED as an individual user, but it is not recommended if you want to run Node-RED as a system-level service. This is because nvm uses scripts in a user’s profile to setup its environment. When running as a service, those scripts do not get used."

I am now thinking I might have to format the SSD and start from the beginning again and use a different method to install nodejs other than NVM.

I think when I first setup this Debian box years ago I installed nodejs a different way as described in this article here in the section of the article titled "Installing Node.js with Apt Using a NodeSource PPA".

cw-kid

@toggledbits I have managed to get MSR up and running again as my none root username.

I have copied the rules / rulesets / reactions back into the installation from a backup copy of all the reactor files I had on my PC. Those have now reappeared in MSR.

I am missing my Global Expressions however. Is there a file or folder I need to copy back for those?

Thanks.

EDIT: I just copied over the expressions.json file from the storage folder and restarted MSR but there are still no expressions showing in MSR.

I just copied the file over again and then looked at the file on the Linux machine and I could see stuff in there. However after restarting MSR and then looking at the file again, its seems to wipe out all the files contents and now it just has {} in the file nothing else.

cw-kid

@toggledbits said in Which user to install nodejs as ? Debian Linux:

nvm is a per-user tool and installs node on a per-user basis. You need to run it logged in as the non-root user that will run Reactor and the other things you want to install. Be sure to install an LTS version of node, not just the highest-numbered version (e.g. nvm install --lts).

Great thanks I will try that today. I already removed what I installed yesterday as the root user.

cw-kid

I also need to install node-red and HA-Bridge for other stuff, looks like I need nodejs installed first before I can install node-red. I use node-red to send TTS announcements to my Google Home speakers.

cw-kid

Hi

Having to rebuild my Linux Debian box as the SSD failed. And I have forgotten exactly what I did the first time to get it all setup.

I have Debian 12 up and running on the new SSD, I only have console no Desktop GUI.

I am trying to do the bare metal install for MSR. However I am not sure if I am meant to install nodejs whlist logged in as the root user or as the none root user with my name ?

I used putty and connected via SSH and logged in as root and I installed nodejs but I think this was wrong as when logged in as my user name and I do a node -v command it says node is not installed or doesn't show any version number anyway.

But when logged in as root and I do a node -v command it does show me its installed and displays the version number. maybe its a path issue for my username and he can't see node is installed?

So now I am thinking I should of installed node whilst logged in as my user name and not as the root user.

This is how I installed nodejs as whilst logged in as root

Thanks in advance.

cw-kid

As for your other comments Gentlemen, I don't disagree with them..

cw-kid

@toggledbits said in Should MSR import this device type from an Ezlo controller?:

value for subcategory that should be assigned

Thanks, I didn't notice that. I will tell them to fix it.

Cheers.

cw-kid

Hi

I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.

They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.

This is how that device looks in the Ezlo API.

Devices Info:

_id: "10696001"
deviceTypeId: "ezlopi"
parentDeviceId: "10696000"
category: "level_sensor"
subcategory: ""
gatewayId: "457a5069"
batteryPowered: false
name: "Gas Sensor Digital"
type: "sensor"
reachable: true
persistent: true
serviceNotification: false
armed: false
roomId: ""
security: "no"
ready: true
status: "idle"
parentRoom: true
protectConfig: "default"

Items Info:

_id: "20696001"
deviceId: "10696001"
hasGetter: true
hasSetter: false
name: "smoke_density"
show: true
valueType: "substance_amount"
scale: "parts_per_million"
value: 2.7472610473632812
valueFormatted: "2.75"
status: "idle"

There is also an Analog Gas sensor that one did import in to MSR OK.

Devices Info:

_id: "10696000"
deviceTypeId: "ezlopi"
parentDeviceId: "10696000"
category: "security_sensor"
subcategory: "gas"
gatewayId: "457a5069"
batteryPowered: false
name: "Gas Sensor Analog"
type: "sensor"
reachable: true
persistent: true
serviceNotification: false
armed: false
roomId: ""
security: "no"
ready: true
status: "idle"
parentRoom: true
protectConfig: "default"

Items Info:

_id: "20696000"
deviceId: "10696000"
hasGetter: true
hasSetter: false
name: "gas_alarm"
show: true
valueType: "token"
enum:
0: "no_gas"
1: "combustible_gas_detected"
2: "toxic_gas_detected"
3: "unknown"
valueFormatted: "no_gas"
value: "no_gas"
status: "idle"

And this is how this MQ2 Gas Sensor looks like on their dashboard:

Digital

Analog

They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!

And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.

THANKS.

cw-kid

That setting is in Users & Account Info - Security - Enable potentially unsafe lua code, like wget and RunLua.

It was unchecked. I checked it again and Reloaded the engine and it started working again. I am not sure how that setting got turned OFF as I didn't do it.

But thanks anyway for pointing me in the right direction !

cw-kid

I was using this method here by @therealdb to run Lua Code from MSR on my Vera Plus but it seems to have stopped working now.

Its the one where you uploaded a file called VeraScenes.lua to your Vera hub and then you could call functions of that file to run particular bits of Lua code from an MSR reaction etc.

This was working well for a long time but I noticed today its not working now.

Looking in the MSR log after I ran a reaction in one of my rules I just saw this:

[latest-23338]2024-02-19T18:41:35.650Z <Engine:INFO> Enqueueing "Front Cam Motion Detection ON or OFF Old Method<RESET>" (rule-klten9w9:R)
[latest-23338]2024-02-19T18:41:35.653Z <Engine:5:Engine.js:1466> [Engine]Engine#1 enqueued reaction rule-klten9w9:R as 22989
[latest-23338]2024-02-19T18:41:35.654Z <Engine:5:Engine.js:1624> _process_reaction_queue() wake-up!
[latest-23338]2024-02-19T18:41:35.655Z <Engine:5:Engine.js:1563> _process_reaction_queue() running task 22989: [Object]{ "tid": 22989, "id": "rule-klten9w9:R", "rule": "rule-klten9w9", "__reaction": [RuleReaction#rule-klten9w9:R], "next_step": 0, "status": 0, "ts": 1708368095651, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] }
[latest-23338]2024-02-19T18:41:35.657Z <Engine:NOTICE> Starting reaction Front Cam Motion Detection ON or OFF Old Method<RESET> (rule-klten9w9:R)
[latest-23338]2024-02-19T18:41:35.659Z <Engine:5:Engine.js:1701> [Engine]Engine#1 reaction rule-klten9w9:R step 1 perform [Object]{ "entity": "vera>system", "action": "x_vera_sys.runlua", "args": { "lua": "VeraScenes.FrontCamMotionDetectionOff()" } }
[latest-23338]2024-02-19T18:41:35.660Z <Engine:5:Engine.js:1577> _process_reaction_queue() task returned, new status 3; task 22989, history 1629572
[latest-23338]2024-02-19T18:41:35.663Z <Engine:5:Engine.js:1624> _process_reaction_queue ending with 1 in queue; none delayed/ready; waiting
[latest-23338]2024-02-19T18:41:35.671Z <VeraController:ERR> [VeraController:performOnEntity] action request failed
[latest-23338]2024-02-19T18:41:35.672Z <VeraController:CRIT> Error: Request failed: 401 Error [-]
Error: Request failed: 401 Error
    at /home/stuart/reactor/server/lib/Controller.js:886:37
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[latest-23338]2024-02-19T18:41:35.673Z <Engine:ERR> [Engine]Engine#1 reaction rule-klten9w9:R step 1 perform x_vera_sys.runlua failed: [Error] Request failed: 401 Error [-]
[latest-23338]2024-02-19T18:41:35.673Z <Engine:INFO> [Engine]Engine#1 action args: [Object]{ "lua": "VeraScenes.FrontCamMotionDetectionOff()" }
[latest-23338]2024-02-19T18:41:35.674Z <Engine:5:Engine.js:1624> _process_reaction_queue() wake-up!
[latest-23338]2024-02-19T18:41:35.675Z <Engine:5:Engine.js:1563> _process_reaction_queue() running task 22989: [Object]{ "tid": 22989, "id": "rule-klten9w9:R", "rule": "rule-klten9w9", "__reaction": [RuleReaction#rule-klten9w9:R], "next_step": 2, "status": 1, "ts": 1708368095651, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise], "attempts": 0, "history_id": 1629572 }
[latest-23338]2024-02-19T18:41:35.676Z <Engine:INFO> Resuming reaction Front Cam Motion Detection ON or OFF Old Method<RESET> (rule-klten9w9:R) from step 2
[latest-23338]2024-02-19T18:41:35.678Z <Engine:5:Engine.js:1753> [Engine]Engine#1 reaction rule-klten9w9:R step 3 notify Telegram with [Object]{ "message": "Front Garden CAM Motion Detection Off", "profile": "default" }
[latest-23338]2024-02-19T18:41:35.685Z <Engine:INFO> Front Cam Motion Detection ON or OFF Old Method<RESET> all actions completed.
[

Was anyone else using this method to have Lua code run on your Vera hub being called via an MSR reaction ? Does it still work for you?

Thanks

cw-kid

Thanks for the replies and tips.

In the end after more Googling for my Debian Buster install this seems to have fixed it for me.

I removed the new /usr/local/bin/node directory that got installed the other day.

rm /usr/local/bin/node

Then running the command "which node" the path was back to the old path of /usr/bin/node and "node -v" was showing the old version again of 16.20.2

I then found these commands on Google and tried them:

curl -fsSL https://deb.nodesource.com/setup_current.x | sudo -E bash -

sudo apt-get install -y nodejs

This seems to have upgraded the 16.20.2 version with a newer version, I saw this line in the terminal output

Unpacking nodejs (20.5.1-deb-1nodesource1) over (16.20.2-deb-1nodesource1)

Now when I do a node -v it says its version 20.5.1 and the alert message in MSR has now gone.

"which node" still says the path is the original path of /usr/bin/node also.

I have no idea if this was the correct way to do it but I think it has worked.

cw-kid

This is the contents of that log file it mentioned:

0 verbose cli /usr/bin/node /usr/bin/npm
1 info using npm@8.19.4
2 info using node@v16.20.2
3 timing npm:load:whichnode Completed in 1ms
4 timing config:load:defaults Completed in 7ms
5 timing config:load:file:/usr/lib/node_modules/npm/npmrc Completed in 3ms
6 timing config:load:builtin Completed in 3ms
7 timing config:load:cli Completed in 10ms
8 timing config:load:env Completed in 1ms
9 timing config:load:project Completed in 26ms
10 timing config:load:file:/root/.npmrc Completed in 10ms
11 timing config:load:user Completed in 11ms
12 timing config:load:file:/usr/etc/npmrc Completed in 1ms
13 timing config:load:global Completed in 1ms
14 timing config:load:validate Completed in 1ms
15 timing config:load:credentials Completed in 6ms
16 timing config:load:setEnvs Completed in 4ms
17 timing config:load Completed in 73ms
18 timing npm:load:configload Completed in 74ms
19 timing npm:load:mkdirpcache Completed in 4ms
20 timing npm:load:mkdirplogs Completed in 1ms
21 verbose title npm install npm@10.2.5
22 verbose argv "install" "--global" "npm@10.2.5"
23 timing npm:load:setTitle Completed in 5ms
24 timing config:load:flatten Completed in 14ms
25 timing npm:load:display Completed in 24ms
26 verbose logfile logs-max:10 dir:/root/.npm/_logs
27 verbose logfile /root/.npm/_logs/2023-12-08T14_42_53_914Z-debug-0.log
28 timing npm:load:logFile Completed in 25ms
29 timing npm:load:timers Completed in 0ms
30 timing npm:load:configScope Completed in 0ms
31 timing npm:load Completed in 138ms
32 silly logfile start cleaning logs, removing 1 files
33 silly logfile done cleaning log files
34 http fetch GET 200 https://registry.npmjs.org/npm 126ms (cache hit)
35 timing command:install Completed in 275ms
36 verbose stack Error: Unsupported engine
36 verbose stack     at Object.checkEngine (/usr/lib/node_modules/npm/node_modules/npm-install-checks/lib/index.js:14:25)
36 verbose stack     at Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:109:16)
36 verbose stack     at async module.exports (/usr/lib/node_modules/npm/lib/cli.js:78:5)
37 verbose pkgid npm@10.2.5
38 verbose cwd /root
39 verbose Linux 4.19.0-21-amd64
40 verbose node v16.20.2
41 verbose npm  v8.19.4
42 error code EBADENGINE
43 error engine Unsupported engine
44 error engine Not compatible with your version of node/npm: npm@10.2.5
45 error notsup Not compatible with your version of node/npm: npm@10.2.5
45 error notsup Required: {"node":"^18.17.0 || >=20.5.0"}
45 error notsup Actual:   {"npm":"8.19.4","node":"v16.20.2"}
46 verbose exit 1
47 timing npm Completed in 774ms
48 verbose code 1
49 error A complete log of this run can be found in:
49 error     /root/.npm/_logs/2023-12-08T14_42_53_914Z-debug-0.log

cw-kid

Looks like it changed the path of the node installation? Maybe MSR is still looking at the old path?
This was from the terminal output:

 installing : node-v21.4.0
       mkdir : /usr/local/n/versions/node/21.4.0
       fetch : https://nodejs.org/dist/v21.4.0/node-v21.4.0-linux-x64.tar.xz
     copying : node/21.4.0
   installed : v21.4.0 (with npm 10.2.4)

Note: the node command changed location and the old location may be remembered in your current shell.
         old : /usr/bin/node
         new : /usr/local/bin/node
If "node --version" shows the old version then start a new shell, or reset the location hash with:
hash -r  (for bash, zsh, ash, dash, and ksh)
rehash   (for csh and tcsh)

There is a file called "node" under both usr/bin and usr/local/bin directories, I can see these using WinSCP to look at the file structure.

This was also in the terminal before the above:

 npm install -g n

added 1 package, and audited 2 packages in 2s

found 0 vulnerabilities
npm notice
npm notice New major version of npm available! 8.19.4 -> 10.2.5
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.2.5
npm notice Run npm install -g npm@10.2.5 to update!
npm notice
root@HP-Thin01:~# ^C
root@HP-Thin01:~# npm install -g npm@10.2.5
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: npm@10.2.5
npm ERR! notsup Not compatible with your version of node/npm: npm@10.2.5
npm ERR! notsup Required: {"node":"^18.17.0 || >=20.5.0"}
npm ERR! notsup Actual:   {"npm":"8.19.4","node":"v16.20.2"}

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2023-12-08T14_42_53_914Z-debug-0.log

I am stuck now and don't know how to fix this?

Thanks

cw-kid

Reactor-Editor / Reactor-ui-Status Errors

every X days field uneditable

[Reactor] Use VirtualEntityController actions to drive a Reolink spotlight

Darker Reactor style

Which user to install nodejs as ? Debian Linux

Reactor (Multi-System/Multi-Hub) Announcements

OpenAI Controller for Reactor

Thanksgiving lighting took a holiday

[How-to] Managing holidays in Reactor

Reference error - null object

Trouble Configuring Multi-System Reactor Logic Across Devices

openLuup email server

MSR UI on a mobile browser

ZWaveJSController - Warning/Error Traceback - Registering action set volume for Aeotec Siren 6 (ZW164)

High temperature sensor for Zigbee

New to Home Automation Looking for a Single app?

UZB/RaZberry Firmwares - Update

Sending data to a USB port to interface with a wireless switch

Seeking Advice:

[Reactor] Assignment to alarm ignored -- expression-driven global cannot be set by assignment

Posts