@cw-kid I have not been able to login since the 28/03.
As to rebel, just a little more blunt than you. As I see it someone was on a purge.
Shame they are purging people that help others, specially vera support, still plenty of support here though.

I am a Electrician. I installed hundreds of smart devices for others prior to having my own home automation. In 2013 I bought a new house and decided to make it smart. I did some homework and settled on Z-wave and VeraPlus.
My installation comprises of
25 Z-wave dimmer/switch inserts
3 Z-wave door sensors
10 sonoff devices(basics,TH16 and Mini) ,
4 Tuya(lamps and RGB strips) ,
6 shellys(connected to motion sensors and 2 controlling dead DIY bolts )
3 Amazon Dots(gen2)
2 Broadlink (RMPro's)
4 DIY RF Venetian Blinds
2 Multi button DIY remotes
1 NVR
1 Network drive/Media server/ftp server.
1 smart thermostat heating and hot water
4 wired 240v/battery Aico smoke and heat detectors (connect to zwave via Relays)
1 robot hover.
1 Siren
Node-red server running on android.
Testing openluup on android.
Automate App running on andorid Boxes/phones.
All tv's are connected to android boxes.
No windows PC.
Debian running on android box.
Plugins Reactor, AlexaTTS, Switchboard and Virtual HTTP Switch.

I can control all of my devices from anyone of these platforms Vera/OpenLuup, Node-red, Automate(phone/tv box) or Alexa.
All devices have a standard/manual switch for anyone to control, and can be controlled even if my VeraPlus stopped working or internet out. My system is stable and may get a luup reload every couple of weeks.

None of my sonoff's or tuya have been flashed. I found Shelly very late into game and will be using these more now i found them, as they offer local control.

I have some coding knowledge from the 90's, but have never worked in the industry.

I now have node-red setting a silent switching of a v device, by saying "wake me up at [any time and/or day]". also depending which echo i use i can set a different v device, so different morning routines for each bedroom.

@catman you can also do all your H A Bridge devices in node red to, as it has the local hue lights bridge to. So you could replace H A Bridge with node-red. It would not be difficult to set a http request to set your virtual alarm.

Hi to all, Thought i would join as not to miss out on anygood information that you developers may share here.

note- The input box for text does not display to well.I can not see what i am typing.
Android 8 full sreen on tv box using firefox mobile view.
If i use desktop view everything is ok.

@CatmanV2 said in This is me:

Well, if I see further, it's because I stand of the shoulders of giants. I've got where I got because of the experts here.

Well said.

@cw-kid

Yes i am here, as always I will help anyone who asks.

Just for info - I have no idea what the reason for my suspension, I have contacted CS but they seem to be just ignoring my request for a clear reason.

As to GDPR if they run servers in europe then we are covered by GDPR, even if they move the servers to the US, as I think there is a privacy agreement with the US.

GDPR in the USA | GDPR compliance in US | GDPR and PII

GDPR in USA - find out how its affect USA, and become compliant with Cookiebot today.

0.5019607843137255, 0, 0.5019607843137255 You may want to round them. LOL

Yes thanks for your efforts @DesT

-- https request  json body
-- Enable potentially unsafe lua code in,  user account - security
local https = require "ssl.https"
local http = require "socket.http"
local ltn12 = require "ltn12"
local json = require "dkjson"
local payload = {{"test", "test", null, 0}}  --payload to be sent

local request_body = { secret = "1.KAddd87s8s8FasL7-ze4KG_p5hrVg4Kee1-t3vnwGFhI=", to = "test@gmail.com", device = null, priority = "high", payload = payload } --the json body
local response_body = {}
request_body = json.encode(request_body)

local r, c, h, s = https.request {
  url = 'https://llamalab.com/automate/cloud/message',
  method = 'POST',
  headers = {
    ["Content-Type"] = "application/json",
    ["Content-Length"] = string.len(request_body)
  },
  source = ltn12.source.string(request_body),
  sink = ltn12.sink.table(response_body)
}

isNaN([1,2,3]) and isNaN("ten"/2) and isNaN("ten" + "eight") are all true

Hey @cw-kid can i see photos of all your switches and the light fitting so i can establish the wiring method and where you can put the dimmer.
Are you going to change the switches to momentary?

I have seen your photos on old forum but they are unclear. The red wire going to earthing position seems odd. Is it just a red sleeve on a bare earth wire or is it a a spare wire they just earthed for safety.

When you take more photos can you get a clear shot of the cables leaving the box an a clear shot of back of switches showing the markings on switch.

A safety note , you are using metal switches, so there should be an earth fly lead from the earth on box to the switch. removing the switch from the box now means the metal on the switch is not earthed.

i get the following error when i run
~/reactor $ npm i --no-save --omit dev
Reactor is running and i see no ill effects so far
Thought i would report for info.

~/reactor $ npm i --no-save --omit dev
npm ERR! code EBADPLATFORM
npm ERR! notsup Unsupported platform for inotify@1.4.6: wanted {"os":"linux","arch":"any"} (current: {"os":"android","arch":"arm"})
npm ERR! notsup Valid OS:    linux
npm ERR! notsup Valid Arch:  any
npm ERR! notsup Actual OS:   android

and here is log for more info

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/data/data/com.termux/files/usr/bin/node',
1 verbose cli   '/data/data/com.termux/files/usr/bin/npm',
1 verbose cli   'i',
1 verbose cli   '--no-save',
1 verbose cli   '--omit',
1 verbose cli   'dev'
1 verbose cli ]
2 info using npm@6.14.10
3 info using node@v14.15.4
4 verbose npm-session e65bf5b70b2ee3fd
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 http fetch GET 200 https://registry.npmjs.org/dev 1079ms
8 http fetch GET 200 https://registry.npmjs.org/dev/-/dev-0.1.3.tgz 161ms
9 silly pacote tag manifest for dev@latest fetched in 1336ms
10 timing stage:loadCurrentTree Completed in 2965ms
11 silly install loadIdealTree
12 silly install cloneCurrentTreeToIdealTree
13 timing stage:loadIdealTree:cloneCurrentTree Completed in 11ms
14 silly install loadShrinkwrap
15 timing stage:loadIdealTree:loadShrinkwrap Completed in 316ms
16 silly install loadAllDepsIntoIdealTree
17 silly resolveWithNewModule dev@0.1.3 checking installable status
18 http fetch GET 200 https://registry.npmjs.org/inotify 788ms
19 http fetch GET 200 https://registry.npmjs.org/inotify/-/inotify-1.4.6.tgz 796ms
20 silly pacote range manifest for inotify@>= 0.1.6 fetched in 1636ms
21 silly resolveWithNewModule inotify@1.4.6 checking installable status
22 timing stage:rollbackFailedOptional Completed in 2ms
23 timing stage:runTopLevelLifecycles Completed in 4975ms
24 verbose stack Error: Unsupported platform for inotify@1.4.6: wanted {"name":"inotify","version":"1.4.6","engines":{"node":">=0.8"},"os":["linux"],"dependencies":{"bindings":"^1.3.1","nan":"^2.12.1"},"optionalDependencies":{},"peerDependenciesMeta":{},"devDependencies":{},"bundleDependencies":false,"peerDependencies":{},"deprecated":false,"_resolved":"https://registry.npmjs.org/inotify/-/inotify-1.4.6.tgz","_integrity":"sha512-WW8/uqIA04O3AePQVe/Ms3ZLR0yGamaz8YOEpaXc4WBAGOPZfzu58wWErEPSUYaPyDrJRIeCn6PEIQgC1ZyQ5w==","_shasum":"c5a51852df1647d1a589d46c4baa2771ed36b8d2","_shrinkwrap":null,"_id":"inotify@1.4.6","_from":"inotify@>= 0.1.6","_requested":{"type":"range","registry":true,"raw":"inotify@>= 0.1.6","name":"inotify","escapedName":"inotify","rawSpec":">= 0.1.6","saveSpec":null,"fetchSpec":">= 0.1.6"},"_spec":"inotify@>= 0.1.6","_where":"/data/data/com.termux/files/home/reactor/node_modules/dev"} (current: {"os":"android","cpu":"arm"})
24 verbose stack     at checkPlatform (/data/data/com.termux/files/usr/lib/node_modules/npm/node_modules/npm-install-checks/index.js:46:14)
24 verbose stack     at thenWarnEngineIssues (/data/data/com.termux/files/usr/lib/node_modules/npm/lib/install/validate-args.js:63:5)
24 verbose stack     at /data/data/com.termux/files/usr/lib/node_modules/npm/node_modules/iferr/iferr.js:3:64
24 verbose stack     at checkEngine (/data/data/com.termux/files/usr/lib/node_modules/npm/node_modules/npm-install-checks/index.js:25:10)
24 verbose stack     at module.exports.isInstallable (/data/data/com.termux/files/usr/lib/node_modules/npm/lib/install/validate-args.js:60:3)
24 verbose stack     at resolveWithNewModule (/data/data/com.termux/files/usr/lib/node_modules/npm/lib/install/deps.js:677:10)
24 verbose stack     at /data/data/com.termux/files/usr/lib/node_modules/npm/lib/install/deps.js:600:7
24 verbose stack     at /data/data/com.termux/files/usr/lib/node_modules/npm/node_modules/iferr/iferr.js:3:64
24 verbose stack     at /data/data/com.termux/files/usr/lib/node_modules/npm/node_modules/call-limit/call-limit.js:28:43
24 verbose stack     at processTicksAndRejections (internal/process/task_queues.js:75:11)
25 verbose pkgid inotify@1.4.6
26 verbose cwd /data/data/com.termux/files/home/reactor
27 verbose Linux 4.9.76
28 verbose argv "/data/data/com.termux/files/usr/bin/node" "/data/data/com.termux/files/usr/bin/npm" "i" "--no-save" "--omit" "dev"
29 verbose node v14.15.4
30 verbose npm  v6.14.10
31 error code EBADPLATFORM
32 error notsup Unsupported platform for inotify@1.4.6: wanted {"os":"linux","arch":"any"} (current: {"os":"android","arch":"arm"})
33 error notsup Valid OS:    linux
33 error notsup Valid Arch:  any
33 error notsup Actual OS:   android
33 error notsup Actual Arch: arm
34 verbose exit [ 1, true ]

