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?

Just updated to latest 21294, ran usual update, It appears to start ok in console, but will not load in browser. The NODE_path looks correct but the console log show the below error.

log

NODE_PATH /data/data/com.termux/files/home/reactor:
[latest-21294]2021-10-23T15:55:41.542Z <app:null> Reactor latest-21294-c13ea5d starting on v14.15.4
[latest-21294]2021-10-23T15:55:41.546Z <app:INFO> Process ID 14540; platform android/arm #1 SMP PREEMPT Wed Jan 16 09:21:08 CST 2019; locale en_US.UTF-8
[latest-21294]2021-10-23T15:55:41.547Z <app:INFO> Basedir /data/data/com.termux/files/home/reactor; data in /data/data/com.termux/files/home/reactor/storage
[latest-21294]2021-10-23T15:55:41.548Z <app:INFO> NODE_PATH /data/data/com.termux/files/home/reactor:
/data/data/com.termux/files/home/reactor/app.js:231
        throw new Error(a0_0x4c6635(0xd9) + process[a0_0x4c6635(0xdb)][a0_0x4c6635(0x107)] + '\x20does\x20not\x20point\x20to\x20the\x20Reactor\x20install\x20directory');
        ^

Error: Environment NODE_PATH=/data/data/com.termux/files/home/reactor: does not point to the Reactor install directory
    at Object.<anonymous> (/data/data/com.termux/files/home/reactor/app.js:231:15)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
    at internal/main/run_main_module.js:17:47
NODE_PATH /data/data/com.termux/files/home/reactor:
[latest-21294]2021-10-23T15:55:41.796Z <app:null> Reactor latest-21294-c13ea5d starting on v14.15.4
[latest-21294]2021-10-23T15:55:41.800Z <app:INFO> Process ID 14547; platform android/arm #1 SMP PREEMPT Wed Jan 16 09:21:08 CST 2019; locale en_US.UTF-8
[latest-21294]2021-10-23T15:55:41.801Z <app:INFO> Basedir /data/data/com.termux/files/home/reactor; data in /data/data/com.termux/files/home/reactor/storage
[latest-21294]2021-10-23T15:55:41.801Z <app:INFO> NODE_PATH /data/data/com.termux/files/home/reactor:
/data/data/com.termux/files/home/reactor/app.js:231
        throw new Error(a0_0x4c6635(0xd9) + process[a0_0x4c6635(0xdb)][a0_0x4c6635(0x107)] + '\x20does\x20not\x20point\x20to\x20the\x20Reactor\x20install\x20directory');
        ^
```===group
```java

===

@huhnmann You could still use the shelly 1 in the same way as a i3. You can disiconnect the relay from the switch. You then end up with what you required, and you are still left with future options if you change you requirements.
p.s. It is OCD no matter how much you deny it.

@akbooer said in "kinda smart" switch to put behind a normal light switch:

I use the MK Grid switch hardware (in the UK)

I use Click Mode, good quality. These are not grid design but still all switches can be interchanged, the have mulitple inserts and colours. And the bonus of being cheaper than MK. and take less space in the box.

@huhnmann said in "kinda smart" switch to put behind a normal light switch:

That light switch has to work exactly as before.

fitting a shelly 1 , the light should function as before but also have smart capabilities, so you get the best of both worlds

The i3 is a bit wasteful if only a single switch. If it is a single switch why not go with a shelly 1 then you make the light smart and can also send http request or subscribe to device mqtt stat topic.

@catmanv2 I never had any luck with the BL plugin under vera or openLuup. They plugin never found any devices. I deregistered device and connected it to wifi only, and still no discovery. This is on Android.

Strange thing I finally tried discovery with a Ezlo plus and it discovered it first time.

This seems to work and stops the race condition, and there is no delay in reaponse from other device.
biuld the same rule for the other device. Both set the global expression dimming to 1 to stop the other reacting , and feeding back

I dont think you need sustained.
You can set ezlo dimmer > 0.
Then set a expression to grab the ezlo dimmer level.
Then in set reaction, set vera dimmer to ${{name_of_expression}},
and reset reaction set to vera dimmer to 0.

You can make the same rule in reverse for vera dimmer

Then if you turn on vera dimmer it will turn on ezlo, and if you turn of ezlo it will turn off vera.

Needs a bit more thought to follow dimming changes after that.

@eonnet, Dam I update yesterday morning, new update that evening lol.

So up date to latest 56 and the sustained is still there and set to changes.

There for me on latest 21243 using chrome for android
Maybe try another browser