-
I have been trying to get my windowshadeautomation (outside window)to work for some time in reactor but I cant get it working good..
What I want is that shades should close if above 20000lux if window is closed else if window open only set shade position to 0.7And if shade is closed and window is opened shade should go to 0.7 and if closed again shade should go back to closed
I have tried so many variants with different results.
I need som help...
/Mattias
I have :Trigger
light sensor ( above 20000 lux )Constraint
Rainsensor ( no rain)
Windsensor(no wind)
Window (closed, or open )Set reaction
Cover close or set 0.7Reset reaction
Cover open -
I have "rainstorm lights", those couple lights in the house that come on during the day when it's gotten so dark due to weather that it's almost like night inside. The trigger for this is mode + solar radiation level.
However, this gets triggered in that last hour before I wake in the morning due to the fact that I switch the house from NIGHT mode to DAY mode at 05:30 so climate control has an hour to warm the house appropriately before I rise at 06:30 weekdays (07:30 weekends.) To circumvent that I've added two "excludes" for hours "not between".
Everything is working great with the exception of blocking the pre-alarm hours. I'm posting what I've created for another set of eyes to review and point out my obvious-to-all-but-me error.
969cb424-f1e6-41da-b785-f0b35e9cc644-image.png 50ee5a24-ac0a-4d2c-9e7b-36923b56c4d9-image.png
-
I have been playing with TTS through an Ikea/Sonos speaker controlled through Hubitat.
When writing the action using variables and then using the PLAY button for that action I get an error message.
Using the PLAY button for the Set Reaction and the TTS works fine.
I'm not sure what the difference is but it is nice that text with variables works fine with TTS. -
Haven't been keeping track with the releases for a while, still on 096.
Is there any risk in using savedata from this old version on the newest, or can i just go ahead and update to the new docker?
Just thinking if there's any changes in savedata format or handling?
-
I have MSR installed on two separate TS-251+ devices with the shared MSR_Data folders kept in sync using Hybrid Backup Sync.
The container on the standby or secondary server is stoped so both versions are not operating at once.
I've tried disabling one and switching to the other and that works well. It is nice to have the data backed up and another system ready to go if the first one fails.
It would be nice to have a way for the backup MSR container to be running and watching the primary MSR and take over automatically. -
We're 60 days out from the 1.0 release date I gave earlier in this category. For about the next 30 days, I'll entertain new feature requests for anything you all feel is absolutely needed and not yet present for a 1.0 release, and you're going to have to make a strong case. Short of that, it will have to live on the wish list for a possible future release.
Identify and discuss in this topic, please... go!
-
OK, people, here we go! At long last, Multi-System Reactor developer preview is available!
The package can be downloaded from the Reactor bug tracker, a MantisBT system (at https://reactor.toggledbits.com/mantisbt/). There is a download button in the left margin, as well as links to the documentation, which you will need for installation.
UPDATE 2021-02-24 -- To keep spammers off, I've locked down registration on the Bug Tracker. To get access to the Bug Tracker and preview downloads, please PM me (not reply here) your full name and email address and I will set up an account for you.
This version of MSR will run on Linux systems, including RPi's under Raspios Buster, running node.js version 12.10 or higher (v14.15.1). For RPi users, there is an installation script that will install a local copy of node.js (for the logged-in user).
Bugs reports will be handled through the bug tracker only. Discussion and questions in this forum are fine, though (if that leads to a bug report, we'll transition).
This version supports Vera (and openLuup to the degree it's compatible with Vera Luup), Hubitat, and Home Assistant. Some of the device support on the H platforms is still a bit basic, but it is largely controlled by configuration and progress can be made quickly.
The documentation beyond installation is a mess. Of course, I started with the existing documentation and have been massaging into MSR's particulars, but it still has a long way to go on the detail.
I know I don't have to say this, but I will anyway... let me know how it goes!
-
This Might have been addressed, but I did not see anything anywhere.
Do the new EZLO controllers work with MSR?
-
I would like an explanation of how I can define a global variable in numeric format.
Scenario 1:
Create a global variable in Expressions > Add Expression > variable name > set initial value = 0 (number zero) When entering Rule Sets > Triggers > Variable Value, the variable created appears to be selected and used in the rule However, in Set Reaction > Set Variable, this variable that was created with a numeric value does not appear, so we cannot change the value.Scenario 2:
Create a global variable in Expressions > Add Expression > variable name > DO NOT SET VALUE, leave as null When to go into Rule Sets > Triggers > Variable Value, the variable created appears to be selected and used in the rule, of course, because it has no value yet it is set to zero In Set Reaction > Set Variable, this variable appears, and we can define a content, that even if it is a number, it will be stored as a characterTo summarize, for scenario 1, I can't find a way to handle the value. For scenario 2, it works, but I can't use it if I want to use the variable for mathematical operations.
A little help from the community.
I use MSR 21153.
Thanks
-
Three LIFX outdoor bulbs, call them #1, #2, #3.
The goal is to have the following outcome:
#1, color A
#2, color B
#3, color C
after 00:00:10, hard shift:
#1, color B
#2, color C
#3, color A
after 00:00:10, hard shift:
#1, color C
#2, color A
#3, color B
after 00:00:10, hard shift:
#1, color A
#2, color B
#3, color CVisual being that the colors essentially move in a single direction across the house all night long.
I thought maybe cannibalizing Reactor Ex Machina until I realized I'm shifting COLORS, not ENTITIES.
Thoughts, anyone?
-
@toggledbits in 21153, I'm getting this rather consistent warning message every time I click on "Status":
System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems.Thing is, my system time and MSR's clock match exactly, and in turn match Internet time precisely for my time zone. Also, the TZ variable is set correctly in my Docker setup.
-
I have some experience with Linux from about 30 years ago and my first thought was to install MSR in a QNAP TS-251+ Debian container. That did not go well as at every step it seemed I needed to add components to the OS to move forward one step. I got so frustrated I ordered a RPi which comes tomorrow. I have tried a few container Linux versions and gotten the furthest with CentOS.
MSR is running but complains about the system time being different from the MSR time. MSR is at my correct local time but the container OS is not. All the searching says that datetimectl is the program to run but I get an error about file or folder being incorrect. As long as MSR is at the correct time is that enough? -
I have a Hubitat device errors of devices that I am pretty sure I have never published to MSR. I have looked through my rules and cant find any reference to the devices and have checked my Maker API instance and the devices are not included. I am using Version 21129. Here is an example:
2021-05-10T01:30:00.013Z Engine:5:1032:Engine.js _process_reaction_queue() running task 4 { "tid": 4, "id": "rule-kodpluwh:R", "rule": "rule-kodpluwh", "__reaction": [RuleReaction#rule-kodpluwh:R], "next_step": 0, "status": 0, "ts": 1620610200011, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] }
2021-05-10T01:30:00.013Z Engine:NOTICE Starting reaction Test-Stairs Light<RESET> (rule-kodpluwh:R)
2021-05-10T01:30:00.013Z Engine:NOTICE Test-Stairs Light<RESET> delaying until 1620610500013<5/9/2021, 8:35:00 PM>
2021-05-10T01:30:00.014Z Engine:5:1036:Engine.js _process_reaction_queue() task returned, new status 2; task 4
2021-05-10T01:30:00.015Z Engine:5:1071:Engine.js _process_reaction_queue() ending with 1 in queue; waiting for 1 (next delayed task)
2021-05-10T01:30:04.873Z HubitatController:ERR HubitatController#hubitat device 96 not found. You may need to publish the device in Maker API to make it accessible to Reactor.
2021-05-10T01:30:04.884Z HubitatController:ERR HubitatController#hubitat device 96 not found. You may need to publish the device in Maker API to make it accessible to Reactor.
2021-05-10T01:30:04.888Z HubitatController:ERR HubitatController#hubitat failed request for device 96 info: Error: unparseable response
2021-05-10T01:30:04.889Z HubitatController:CRIT Error: unparseable response
Error: unparseable response
at /opt/reactor/server/lib/Controller.js:486:35
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:93:5) -
When using Vera I made use of Deus Ex Machina II after Patrick took it over. Worked brilliantly for ghosting lights on and off when I was away.
Now that my devices are migrated to Hubitat I can't make use of DEMII.
Any thoughts on how to replicate this randomness with two or three lights in MSR?
-
Knowing that MSR Preview may not yet fully implement LuaXP (CORRECTION: MSR uses a different language lexpjs), I could not resist whipping up some text expressions for fun. Whereupon two things popped out at me:
The new scaling (0.00 - 1.00) of Dimming Level will require a rewrite of certain Expressions that I use to balance my light levels. For example, it was my custom to monitor one lamp's brightness (0 - 100) with Reactor Luup, then set another lamp to 93% of that level, using this Expression: floor(getstate( 9, "urn:upnp-org:serviceId:Dimming1", "LoadLevelTarget" ) * 0.93)Now, in MSR, it will become necessary to modify that to read:
floor ((getEntity( "vera>device_9" ).attributes.dimming.level * 0.93)*100)/100which effectively scales the value up x 100 (so that floor() can act upon it correctly), then downscale it / 100. Just an FYI to ponder.
I'm noticing that every edit, however minor, of an Expression in MSR requires an immediate SAVE click before the 'Run' button will become active. That is to say, I cannot repeatedly evaluate the Expression during editing, without clicking SAVE first.Only mentioning this latter behavior since it departs so dramatically from Reactor Luup's paradigm.
-
Having issues with gmail. This was working 3 days ago. I updated to nodejs14 and for some reason had to reinstall MSR I did not have backup of notification.yaml, so re-entered the settings. The log is showing the smtp call is timing out. Any Ideas. I turn logging to 6 but no aditional info.
-
Hi
I had an MSR rule to run some LUA code that would randomly run different Vera scenes to change the colours on some garden lights, the rule would pulse every 15 minutes, so a different Vera scene was selected to change to a different colour etc.
local scenes = {"172", "173", "174", "175", "176", "271", "272"} local tmp_random_number = math.random(1,7) local scene_id_to_launch = scenes[tmp_random_number] luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1", "RunScene", {SceneNum = scene_id_to_launch}, 0)This was working OK, but then I have been deleting lots of scenes off my Vera Plus and making them MSR Global Reactions instead and I forgot about this setup and now its broken as the Vera scenes have gone.
So now I have several MSR Global Reactions for setting each colour on these garden lights. But don't know how to achieve the same thing but by using Global Reactions instead of Vera scenes.
fe50d423-137d-438a-a090-d3cd709270be-image.png
Anyone good with expressions ? Or another way to do this in a rule?
Thanks
-
Hi!
In Home Assistant I sometimes uses the TTS, either to my Sonos or Google speakers. With reactor in Vera I also use TTS.
But in MSR I can't select the TTS-service. It's simply not there. Am I missing something, or is this the case, so far?
Thanks!
/Fanan -
Hi
Are there any plans to password protect the MSR web GUI with a username and password login ?
If so when might we expect that feature ?
Thank you.
Issues installing MSR on Debian 10 Linux
-
Hi
I bought a cheap HP T520 Thin Client machine with an SSD to run MSR on, rather than running it on my Rpi with SD card etc where it is located currently.
I installed node js It says I have version 10.24.0 of node js installed.
When I run this command to test MSR "node app.js" it says:
"Error: This application requires nodejs 12.20.1 or higher"
I have run "apt update" command and it says all packages are up to date, so I am not sure how to increase the version number of node js on this Debian install ?
Any tips ?
Thanks
EDIT:
I followed this guide here the PPA section, now node is showing as version 12.22.1
I can now acceess MSR in the web browser.
So just need to figure out how to make MSR auto start on boot under Debian 10 Buster.
-
If your platform doesn't offer a more current nodejs, you'll have to download nodejs directly and install it using their documentation for Linux installs.
Note: To avoid confusion, remove the nodejs and npm packages you installed before downloading and installing.
Note 2: You really should go to node 14.15 or higher. I'm going to remove support for 12 before release this summer.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@toggledbits said in Issues installing MSR on Debian 10 Linux:
You really should go to node 14.15 or higher. I'm going to remove support for 12 before release this summer.
So I've done it all wrong then.
Don't even know how to uninstall what I have just installed LOL. More Googling then...
-
Just checked my Raspberry Pi that is running the live version of MSR currently and that is node version 12.22.0
-
@cw-kid said in Issues installing MSR on Debian 10 Linux:
So just need to figure out how to make MSR auto start on boot under Debian 10 Buster.
Here's a sample service configuration for systemd. You would modify and place this file in (typically)
/etc/systemd/system/reactor.service.[Unit] Description=Multi System Reactor After=network.target [Service] Type=simple User=patrick WorkingDirectory=/home/patrick/Documents/reactor ExecStart=/usr/local/bin/node app -p Restart=on-failure RestartSec=5s [Install] WantedBy=multi-user.targetThe key things you need to modify are the
Uservalue (do not run Reactor as root), theWorkingDirectory(path to the Reactor install directory), andExecStartfor the correct path to yournodeexecutable.Then run the following commands:
sudo systemctl daemon-reload # tells systemd the config has changed sudo systemctl enable reactor # tells systemd to start the service at boot sudo systemctl start reactor # tells systemd to start the service nowAlso since you've just installed/upgraded nodejs, don't forget to run
npm i --no-savein your Reactor install directory before starting Reactor. -
@toggledbits said in Issues installing MSR on Debian 10 Linux:
To avoid confusion, remove the nodejs and npm packages you installed before downloading and installing.
OK thanks that's helpful about running it as a service, but I am not that far along yet I don't think.
Now need to uninstall node js and the npm packages and then install the 14.x node js version etc.
Which I am not sure how to uninstall things yet.
-
OK I think I have uninstalled everything using these commands:
apt remove nodejs
apt autoremove
I've downloaded the x86 64bit Linux version of node js and I am looking at installing that one instead now.
-
It looks like the PPA link you gave recommends adding a package repository and installing them via apt, so uninstall should just be:
sudo apt remove nodejs npmThose PPA instructions also tell you how to get the version you want.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@toggledbits said in Issues installing MSR on Debian 10 Linux:
sudo apt remove nodejs npm
Bit late to run that command:
apt remove nodejs npm Reading package lists... Done Building dependency tree Reading state information... Done Package 'npm' is not installed, so not removed Package 'nodejs' is not installed, so not removed 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.I think the commands I ran earlier have removed things but I still see a .npm folder in my home folder.
I am working out now how to install the later 14.x version of node js.
EDIT:
I installed again using the PPA method and just changed the curl command to use the 14.x
curl -sL https://deb.nodesource.com/setup_14.x -o nodesource_setup.shI now have node version 14.17.0 installed.
-
Don't forget to complete the Reactor install instructions here: https://reactor.toggledbits.com/docs/Installation/#new-install-linux-various-bare-metal-without-docker
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
OK making some progress slowly. I now have MSR up and running automatically after a system reboot.
And I am on node js version 14.17.0
Now to copy everything from my Rpi installation to the new HP Thin Client installation to get all my rules moved over.
I assume I can just copy the entire reactor folder from one machine to the other.
-
You just need
configandstoragesubfolders. It won't hurt to copy everything, but it's overkill. -
OK many thanks.
Just looking at setting a static LAN IP first on the new HP thin client box.
-
Probably a good idea to make sure you have NTP running on the box as well (network time).
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@toggledbits said in Issues installing MSR on Debian 10 Linux:
NTP running on the box
OK I'll have to look in to how to do that then also.
-
@cw-kid, yeah it takes a little googling to set up and brand new debian OS but I am sure you will get there. I went through the same thing setting up my T640. Debian takes a little bit more work than ubuntu which has a lot of these setup by default.
-
I'm reading this article about Debian and time here.
The date and time is currently set correctly:
"By default, Debian 10 runs the standard ntpd server to keep your system time synchronized with a pool of external time servers. We can check that it’s running with the systemctl command:"
sudo systemctl status ntpWhen I run this command in Putty it says:
Unit ntp.service could not be found.It goes on to say "To get more information about the status of ntpd we can use the ntpq command:"
ntpq -pI get the response:
-bash: ntpq: command not foundSo maybe its not currently installed on my installation.
its only a 16GB SSD in the HP Thin Client, so I don't have a desktop environment installed only SSH server etc.
I will look at installing this ntpd service next.
EDIT:
Ran this command to install it:
apt-get install ntpNow the above commands are working.
-
Hi, well I bought the HP T520 Thin Client because of what you said to me previously. It was cheap enough from eBay.
I had some issues with the power supply however as it didn't come with one.
I did have a spare suitably spec'd laptop power supply, but it had the wrong DC connector plug on the end of it.So I ordered the correct "DC Tip 7.4x5.0mm Power Plug Socket Connector" off eBay and cut the other one off and soldered the new one on.
However the HP Thin Client was not turning on, no power nothing at all and totally dead.
I then read that you have to use a genuine HP power supply, as they have some kind of checking so that the thin clients won't power on if you are using a 3rd party power supply.
Corporate Greed !
I then found an article about hacking the unit and soldering in a 240K resister on the back of the power input jack and I did this today and amazingly it worked and the thin client powered on.
One thing I can't figure out how to do yet is to update the BIOS without having one of their supported OS installed.
-
I don't have this exact model but... my HP desktops all have the ability to update the BIOS from within the UEFI BIOS. Have you tried that? Sorry for the song and dance on the power supply. I never encountered this since I always got power bricks with the ones I bought and I actually have spare power supplies... Great soldering job though!
-
There is an option in the BIOS menu to update / flash the BIOS but when I click OK on it, it says:
"Can not find bios update interface"
I've not really looked in to it properly yet as I was keen to get MSR up and running first.
From the quick Google searches I did, most suggested you need to have one of the HP supported operating systems installed to be able to update the BIOS.
But there must be some work around some how. I need to read in to it more.
