-
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!
-
-
-
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
-
-
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
Running Lua Code ? And watching device properties?
-
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.
Then this condition in PLEG:
(LoungeSceneActivated;LoungeLastSceneTime) and (LoungeLastSceneID == 15)
Runs an action when I double click the Lounge Light wall switch.
Thanks
-
I have a similar in scope system and I run dynamic code via RunLua action. So, I have a function on a lib imported at startup and I’m sending values this way. Another route is to use RunScene and write the code in your scene. So, plenty of choices.
-
Another example of something I am doing in PLEG and not sure if I can do this in MSR?
I have two side table lamps in my lounge.
I have a virtual device dimmer switch in Vera.
In PLEG I have a "Device Property" to monitor the current Dimming Level of the virtual device dimmer switch
My PLEG condition just references the device property "LoungeLampsMaster"
And in my PLEG action I added the two real lamp devices
And set their loadleveltarget to be whatever the virtual device "Master" dimmer is, by using this in the newLoadLevelTarget
{(LoungeLampsMaster)}
Can something like this be setup in MSR ?
-
@therealdb said in Running Lua Code ? And watching device properties?:
Another route is to use RunScene and write the code in your scene
That I understand
@therealdb said in Running Lua Code ? And watching device properties?:
I run dynamic code via RunLua action. So, I have a function on a lib imported at startup and I’m sending values this way
This I don't understand, you might as well be talking in Greek.
Where are these "RunScene" and "RunLua" actions ?
I only see these in the Set Reaction area.
-
You need to select 'Entity Action' in the first drop down and then from --choose device-- in the dropdown that appears, select the script you want to run from the 'Scripts' section.
-
Thanks Ian I can see that now its listing all my Vera scenes so that's easy enough to have your Reaction run a Vera scene and then in turn any Lua Code that scene may contain.
I'm interested to hear more about what TheRealDB mentioned regarding a RunLua action.
-
To RunLua you would need reactor on the vera. you could then call it from MSR
Also the {variable or luaxp} works in reactor and will be working in MSR in the near future
-
@elcid said in Running Lua Code ? And watching device properties?:
To RunLua you would need reactor on the vera. you could then call it from MSR
Yep that also make sense. Is that what TheRealDB was referring too ?
@elcid said in Running Lua Code ? And watching device properties?:
Also the {{variable or luaxp}} works in reactor
I don't know what this means.
-
{variable} - refers to expression variable.
you can set dynamic names in input fields and you can also use luaxpThis reactor page explains more https://www.toggledbits.com/static/reactor/docs/3.6/Expressions-%26-Variables/#luaxp-built-in-functions
This will probably be available in MSR to.
-
You can monitor the dimming level of a dimmer using an Entity Attribute condition and checking
dimming.level
for the dimmable entity. You can easily do a "master-slave" (or Submasters !) style of dimming mirroring in MSR.I'm still working on the scene controller device mapping. Please remember that this is a developer preview, first time this code has run outside of my hands, and is expected to be incomplete. It's not a finished product at this point and isn't intended to be. If you're using it with that eye, you may want to wait a couple of months.
You can run scenes from MSR on the Vera using an Entity Action. Each scene has a corresponding
script
entity in MSR, with ascript.run
action available.And of course, the XY-Problem aspect of this... if you tell us what you think you need to run in Lua, there's a chance there may actually be a way to do it without Lua, or its something reasonable to consider as a regular feature addition to MSR, Vera Reactor, or both.
-
@cw-kid you can run lua code via http call. Just compose a call like this
Ie, if you have a function named doSomething in your startup code, accepting two values, just call this endpoint
I’m using it to concatenate multiple actions in one http call, while still maintaining flexibility.
-
Thanks guys for the information.
Yes I admit I need to keep remembering things might not be implemented yet.
But as I have never used Reactor plugin for Vera, I have nothing to compare MSR against other than PLEG.
I don't know what is currently possible in the Reactor plugin for Vera etc which isn't helping me when looking at MSR.
I am moving my more simple PLEG actions over to MSR now and have already disabled several PLEG conditions on the Vera box.
Schedules in MSR I am still testing and struggling with a bit, so I only have two moved over to MSR currently and one isn't running at all and one ran this morning but later than I expected it to do so.
I have some pretty long LUA scrips in PLEG for some stuff, I don't think I could do it easily without using LUA code.
Are there any examples of a Master Slave dimmer setup which I can follow ?
Cheers.
-
@therealdb said in Running Lua Code ? And watching device properties?:
you can run lua code via http call
OK that's a clever idea.
So the LUA code is stored where? In a function in the Vera startup right. And then you are just calling it to run via a HTTP request from MSR.
-
-
This is how it will go:
That said, this won't work today, because I haven't yet connected the expressions to the action parameters (the
{master_level}
value in the dimming action won't work yet). That's coming, but not yet. You can, however, do exactly this in Vera Reactor to see how it works. It will work the same way in MSR.Edit... let me explain how it works (on both Vera Reactor and MSR):
The expression keeps the current value of the master dimmer. So on my system,
vera>device_105
is named "Virtual Dimmer 18". The trigger condition looks for any change in the dimming level of that dimmer. When it changes, the set reaction sets the current value (from the expressionmaster_level
) on the slave dimmer "Virtual Dimmer 20". Bob's your uncle. -
@toggledbits What you just explained makes perfect sense.
However I would not have had a clue how to correctly construct that expression with the correct syntax.
I think I have mine setup correctly now.
I understand it wont actually work yet though.
-
@cw-kid said in Running Lua Code ? And watching device properties?:
However I would not have had a clue how to correctly construct that expression with the correct syntax.
Right, so I think this is a big issue in your case. My intent with this developer preview was to have experienced Reactor users help me test MSR. You're in the tough spot of coming from PLEG, with no prior Reactor experience, so not only do you not know the current product, but you also don't know if what you're looking at in the new product is right or wrong, same or different. That makes it palpably frustrating for you, and frankly for me as well, because you are not at the level I set for this test. I suspect you're also a bit irritated at having to do this at all, since Richard seems to have abandoned his product years ago (as evidenced by his near-total absence in the forums, the maturity of his product notwithstanding), and the prospect that no PLEG for eZLO seems to be in the works that I've heard.
None of that matters, at least to me, and I appreciate the effort you're putting in, and you're finding bugs and helping, so all is cool in my book, but for the fact that I feel like you're sometimes losing your perspective and treating this as if it's finished and shipped. This is a developer preview, and again, it's known to be incomplete, and its intended audience was existing Reactor users. Those users would know how to build the expression. If you're going to continue to participate, and I hope that you do, please keep this in mind. Making contact with the product this early, you are not only positioning yourself to be a master of it in future, but you're in a position to shape its future, and you have my attention.
You might take a read of the docs for Vera Reactor, to get a better lay of the land, including expressions. Things are different between the two systems, for sure, but the strong flavor is nonetheless there. You can also experiment with Vera Reactor on your Vera directly, and this may actually be very useful in helping identify other differences or gaps that should be at least documented if not closed. Either way, as the more mature product and very stable, it should help remove some of the questions and the trips in your learning curve caused by my errors in the new product. That said, I think I've shown that I will work as quickly as possible to get things shored up so that you can be productive on MSR.
Vera Reactor Docs: https://www.toggledbits.com/static/reactor/docs/
-
@cw-kid yes, but if you define a library and register it at startup, you could do that too. I’m currently using this approach, and I like it because it’s inside a file and not a textbox.
-
All fair comments and observations Patrick. I certainly don't want to cause frustration to anyone.
In PLEG there was no need to of even written an expression just to monitor the value of a devices Dimming level for example. I'd just create a device property.
PLEG device properties are similar to how you build triggers in MSR, in the respect that you just select things from drop down lists. So monitoring a devices Dimming level in PLEG is trivial to setup.
Conditions in PLEG are not so trivial however and are more like writing expressions.
If MSR could build device properties or watch variables as PLEG does I think you'd be making it super easy for any user to pick up and run with MSR.
-
In vera reactor to watch a device state you just set a variable and there is a button to pick what you want to get/watch, this creates the expression for you. The button exists in MSR, but as Patrick says expressions are not fully implemented yet. When it is you will see how simple it is. Install Vera reactor just to have a play.