-
Scenes and room don't flash as frequently as they used to but they still do.
I am starting a thread here though it seems to be an openLuup issue.
Everytime something in a room updates, the room entity flashes which is to be expected but I am seeing the same thing with scenes which are not running or triggered.I also open a ticket regarding an error I am seeing at startup regarding HVAC devices on openLuup which appears to be a syntax error.
-
Trying to install under termux on my nvidia shield. Having a problem unpacking. See attached picture.
-
I have a docker running smoothly now, thought i'd share it. (and BTW, it looks awesome, Patrick!)
So far i've only opened 8111, and /config as volume. Mabye the full /reactor folder should be exposed for easy updating?docker compose:
version: "3.9" services: MSR: container_name: MSR restart: always image: perhu/msr-alpine:latest ports: - "8111:8111" volumes: - type: volume source: MSR-config target: /etc/reactor/config - type: volume source: MSR-Storage target: /etc/reactor/storage volumes: MSR-config: name: MSR-config MSR-storage: name: MSR-storagedockerfile for those who want to modify the image:
FROM alpine:latest COPY /reactor/. /etc/reactor/ RUN apk add --update nodejs npm && cd /etc/reactor \ && npm install --loglevel error --no-save \ && cp dist-config/* config/ VOLUME ["/etc/reactor/config"] VOLUME ["/etc/reactor/storage"] EXPOSE 8111 CMD ["/bin/sh"] WORKDIR /etc/reactor CMD ["node", "/etc/reactor/app.js"] -
Hi
I have a rule that turns on my interior porch entrance light when its night and the front door is opened.
Its set to keep the light on for 1 minute and then turn it off.
I've been back in the house for well over an hour but just noticed the porch light is still on and hasn't turned off.
Its 21:17 pm here now.
This is the rules summary card:
d3dd2022-256c-4e75-b93b-3d1f40a9689b-image.png
I setup the Night rule as a Global Rule and its referenced in this rule.
Any clues ?
Thanks
EDIT: I should add that this rule has worked OK previously and the light has turned off after I have entered and the minute has passed.
-
Screen Shot 2021-02-25 at 19.56.59.png
Some font issues to be addressed I think on the dashboard.
-
@toggledbits said in Multi-System Reactor Developer Preview AVAILABLE:
Version 21054 now available.
...
2. This version runs on Windows, and there are draft instructions for how to get it installed.I am so excited!
Sorry that I need to bother with a noob question at the first step😂
Does this box need to be checked for MSR to run nicley?
7bc519af-f0e4-46af-a040-0ce261d08a8f-image.png -
Hi
Does the Reactor plugin for Vera support some 3rd party Vera plugins such as the Logitech Harmony plugin for example ?
In PLEG I am able to select a Harmony hub device and create some logic based on its various states.
2ecefb43-5b2d-4505-aef1-dd0c5b09dc3f-image.png
Other plugin examples might be the RGB Controller plugin which I am using with Fibaro RGBW modules, I can start the various light animations on the Fibaro RGBW module.
19962434-a707-4301-b168-00787fea16ed-image.png
8a629a9c-1968-40d8-a7c2-129bfebc9ac2-image.png
Or the AltHue plugin which exposes aspects of the Hue Bridge like ColorLoop or to be able to start Hue Scenes etc.
a8a67942-b862-4c3e-871f-f41081b20e8c-image.png
With MSR all this type of functionality is currently lost.
Obviously a work around would be to create Vera scenes instead and have those use these types of 3rd party plugins features and have MSR call those scenes. Don't think that would work for the Harmony plugin though where you are wanting to query states of the hub in your logic.
I am just wondering how Reactor plugin for Vera currently works in this respect and what any plans for MSR might be ?
Thank you.
-
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, 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!
-
Go ahead and open a PR for it, and we'll use that to track it.
-
"You need to use 0.0 to 1.0, not 0 to 255 (just like dimming values)."
How would I set the colour Purple as an example ?
Its RGB value is: 128, 0, 128
Thanks
-
Just to let you know that I've updated to version 21054, but the added basic support for generic thermostats still does not allow me to set the current setpoint for either my Horstmann Thermostat or the Auto Virtual Thermostat.
-
Having updated to 21054 it still states 21053 in MSR although hard refresh in Chromium (Ctrl-F5) and even re-boot. Reading the startup log it runs 21054:
2021-02-24T06:30:51.773Z app:null Reactor application v21054 starting on v14.15.4
2021-02-24T06:30:51.779Z app:INFO Process ID 1801; platform linux/arm #1402 SMP Tue Feb 16 14:12:18 GMT 2021
2021-02-24T06:30:51.818Z default:INFO Module Entity v21025
2021-02-24T06:30:51.825Z Controller:null Module Controller v21054
2021-02-24T06:30:51.827Z default:null Module Structure v21050
2021-02-24T06:30:51.843Z default:null Module Ruleset v21041
2021-02-24T06:30:51.844Z default:null Module Rulesets v21041
2021-02-24T06:30:51.874Z default:null Module Rule v21051
2021-02-24T06:30:51.882Z default:null Module Engine v21054
2021-02-24T06:30:51.884Z default:null Module httpapi v21041
2021-02-24T06:30:51.891Z default:null Module httpproxy v21054
2021-02-24T06:30:51.945Z default:null Module wsapi v21053
...Probably something I am missing but can not figure out why
-
I have entered in Maker API that allow endpoint to control Modes. But in MSR I cant find modes entity for hubitat. The vera plus has it.
Is it not just mapped in MSR?
/Mattias -
I guess there is no way to do IF Else statements without using LUA code ?
This is a small portion of code, I've just copied out of one of my PLEG actions run LUA Code.
The code checks a WOL with Ping switch in Vera, if its ON, it then sends a particular HTTP request to that Kodi HTPC to bring an IP Camera image on screen
It then does the same check for the next WOL with Ping switch / Kodi HTPC and so on etc.
Also the code checks Harmony activities to see if I'm currently in a FireTV activity instead? and if so sends a particular HTTP request to do Picture in Picture on the FireTV stick.
local status = luup.variable_get("urn:upnp-org:serviceId:SwitchPower1", "Status", 38) --Check Status of KODI01 WOL switch if status == "1" then --If on then send command to show Security Cam os.execute('curl -X POST -H "content-type:application/json" http://kodi:kodi@192.168.1.101:8080/jsonrpc -d \'{"jsonrpc":"2.0","id":1,"method":"Addons.ExecuteAddon","params":{"addonid":"script.frontgardencam"},"id":"1"}\'') else end local status = luup.variable_get("urn:upnp-org:serviceId:SwitchPower1", "Status", 39) --Check Status of KODI02 WOL switch if status == "1" then --If on then send command to show Security Cam os.execute('curl -X POST -H "content-type:application/json" http://kodi:kodi@192.168.1.102:8080/jsonrpc -d \'{"jsonrpc":"2.0","id":1,"method":"Addons.ExecuteAddon","params":{"addonid":"script.frontgardencam"},"id":"1"}\'') else endI can't see that this would be possible using just an MSR rule ?
Thanks
-
Him ... Got The reactor up and running but I can't see my Vera Plus and Hubitat.
I have restarted the reactor after doing necessary input in the reactor.yaml file.reactor:
What could I be doing wrong? Runs on a RPI
Is it correct ?
baseurl - The base URL to access the Reactor system.baseurl: "http://192.168**.***:8111"
units - imperial or metricunits: metric
location:node app js
city: "Stockholm City"
# Non-US users please use "province"
state: "GA"
#province: "Akersberga"
postal: "18494"
# Must be ISO two-character country code (i.e. the ISO 3166-1 Alpha 2 code)
country: "SE"
# Must be properly set for sunset/sunrise calculation.
latitude: 59.26465
longitude: -18.14490
# Units of elevation are meters (multiply feet by 0.3408 to get meters)
elevation: 0controllers:
id: vera
enabled: true
implementation: VeraController
name: Penthouse 🙂
config:
source: 'http://192.168..*_3480'id: hass
enabled: false
implementation: HassController
name: A Home Assistant system
config:
source: 'http://192.168.0.7:8123'
access_token: "place long-lived access token within"id: hubitat
enabled: true
implementation: HubitatController
name: Penthouse
config:
source: 'http://192.168..'
access_token: '*************************************' -
Hi
In some of my PLEG actions I run Lua code.
I guess I can't do that now with MSR. Assume I have to create a Vera scene with that same LUA code and have the MSR action call that scene etc.
What about the people who were using Reactor plugin for Vera? I assume they can run Lua code.
But won't be able to when using MSR on a separate box to Vera.
I am also seeing other things I am doing in PLEG but don't think I will be able to on MSR? Like monitoring devices for certain things.
For example I use PLEG with Fibaro Dimmer 2 modules to enable me to use the Scene Activation for double and triple clicks on the actual wall switches, PLEG sees this happening and then my action can run a Vera scene or whatever else I want.
I have three "Device Properties" setup in PLEG to monitor those aspects of the Fibaro Dimmer 2 device.
078cad4f-ebee-4951-a631-304da033d60f-image.png
Then this condition in PLEG:
(LoungeSceneActivated;LoungeLastSceneTime) and (LoungeLastSceneID == 15)Runs an action when I double click the Lounge Light wall switch.
Thanks
-
As per the title, I tried the update process twice.
-
If my longer term goal is to just use Vera as a Z-Wave radio only.
Or to maybe even replace Vera and Ezlo altogether with another Z-Wave hub like Hubitat or perhaps even a USB stick Z-Wave.me Z-Way or something (Assuming MSR supports that platform you plan to move to etc) .
Then all my "Scenes" might end up being rules in MSR.
These rules in MSR may have triggers that are automated as I'm setting up right now, or they may not have any triggers at all, other than being manual, like you can setup a manual scene in Vera.
I'd then want to be able to initiate some of those "scenes" by sending http requests to MSR from other devices and apps on my LAN.
Presumably for controlling Z-Wave devices directly on / off / dim etc, I'd been sending http requests to whatever the new Z-Wave hub might be? Hubitat or whatever.
Just thinking how you'd fully move away from Vera and any Vera scenes.
Or is this more the realm of OpenLuup? With using Vera still as the Z-Wave radio or a Z-Wave USB stick, which do they support?
In short I'd like to be able to send a simple one line HTTP request to MSR to have it run a particular "Set Reaction" action(s).
-
Schedule to turn on two side table lamps, 40 minutes before Sunset (everyday of the week) with some Constraints (Conditions) attached.
Condition 1 = Both lamps have to be off in the first place
AND
Condition 2 = A virtual switch called “Dark Mode” should be off
AND
Condition 3 = Vera is NOT in either house mode “away” OR “vacation”
I hope the screen shot is readable.
1de0e3ca-0104-40b6-a3f3-0fbf2b33ea87-image.png
I am a Reactor luddite and just want to make sure I am getting things in the right order / areas of the rule.
Thanks
-
Hi
77ae523e-9b97-4659-b113-40da6fcfcca2-image.png
I've just created four new rules as you can see in the screen shot above.
In the dark blue banners, the first two rules show text of:
Group: rule-klgiivpk-trig;
and
Group: rule-klghttuk-trig;
and the bottom two rules have text of:
Group: trig;
I've named each of my rules as you can see in the screen shot.
I was just wondering about the text in these dark blue banners.
There doesn't appear to be a way to edit that text at all.
All the rules are working fine as expected though.
Thanks
Continuous triggering
-
I don't know if this is according to design.
I have a very simple trigger for a rule with two conditions:- between sunrise and sunset
- When Lux is above a certain level, let's say 35 Lux for 60 seconds
Then the reaction is to turn of a light and it works fine. However it re-triggers again when the sensor changes values above 35 Lux which results in a new 60 second period. This results in many re-triggerings (is that a word?) when the light changes even above the threshold. I don't remember this behavior for Reactor in Vera.
-
OK. Can you open a PR on the bug tracker? I'll take a look...