-
I just gave up waiting for the HASS Z-wave.me integration to finish, and set up Zwave JS UI instead. In the same operation, all zigbee and 433 devices was moved from openluup to HASS as well, so all devices now have a new address.
I thought I saw some "replace device" function in MSR earlier, but now I didnt find it?
I've done a lot of the changes manually now, and removed openluup as a system, but at every restart I still get the warning/errors about the old units. I assume it's because rules ask for them? This is where that "replace this with this" would come in handy..
Right now, my problem is that the rules i did update doesn't pull any levers in HASS. If I go in and run the action line in the rule manually, it works, but only with the arrow button on the actual action, not the common arrow button in "set reaction".
Any tips/hints on making this transition easier is much appreciated. 🙂
-
Reposting here because core people seem to be here daily.
Hello Everyone,
I am using iPhone locator on Vera, and yesterday it stopped working. Looking at the logs, I can see the connection is refused, but nothing on my end changed. iPhone locator is really important in my particular setup, so I guess I have two questions.
Is it broken, or is it me?
I don't see anyone else saying there is an issue, but I am not sure how many people are still using it (or Vera for location) at this point. I installed it on a blank Vera test controller, same issue. It might be something with the iCloud account, but it works everywhere else.Is there something similar on another platform?
Mainly what I would like is the ability to force a poll of iCloud location on demand. I have a bunch of triggers setup, including magnetic sensors in my driveway to sense vehicles and determine if the motion is egress or ingress. These triggers in conjunction with MSR have been a great way to double check phone location, and I would hate to lose this functionality. It looks like HA might have something with "iCloud3". Is anyone using it?
Thanks,
Mike -
Hello,
Have a couple of areas defined by Long and Lat. In Entities I can see the values updating.Amy S9
hass>sensor_amy_s9_geocoded_location
"14320 NE 20th St, Bellevue, WA 98007, USA"
11:30:46 AMstring_sensor.value="14320 NE 20th St, Bellevue, WA 98007, USA"
value_sensor.units=null
value_sensor.value=14320
x_hass.domain="sensor"
x_hass.entity_id="sensor.amy_s9_geocoded_location"
x_hass.services=["sensor"]
x_hass.state="14320 NE 20th St, Bellevue, WA 98007, USA"
x_hass_attr.administrative_area="Washington"
x_hass_attr.country="United States"
x_hass_attr.friendly_name="Amy S9"
x_hass_attr.icon="mdi:map"
x_hass_attr.iso_country_code="US"
x_hass_attr.latitude=47.613968
x_hass_attr.locality="Bellevue"
x_hass_attr.location=[47.628323099999996,-122.14942209999998]
x_hass_attr.longitude=-122.16925
x_hass_attr.name="14320"
x_hass_attr.phone="null"
x_hass_attr.postal_code="98007"
x_hass_attr.premises="null"
x_hass_attr.restored=true
x_hass_attr.sub_administrative_area="King County"
x_hass_attr.sub_locality="null"
x_hass_attr.sub_thoroughfare="14320"
x_hass_attr.supported_features=0
x_hass_attr.thoroughfare="Northeast 20th Street"
x_hass_attr.url="null"
Capabilities: string_sensor, value_sensor, x_hass
Actions:In my rule they are not:
Entity Attribute: Amy S9 (hass>sensor_amy_s9_geocoded_location) x_hass_attr.longitude not between -122.183 and -122.166
-122.16925 -- false as of 11:32:38 AM
AND Entity Attribute: Amy S9 (hass>sensor_amy_s9_geocoded_location) x_hass_attr.latitude not between 47.603 and 47.617
47.613968 -- false as of 11:32:38 AM -
I would like to ask if this is possible and if others would find this useful.
I have multiple rules that check if lights are turned on manually and then have “Condition must be sustained for” xxxx amount of seconds then use the set reaction to turn off the light if it has not been shutoff. I like the UI when the rule is expanded that shows sustained time. (See Screenshot Below) Could a “Widget” have this information on the status screen that would show which rules conditions are waiting to come true with the sustained time? Similar to the Running Reactions widget.
Screen Shot 2022-10-04 at 7.44.09 PM.png Thanks
latest-22274
Synology Docker -
Iron: QNAP NAS
Running MSR and HAAS on Docker (QNAP Container Station)
Reactor (Multi-hub) stable-22203-81a2f3cc
Home Assistant Core 2022.6.7
Vera 1.7.5186 (7.31)
Config files are stored in shared volumes on the NAS.
Office light in example is joined to Vera-PlusHello all,
I decided to upgrade MSR to latest-amd64. It wasn’t until afterwards that I noticed all rulesets broken. So unfortunately I’m not sure if this was already broken before or I broke it after upgrading. Yes poor judgement on my part for being complacent.
Never the less, this is broken globally across all rulesets, even though I can see the triggers change to “True” (Turn green).
For this example, I have a boolean helper toggle in HAAS called “TV MODE HAAS SW”.
When toggled ‘on’, MSR should turn my Vera office light OFF and it doesn’t, but if I manually select the play button to the right of the line in the Set Reaction, it executes properly and turns off the Vera office light.
The MSR Rule does not have any Constraints set.
I can see in MSR it recognizes the state changes yet doesn’t execute the “Set Reaction”.
Any help greatly appreciated.
Log files from reactor.log and screen shots to follow:
Reactor.log when toggling the haas helper, Set Reaction doesn’t execute.
[stable-22203]2022-10-02T21:21:34.799Z <Rule:INFO> TV MODE ON (Rule#rule-l2hvuz8r) starting evaluation; because entity-changed Entity#hass>input_boolean_tv_mode [stable-22203]2022-10-02T21:21:34.800Z <Rule:INFO> TV MODE ON (Rule#rule-l2hvuz8r) evaluated; rule state transition from RESET to SET! [stable-22203]2022-10-02T21:21:34.819Z <Rule:INFO> TV MODE ON (Rule#rule-l2hvuz8r) evaluation complete [stable-22203]2022-10-02T21:21:34.820Z <Engine:INFO> Enqueueing "TV MODE ON<SET>" (rule-l2hvuz8r:S) [stable-22203]2022-10-02T21:21:34.835Z <Engine:NOTICE> Starting reaction TV MODE ON<SET> (rule-l2hvuz8r:S) [stable-22203]2022-10-02T21:21:34.835Z <Engine:INFO> TV MODE ON<SET> all actions completed.Reactor.log when manually triggering the Set Reaction with the play button which correctly turns off the light
[stable-22203]2022-10-02T21:23:25.035Z <HassController:null> HassController#hass: sending payload for power_switch.off on Entity#hass>light_office_86 action: [Object]{ "type": "call_service", "service_data": { "entity_id": "light.office_86" }, "domain": "homeassistant", "service": "turn_off" }When toggled ON
toggled_on.pngRule config screen
tv_mode_config.png -
Hubitat C7 = 2.3.2.141 AND 2.3.3.123
MSR in a docker = latest-22264-93bf3814 and latest-22266-88868fc0I'm curious if this is a bug or expected behavior. Unfortunately I don't know exactly when this began either. I have renamed a few devices over the course of the last few MSR builds, but never really brought it up before. Plus I don't rename devices too often. But I have a motion sensor right now that I renamed in Hubitat from "Office Motion" to "Living Room Motion" over 2 weeks week ago. Probably closer to 3 or 4 weeks now. I have restarted MSR several times since the rename, hard refreshed the browser, tried a different machine and different browser, and even an updated version of MSR. MSR is still showing the old name within the Entities section. I know I could rename it within MSR, but I would prefer to only have to rename devices in one location. I don't recall how long ago I started noticing this, which I know does not help at all.
-
Hey Patrick, this is probably a rather large request but it would be nice to be able to download a back-up of MSR through the UI similar to how we could do it with R4V. Beyond that maybe even having the ability to create a rule set that auto backups to a NAS would be even more useful! Currently I know you can just copy the complete reactor file from the machine MSR is running on but using the UI would make backing possible from anywhere and much simpler and quicker!
-
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.
Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed. -
Maybe a dumb question if I'm missing something obvious, but I checked the manual and searched the forum without finding anything relevant...
Can the Rule Sets on the left side of the MSR web UI be re-sorted? I just realized that it seems to be sorted with the newest ones at the top and I would prefer to have them alphabetical... and to have a multi-level tree with nested rulesets... but I'll settle for alphabetical for now if there's a way to do it 🙂
MSR latest-22266 / Raspberry Pi 4 / Docker
-
The reason for my question is a rather long story involving a virtual thermostat on my Hubitat and using InfluxDB and Grafana to graph the state of the thermostat.
The TL;DR version is that it would be helpful if I could send MSR expressions (variables) to InfluxDB. I don't currently see any way to do that, and if it isn't a current capability of MSR it might be useful as a future enhancement.
Long version: I have a rule in MSR that runs every minute to pull the thermostat information from my thermostat's cloud API. I parse the response into global variables, and then update a Hubitat virtual thermostat when those global variables change. I added the x_hubitat_Thermostat entity, along with selected capabilities, to my reactor.yaml in the InfluxDB section, 'default_capabilities', so the changes to the virtual thermostat get logged into the db.
It's working OK except when the API reports that the temperature has reached the setpoint but the system is still operating. For example, in the morning when the heat is turned up, the temp will climb until the setpoint == the temperature, but the system will continue heating for a while afterwards. It's a variable speed/heat system so it continues to run at very low output for quite a while after the temps match.
The issue I'm having is that when the temperature matches the setpoint, the Hubitat virtual thermostat switches to idle mode on it's own, despite the fact that the API is still reporting heating mode. When the virtual device sees that the setpoint has been reached, it automatically changes to idle, which makes sense as that's how you'd want a real thermostat to work .
I am working around this by having the rule that updates the temperature on the virtual device also update the operatingState. This fixes it, but for just a few milliseconds the virtual thermostat switches to idle before the rule sets it back to heat, and that state change shows up in Grafana.
If I could just directly log changes to the expressions to InfluxDB I could avoid the issue and get the same data into the database. Also I can see other applications for something like this with other APIs where MSR and InfluxDB could be used to log data without having any virtual device entities involved.
-
Hey Patrick, had to switch over my HA VM from VirtualBox to VMware since VirtualBox stopped playing well. Anyways I updated the IP address to the new VM IP and deleted the Long Lived Access Token and created a new one just in case (copy pasted the new token into the config file). Tried rebooting both the HA machine and the MSR one too and MSR is still not connecting. The only thing I have not tried yet is creating another controller entry, but I am worried it may create all new entities for everything forcing me to redo all my logic. Here are some logs:
[latest-22258]2022-09-20T21:17:24.749Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:17:24.749Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation [latest-22258]2022-09-20T21:17:24.749Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:18:09.753Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket [latest-22258]2022-09-20T21:18:24.761Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:18:24.761Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation [latest-22258]2022-09-20T21:18:24.761Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:19:01.083Z <VeraController:INFO> VeraController#vera 0 dead entities older than 86400000s purged [latest-22258]2022-09-20T21:19:14.780Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket [latest-22258]2022-09-20T21:19:29.785Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:19:29.785Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation [latest-22258]2022-09-20T21:19:29.785Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:20:24.791Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket [latest-22258]2022-09-20T21:20:39.813Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:20:39.820Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation [latest-22258]2022-09-20T21:20:39.820Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out -
Patrick,
I've just imported a large set of rules from Vera, and I had already played with creating rules in MSR that are mixed throughout the existing Vera rules. Is there any sort of way to "find/replace" in MSR, so I can find all matches to the old rules and replace them with the new ones? -
Patrick,
Yesterday I migrated a large luup Reactor group over from Vera to MSR, following the directions to importing it from Vera in the documentation. One of the odd things in the migration was the conditional rules for House Modes. Many of my rules had conditions such as "House Mode is any of Home, Night, or changes to Away.The way the import did it was changes from 1,3 to null. This importation did not seem to trigger rules correctly.
I was able to fix all the instances by creating multiple triggers in a group:
Entity Attribute: House Mode (vera>housemode) x_vera_housemode.mode contains home
OR Entity Attribute: House Mode (vera>housemode) x_vera_housemode.mode contains nightIs this what you are expecting in importation?
-
Good morning all,
This weekend I've been playing around with Home Assistant as a replacement (long term) for my aging Vera platform. I'm pretty amazed how much more capability it has. On the other hand, the sheer amount of variables it pulls in from devices is massive.In any case, I have added Google Calendar into Home Assistant for things like Federal Holidays and my daughter's school calendar. It connected to them without issue, which I had been having problems with in Vera an GCal3.
I connected MSR to Home Assistant, so I can start using some of the systems I've integrated into Home Assistant in MSR, and continue migrating my luup Reactor rules over to MSR. Now I'm trying to create a rule based on if today is a Federal Holiday or not. Reactor sees the calendar just fine, however, for whatever reason, it's not pulling data for today, but the next event, which in this case is Columbus day, three weeks away. The attribute that is pulling this is x_haas_attr.message.
I tested with my daughter's school calendar, and it did have an entry for today, and none of the other values seemed to be different, such as a "true" or something to tell me there is an entry.
a8478a6e-d8eb-4572-ac84-c94ff012a1ec-image.png
60632486-e80b-4f0f-aed9-dc67113689a4-image.png
ab04cd0f-f849-4e14-be7d-f4c00735da77-image.png
The only thing I've been able to come up with, is there is a start_time attribute, which shows the date as 2022-10-10 00:00:00
1cbe4526-7f63-4329-a088-b331f1d03376-image.png
The only thing I can think of is there might be a way to compare the current system date to that date, but I can't seem to figure that out in MSR.
Has anybody done this? Any suggestions?
-
I started kicking around the VEC last evening, was cut short, and dug in a bit more this morning.
My reactor.yaml:
d3df4d99-aa7f-4b8b-8fb9-5a6c615daad9-image.png
I verified the yaml is good at https://yamlchecker.com/
What I'm seeing in MSR:
0f89ce8e-7abe-4779-baca-43123e030cf4-image.png
87560ded-7dfa-4340-8585-8be58ff22852-image.png
I believe I have followed all steps (standard disclaimers apply).
Anyone else started to tinker with this newness and, if so, what were your results?
-
Having just embarrassed myself to @toggledbits by asserting that the latest release somehow had a bug when in reality it was surfacing underlying issues with my approach to building out my rulesets and automations I wanted to ask the collective for their feedback on how they've designed their rulesets.
For me, I built out a list of Global Reactions that I commonly use. For instance, for mode changes I typically change the mode entity and write that mode to a variable for some future use. When building out a ruleset I just pull in that Global Reaction vs manually recreating the entity list as my ruleset Reaction. Example, for lighting:
270bbe18-9680-491d-81d4-20308a9fe63c-image.png
Each of these contains the appropriate group of lights to turn on/off, etc.
I also have what I've dubbed my "Armed for..." rulesets. These are rulesets that can be referenced as true or false in other rulesets. Example, for my various lighting configurations in and out of the house I have these:
0d9f55d4-5d5d-42e2-a83c-8afa95df08fb-image.png
I think this is resulting in reactions stomping on other reactions creating race conditions that result in things looking like they're working when, in reality, they're one restart away from disaster.
So how are you all designing your superstructure, if you will, at a high level?
-
Maybe more of a cosmetic issue, but certain entities could be hidden from entity actions as you cannot set any meaningful action? See Vera as an example:
Screenshot 2022-09-16 at 15.11.29.png
vera>system is then obviously a different story and should be there
-
Hi @toggledbits,
I have a bridge consuming Vera's variable using the MQTTController in MSR, and I've noticed that after I've updated to the latest version (22257), some variables are not echoed. I've already tried to reboot MSR, with no luck.
These variables are under urn:smarthome-community:serverId:Vacuum
0fe837ed-3a29-4d5d-a06c-445981d44e13-image.png
A trace via MQTT explorer:
cf919028-4f7b-4761-b99a-c3943945704a-image.pngMy config has just exclude_capabilities: [] and it was working OK before the latest build. Even /query command doesn't seem to retrieve all the attributes. The values are retrieved correctly from the Vera controller, and I could use them in MSR, they're just not echoed to the bridge. Thanks!
-
Good morning all,
I"m working on converting my luup Reactor scenes over to MSR, so I can eventually introduce an Ezlo plus into the mix and not loose all the work I've done with Reactor. If nothing else, this should free up some resources on my aging Vera Plus, and maybe speed up some functions. Maybe that's just wishful thinking.In any case, I'm moving move my first Reactor set, which is a set of rules to control the blilnds/window coverings in my home. I have two types of blinds:
iBlinds retrofit motors (IB2.1-ZWx) version from late 2019.
Bali roman shades with factory installed Somfy CSZ1 Z-wave motors.I'm setting up reactions for both types of window coverings. One of the problems I always had in Vera was with iBlinds, I had to do it by luup commands:
luup.call_action("urn:upnp-org:serviceId:Dimming1","SetLoadLevelTarget",{ newLoadlevelTarget="50" },316)The reason for this, is that the open position was 100%, and the close position was 0%. In other words, the blinds were closed one way 100% an closed 100% the other way. I've been informed by iBlinds support that even in Ezlo, they still do it this way, which is different than most other Z-wave controller manufacturers. I'm not sure how the others do it, but some how "open" is right in the middle (50%).
So, in MSR, i can still set the Dimming1.SetLoadLevelTarget to 50, but I also noticed some other commands I haven't seen before in Reactor
3cdeeb89-5986-45bc-8a3b-79067050a22c-image.png
Is there some way in MSR to set that middle value to 50% so I can use cover.open? The command cover.close works as expected, so I'm wondering how I might use that cover.set.
Thanks for any advise.
-
I configured OWM Weather on MSR (latest-22257-dd9b9271), created an account with OWM, generated an API key, put the key in the yaml file, and I’ve waited over a day now. OWM Weather shows as up on the the Controller Status widget.
I’ve tried to create a trigger or constraint to use the data, and nothing is really showing up.
5B8611C1-33D0-4D3C-B507-7383CB81E25A.jpeg
I only have a free subscription with OWM, but I was expecting some data.
Is this expected behavior (i.e., still in development), or do I do more configuration other than the .yaml file?’
I still am able to pull Weather data through Dark Sky in my Vera plus controller, however, I know that will no longer work at some point.
Synology Docker installation
-
@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):
Concurrently, 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!!
- Libra
FOLLOW-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. -
If someone smarter than me wishes to volunteer a simple write-up on the exact steps required to get MSR up and running on my Synology NAS (with Docker installed and active), I'd be delighted to give it a try. I realize a dedicated Docker-ized version of MSR is perhaps ideal -- and I'm happy to wait for that to manifest -- but if, in the meantime, someone out there can propose a build-your-own solution with minimal footprint, I'm game.
Unspoken here is how much I cringe when dealing with anything Linux, because for me it's like reading Chinese. But I can follow written instructions very well and provide meticulous feedback.
So thanks in advance...- Libra
-
I don't have any docker containers yet. The bug list is looking pretty quiet for things urgent at the moment, so maybe I'll spend an hour or two seeing what I can get built. I also have a Synology NAS, so I have a ready test platform. The image/container itself is easy, but I'm still figuring out the correct (Synology) way to do the volumes (or bind mounts, whatever they use) for the config and data.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
I would encourage you to open a new thread? I will fork it if you don't mind.
-
Concur, and let's get @toggledbits ' earlier Docker-related notes copied into this thread as well. Dunno if they were higher up in the "MSR Available" thread?
-
Hopefully not about to ask the world's dumbest question, but here goes...
I'm stumped at Step 1 of the "Getting Started" docs (https://reactor.toggledbits.com/docs/Getting-Started/), since I'm unable to locate the referenced reactor.yaml file.
The only files I see under my <reactor-data>/config folder are:
all-json.out (2 bytes)
all-yaml.out (3 bytes)IMPORTANT NOTE: I'm running MSR under Docker on my Synology NAS, but I believe it behaves identically in all respects to bare metal (Linux) installs. I'm wondering if it's possible that the desired YAML file exists within the distributed image, but is not being exposed yet by the container running MSR.
Will not proceed until advised by someone more knowledgeable. Until then, I have no "Hub/HA" defined, so cannot do anything, really, with MSR. (Makes me kinda wish these settings lived within MSR's panels and not a YAML file, LOL!)
Thanks - Libra
-
The docker container is slightly different in that the data folder does not live within the container, it lives on a volume that the container mounts separately. This is so that the container can read and write data as needed and it is not destroyed when the image or container is replaced (e.g. you would otherwise lose your config and all your rules and reactions), and so you can edit your config without having to breach the walls of the container.
The install steps for the docker container has a step for you to create a directory that would become this volume. To confirm you are looking in the right place, open Docker via the package manager. Go to Container, then click the Reactor container. Hit the Details button, and then the Volume tab. The line that shows the mount path "/var/reactor" is the place where your config and data are stored (not /var/reactor, the path to the left of that under File/Folder. So check that to make sure you are looking in the right place. You should see
config,logsandstorageat a minimum, and possibly alsolocalandsys.Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@toggledbits said in Multi-System Reactor Developer Preview AVAILABLE:
You should see config, logs and storage at a minimum, and possibly also local and sys
In that folder (which in my case happens to be Reactor/Data, I only see the following subfolders:
config
storage -
(Dang it, I should have posted this latest question under the "Synology Docker" thread... @rafale77 can you please bump us over??)
-
OK, then somehow the initial data didn't get copied. If you haven't already, open a PR for that on Mantis, and I'll post the two files so you can put them into the folder yourself, and I'll hunt down why it didn't copy them in the first place.
-
@LibraSun
sitôt dit, sitôt fait. (sorry I don't know the equivalent in english) -
"no sooner said than done" I believe.
-
I like, "Your wish is my command."
-
FYI, I can move them also.
-
Beneath your pay grade sir.
-
No job too big or too small. If it needs to get done, I'm happy to do it.
-
Strictly FYI, I've gone ahead and installed NODE.JS v12 on my Synology NAS in anticipation of attempting the Reactor backup conversion to MSR Rulesets. In my Linux-challenged mind, that's a step in the right direction. Next, I'll need to (re-)learn how to SSH into the NAS for executing Terminal commands. Will let you know if this gets me further along that trajectory.
EDIT: Nope, I was clearly jumping the gun. Will have to take another tack.
-
I've also rolled 21062 (today's daily build) into a docker container for Synology. Link is in PR #58 on the bug tracker.
-
Installed. Works like a charm. Your instructions were spot on, as per usual.
-
We can both thank @kfxo for those instructions!