Depandencies

{"dependencies": {
    "@influxdata/influxdb-client": "^1.18.0",
    "@mdi/font": "^5.9.55",
    "body-parser": "^1.19.0",
    "bootstrap": "4.6.0",
    "bootstrap-icons": "1.5.0",
    "cookie": "^0.4.1",
    "digest-fetch": "^1.2.1",
    "diskusage-ng": "^1.0.1",
    "express": "^4.17.1",
    "feather-icons": "^4.28.0",
    "font-awesome": "^4.7.0",
    "gridstack": "^5.0.0",
    "jquery": "3.6.0",
    "jquery-ui-dist": "1.12.1",
    "js-yaml": "^3.14.1",
    "node-fetch": "^2.6.7",
    "nodemailer": "^6.5.0",
    "qs": "^6.10.1",
    "serve-static": "^1.14.1",
    "uuid": "^8.3.2",
    "ws": "^7.5.6"
  }

There are plenty of 24v thermostats with remote sensors here in UK (about £30). The OP wanted "Trying to determine the best platform for a set it and forget it black box that works with as close to zero maintenance as possible."!

So my thinking is thermostat in tandem with external sensor, A little wiring job done. You could also probably use a shelly 1 with temp sensor addon if you want feedback.

Hi, would it not be simpler to add a second external thermostat on the return loop, which mimics ( connects to same wires) the external stats functions. So if loop goes below set point it switches to aux heat

@toggledbits said in Multidimensional Array:

There is no === operator in the expression language, it's just ==

Not according to your doc's.

Also used in a test expression and working.

Noted used "in" rather than "of" as I thought he wanted a 2D array not a object/dictionary.

${{[["Window 1","Status On"],["Window 2","Status On"],["Window 3","Status Off"],["Window 4","Status On"]]}}

should work
and to find all Status on's

each val in testarray : if val[1] === "Status On" then val[0] endif

and to find the value of Window 1

(each val in testarray : if val[0] === "Window 1" then val[1] endif)[0]

just confirming 21297 working with original app.sh

That's how i start MSR on my android system, then the console is clear and usable. How would you suggest I start it now under termux?

ok i removed :${NODE_PATH} from app.sh on line 11 and now it starts and shows in browser using nohup ./app.sh &

server/lib/Logger.js is there in the reactor folder
I can start reactor with NODE_PATH=$(pwd) node app.js and see it in browser
but using nohup ./app.sh & i can not open reactor in browser

app,sh

#!/bin/bash

WD="."
if [ "$1" == "-C" ]; then
	WD=${2:-.}
	shift 2
fi
WD=`realpath "${WD}"`

cd $WD || exit 1
export NODE_PATH="${WD}:${NODE_PATH}"
rm -f app.stop
while [ ! -f app.stop ]; do
	node app.js $* >> logs/console.log 2>&1
	[ $? -eq 127 ] && break;
	sleep 5
done

exit 0

is the : in line 11 the error?