Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Finding Missing Devices & Migrating Devices
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
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.
Multi-System Reactor
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S
I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved. The Runtime Error is different in the two browsers Safari v18.3 @http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Google Chrome 133.0.6943.142 TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Steps to reproduce: Click the pencil to edit a global reaction with a group. Click the Exit button. Runtime error appears. or Click Create Reaction Click Add Action Select Group Add Condition such as Entity Attribute. Add an Action. Click Save Click Exit Runtime error appears. I don’t know how long the error has been there as I haven’t edited the global reaction in a long time. Reactor (Multi-hub) latest-25060-f32eaa46 Docker Mac OS: 15.3.1 Thanks
Multi-System Reactor
Cannot delete Global Expressions
SnowmanS
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons. I have not created a global expression for some times and just noticed this while doing some clean-up. I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success. Here's what the log shows. [latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } Reactor latest-25067-62e21a2d Docker on Synology NAS
Multi-System Reactor
Local notification methods?
CatmanV2C
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method. This was prompted by yesterday's fun and games with my ISP. I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone) I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions? TIA C
Multi-System Reactor

Finding Missing Devices & Migrating Devices

Scheduled Pinned Locked Moved Multi-System Reactor
10 Posts 4 Posters 441 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • LibraSunL Offline
    LibraSunL Offline
    LibraSun
    wrote on last edited by
    #1

    @toggledbits Is there a prescribed (read: easy) way to identify which Rule(s) a particular device is explicitly mentioned in? I'm busy replacing an in-wall dimmer, and /think/ I know which two Rules the old module participated in, but want to be 100% certain. Thanks!

    1 Reply Last reply
    1
    • LibraSunL LibraSun

      Too cool for school, sir! I've been in lurk mode lately due to life interrupting, but didn't want this genius move to go unnoticed.

      Next stop: Cause Ezlo firmware to be deleted from Ezlo boxes, leaving only the good stuff. Watching old Forum tells me they are still moving in many odd directions half a step at a time. Yawn. Should my Vera die, I will almost certainly jump to Hubitat + Reactor.

      3 Offline
      3 Offline
      3rdStng
      wrote on last edited by
      #2

      @librasun said in Fun Stuff:

      Should my Vera die, I will almost certainly jump to Hubitat + Reactor.

      I saw the writing on the walls, from other 3rd party vendors, about the Vera line and made that change. HE C7 + MSR docker. Thrilled I did and removed my last Vera device a couple of days ago. I have my second HE C7 hub staged and ready to replace the Vera+ at my cabin next week. I'll be using the Rule Machine there though. Not as friendly as MSR, but easily as powerful.

      @librasun said in Fun Stuff:

      @toggledbits Is there a prescribed (read: easy) way to identify which Rule(s) a particular device is explicitly mentioned in? I'm busy replacing an in-wall dimmer, and /think/ I know which two Rules the old module participated in, but want to be 100% certain. Thanks!

      I would second this. Maybe list out the locations they are used within the Entities section? Although now that I'm off Vera, I don't plan many changes. I updated the rules I could remember/find and then waited a day or two to see the Alerts for the ones I missed. I ended up documenting all my Vera ID numbers of the devices because one would creep up a week later and I had a hard time remember who Vera>256 was.

      LibraSunL 1 Reply Last reply
      1
      • 3 3rdStng

        @librasun said in Fun Stuff:

        Should my Vera die, I will almost certainly jump to Hubitat + Reactor.

        I saw the writing on the walls, from other 3rd party vendors, about the Vera line and made that change. HE C7 + MSR docker. Thrilled I did and removed my last Vera device a couple of days ago. I have my second HE C7 hub staged and ready to replace the Vera+ at my cabin next week. I'll be using the Rule Machine there though. Not as friendly as MSR, but easily as powerful.

        @librasun said in Fun Stuff:

        @toggledbits Is there a prescribed (read: easy) way to identify which Rule(s) a particular device is explicitly mentioned in? I'm busy replacing an in-wall dimmer, and /think/ I know which two Rules the old module participated in, but want to be 100% certain. Thanks!

        I would second this. Maybe list out the locations they are used within the Entities section? Although now that I'm off Vera, I don't plan many changes. I updated the rules I could remember/find and then waited a day or two to see the Alerts for the ones I missed. I ended up documenting all my Vera ID numbers of the devices because one would creep up a week later and I had a hard time remember who Vera>256 was.

        LibraSunL Offline
        LibraSunL Offline
        LibraSun
        wrote on last edited by
        #3

        @3rdstng said in Fun Stuff:

        I would second this.

        Glad I'm not along in wanting this feature, which -- full disclosure -- I'm hoping would further ease my eventual transition away from Vera and onto, say, Hubitat.

        So that's two scenarios in which MSR could help:

        (a) Swapping a faulty device (e.g. wall switch) for a direct replacement, paired with the existing hub;
        (b) Finding each occurrence in MSR of OldHub>Device_X tied to (but unpaired from) my old hub, to swap it for NewHub>Device_X on the new hub.

        Hope that makes sense. It's almost like asking for an EDIT > FIND & REPLACE feature in a word processor. 🙂

        1 Reply Last reply
        0
        • 3 Offline
          3 Offline
          3rdStng
          wrote on last edited by
          #4

          MSR being the bridge between the two hubs was incredible. Couldn't have done it without it. I moved my Reactor for Vera over first and cleaned that up. Then I moved ALL my scenes and steps that the House Modes did. This set either hub to purely be a device connection point with no rules running on either. I started the migration near the end of August and did 3 - 5 devices at a time, every few days. Any more than 5 at a time was hard to track and adjust MSR along the way. The only real issue was towards the end when I had a couple of switches that would not communicate back to Vera. They were too far away, forcing me move the Vera hub. Luckily I only needed to move it once and get that side of the house in one swoop.

          G 1 Reply Last reply
          0
          • 3 3rdStng

            MSR being the bridge between the two hubs was incredible. Couldn't have done it without it. I moved my Reactor for Vera over first and cleaned that up. Then I moved ALL my scenes and steps that the House Modes did. This set either hub to purely be a device connection point with no rules running on either. I started the migration near the end of August and did 3 - 5 devices at a time, every few days. Any more than 5 at a time was hard to track and adjust MSR along the way. The only real issue was towards the end when I had a couple of switches that would not communicate back to Vera. They were too far away, forcing me move the Vera hub. Luckily I only needed to move it once and get that side of the house in one swoop.

            G Offline
            G Offline
            gwp1
            wrote on last edited by
            #5

            @3rdstng This.

            I implemented the same plan. Have a couple hours doing laundry? Perfect. Migrate as many devices as that time allows and update the previously-migrated rules from Vera Reactor to MSR.

            The migration script @toggledbits provided for Vera Reactor users was huge. Making adjustments was much quicker than rebuilding rulesets from scratch.

            I started almost Day One of MSR being released and just this past weekend removed the final hard device from Vera as well as officially shut down my SiteSensors.

            *Hubitat C-7 2.4.1.151
            *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

            *HASS 2025.3.4
            w/ ZST10-700 fw 7.18.3

            *Prod MSR in docker/portainer
            MSR: latest-25082-3c348de6
            MQTTController: 24257
            ZWave Controller: 25082

            1 Reply Last reply
            0
            • LibraSunL Offline
              LibraSunL Offline
              LibraSun
              wrote on last edited by
              #6

              Welp, it got to be late last night and I had the Amazon browser window open, so guys... I pulled the trigger and ordered my Hubitat. Will be here tomorrow and I fully intend to put it through its paces. Vera Plus retirement, here we come!!

              P.S. This will leave me with perfectly good (2) Vera Plus, (1) Vera Edge, (1) ezlo Plus and (1) ezlo Atom sitting in my closet, hoping to sell. Is there a "Marketplace" section on the Forum??

              1 Reply Last reply
              0
              • toggledbitsT Offline
                toggledbitsT Offline
                toggledbits
                wrote on last edited by
                #7

                @librasun said in Finding Missing Devices & Migrating Devices:

                Is there a prescribed (read: easy) way to identify which Rule(s) a particular device is explicitly mentioned in?

                I thought this deserved its own topic.

                At the moment, no, at least, nothing very tidy. If you're on a Linux-based platform (including NAS docker containers), you can fgrep the storage directory for the device ID.

                $ fgrep -r 'vera>device_10' storage/rules/*
                storage/rules/rule-klmlmzg9.json:                        "entity": "vera>device_10",
                storage/rules/rule-kln4zy9e.json:                        "entity": "vera>device_10",
                storage/rules/rule-klvag40b.json:                        "entity": "vera>device_10",
                storage/rules/rule-klwtr0re.json:                        "entity": "vera>device_10",
                storage/rules/rule-km6w0xwi.json:                        "entity": "vera>device_10",
                storage/rules/rule-kmkt2705.json:                        "entity": "vera>device_10",
                

                You can then open each of those files and look for the name field to find the rule name. Not great, but maybe better than nothing. Once you're used to it, it's quick. If you expand the search to the storage directory in general, you'll also find the expressions and reactions.

                The issue at hand is that Reactor doesn't use a proper database for storage currently. The database I'd most like to use, mongodb, would lend itself to storing this type of data and maintaining a lot of flexible relationships that would allow queries of this kind to be easy, but comes at a high cost: mongodb just as an add-on is much larger than Reactor itself, more than doubling the demand on both storage and RAM before even doing any work; and as a separate service on which Reactor would then depend entirely, it introduces a big new point of failure in the system.

                I haven't come up with a solution I like yet, but I'll confess it's also something I haven't spent a huge amount of time thinking about. It may simply be that for the relatively low use this type of query would receive, brute force is the best answer (i.e. something under Tools that just rips through the objects directly, no database storage/overhead).

                Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                3 1 Reply Last reply
                1
                • LibraSunL Offline
                  LibraSunL Offline
                  LibraSun
                  wrote on last edited by LibraSun
                  #8

                  [SOLVED - OK to remove this]

                  SOLUTION: I had mistakenly assigned the NAS folder /REACTOR instead of REACTOR/DATA to the '/var/reactor' volume when setting up the Docker Container for MSR. Once rectified, all Rulesets reappeared like magic.

                  Speaking of finding missing items, I've consulted the Docs under "Installation" and come up empty on solving a mini-crisis I got myself into tonight after rebuilding my RAID volume. On my Synology NAS > Docker > MSR setup, I had taken pains to backup the entirety of the shared REACTOR folder contents. That went well.

                  After successfully building my new RAID array (with larger, more reliable HDDs), I restored all the REACTOR folder contents in the same (top-level) location on my NAS. It was time to reinstall Docker, download the Reactor 'latest' image, then get the Container going. Again, all went smoothly.

                  Here's my problem: MSR latest-21307-1746e27 is running fine, and although it lives among all the restored folders and subfolders - full of my existing Rulesets, etc. - the UI shows none of them. Instead, I get the classic, "This rule set is empty. Click "Add Rule" to add a rule to it."

                  Q: How can I force a fresh MSR installation to 'see' my existing settings?

                  THANKS for any guidance! I'm a little scared now, and all sphincters still unclenching from the NAS HDD replacement surgery.

                  1 Reply Last reply
                  0
                  • toggledbitsT toggledbits

                    @librasun said in Finding Missing Devices & Migrating Devices:

                    Is there a prescribed (read: easy) way to identify which Rule(s) a particular device is explicitly mentioned in?

                    I thought this deserved its own topic.

                    At the moment, no, at least, nothing very tidy. If you're on a Linux-based platform (including NAS docker containers), you can fgrep the storage directory for the device ID.

                    $ fgrep -r 'vera>device_10' storage/rules/*
                    storage/rules/rule-klmlmzg9.json:                        "entity": "vera>device_10",
                    storage/rules/rule-kln4zy9e.json:                        "entity": "vera>device_10",
                    storage/rules/rule-klvag40b.json:                        "entity": "vera>device_10",
                    storage/rules/rule-klwtr0re.json:                        "entity": "vera>device_10",
                    storage/rules/rule-km6w0xwi.json:                        "entity": "vera>device_10",
                    storage/rules/rule-kmkt2705.json:                        "entity": "vera>device_10",
                    

                    You can then open each of those files and look for the name field to find the rule name. Not great, but maybe better than nothing. Once you're used to it, it's quick. If you expand the search to the storage directory in general, you'll also find the expressions and reactions.

                    The issue at hand is that Reactor doesn't use a proper database for storage currently. The database I'd most like to use, mongodb, would lend itself to storing this type of data and maintaining a lot of flexible relationships that would allow queries of this kind to be easy, but comes at a high cost: mongodb just as an add-on is much larger than Reactor itself, more than doubling the demand on both storage and RAM before even doing any work; and as a separate service on which Reactor would then depend entirely, it introduces a big new point of failure in the system.

                    I haven't come up with a solution I like yet, but I'll confess it's also something I haven't spent a huge amount of time thinking about. It may simply be that for the relatively low use this type of query would receive, brute force is the best answer (i.e. something under Tools that just rips through the objects directly, no database storage/overhead).

                    3 Offline
                    3 Offline
                    3rdStng
                    wrote on last edited by
                    #9

                    @toggledbits said in Finding Missing Devices & Migrating Devices:

                    At the moment, no, at least, nothing very tidy. If you're on a Linux-based platform (including NAS docker containers), you can fgrep the storage directory for the device ID.

                    I don't like to mongodb idea. Reactor is very light and nimble. Plus with everything being text based files, it's harder to corrupt than a DB, thus easier to restore to if you need to.

                    I do like something under the tools section. Maybe just a stupid simple GUI to a fgrep cli command with collected variables that then display the results in the GUI as well? It's crude, but it should work. Maybe? And also now that my migration is done, I think I would only really use it to find a device I know is in use within a rule I nested elsewhere. I've tried to keep them grouped in areas, like Roller Shades, Light Schedules, Announcements, etc. But every once in a while there is a rule that straddles both and I hunt for it. Aside from that, I am perfectly fine with the red bell in the top right.

                    LibraSunL 1 Reply Last reply
                    1
                    • 3 3rdStng

                      @toggledbits said in Finding Missing Devices & Migrating Devices:

                      At the moment, no, at least, nothing very tidy. If you're on a Linux-based platform (including NAS docker containers), you can fgrep the storage directory for the device ID.

                      I don't like to mongodb idea. Reactor is very light and nimble. Plus with everything being text based files, it's harder to corrupt than a DB, thus easier to restore to if you need to.

                      I do like something under the tools section. Maybe just a stupid simple GUI to a fgrep cli command with collected variables that then display the results in the GUI as well? It's crude, but it should work. Maybe? And also now that my migration is done, I think I would only really use it to find a device I know is in use within a rule I nested elsewhere. I've tried to keep them grouped in areas, like Roller Shades, Light Schedules, Announcements, etc. But every once in a while there is a rule that straddles both and I hunt for it. Aside from that, I am perfectly fine with the red bell in the top right.

                      LibraSunL Offline
                      LibraSunL Offline
                      LibraSun
                      wrote on last edited by
                      #10

                      @3rdstng said in Finding Missing Devices & Migrating Devices:

                      Maybe just a stupid simple GUI to a fgrep cli command with collected variables

                      I think Hubitat handles it by adding a reference - complete with hyperlink - for every Rule containing a specific device or virtual device. One click to jump over to the Rule. Kinda neat.

                      As someone mentioned above, I think the idea place for MSR to have this (if it were to become a feature) is under Entities. Truly it could spare me many hours of hunting and pecking - and never being entirely certain - that I sadly do not have most days.

                      1 Reply Last reply
                      0
                      • toggledbitsT toggledbits locked this topic on
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      Recent Topics

                      • Advice reqeusted to migrate MSR from Bare Metal to Container
                        T
                        tamorgen
                        0
                        5
                        38

                      • Reactor (Multi-System/Multi-Hub) Announcements
                        toggledbitsT
                        toggledbits
                        5
                        122
                        35.4k

                      • Z-Wave Future....
                        CatmanV2C
                        CatmanV2
                        0
                        5
                        131

                      • Can´t restart or upgrade/deploy MSR
                        toggledbitsT
                        toggledbits
                        0
                        4
                        86

                      • [Solved] Limit HA Entity in MSR
                        wmarcolinW
                        wmarcolin
                        0
                        7
                        191

                      • Disaster recovery and virtualisation
                        CatmanV2C
                        CatmanV2
                        0
                        5
                        662

                      • Remote access of Zwave stick from Z-wave server
                        CatmanV2C
                        CatmanV2
                        0
                        3
                        384

                      • Organizing/ structuring rule sets and rules
                        G
                        gwp1
                        0
                        5
                        374

                      • Moving MSR from a QNAP container to RP 5 - some issues
                        G
                        gwp1
                        0
                        5
                        346

                      • Widget deletion does not work and landing page (status) is empy
                        G
                        gwp1
                        0
                        4
                        338

                      • Need help reducing false positive notifications
                        T
                        tamorgen
                        0
                        7
                        520
                      Powered by NodeBB | Contributors
                      Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Unsolved