Night and day difference for me. I think I was getting a lot of interference in my media closet. Devices were very slow to respond and sometimes not at all. Switched to UZB and used a USB extender to place it a good 5 ft from the location of my pi. Now things are fast and reliable.
-
Have a number of TKB plug switches (TZ68) that are not reporting to the controller. Believe they should be associated to Z-Way in Group 1 but am not able to get the devices to report groups in the interview/call for NIF process and so there are no associations possible. Thermosat is telling them to come on/off (hurrah!) but they don't report their on/off status in the gui.
In Associations tab: Can not configure associations: groups were not reported by the device. Do interview.
-
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!
-
-
MSR is a bit different then the Reactor.
Trigger :
A changes
Constraints :
A is true
Reaction:
Close window shadeHow do i " Else if A is false ! then Open shades
??In old reactor it was easy but cant get it with msr....
/Mattias
-
I made a video with a first look at Multi-System Reactor. In this video, I show the major components of the system, and run a demo automation where a light switch on HomeAssistant controls a light on my house Vera Plus.
This project is coming along nicely, but there is much documentation to write, and lots to "to-do" list items yet to be implemented, most on the critical path to working outside of my own hands, but a few still are.
Comments and feedback welcome.
YouTube: https://youtu.be/EcdPLnd2ybo
Rumble: https://rumble.com/vccph1-preview-of-multi-system-reactor-first-look.html
Chat with me on Discord: https://discord.gg/B3FDcBNR
-
After having optimized my video processing integration of 8 cameras into my openLuup based automation, I have been wondering what I could possibly improve on my setup. Instead of pestering @akbooer with petty localized console optimizations I am looking at these Apple Homepod minis as a potential improvement from my alexa based voice command system. openLuup is presently already bridged to both platforms using habridge and homekitbridge.
I am seeing two issues with Alexa:
Speed. The cloud processing of the voice commands takes ~1s (I don't use anything cloud to cloud) and I would really prefer it to be local. These devices can go a bit crazy when they lose DNS connections and sometimes do random things. Privacy because all the recordings go to the amazon cloud all the time.I have been exploring open source solutions for this but I would lose the benefit of optionally being able to go to the cloud for search information.
The downside of the homepods are that siri is not nearly as good in terms of helpfulness as alexa at this point. They also don't have a version with a screen which I found to be very useful at a couple of locations on the other hand, the sound quality of the homepod minis seem to be better than the echos...
What do you guys think?
This thread from longtime vera user @dJOS inspired me
Feb 4 Hubitat + HomeKit + HomeBridge + HomePod Mini = WOW Hubitat + HomeKit + HomeBridge + HomePod Mini = WOWHowdy all, I got a HomePod Mini very recently for my study (the audio quality is great and hand-off is magical) and to replace my iPad as the main HomeKit controller for my house (we use HomeKit mainly for Presence detection which is IMO best in class). We also have a dozen Amazon Echo's of...
-
Q: Is it fair/accurate to say that MSR cannot directly set the "LoadLevelLast" attribute of a Z-Wave light switch (paired with Vera)?
Reason I'm asking is that I routinely use Luup-based Reactor to set that value (e.g. to "60") whenever the switch is turned OFF, which causes future ON commands to automatically dim the light to that value (in this case, "60"). Kind of a built-in brightness limiter.
Granted, insofar as "LoadLevelLast" is intended as a read-only, derived value -- not meant to be set directly by Reactor in the first place -- I know this sounds like a trick question. And admittedly, the manner in which Reactor has done this for me in the past was by executing a snipped of Luup code containing a [variable_set] command. But it has worked (in most cases I've applied it to).
Is there any way to replicate this functionality -- however ill-advised in the grand scheme of things -- with MSR?
-
This morning I signed up for Starlink internet. This is the Musk project that has been aboard many of the SpaceX launches for some time. I watched this morning's launch (60 additional Starlink satellites), and they announced that the Beta was open in some areas. I went to the site, and it was open in my area.
The site (starlink.com) quoted $99/mo with $499 initial equipment and setup. I realize that's pretty pricey compared to Internet access in many areas, but I currently pay a fair amount more (monthly) to my current cable- (TV) based ISP, quality and speed are inconsistent, and every year I have to fight their customer retention staff to keep my pricing from nearly doubling as my "special offer" expires.
Verizon, the dominant cellular carrier where I live, has been slow to roll out home-based Internet on 5G. This is another alternative I've been excited to investigate, but still waiting.
I'm pretty excited. Yes, I'm a Musk fan-boy. Don't judge me. 🙂
-
Is the "Insert Entity Attribute Value" button (i.e. MSR's analog to "Expression Builder" in Reactor) in Expressions meant to be functional yet? I've noticed that clicking it has no effect, but chalked that up to this being a dev release. Just wanted to make sure, since it's not greyed out in the UI.
-
Hi
I've been having trouble again, with a Qubino DC Shutter module today. I actually deleted one and added a new one.
Now in MSR I have several instances of "Lounge Blind"
Device number 644 is the one that is on Vera.
77cbd356-145d-40c1-9d43-5f1724f33b86-image.png
If I search Vera for devices numbered - 638, 643 they don't exist on Vera.
Also there is one in MSR called "device_642" that device doesn't exist on Vera either.
Also the device named _Window Covering with ID 640 that doesn't exist on Vera now rither.
So when devices or scenes are added or removed on Vera how does MSR keep in sync is there something I have to do ?
Thanks
-
I've created a ticket for scene activation here.
In PLEG I have to use this service ID:
urn:micasaverde-com:serviceId:SceneController1
And monitor these properties:
sl_SceneActivated
LastSceneID
LastSceneTime -
A long while ago (May, 2015) I wrote my 2000-th post on another forum: openLuup - running unmodified plugins on any machine. Here’s the gist of it:
...I want to work in a more open and stable [Vera] environment...
...All would be solved if Luup was open source and could be run on the plethora of cheap and reliable hardware available today. But it’s not. But we could get something like that effect if we engineered a sufficient subset of Luup to run on such a platform. Could it be done? What would we need?
1. UI
2. scheduler
3. web server
4. Luup compatible API
5. Device and Implementation xml file reader
6. Zwave bridge to Vera
7. runs most plugins without modificationWhat we wouldn’t need is UPnP.
What have we (nearly) got already?
We have, courtesy of @amg0, the most excellent AltUI: Alternate UI to UI7, and that, I think, is probably the hardest one to do in the above list. Items 2 - 5, and 7, I’ve prototyped, in pure Lua, and posted elsewhere: DataYours on Raspberry Pi, running selected plugins unmodified, including: DataYours, EventWatcher, Netatmo, RBLuaTest, altUI. See screenshot attached.Is it worth the effort? Probably not. Will I pursue this quest? Yes.
openLuup was the result.
-
Is it possible to have an action for the Hass controller that would allow for defining a service call by inputting the desired service and service data parameters? This would provide an easy way to perform services for entities in Hass that are not mapped.
-
Have found these videos very informative as a zway novice ....
Z-Wave Network Diagnostics with Z-Way controller Z-Way webinar series: Z-Way Advanced Usage Z-Way webinar series: Introduction to Z-Way Home Automation -
I expect this document to be dynamic based on inputs from people who try but did not want to completely rewrite it here:
rafale77/Z-Way rafale77/Z-WayZway plugin for openLuup . Contribute to rafale77/Z-Way development by creating an account on GitHub.
-
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 == 14)Runs an action when I double click the Lounge Light wall switch.
Thanks
-
Patrick, Just confirming this is now working ok for me.👍
-
I have this block of lua and I am using luup.call_delay to delay the sending of IR codes. it works as intended but I am trying to eliminate the use of luup.sleep for the delay before the tcp:close() as well. i cant figure out how to implement luup.call_delay() for the tcp:close() and keep the luup.call_delay intact for the delay between the IR codes.
Thanks in advance.
function Delay1() --[[HDMI Matrix B1--]] local socket = require("socket") tcp = assert(socket.connect("192.168.255.204", 4998)) tcp:send("sendir,1:3,1,38000,1,69,341,171,22,21,22,21,22,21,22,21,22,21,22,21,22,21,22,21,22,64,22,64,22,64,22,64,22,64,22,64,22,64,22,64,22,21,22,21,22,64,22,21,22,64,22,21,22,21,22,21,22,64,22,64,22,21,22,64,22,21,22,64,22,64,22,64,22,1493,341,85,22,3669" .. "\r\n") luup.sleep(1050) tcp:close() end luup.call_delay("Delay1", 1) function Delay2() --[[HDMI Matrix B2--]] local socket = require("socket") tcp = assert(socket.connect("192.168.255.204", 4998)) tcp:send("sendir,1:3,1,38000,1,69,343,171,21,21,22,21,22,21,22,21,21,21,22,21,22,21,21,21,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,21,22,63,22,21,21,21,22,21,22,21,21,22,21,21,22,63,22,21,22,63,22,63,22,63,22,1528,342,85,22,1528" .. "\r\n") luup.sleep(1050) tcp:close() end luup.call_delay("Delay2", 5) -
@toggledbits I followed to the letter your excellent step-by-step guide on launching a Docker container from the image I fetched from PR #58 this morning.
All proceeded swimmingly – folder creation, image upload, settings & parameters, etc. – until the moment of actual Launch.
Whereupon, Docker threw up the following on-screen "Stopped Unexpectedly" warning (which repeated every 30 seconds or so until I Stop'ped the container from running/restarting):
docker_msr_stopped.pngConcurrently, every attempt to access http://<mySynNAS_IP>:8111/ resulted in a "This site can't be reached" error page in Chrome (under Windows, mind you).
Immediately, I took the liberty of inspecting and Export'ing the logfile (Container ► Details ► Log) as an HTML file, which I attach below (oops, no attachment feature in this forum, so here is the direct link) for your inspection.
Hope you find some clues, because I'm not at all sure where things went wrong. (The only facet of setup where I expressly deviated from your typed notes involved creating a "Shared" (i.e. top-level, rather than under /home) folder called "Reactor" with r/w access, under which I created a subfolder named "Data", to which I pointed /var/reactor during container creation.)
Excellent write-up and thanks for the chance to test this out!!
LibraFOLLOW-UP NOTES
I do see where Container ► Edit ► Environment ► variable PATH has a value of "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" which strikes me as odd, but maybe that's normal nomenclature? (By contract, Windows and DOS always use semicolons, not colons, to separate PATH variable entries.)RESOLVED
Noting that the Log displayed an error message related to /var/reactor/config, I went and created a folder named 'config' (all lowercase) under the NAS's top-level Reactor\Data folder, then restarted the container. It's running fine now, and I'm able to access the :8111 interface for the first time.
Log ► "Configuration path: /var/reactor/config resolved /var/reactor/config"SUGGEST
Please add explicit declaration in your How-To regarding the need for a /config underneath the data folder.
Best posts made by kfxo
-
Switched from RaZberry to UZB
-
RE: Moving to Docker
@akbooer
I have been messing with this today. I do not currently run openluup through docker so this may not even be the best way to do this but it is what I did to get it up and running and with the ability to easily see and manipulate all openluup files within "File Station" on the synology.I created three folders on my synology:
/docker/openLuup/cmh-ludl
/docker/openLuup/logs
/docker/openLuup/backupsThen I created three volumes with a bind to the created folders
'openluup-env' bound to '/volume1/docker/openLuup/cmh-ludl'
'openluup-logs' bound to '/volume1/docker/openLuup/logs'
'openluup-backups' bound to '/volume1/docker/openLuup/backup'I used portianer but you can ssh into your synology and use the command line to create these volumes with the binds, see this
Then I created the container using portainer making sure to set the correct ports and volume mappings, which can also be done in the command line with
docker run -d \ -v openluup-env:/etc/cmh-ludl/ \ -v openluup-logs:/etc/cmh-ludl/logs/ \ -v openluup-backups:/etc/cmh-ludl/backup/ \ -p 3480:3480 vwout/openluup:alpine
Hope this helps.
Edit: The binds are not necessary, I only did it to make it easy to access the files. Without the bindings, the volumes are somewhat hidden on synology that is not easily accessible for example at '/volume1/@docker/volumes/openluup-env/_data'
-
RE: Delete all device in Room 101
@akbooer said in Delete all device in Room 101:
Yes, absolutely (although I kind of wonder how you reached that figure...!)
The openLuup plugin has an action EmptyRoom101 with the parameter named AreYouSure which requires the value yes (to save nasty accidents.)
Thanks. I see it. They are all old verabridge devices ( and some z-way devices that I had to repair) that are no longer needed as I am fully cloned to z-way and mostly vera free
(still have two zigbee door sensors on vera).
-
Change Parameter of Z-wave device through Z-way API
Parameters of devices can be set through the api using this URL
YOURIP:8083/ZWaveAPI/Run/devices[DEVICE#].instances[0].Configuration.Set(PARAMETER,PARAMETER_VALUE,size=PARAMETER_SIZE)
Replace:
YOURIP with the IP of Z-way for example 192.168.1.2.
DEVICE# with the Z-way device # of the devices parameter you want to change
Parameter with the parameter # you want to change
VALUE with the Parameter value
PARAMETER_SIZE with the size of the parameter (should be 1, 2, or 4)An example to change device 51's parameter 3 to a value of 1 with a size of 1:
192.168.1.2:8083/ZWaveAPI/Run/devices[51].instances[0].Configuration.Set(3,1,size=1)
To run it in Luup code
local status, result = luup.inet.wget("192.168.1.2:8083/ZWaveAPI/Run/devices[51].instances[0].Configuration.Set(3,1,size=1)", 5)
-
RE: MSR in Alpine Docker
@toggledbits said in MSR in Alpine Docker:
OK. Let's see how this does in your hands. I've installed and uninstalled 3-4 times and it seems OK. In the bug tracker, go to #58, in the notes you'll find a download link and draft installation instructions. You can use the "monitor" function to follow that PR (emails you when things are posted--might get chatty with a lot of people in there, though). Please use that PR for reporting install-related issues.
This loads up nicely. Running unconfigured right now. I will transfer over my configs later and test it out.
-
RE: Multi-System Reactor Developer Preview AVAILABLE
Another good release. Confirming that 0000078 and 0000077 are tested and working on my system.
-
RE: Delete all device in Room 101
@rafale77 said in Delete all device in Room 101:
Congrats on the move! Please report back on positive or negative effects.
Will do. Still working through things and figuring stuff out. So far, the experience has been mostly positive with a few minor hiccups. I also have some scripts I wrote that I plan to share that helped ease my transition.
-
RE: MQTT – setup and use
Which synology NAS are you looking at? I have a DS920+ and run MQTT in a docker container. Works great and easy to set up. Some of the lower end ones may not support docker.
-
RE: Almost there!
Spinning up a dedicated VM on my synology right now in anticipation of the first preview. Can't wait!
-
RE: Imperihome - missing devices
@perh said in Imperihome - missing devices:
While i wait for a replacement app for my local UI devices, i want to use imperihome as long as I can.. But i'm missing a lot of devices!
All Z-Way bridge devices, all security/smoke and motion sensors (local RFXtrx child devices)..
Found the "include vera bridge" in imperihome.lua, what else could cause this?
I had the same issue. Check that the attribute "disabled" is not set to '1' for the missing devices. See this thread
Latest posts made by kfxo
-
RE: Feature Request: Hass service call action
@toggledbits said in Feature Request: Hass service call action:
Literally, yes, but I'm afraid if I do it, I'll never get things mapped that need to be mapped: if there's a workaround, everyone will use the workaround and never ask for a formal mapping; when the formal mapping is released, they won't change from the workaround.
The beauty would be you would not have to do mapping for many things, but I understand why you would rather have them formally mapped at this stage. Hass moves so fast with integrating (and they already have so many) things that I fear you will never be able to keep up.
At this stage, I'd prefer to run down the mappings that need to be done. It's part of the purpose of this phase of testing. What I would rather do is document how to do mappings and get others to do them and contribute them. Would you be willing to do that?
Yes. I would be willing to learn how to do the mappings and contribute.
-
Feature Request: Hass service call action
Is it possible to have an action for the Hass controller that would allow for defining a service call by inputting the desired service and service data parameters? This would provide an easy way to perform services for entities in Hass that are not mapped.
-
RE: Running Lua Code ? And watching device properties?
@toggledbits This looks great. So much easier then having to write out the http request.
-
RE: Running Lua Code ? And watching device properties?
@tarkus said in Running Lua Code ? And watching device properties?:
In preliminary testing the big issue I see with lua in Vera scenes is stability. I tried moving some of my lua into scenes and invoking the scenes thru MSR and everything just became real unstable with Luup restarts.
I think you already discovered the problem. Running the lua through scenes is probably not a good idea. Have you attempted what was suggested by @therealdb in this thread defining a library at startup and calling your lua through that? IMO this is the correct way to do it.
-
RE: Multi-System Reactor Developer Preview AVAILABLE
Another good release. Confirming that 0000078 and 0000077 are tested and working on my system.
-
RE: Timers in my log
That actually makes perfect sense and upon further inspection I see that the timers I was noticing in the logs are with respect to one rule that I had recently turned on that resets often.
-
RE: Timers in my log
Im seeing the same as @Matohl . Let me know if you want me to supply some logs too.
-
RE: Multi-System Reactor Developer Preview AVAILABLE
@librasun said in Multi-System Reactor Developer Preview AVAILABLE:
IN reading the MSR docs, I see we'll soon have the capability to import backup files saved from a Vera hub's master Reactor device, thereby auto-creating Rulesets on the receiving MSR.
I presume the necessary conversion applet (in the form of a .JS script) will be forthcoming as part of the /tools folder under MSR?
Has anyone tested this feature out yet? I wouldn't mind being a guinea pig, if more data points are required to iron out kinks.
Indeed that feature is already available. I imported close to 400 rules and it has been pretty smooth. We have ironed out a couple bugs already. But as pointed out in the guides, you really got to go through it all and fix some things as you go. My initial plan was to start fresh but I'm glad I didn't as it has saved me a lot of time. If you have a lot to transfer over I would definitely give it a shot.
-
RE: MSR in Alpine Docker
@kfxo said in MSR in Alpine Docker:
@toggledbits said in MSR in Alpine Docker:
OK. Let's see how this does in your hands. I've installed and uninstalled 3-4 times and it seems OK. In the bug tracker, go to #58, in the notes you'll find a download link and draft installation instructions. You can use the "monitor" function to follow that PR (emails you when things are posted--might get chatty with a lot of people in there, though). Please use that PR for reporting install-related issues.
This loads up nicely. Running unconfigured right now. I will transfer over my configs later and test it out.
Just an update, I copied over config and storage directories to the mounted docker volume and Reactor would not start until I also created a 'logs' directory in the mounted docker volume. All looked well after that but going to continue to run it on my Debian VM for now.
-
RE: MSR in Alpine Docker
@toggledbits said in MSR in Alpine Docker:
OK. Let's see how this does in your hands. I've installed and uninstalled 3-4 times and it seems OK. In the bug tracker, go to #58, in the notes you'll find a download link and draft installation instructions. You can use the "monitor" function to follow that PR (emails you when things are posted--might get chatty with a lot of people in there, though). Please use that PR for reporting install-related issues.
This loads up nicely. Running unconfigured right now. I will transfer over my configs later and test it out.