-
Hi,
Am I correct in assuming that MSR cannot be installed on a pi running HASS.OS?
Thanks.
-
Hello,
Trying to convert my Reactor scripts to MSR. Couldn't get the import to work so gave up on that. Anyway, curious on how to work with the following example.Have a motion sensor on my back porch. Very simple logic:
7fbcd69e-9f85-4b7f-8138-1267d4e4ba1a-image.png The Reactor activities are as follows:
34e715fd-c2f1-4b92-99ea-e2838fc5d3dc-image.png.In MSR, how do you tie activities to sub conditions like I have with the last action in activities.
In this case I was to trigger BlueIris to trigger regardless of the time of day, but only want the light to come on at night. Do I need multiple Rule Sets?Thanks,
Roger -
Seeing this error in MSR logs:
2021-07-29T02:01:27.663Z HassController:NOTICE HassController#hass attempting reconnection to ws://192.168.0.15:8123/api/websocket
2021-07-29T02:01:27.664Z HassController:NOTICE HassController#hass connecting via WS to ws://192.168.0.15:8123/api/websocket
2021-07-29T02:01:27.665Z HassController:WARN HassController#hass websocket error during open/negotation: Error: connect ECONNREFUSED 192.168.0.15:8123
2021-07-29T02:01:27.666Z HassController:NOTICE HassController#hass websocket to ws://192.168.0.15:8123/api/websocket closed during open/negotiation
2021-07-29T02:01:27.666Z HassController:WARN HassController#hass failed to connect/initialize communication: Error: connect ECONNREFUSED 192.168.0.15:8123On latest version of MSR. Also just installed HASS so it is latest as well.
Configure a default setup of Home Assistant (frontend, api, etc)
config.yaml in HASS looks like this:default_config:
Text to speechtts:
platform: google_translatehttp:
server_host: 0.0.0.0websocket_api:
sensor:
platform: websocket_apigroup: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yamlUsing new LTAT. Have tried several new ones.
Any ideas on what is wrong?
-
Well, it's July 19th, and as previously advertised, Reactor (Multi-System, aka MSR) has been published at release 1.0.0.
Docker images are on DockerHub, and download package for bare-metal installs is available at https://reactor.toggledbits.com/download/
Those of you with access to the Mantis Bug Tracker for the project, please continue to use it, particularly if you stick with the "latest" docker image tag (which will continue to be updated periodically, as will the bare-metal tarball). Feel free to open issues there on behalf of other users who do not have accounts if it seems appropriate.
-
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 -
I am running MSR 1.0.0-21200-16a604f and am seeing the message:
HomeAssistant on "hass" may be an unsupported version. The reported version (2021.7.3) has not been certified/tested with this version of Reactor and may cause errors. You must either modify your HomeAssistant install, or see if an update to Reactor has been made available.
-
Hi
I just tried to add a connection for my Ezlo Atom, its added the Atom system in to the MSR Entities, but it has a "false" state and hasn't found my devices that are paired to the Atom.
ff7f286a-e987-4b2b-a56e-0b7a067aff6e-image.png
Also note that on the Atom controller there is no settings for:
offlineAnonymousAccess: true or false
offlineInsecureAccess: true or false
So this line in the reactor.yaml file won't work for Atom's.
set_anonymous_access: trueThis was what I added to my reactor.yaml file.
- id: ezlo-atom enabled: true implementation: EzloController name: Ezlo Atom config: source: "wss://192.168.0.101:17000" # change the IP address serial: "70060304" # put your hub's serial here username: "myusername" # put your username here between quotes password: "mypassword" # and password # set_anonymous_access: trueThanks
-
I am seeing errors like these in the log file:
<VeraController:NOTICE> Controller VeraController#vera-edge is now online. 2021-07-22T15:41:29.586Z <default:ERR> [Entity:setPrimaryAttribute] Attempt to set primary to power_switch.state invalid, not in { "x_vera_device": { "device_number": 139, "device_type": "urn:schemas-upnp-org:device:RGBController:1", "parent_device": 0, "failed": false, "configured": --null--, "mapped_class": "rgbcontroller_plugin", "mapped_by": "*;device_type=urn:schemas-upnp-org:device:RGBController:1" }, "x_vera_svc_upnp_org_RGBController1": { }, "x_vera_svc_upnp_org_SwitchPower1": { }, "x_vera_svc_micasaverde_com_HaDevice1": { }, "x_vera_rgbcontroller_plugin": { "device_type": "FGRGBWM-441", "configured": true, "color": "#0000000000", "message": "" } } 2021-07-22T15:41:29.587Z <VeraController:ERR> VeraController#vera exception/error while updating VeraController#vera 2021-07-22T15:41:29.588Z <VeraController:CRIT> Error: Entity#vera>device_139:setPrimaryAttribute() can't set power_switch.state, not defined for entity Error: Entity#vera>device_139:setPrimaryAttribute() can't set power_switch.state, not defined for entityand
<default:ERR> [Entity:setPrimaryAttribute] Attempt to set primary to power_switch.state invalid, not in { "x_vera_device": { "device_number": 75, "device_type": "urn:schemas-micasaverde-com:device:WindowCovering:1", "parent_device": 1, "failed": false, "configured": false, "mapped_class": "fibaro_cover_scenecontrol", "mapped_by": "*;device_type=urn:schemas-micasaverde-com:device:WindowCovering:1;pnp=/^(3222)$/" }, "x_vera_svc_upnp_org_SwitchPower1": { }, "x_vera_svc_upnp_org_Dimming1": { }, "x_vera_svc_upnp_org_WindowCovering1": { }, "x_vera_svc_micasaverde_com_Protection1": { }, "x_vera_svc_micasaverde_com_EnergyMetering1": { }, "x_vera_svc_micasaverde_com_HaDevice1": { }, "x_vera_svc_micasaverde_com_ZWaveDevice1": { }, "x_vera_svc_micasaverde_com_ZWaveNetwork1": { }, "x_vera_svc_micasaverde_com_GenericSensor1": { }, "x_vera_svc_micasaverde_com_Color1": { }, "x_vera_svc_micasaverde_com_SceneController1": { }, "cover": { "state": false }, "position": { "value": 0 }, "zwave_scene_controller": { "scene_activated": "0", "key_attribute": --null--, "scene_deactivated": --null--, "central_scene": --null-- }, "x_vera_scene_controller": { "last_scene_id": "26", "last_scene_time": "1626714753" } } 2021-07-22T15:41:28.925Z <VeraController:ERR> VeraController#vera exception/error while updating VeraController#vera 2021-07-22T15:41:28.926Z <VeraController:CRIT> Error: Entity#vera>device_75:setPrimaryAttribute() can't set power_switch.state, not defined for entity Error: Entity#vera>device_75:setPrimaryAttribute() can't set power_switch.state, not defined for entityWhat does it mean?
One is an RGBW Plugin device the other is a real Z-Wave device, a Fibaro Roller Shutter 2.
Thanks
-
Having gotten the Ezlo controller to connect I see these device items
x_ezlo_item.learn_ir_code=0
x_ezlo_item.learn_rf_code=0
x_ezlo_item.send_ir_code=""
x_ezlo_item.send_rf_code=""But they are not listed in the capabilities. It would be nice if to send Ir and Rf codes direct from MSR.
If possible couild you add this feature.
-
In Entities area, I selected the Ezlo controller. However when using the Capabilities drop down list, I can also see capabilities from the Vera firmware hubs as well, is that expected behaviour?
Thanks
-
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!
-
Hello,
Looking for a "how to" for this. That section is TBD in the documentation.
Thanks,
Roger -
Moving my washer and dryer monitor from Reactor to MSR. I have a virtual switch to turn off notification that has worked well under Reactor. Recreating it in MSR and I cannot get the rule to save the restriction that the switch must occur prior to the wattage monitor triggering. When ever I save the rule, the restriction reverts to the default state of blank.
Currently on 21168 running on docker.
Let me know of any additional info you need.
-
I've read the thread and the docs, thought I'd setup everything correctly, but MSR doesn't connect to my Ezlo controller.
The docs don't say what to do if you have already previously enabled anonymous access via their Online API Tool.
“offlineAnonymousAccess” and “offlineInsecureAccess” are set to true on my controller already.
In my Reactor.yaml file I decided to try it first with the username and password entries commented out and also the "set_anonymous_access: true" commented out.
I see these errors in the log file:
2021-07-16T08:53:56.225Z <app:NOTICE> Starting Structure... 2021-07-16T08:53:56.235Z <Structure:INFO> Structure#1 starting controller interface vera (VeraController) 2021-07-16T08:53:56.245Z <Structure:INFO> Structure#1 starting controller interface vera-edge (VeraController) 2021-07-16T08:53:56.248Z <Structure:INFO> Structure#1 starting controller interface ezlo (EzloController) 2021-07-16T08:53:56.250Z <Structure:INFO> Structure#1 starting controller interface weather (OWMWeatherController) 2021-07-16T08:53:56.252Z <Structure:INFO> Structure#1 starting controller interface reactor_system (SystemController) 2021-07-16T08:53:56.379Z <default:null> Module VeraController v21195 2021-07-16T08:53:56.402Z <default:null> Module OWMWeatherController v21140 2021-07-16T08:53:56.407Z <default:null> Module SystemController v21102 2021-07-16T08:53:56.419Z <VeraController:NOTICE> VeraController#vera starting 2021-07-16T08:53:56.582Z <VeraController:INFO> VeraController#vera loaded mapping ver 21177 rev 1 format 1 notice 2021-07-16T08:53:56.623Z <VeraController:NOTICE> VeraController#vera-edge starting 2021-07-16T08:53:56.629Z <Controller:CRIT> Controller: failed to load ezlo implementation file:///home/username/reactor/server/lib/EzloController.js: Error: Cannot find module 'uuid' Require stack: - /home/username/reactor/server/lib/EzloController.js 2021-07-16T08:53:56.632Z <Controller:CRIT> Error: Cannot find module 'uuid' Require stack: - /home/username/reactor/server/lib/EzloController.js Error: Cannot find module 'uuid' Require stack: - /home/username/reactor/server/lib/EzloController.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js:885:15) at Function.Module._load (internal/modules/cjs/loader.js:730:27) at Module.require (internal/modules/cjs/loader.js:957:19) at require (internal/modules/cjs/helpers.js:88:18) at Object.<anonymous> (/home/username/reactor/server/lib/EzloController.js:478:84) at Module._compile (internal/modules/cjs/loader.js:1068:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1097:10) at Module.load (internal/modules/cjs/loader.js:933:32) at Function.Module._load (internal/modules/cjs/loader.js:774:14) at ModuleWrap.<anonymous> (internal/modules/esm/translators.js:199:29) 2021-07-16T08:53:56.692Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. 2021-07-16T08:53:56.828Z <Structure:ERR> [Structure:start] failed to start controller ezlo: Error: Cannot find module 'uuid' Require stack: - /home/username/reactor/server/lib/EzloController.js 2021-07-16T08:53:56.829Z <Structure:CRIT> Error: Cannot find module 'uuid' Require stack: - /home/username/reactor/server/lib/EzloController.js Error: Cannot find module 'uuid' Require stack: - /home/username/reactor/server/lib/EzloController.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js:885:15) at Function.Module._load (internal/modules/cjs/loader.js:730:27) at Module.require (internal/modules/cjs/loader.js:957:19) at require (internal/modules/cjs/helpers.js:88:18) at Object.<anonymous> (/home/username/reactor/server/lib/EzloController.js:478:84) at Module._compile (internal/modules/cjs/loader.js:1068:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1097:10) at Module.load (internal/modules/cjs/loader.js:933:32) at Function.Module._load (internal/modules/cjs/loader.js:774:14) at ModuleWrap.<anonymous> (internal/modules/esm/translators.js:199:29) 2021-07-16T08:53:56.831Z <Controller:CRIT> Controller: failed to start controller reactor_system (file:///home/username/reactor/server/lib/SystemController.js): TypeError: Can't set NaN on attribute suninfo.astronomical_dawn (reactor_system>sun) 2021-07-16T08:53:56.832Z <Controller:CRIT> TypeError: Can't set NaN on attribute suninfo.astronomical_dawn (reactor_system>sun) TypeError: Can't set NaN on attribute suninfo.astronomical_dawn (reactor_system>sun) at Entity.setAttribute (/home/username/reactor/server/lib/Entity.js:308:19) at SystemController.run (/home/username/reactor/server/lib/SystemController.js:224:643) at /home/username/reactor/server/lib/SystemController.js:172:35 at new Promise (<anonymous>) at SystemController.start (/home/username/reactor/server/lib/SystemController.js:170:76) at /home/username/reactor/server/lib/Controller.js:273:89 2021-07-16T08:53:56.833Z <Structure:ERR> [Structure:start] failed to start controller reactor_system: TypeError: Can't set NaN on attribute suninfo.astronomical_dawn (reactor_system>sun) 2021-07-16T08:53:56.833Z <Structure:CRIT> TypeError: Can't set NaN on attribute suninfo.astronomical_dawn (reactor_system>sun) TypeError: Can't set NaN on attribute suninfo.astronomical_dawn (reactor_system>sun) at Entity.setAttribute (/home/username/reactor/server/lib/Entity.js:308:19) at SystemController.run (/home/username/reactor/server/lib/SystemController.js:224:643) at /home/username/reactor/server/lib/SystemController.js:172:35 at new Promise (<anonymous>) at SystemController.start (/home/username/reactor/server/lib/SystemController.js:170:76) at /home/username/reactor/server/lib/Controller.js:273:89 2021-07-16T08:53:56.835Z <app:INFO> Structure running; pausing for controllers' initial ready -
Everyone, I've had a change in thinking.
As many of you know, I had decided to not build an MSR interface for eZLO's new controllers, for multiple reasons, not the least of which was that I had chosen not to use an eZLO hub in my future HA. I am currently straddling three hubs: Vera, Home Assistant, and Hubitat. I am actually very much enjoying the flexibility this has provided. But these three hubs are enough for the moment, and when the venerable Vera Plus on which my house has operated since 2017 dies, I will likely just move the rest of my ZWave devices to the other hubs and reduce by one.
Another reason for my previous decision was the risk of fluidity/instability in the eZLO APIs. Since this is first generation work, and even now as they approach the three-year mark on development and are still in "beta" with much functionality still incomplete or missing altogether (plugin UI framework?... anyone? anyone?), it stands to reason that, like all projects in this phase in particular, choices are made that need to be revisited. To be fair, Hass and Hubitat are not immune from this either, even as much more mature products with greater market penetration. In any case, I've demurred because of the high perceived risk of change and breakage, and didn't want to put myself (again) on the critical path of my own user base waiting for me to catch up. I accept now, however, that events like this are just part and parcel of the environment in which I've chosen to work. As I said, if it's not eZLO changing something, it's going to be Hass, or something else. I haven't had a breaking change hit from the Hubitat side yet, but it's probably just a matter of time. Just as I seek to improve my work, they must seek to improve theirs.
The upshot is that I've decided to write an eZLO interface, and I've been working on that for a few days and now have a working prototype running. It works with the few devices I have available for it, and there's a lot that's assumed and untested about all the others. Think back to March, when MSR was first released -- the process of going through and stabilizing these interfaces under all the different external conditions, with devices in your environments that I don't, and sometimes cannot, have -- it takes time. Drilling out all of the details of device behaviors and data, and how each hub handles them differently, takes time. But it's going to be a reality. Aside from this, reading the other forums makes me realize just how much this is needed, if only because there appears as yet to be no articulated concrete plan (e.g. words beyond a promise with no date) to support easy migration from a Vera to an eZLO. MSR touts itself as a tool to assist such migrations between hubs. An eZLO interface must exist.
To set expectations: you'll see the first version of this interface in a build in the next couple of weeks. It will be an add-in. Like MSR itself, I will be limiting the initial audience, and those of you that participate in the early use and testing will be asked to provide lots of diagnostics and feedback (so please don't ask/participate if you're not willing and able to put in the time). It's brand new, unfinished work; there will be lots of bugs, and lots of holes, and it's going to take a lot to get them all squashed and filled, respectively.
Based on what I've learned so far from this project, I also want to forewarn you that it may include access to my cloud infrastructure for automatic logging (to make our mutual efforts to examine problems easier and faster), at least during the early stages. At the moment, MSR has no hard Internet-access dependencies, so this is a change for this interface work.
Also, I probably will ultimately be charging a modest monthly or annual subscription for the eZLO interface, which is a change from policy and practice to date. The amount of effort the project has demanded and can demand in future makes it necessary that I consider a business model. I know that gives some pause, but it should also give you confidence that I am thinking of a long-term future. But, those of you who, as of this writing, hold active accounts on the MSR bug tracker and have participated so valuably in the testing and improvement of MSR, are grand-fathered in to a perpetual (personal/non-commercial use) license to MSR and this interface (no fees, at least for what parts are produced by my hand; I cannot control what others may choose to do if/when third party development takes root). I am considering extending that benefit to everyone who has donated to my projects from the start to date; that is, including those who supported Reactor for Vera, without which MSR would never had been born.
I can probably predict from these forums and others who the active eZLO users are going to be, but if you want to work with me on it, please let me know by reply here. I will be relying on you heavily, because I am not going to be a big consumer of the hub, so a lot of the work will require data collected from you and your hub and investigative work on that evidence, rather than first-hand experience and witnessed events in my own environment. But I'm confident it will work, as much gets done this way already, and investing in more and deeper troubleshooting tools is always a good investment.
Thanks to all of you who have supported this project. Onward...
-
Seems simple enough: same landscape lights for Independence Day, Memorial Day, and Labor Day.
Complication: one is a static date each year, the others are "last Monday of" and "first Monday of" respectively.
Here's what I have:
80869959-4370-489a-bf61-2810fb7da1b9-image.pngHow far off am I?
-
I'd like to trigger off of the entry of someone's lock code into my Schlage CONNECT lock. I've stared at my options in the Entities and the closest I can come is the stored x_hubitat_extra_attributes.lastCodeName="Nik".
It just doesn't feel quite 100% like what I'm looking for - but nothing else comes even close.
-
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!
-
@toggledbits said in Build 21117:
I just added a GET for this as well just for simplicity/basic use only, to be in next build:
http://msr-ip:8111/api/v1/variable/testme/set?value=123I updated and tried this:
http://192.168.0.100:8111/api/v1/variable/run/set?value=123"run" is the name of my Global Expression.
In the web browser I get this response:
Cannot GET /api/v1/variable/run/setI can't see anything related in the reactor log file.
-
Hi!
Is it possible to play mediafiles (mp3) with a Sonos speaker from the media folder within Home Assistant, with a MSR reaction? For example no one is home and a potential thief is sneaking around in my backyard - then I would want to play a certain mp3 file (a barking dog or something else). Is it possible? I have done this before, in Veras reactor, when I had the mp3 file in the "cmh-ludl" folder. But because I want to keep the Vera as unloaded and free as possible, I would like to use HA instead. Thanks in advance!
/Fanan
Is this correct? Text shown in the blue banners on the rule summaries
-
Hi
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
-
Seems to be related to copying an existing rule from one group to another or even within the same group.
Also when I copied this rule from one group to another the "Set Reaction" action was fired and ran as it turned on my "Globe lamp".
-
That's a bug; that view is still a work in progress. As I mentioned in the other thread, the constraints are missing from this display, as are any expressions local to each rule. Much work yet to be done, but this kind of thing usually mops up quickly. I wanted to get at least this much out so one could see what was going on. In any case, it should show nothing there for the "root" (highest-level) group.
-
And the "Set reaction" action actually running when copying a rule ?
Would you like me to create a ticket on the tracker for this ?
Thanks
-
@cw-kid said in Is this correct? Text shown in the blue banners on the rule summaries:
And the "Set reaction" action actually running when copying a rule ?
That's new information. What's that?
-
Then I copied that "Globe Lamp On or Off" rule from my group called "Moodlights" to the group called "Security" the action in the "Set Reaction" was fired and ran because my Globe lamp actually turned on.
-
You can open a bug, but it needs to have reproducible steps, please.
-
OK its happened twice now when copying that particular rule and the Globe lamp is turned on for real.
-
Just to be clear, if you copy a rule to new rule, the new rule has no states, so if that rule is enabled, it will evaluated and it will run. So that may actually be normal and expected. The states of the original rule are not copied with the rule.
-
OK I've created a ticket you can decide.
Thanks
-
I can't comment on the ticket now its closed.
Yes having the new copied rule disabled initially will work, you generally then want to edit and tweak that copied rule anyway and then you can enable it.
This will stop the copied rule just firing when you don't want it to do so.
Thanks.