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!

So, after more than 10 years and 4 Vera's, my vera forum account is suspended.

I think the monkey of the company, called melih is not man enough te have any critic. In the topic about the "great to come app" I responded to the topic (not off topic!) that a subscription can also be seen (financially) as buying a box, run it for 2 years and come to market with a better one (in better wordings).
That means that if you as a company hast a box of 50USD cost, sell it at 250USD would give him a monthly subscription of 200/24=8.33 USD... Users that would last 5 years would pay a monthly of 3.33USD.

But... the monkey on the rock has bolded his fists and said: ban him! He just can't take any criticism.

To be honest! I am not even sad! It was a very rough journey with Vera. The journey stopped when Ezlo and the monkey took over the name.

After that it quickly went downhill...

Goodluck all! (except the monkey).

Edit:
The topic:

Aug 16, 2020 MiOS Application - early Beta enrollment MiOS Application - early Beta enrollment

are you serious? would I become a cost? that is, customers who periodically replace the control unit and are happy with the service praise the Vera system and therefore also free advertising but, the new “company” decides to charge less to bind the customer with a subscription … But the genius...

The post:
The point you are missing is:

If the hardware would “cost” around 50USD, and you sold it for 250USD, an average life span of 5 years would mean 200/(5×12)=3.33USD per month. Thats how Vera used to do it.

Then release a faster/better “beast” every 2 years gives you 200/(2×12)=8.33USD per month. That’s how vera used to do it.

And that’s how I did it for around 8 years and 4 veras with them untill you bought the company.

This is just a matter of how you look at it and explain it.

I dont frikking care how you do the maths, I only liked a working product and a close user community (like it was).

Now all I see on this forum is a lot of “we are going to” and “we are working on”, “keep them coming guys”. But the reason for ever considering to buy a new vera every 2 years is gone…

No clear migration path, no clear compatibility path and no clear integration path…

That’s why I started to look for alternatives…

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.

Go ahead and open a PR for it, and we'll use that to track it.

@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

"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 end

I 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 metric

units: 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: 0

controllers:

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

Some of you may know that I took at shot at building an alternate geofencing solution for Vera. The core of it was system agnostic, using the OwnTracks application and AWS lambdas to track devices and keep a central data, then disseminate that to the Vera via a websocket-based plugin. It worked with other apps as well, including Tasker and GPSLogger, but of the dozen people that were testing it, most used OwnTracks.

A lot was learned in the process, not the least of which is that the success of any such solution is highly dependent on the phone and its settings. Phone manufacturers love to set things up for the longest battery life, of course, but that's usually very anti-geofencing behavior. In the case of at least one brand, it was unusable and the settings could not be modified. It was also cost-prohibitive to maintain on Amazon, as AWS grabs a dime here and a dollar there and before you know it, it added $100/month to my AWS bill, which my wife deducted from my Scotch budget. Unacceptable.

But it's quite reasonable to use OwnTracks to a local endpoint, and I could pretty easily replicate the functionality as a local application, or maybe even as an additional endpoint built into MSR's API (still separate port and process, but in the package).

So the question really is... would you do it, or would you be too concerned about the security risks associated (e.g., dynamic DNS and NAT mapping in the firewall necessary for the phone to contact the service when not on LAN)?

Installed Sitesensor yesterday. Defined a http request towards yr.no for the weather.
Default it only sends requests when the device is armed. When I armed the sensor both of my sirens started bleeping. Not funny with at night with two kids asleep.

Simultaneous with arming the device, the first http request probably is send and my first http request did not have the Useragent http header so the result was a 403; this probably made the sitesensor device being triggered.

I unchecked the box "only send requests when armed" and disarmed the sitesensor. This works ok but only one slight mistake with thick fingers and I have armed it again.

I see the sitesensor device is being configured as a SecuritySensor (as it implements the securitysensor serivce?). This makes that sirens react when the sitesensor trips. I have a leakage sensor as well and I know this one triggers the sirens as well. Do not have any doorsensors right now but hope these will not trigger sirens as well.

Is there a way to tell Sirens to ignore Sitesensor and/or other specific devices. Or should sitesensor not be configured as a security device?
Is there an easy solution?

Grtz Swiddy

Some details:
-Vera Secure box with built in siren (siren is a separate device)
-POPP Smokedetector with siren
-Upto-date with Vera firmware and Not on Openluup yet but don't think this would make a difference here

So cool to find the forum of all the banned vera gurus!

I've had a Vera Plus for about 6 years now, and have had a fairly problem free time with it compared to many other stories. The last years have however been lacking in progression in many fields i'd like to explore, so now i'm looking closely at Openluup.
Other systems have been tested as well, but i find that the community and plugins made for vera is kind of special, and something i'd like to contribute to as well. (getting older and not wanting to change to new stuff probably plays a part too!)

So, my stab at opeluup starts with an HP Chromebox 1 i got for free. Its a fairly powerfull thing, but as google wants to sell new ones, its now EOL.
I wiped it clean and installed debian, as it seems to be the closest thing to raspberry which many use for openluup.

Openluup installed fine, and i got the vera bridge working fairly well by bothering ppl at the vera forum with questions. Its now running OK, but there seems to be an issue with Icons?

f0e29622-0397-4b84-819c-f1b632daab41-image.png

Also at the devices tab:
2892faff-a3ee-4f21-9db8-2a03f604fc74-image.png

I did the "GetFiles", and I see the /icons/ is populated, but no icons. In the luup log says that its trying to GET the icon, but returns no packages.

2020-09-15 17:04:30.818 openLuup.server:: GET /cmh/skins/default/img/devices/device_states/dimmable_light_off.png HTTP/1.1 tcp{client}: 0x55eca8d90cb8 2020-09-15 17:04:30.819 openLuup.server:: request completed (0 bytes, 0 chunks, 0 ms) tcp{client}: 0x55eca8d90cb8

I do have a UZB stick on the way, but before i go down that road i'd like to be sure that the installation is stable and sound.. Do I have all the nessecary packages/background processes? I did install cjson which helped on some things..

Also fairly new at linux in general, so bear with me. 😉

Roadmap:

Get the openluup/AltUI running smoothly
Transfer Z-wave devices
Transfer 433 devices (RFXtrx plugin)
Transfer Zigbee devices (Vera or mabye ezlo plus? zigbee stick?)

more questions will follow!

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

Screen Shot 2021-02-23 at 07.14.43.png

@akbooer , I just noticed these last 3 watches which have a serviceID appended behind them in the console. It is only the last 3 and I can't figure out why. Any idea?