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. Switching from Vera to Hubitat
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
Handling Dead Entities and Renamed Entities
PablaP
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down. I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor). My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only). Anyway, here's my reactor-mqtt-contrib package: https://github.com/dbochicchio/reactor-mqtt-contrib Simply download yaml files (everything or just the ones you need) and you're good to go. I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them. The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression. Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
Multi-System Reactor
HA 2025.9.4 Supported Yet?
CatmanV2C
Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off Cheers C
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Rule Set UI bug - RESOLVED
3
Topic thumbnail image
Multi-System Reactor
[Reactor] Copy&Paste of Rules
therealdbT
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me. While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users. I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do. Just an idea
Multi-System Reactor
[Reactor] Help with screne controller cycling logic
therealdbT
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically. That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button. Example: Light 1 ON → OFF, then Light 2 ON → OFF. The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule. Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Expose MSR entities
CatmanV2C
Probably a really dumb question. Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great. Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly. Any thoughts? Apologies if the ask is not clear/ TIA C
Multi-System Reactor
Comment in Globa Expressions
Tom_DT
I have several Global Expressions that are set by a rule so the definition area is blank. I'd like to add a comment in this area that explains what is setting the value. Commenting in this area breaks the remote setting. Any way to document what is setting the GE?
Multi-System Reactor
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Multi-System Reactor
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
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 customize home page
G
I foolishly let my system wipe all cookies this morning and with it my settings for my MSR home page. Once logged back in I can no longer remove errant panes nor is the + available to add new ones. Brave Browser v1.80.122 (Jul 16, 2025) What have I done?! Will check other browsers on my M1. UPDATE: Safari exhibits same behaviour. I've tried both sans last-four public key entry and with - no change.
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor

Switching from Vera to Hubitat

