Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
ElcidE

Elcid

@Elcid
HA and AI
CatmanV2C
Having hours of (actually quite fun) interaction with AI (Chat GPT) making up dashboards and sensors for HA. It's OK (well it's better than I am!) but it makes soooo many mistakes. Gets there in the end though, if you've half a clue (which I do half the time) C
Home Assistant
How to upgrade from an old version of MSR?
cw-kidC
Hello I haven't updated my installation of MSR in a very long time. Its a bare metal Linux install currently on version 24366-3de60836 I see the latest version is now latest-26011-c621bbc7 I assume I cannot just jump from a very old version to the latest version? Or can I? Thanks
Multi-System Reactor
Access control - allowing anonymous user to dashboard
tunnusT
Using build 25328 and having the following users.yaml configuration: users: # This section defines your valid users. admin: ******* groups: # This section defines your user groups. Optionally, it defines application # and API access restrictions (ACLs) for the group. Users may belong to # more than one group. Again, no required or special groups here. admin_group: users: - admin applications: true # special form allows access to ALL applications guests: users: "*" applications: - dashboard api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin_group allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: true session: timeout: 7200 # (seconds) rolling: true # activity extends timeout when true # If log_acls is true, the selected ACL for every API access is logged. log_acls: true # If debug_acls is true, even more information about ACL selection is logged. debug_acls: true My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
Multi-System Reactor
VEC Virtual Switch Auto Off
S
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules. I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds). Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off? With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches. Thanks Reactor (Multi-hub) latest-26011-c621bbc7 VirtualEntityController v25356 Synology Docker
Multi-System Reactor
Upcoming Storage Change -- Got Back-ups?
toggledbitsT
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future. In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level. Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way. I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption. A few other things to know: If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc. Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy). The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON. You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach). The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case. This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change. This thread is open for any questions or concerns.
Multi-System Reactor
Oddness in Copy/Move of Reactions
G
Topic thumbnail image
Multi-System Reactor
[Solved] function isRuleEnabled() issue
CrilleC
Topic thumbnail image
Multi-System Reactor
[Reactor] Problem with Global Reactions and groups
therealdbT
Topic thumbnail image
Multi-System Reactor
Possible feature request 2?
CatmanV2C
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks. Any chance of a 'bulk delete' option? No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices Cheers C
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Genuinely impressed with Zigbee and HA / Reactor
CatmanV2C
Just for the record, in case anyone is following, I'm really rather impressed. I have installed one of these: https://www.amazon.co.uk/dp/B0B6P22YJC?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 That's connected (physically) to the VM running on my Synology, with a 2m USB extension. The same host also runs Openluup, Mosquito, HA Bridge. Yesterday I installed Zigbee2mqtt. That was a bit of a PITA but mostly because of ports and permissions. Once up and running, and the correct boxes ticked, immediately visible in Home Assistant via the MQTT integration, and thence into Reactor I've only got two devices. I bought the cheapest sensor I could find, which is a door sensor. Dead easy to add to ZIgbee2mqtt and again, immediately visible in HA. https://www.amazon.co.uk/dp/B0FPQLWRW1?ref=ppx_yo2ov_dt_b_fed_asin_title The dongle is on the top floor of the house, and I wanted the sensor on the back door (just about as far apart as it's possible to get short of going into the garage) When I moved the sensor downstairs it dropped out pretty instantly (which wasn't a huge surprise) so quick bit of research found out that smart plugs will act as routers so... https://www.amazon.co.uk/dp/B0FDQDPGBB?ref=ppx_yo2ov_dt_b_fed_asin_title Took me about 30 seconds to connect. Updated the name. Instantly visible in Reactor with the new name pushed over from Zigbee2mqtt. And lo, the door sensor now has a signal of 140 and works as far as I can tell perfectly and instantly (unlike my z-wave one). A few more of those will be purchased and used to replace the Tuya wifi cloud devices and the (continually failing) Z-wave plugs (yeah, they were TKB so....) Commended to the house. Thanks for everyone that got me on the right lines. C
Zigbee
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[HowTo] Using HABridge with Reactor
therealdbT
If you’re like me and still running HABridge to control your devices locally via Alexa, you might need to tweak your endpoints to call Reactor via HTTP. Here’s the best way to do it, IMO: Insert the Reactor Canonical ID (e.g., zwavejs>71-1) into the MapID field, but make sure it’s URL-encoded like this: zwavejs%3E71-1. Then, configure these endpoints as needed: On: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.on Off: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.off Dim: For lights: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/dimming.set?level=${intensity.decimal_percent} For roller shutters: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/position.set?value=${intensity.decimal_percent} Color: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/rgb_color.set_rgb?red=${color.r}&green=${color.g}&blue=${color.b} Just replace [ReactorIP] with your actual IP address. By using these placeholders, you can standardize your endpoints across all devices, making maintenance easier. This setup works with any device mapped under MSR, regardless of the controller (ZWaveJS, Vera, HASS, OpenSprinkler, virtual, MQTT, DynamicEntities, etc.). If you need different calls, just go to the entities, get the action and parameters, and adjust accordingly. Enjoy super fast access to your devices via Alexa! If you're migrating from Vera, the endpoints are (URL-encoded) in a file called device.db, in JSON format, under your config. You'd write a script to align the new endpoints to the new one, if you prefer to do it automatically. YMMV.
How-To
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
About
Posts
251
Topics
20
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial
  • An electricians or wiring experts here?
    ElcidE Elcid

    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.

    General Discussion
  • npm ERR! code EBADPLATFORM reactor 20022
    ElcidE Elcid

    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"
  }
    Multi-System Reactor
  • Looking for ideas on how to implement an automation.
    ElcidE Elcid

    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.

    General Discussion
  • Looking for ideas on how to implement an automation.
    ElcidE Elcid

    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

    General Discussion
  • Multidimensional Array
    ElcidE Elcid

    @toggledbits said in Multidimensional Array:

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

    Not according to your doc's.
    Screenshot_20211126-211238.png

    Also used in a test expression and working.

    Screenshot_20211126-211533.png

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

    Multi-System Reactor
  • Multidimensional Array
    ElcidE Elcid 
    ${{[["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]
    Multi-System Reactor
  • Reactor not starting on latest 21294
    ElcidE Elcid

    just confirming 21297 working with original app.sh

    Multi-System Reactor
  • Reactor not starting on latest 21294
    ElcidE Elcid

    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?

    Multi-System Reactor
  • Reactor not starting on latest 21294
    ElcidE Elcid

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

    Multi-System Reactor
  • Reactor not starting on latest 21294
    ElcidE Elcid

    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?

    Multi-System Reactor
  • Reactor not starting on latest 21294
    ElcidE Elcid

    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

    ===

    Multi-System Reactor
  • "kinda smart" switch to put behind a normal light switch
    ElcidE Elcid

    @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.

    General Discussion
  • "kinda smart" switch to put behind a normal light switch
    ElcidE Elcid

    @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.

    General Discussion
  • "kinda smart" switch to put behind a normal light switch
    ElcidE Elcid

    @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

    General Discussion
  • "kinda smart" switch to put behind a normal light switch
    ElcidE Elcid

    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.

    General Discussion
  • Broadlink setup
    ElcidE Elcid

    @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.

    Vera/openLuup plugins
  • Sustained condition is missing from MSR
    ElcidE Elcid

    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
    Screenshot_20210914-184140.png Screenshot_20210914-184237.png Screenshot_20210914-184311.png Screenshot_20210914-185552.png

    Multi-System Reactor
  • Sustained condition is missing from MSR
    ElcidE Elcid

    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.

    Multi-System Reactor
  • Sustained condition is missing from MSR
    ElcidE Elcid

    @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.Screenshot_20210914-140102.png

    Multi-System Reactor
  • Sustained condition is missing from MSR
    ElcidE Elcid

    There for me on latest 21243 using chrome for android
    Maybe try another browser
    Screenshot_20210914-130221.png

    Multi-System Reactor
  • Login
  • Don't have an account? Register
  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved