Posts made by cw-kid | Smart Home

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

I just read on the last MSR update that we need to update node.js. I just checked and on my Linux Debian machine its version 16.17.0.

I then at the terminal ran this command but it says I already have the latest version of node.js which doesn't seem right.

sudo apt-get install nodejs
Reading package lists... Done
Building dependency tree
Reading state information... Done
nodejs is already the newest version (16.17.0-deb-1nodesource1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Any tips?

Thanks

EDIT:

I ran these commands instead to update all packages.

sudo apt update

then

sudo apt upgrade

I then did a node -v and now its version 16.20.2

However the announcement says "all nodejs versions earlier than 18 are now end-of-life".

EDIT2:

I then tried these commands:

npm install -g n

n latest

Now a node -v says its version 21.4.0

However after restarting MSR I still get this alert error:

cw-kid

You mean the <> brackets ? I did try without the brackets around SignalLevel.

Oh the : should not be there.

This works

match( Cam1103Response, "<SignalLevel>(\\d+)", 1 )

cw-kid

Hi

I am stuck trying to extract the "SignalLevel" value which is the WIFI Signal Strength off my Foscam via a http request. The request returns this, which isn't Json formatted data I don't think.

<CGI_Result>
    <result>0</result>
    <SignalLevel>52</SignalLevel>
</CGI_Result>

I created a rule that saves the http response into a Global Expression

But I am struggling to work out what is the correct expression code to extract the value?

Can anyone more knowledgeable please help?

Thank you.

cw-kid

Hi

Today in MSR alerts I see 100 alerts saying that the devices on my Ezlo controllers no longer exist.

They do still exist. I checked some of these devices in the Ezlo Online API Tool doing a hub.devices.list query.

I then checked that the ID numbers were the same for the devices and they are the same device ID's still.

So my devices do still exist with the same device ID's it seems.

So not sure why MSR has over 100 alerts saying otherwise.

I then looked in Entities selected my Ezlo Plus controller and it listed all my devices OK I think and nothing looked out of place.

Thanks

cw-kid

I've just updated to this version latest-23218-479da148 I will see how I get on with that.

UPDATE - I think this version is working I can see the Global Expressions auto evaluating.

cw-kid

@toggledbits

Hi Patrick.

I'm still not sure these Global Expressions are auto evaluating?

It's pretty hot here in the UK at the moment, been 27 degrees C today, still pretty hot now at midnight.

I just added additional fan cooling behind my router and its just dropped the CPU temp by another 4 degrees from 67 to 63.

However the Expression that makes the value pretty like 63.x degrees or whatever, for display on the Home Remote dashboard tile, did not auto evaluate as you can see in this screenshot.

I waited a while and it didn't update or change.

I then pressed the Play button on it and then it did update OK.

These should auto evaluate quite immediately right on any changes ?

Thanks.

EDIT: Looks like the CPU temp has just dropped again to 60 degrees but the other Global Expression hasn't evaluated or updated as you can see.

EDIT2:

And dropped again.

cw-kid

@toggledbits OK great. I think I have everything setup and working now. I also made all the Router Temperature expressions just Global ones, I was using a mixture of global and also local as I didn't realise I could use global expression values in the action with the $ wild card thing.

I will monitor my setup but I think its all working now.

Thank you.

cw-kid

I am confused now. I deleted the local expressions in the rule. I then created the global ones again. When I run the actions of the rule e.g. run the shell command and populate the "RouterMemoryResponse" Global expression that works OK.

However the other two global expressions were not automatically evaluated.

I pressed the play button on one and that is why that one has a value now. but the other one does not have a value.

Running the rules actions again and its the same.

Looking in a test trigger in a rule the value is null for "RouterMemoryUsed".

So I am still not convinced these global expressions are auto evaluating.

EDIT: Ignore this I forgot to restart MSR, seems I have to do that first ?

Now when I run the rules actions all three Global Expressions flash green.

cw-kid

OK cool I didn't know you could do that and it was that simple !

cw-kid

Yes I understand what you just said.

But back to my other question then, is it possible to use a Global Expression value in a rules action with a value like ${{ RouterMemoryFree }} but for the Global Expression rather than any local one.

cw-kid

Yes that's right, info only

The routers CPU temp and WIFI chip temps however I am using those in another rules trigger to warn me if its getting hot. so those had to be Global Expressions.

cw-kid

Seems I can just do them as Local Expressions after all instead of Global ones.

MSR UI on a mobile browser

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

[Reactor] [Dev] Clarifications/Docs for refreshCapabilities and Entity action implementations return types

Looking for Remote Switch boxes that can also be used with a wireless Decora Style Switch.

Openluup - verabridge can not load devices.

Access to log file viewer denied

Why different types of Triggers within openLuup & ALTUI

High temperature sensor for Zigbee

Darker Reactor style

openLuup_install.lua - URL changed?

Just starting what hub is best.

TTS in MSR?

OpenLuup : Loading Global Modules

Should MSR import this device type from an Ezlo controller?

Reactor (Multi-System/Multi-Hub) Announcements

A couple of things about Reactor 24293

cw-kid

Posts