Scheduled Pinned Locked Moved Multi-System Reactor
9 Posts 3 Posters 1.0k 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.
  • wmarcolinW Offline
    wmarcolinW Offline
    wmarcolin
    wrote on last edited by
    #1

    Well finally after a long time, I bought my Hubitat and start the process of working with 2 hubs, with the final goal of staying only with Hubitat.

    I want to share my first insight, and of course then a shortlist if you can help to speed up my change with some information.

    First perception Hubitat is much more professional, lighter, more technical, and thus more difficult for beginners. Vera has the Dashboard and Devices part more visually elaborated, it is easier and faster to see things, something that Hubitat has to build but gives much more potential for creation. Hubitat's manuals and documents are infinitely better. In summary, the more technical features in my opinion, far outweigh the visual point of Vera.

    Some small doubts:

    1. Is there in Hubitat a way to update/force neighbor nodes?
    2. In Vera I use the variable x_vera_device.failed or zwave_device.failed to detect devices with problems (long discussions in other posts), in MSR I don't see this variable for Hubitat devices, how to know the device is in a failure state? In MSR Entities I see that Vera devices have many more variables than Hubitat devices.
    3. In this matchEntities({capability:['x_vera_device']}) expression that lists all the devices, for this x_vera_device parameter it only shows what is in the Vera, which would be common to any hub?
    4. Who is the equivalent of Vera's Switchboard Plugin from @toggledbits on Hubitat? Do you have something like SiteSensor?

    Sorry for asking these questions, I have already searched the manuals and forums and they are issues that after a week of searching I still can't solve.

    Thanks.

    toggledbitsT 1 Reply Last reply
    0
    • wmarcolinW wmarcolin

      Well finally after a long time, I bought my Hubitat and start the process of working with 2 hubs, with the final goal of staying only with Hubitat.

      I want to share my first insight, and of course then a shortlist if you can help to speed up my change with some information.

      First perception Hubitat is much more professional, lighter, more technical, and thus more difficult for beginners. Vera has the Dashboard and Devices part more visually elaborated, it is easier and faster to see things, something that Hubitat has to build but gives much more potential for creation. Hubitat's manuals and documents are infinitely better. In summary, the more technical features in my opinion, far outweigh the visual point of Vera.

      Some small doubts:

      1. Is there in Hubitat a way to update/force neighbor nodes?
      2. In Vera I use the variable x_vera_device.failed or zwave_device.failed to detect devices with problems (long discussions in other posts), in MSR I don't see this variable for Hubitat devices, how to know the device is in a failure state? In MSR Entities I see that Vera devices have many more variables than Hubitat devices.
      3. In this matchEntities({capability:['x_vera_device']}) expression that lists all the devices, for this x_vera_device parameter it only shows what is in the Vera, which would be common to any hub?
      4. Who is the equivalent of Vera's Switchboard Plugin from @toggledbits on Hubitat? Do you have something like SiteSensor?

      Sorry for asking these questions, I have already searched the manuals and forums and they are issues that after a week of searching I still can't solve.

      Thanks.

      toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by
      #2

      @wmarcolin said in Switching from Vera to Hubitat:

      Is there in Hubitat a way to update/force neighbor nodes?

      We don't even know that a node is ZWave. But that's not different from Hass. One of the disappointments of those platforms.

      @wmarcolin said in Switching from Vera to Hubitat:

      In Vera I use the variable x_vera_device.failed or zwave_device.failed to detect devices with problems (long discussions in other posts), in MSR I don't see this variable for Hubitat devices, how to know the device is in a failure state?

      See #1

      @wmarcolin said in Switching from Vera to Hubitat:

      In this matchEntities({capability:['x_vera_device']}) expression that lists all the devices, for this x_vera_device parameter it only shows what is in the Vera, which would be common to any hub?

      x_vera_device is a capability that exists only on Vera devices. It's a container for the additional information we can get from the Vera that other platforms don't have in common.

      @wmarcolin said in Switching from Vera to Hubitat:

      Who is the equivalent of Vera's Switchboard Plugin from @toggledbits on Hubitat? Do you have something like SiteSensor?

      This is two separate questions. Virtual devices can be created on Hubitat by clicking "Add Virtual Device" in the Devices list.

      I'm not aware of anything like SiteSensor on Hubitat, but I'm not deeply familiar with the breadth of their community apps. It's a good bit of a looser environment than the Vera App Marketplace defined. But, MSR can fulfill the SiteSensor role, as has been discussed in this category in other posts.

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

      1 Reply Last reply
      0
      • wmarcolinW Offline
        wmarcolinW Offline
        wmarcolin
        wrote on last edited by
        #3

        @toggledbits hi!

        Regarding x_vera_device.failed or zwave_device.failed I understand and I am disappointed by this as well. Well, I follow the search task on the forums to see what I can find, surely I am not the only one who wants to do a check when a device stops responding.

        With the point of listing all devices, something similar to x_vera_device for Hubitat to give the same? Any suggestions on what would be a common point across all Hubitat devices?

        Ok, now I understand Add Virtual Device, but nothing compared to Switchboard 😞 searching now how to create a radio switch.

        Site Sensor ok I will follow what we have discussed in this forum, I don't like, Sitesensor seems more transparent/impactful than being in a recurrent way triggering the MSR to test every 5 seconds the internet.

        I'm seeing that the road will be longer than I thought, strong advantage that I'm really seeing is the compatibility with devices, especially S2, and of course start using Zigbee, I have 4 devices that I bought more than a year and finally will use.

        toggledbitsT 1 Reply Last reply
        0
        • wmarcolinW wmarcolin

          @toggledbits hi!

          Regarding x_vera_device.failed or zwave_device.failed I understand and I am disappointed by this as well. Well, I follow the search task on the forums to see what I can find, surely I am not the only one who wants to do a check when a device stops responding.

          With the point of listing all devices, something similar to x_vera_device for Hubitat to give the same? Any suggestions on what would be a common point across all Hubitat devices?

          Ok, now I understand Add Virtual Device, but nothing compared to Switchboard 😞 searching now how to create a radio switch.

          Site Sensor ok I will follow what we have discussed in this forum, I don't like, Sitesensor seems more transparent/impactful than being in a recurrent way triggering the MSR to test every 5 seconds the internet.

          I'm seeing that the road will be longer than I thought, strong advantage that I'm really seeing is the compatibility with devices, especially S2, and of course start using Zigbee, I have 4 devices that I bought more than a year and finally will use.

          toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by
          #4

          @wmarcolin said in Switching from Vera to Hubitat:

          With the point of listing all devices, something similar to x_vera_device for Hubitat to give the same? Any suggestions on what would be a common point across all Hubitat devices?

          It is the purpose of the x_ capabilities to express hub-specific data and behavior. It is the purpose of the "standard" capabilities ( like power_switch and temperature_sensor) to provide a "lingua franca" interpretation of the data when possible (and I encourage you to use those capabilities when possible in preference to the x_ capabilties).

          The x_ capabilities try to expose as much information as the hub offers in its raw form, so I would examine your entities and look at what's there. If there are opportunities to map those to standard services and it hasn't been done, bring that to my attention and I can add that mapping. But nonetheless, you are not cut off from the data; it's all there. What you don't find there is data that doesn't exist (i.e. isn't offered by the hub).

          In the case of Hubitat, if data or capability (action) is not exposed through MakerAPI, the Hubitat forums should receive that complaint. And it's more effective if those complaints come from multiple users (i.e. not just me). But Hass, Ezlo, it's all the same... if there's a way to figure it out, I will (especially if you help by providing data I don't have access to), but if the hub's API doesn't offer the necessary data, the hub has to change, not MSR.

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

          wmarcolinW 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            @wmarcolin said in Switching from Vera to Hubitat:

            With the point of listing all devices, something similar to x_vera_device for Hubitat to give the same? Any suggestions on what would be a common point across all Hubitat devices?

            It is the purpose of the x_ capabilities to express hub-specific data and behavior. It is the purpose of the "standard" capabilities ( like power_switch and temperature_sensor) to provide a "lingua franca" interpretation of the data when possible (and I encourage you to use those capabilities when possible in preference to the x_ capabilties).

            The x_ capabilities try to expose as much information as the hub offers in its raw form, so I would examine your entities and look at what's there. If there are opportunities to map those to standard services and it hasn't been done, bring that to my attention and I can add that mapping. But nonetheless, you are not cut off from the data; it's all there. What you don't find there is data that doesn't exist (i.e. isn't offered by the hub).

            In the case of Hubitat, if data or capability (action) is not exposed through MakerAPI, the Hubitat forums should receive that complaint. And it's more effective if those complaints come from multiple users (i.e. not just me). But Hass, Ezlo, it's all the same... if there's a way to figure it out, I will (especially if you help by providing data I don't have access to), but if the hub's API doesn't offer the necessary data, the hub has to change, not MSR.

            wmarcolinW Offline
            wmarcolinW Offline
            wmarcolin
            wrote on last edited by
            #5

            @toggledbits thanks for the reply online, I will take your message and see what I should do and of course try to help.

            But today I am really bothered by Hubitat not signaling clearly that a device is failing. Yesterday, more than 24 hours ago, I purposely unplugged a plug from the electricity supply to see if there were any failure signals, and there are none.

            This to me is extremely serious, devices can for some reason lose communication, stop working, and only when an action fails should we investigate and understand. This is absurd to me, if I go on vacation and the door/window or motion sensors are not responding, does that mean that the alarm will not work? Maybe my analysis is hasty, but this is serious, I want to act before, when I already know that a communication established by wakeup interval does not happen, I will be warned.

            I posted a similar message in the Hubitat group of users and received this comment (https://community.hubitat.com/t/how-many-ex-vera-owners-are-here/44951/122), I will look into this Device Activity Check that you have developed.

            Again Patrick, thank you very much for your always kind attention, I saw that in another chat you mention that you have to take some time for your son, to go to University. Good luck, and unplug for a while 🙂 who knows, maybe you'll come back with more brilliant ideas for all of us.

            Thanks.

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

              This is another reason I'm doing my own ZWave-JS integration for MSR, and not relying on, for example, HA (which uses ZWave-JS now) to be a sufficient pass-through. That makes Reactor much more "hub-ish", I realize, but this is a clear example where the middle-man (HA) is not contributing to capability.

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

              wmarcolinW 1 Reply Last reply
              1
              • toggledbitsT toggledbits

                This is another reason I'm doing my own ZWave-JS integration for MSR, and not relying on, for example, HA (which uses ZWave-JS now) to be a sufficient pass-through. That makes Reactor much more "hub-ish", I realize, but this is a clear example where the middle-man (HA) is not contributing to capability.

                wmarcolinW Offline
                wmarcolinW Offline
                wmarcolin
                wrote on last edited by
                #7

                @toggledbits

                Completing one week of full Hubitat use, and a few comments:

                • Dashboard assembly, super easy to use, lots of customization potential, I don't believe I have to use anything external, positive point;
                • Undoubtedly better the part of drives to add devices, accepted S2 devices that with Vera I couldn't add, finally I believe I will use Zigbee devices, extremely favorable point;
                • Despite being easy to add devices, very, very bad antenna signal. What covered my house quietly with Vera, I am having a very difficult time with the signal. It's been 5 days since I migrated more than 80 devices, half of them connected directly to the electrical network, i.e. they are repeaters, and I still have communication failures, a worrisome point;
                • My first impression is that Hubitat is slower than Vera, at least it has failed a lot with MSR. I see that MSR sends a command, and Hubitat ignores it, or doesn't execute all the action steps. I know there has already been some comment in this forum of interval times, I have to find the discussion and understand this detail, MSR flies and Hubitat walks, point of concern;
                • No doubt cleaner drives, attributes are only the main thing without loading a lot of unnecessary stuff as Vera has, but I complain again and have already put in support, the fact of not having the device_fault, or zwave_fault as an attribute to indicate failure is very bad. The option to use the community's APP, I didn't like at all, because everything involves a complexity that used to be easier to see in the Vera panel, and now with MSR's DynamicGroup it would be great to manage failures, bad point.

                Well, I hope this weekend I can have some time to dedicate to understanding what I can do to improve the Mesh network that they say Hubitat handles well, but that is not what I see.

                Well Patrick, waiting your ZWave-JS 🙂

                G 1 Reply Last reply
                0
                • wmarcolinW wmarcolin

                  @toggledbits

                  Completing one week of full Hubitat use, and a few comments:

                  • Dashboard assembly, super easy to use, lots of customization potential, I don't believe I have to use anything external, positive point;
                  • Undoubtedly better the part of drives to add devices, accepted S2 devices that with Vera I couldn't add, finally I believe I will use Zigbee devices, extremely favorable point;
                  • Despite being easy to add devices, very, very bad antenna signal. What covered my house quietly with Vera, I am having a very difficult time with the signal. It's been 5 days since I migrated more than 80 devices, half of them connected directly to the electrical network, i.e. they are repeaters, and I still have communication failures, a worrisome point;
                  • My first impression is that Hubitat is slower than Vera, at least it has failed a lot with MSR. I see that MSR sends a command, and Hubitat ignores it, or doesn't execute all the action steps. I know there has already been some comment in this forum of interval times, I have to find the discussion and understand this detail, MSR flies and Hubitat walks, point of concern;
                  • No doubt cleaner drives, attributes are only the main thing without loading a lot of unnecessary stuff as Vera has, but I complain again and have already put in support, the fact of not having the device_fault, or zwave_fault as an attribute to indicate failure is very bad. The option to use the community's APP, I didn't like at all, because everything involves a complexity that used to be easier to see in the Vera panel, and now with MSR's DynamicGroup it would be great to manage failures, bad point.

                  Well, I hope this weekend I can have some time to dedicate to understanding what I can do to improve the Mesh network that they say Hubitat handles well, but that is not what I see.

                  Well Patrick, waiting your ZWave-JS 🙂

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

                  @wmarcolin I did this migration over the last several months, finally turning off my Vera (to eliminate useless radio interference) just last week.

                  "My first impression is that Hubitat is slower than Vera"

                  That's interesting to me as my first thought was "wow, this thing is like greased lightning - it barely lets me finish a command and it's done", even when using the Alexa/Google/Homekit integrations which should be adding latency having to traverse the web and back.

                  I was heavily using the Reactor plugin in Vera along with two SiteSensors for calling weather APIs. I very recently replaced both of those SiteSensors with Expressions in MSR and they work flawlessly.

                  I do have H-A but it's mostly for dashboarding and my dislike toward paying another $5/month for another service from another hub to make my hub accessible online for status checks.

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

                  *HASS 2025.9.4
                  w/ ZST10-700 fw 7.18.3

                  *Prod MSR in docker/portainer
                  MSR: latest-25264-2fbe9217
                  MQTTController: 25139
                  ZWave Controller: 25139

                  wmarcolinW 1 Reply Last reply
                  0
                  • G gwp1

                    @wmarcolin I did this migration over the last several months, finally turning off my Vera (to eliminate useless radio interference) just last week.

                    "My first impression is that Hubitat is slower than Vera"

                    That's interesting to me as my first thought was "wow, this thing is like greased lightning - it barely lets me finish a command and it's done", even when using the Alexa/Google/Homekit integrations which should be adding latency having to traverse the web and back.

                    I was heavily using the Reactor plugin in Vera along with two SiteSensors for calling weather APIs. I very recently replaced both of those SiteSensors with Expressions in MSR and they work flawlessly.

                    I do have H-A but it's mostly for dashboarding and my dislike toward paying another $5/month for another service from another hub to make my hub accessible online for status checks.

                    wmarcolinW Offline
                    wmarcolinW Offline
                    wmarcolin
                    wrote on last edited by
                    #9

                    @gwp1

                    I really don't know if I did something very wrong, but I consider myself an experienced person, so what I am witnessing in my Hubitat is making me extremely worried.

                    See the report below that I just ran, 31 nodes failing.

                    633ffbae-3cb8-4f34-8300-f88914027483-image.png

                    You comment about leaving Reactor that I'm sure was happy, and now using MSR, this opens up a huge universe of possibilities, I'm really a fan, I just hope to have a hub at the same level as MSR.

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


                    Recent Topics

                    • Caution: zwave-js-ui docker 11.4.0 is broken
                      toggledbitsT
                      toggledbits
                      0
                      2
                      37

                    • [Reactor] Variables not updating correctly in latest-25201-2aa18550
                      toggledbitsT
                      toggledbits
                      0
                      68
                      4.9k

                    • Shelly Wall Display XL
                      therealdbT
                      therealdb
                      2
                      6
                      98

                    • Handling Dead Entities and Renamed Entities
                      PablaP
                      Pabla
                      0
                      5
                      88

                    • Strange behavior for MQTT templates using payload and attributes
                      toggledbitsT
                      toggledbits
                      0
                      6
                      138

                    • [MSR] reactor-mqtt-contrib package for additional MQTT templates
                      therealdbT
                      therealdb
                      1
                      46
                      8.3k

                    • HA 2025.9.4 Supported Yet?
                      toggledbitsT
                      toggledbits
                      0
                      2
                      91

                    • The reaction stopped working (Google Nest max playing a video)
                      toggledbitsT
                      toggledbits
                      0
                      7
                      359

                    • Rule Set UI bug - RESOLVED
                      toggledbitsT
                      toggledbits
                      1
                      2
                      234

                    • [Reactor] Copy&Paste of Rules
                      therealdbT
                      therealdb
                      0
                      1
                      301

                    • [Reactor] Help with screne controller cycling logic
                      toggledbitsT
                      toggledbits
                      0
                      5
                      405

                    • Stop the MSR by an external switch on Hubitat.
                      Tom_DT
                      Tom_D
                      0
                      6
                      740
                    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