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. Recommendation for new hub
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
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

Recommendation for new hub

Scheduled Pinned Locked Moved Multi-System Reactor
7 Posts 6 Posters 505 Views 8 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.
  • S Offline
    S Offline
    sebby
    wrote on last edited by
    #1

    My trusty vera plus is starting to have some issues that are making me think that it is about to die. i now get constant luup reloads even though i've moved almost everything except for z-wave devices and the iphone locator off that machine. it is even booting off an ssd drive to minimize wear and tear on the internal memory. I've moved all my logic off box to MSR, so it is just a glorified zwave adapter. I would love to hear any ideas that would make moving 60ish devices off that box to something else as painless as possible. the thought of excluding and including the devices sends shivers down my spine, so anything that helps me migrate the network would be greatly welcomed. anyone have any suggestions?

    1 Reply Last reply
    0
    • G Offline
      G Offline
      gwp1
      wrote on last edited by
      #2

      I, too, moved ~50 devices from my VeraSecure to my Hubitat. It wasn't as daunting as you think, tbh. I did it over the period of a couple months (from the sounds of things you may not have quite that long) but it's really just a matter of taking 15:, 20: a day and doing the needful.

      For me, plugging them into the existing rulesets was more painful - but even that wasn't awful.

      *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
      • A Offline
        A Offline
        Alan_F
        wrote on last edited by
        #3

        I also recently made the switch from VeraPlus to Hubitat, and now have some very simple rules running on the Hubitat and more complex rules running on MSR and Node-Red.

        I had some flood/leak sensors that I bought in anticipation of them being integrated into the next Vera firmware release, and then that release never came out of beta. Then I had an issue with devices disconnecting that was probably related to the Vera running out of storage space. Support was able to fix it, but that was the thing that pushed me over the edge to make the platform switch. I'm still maintaining a VeraPlus with a pretty simple setup at my parents' house, and plan to keep that one running as long as it keeps working with my old one serving as a backup if theirs ever fails. My VeraPlus is still powered on for the moment, but there are no z-wave devices on it, all it is doing is logging some data into Datamine2.

        It took a few days and some searching online to figure out some quirks on the Hubitat, but there is enough of a user community that I have always quickly found a thread that pointed me in the right direction. I was able to recreate everything I was doing on the Vera and more.

        The biggest plus for me is that I have some Sengled Zigbee lights and the VeraPlus Zigbee hub didn't work with their RGB functions, so I had to have a Sengled hub connected to those. While I could do some integration to them via the Sengled API and Python scripting, they were totally cloud dependent. Within a week of getting them connected locally to the Hubitat, Sengled had an extended server outage that would have left those lights uncontrollable (other than the wall switch) for a day or so. Since they're connected to the Hubitat, the outage didn't affect me.

        So my setup now is a Hubitat C-7 and a RPi4 that is running Node-Red on 'bare metal', plus Reactor, InfluxDB / Chronograf / Telegraf (which I haven't had time to figure out yet), Portainer, MQTT, and Gotify (for self-hosted push notifications) running under Docker.

        When you count Z-Wave, Zigbee, WiFi lights, virtual devices, device groups, smart home speakers, and phone apps - all of which count as devices on the Hubitat - I have 80 devices on the hub.

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

          Hi @sebby

          Come be happy with Hubitat, unfortunately, we have been orphaned by Vera, who was useful to us for a long time, but the new owners have buried her evolution.

          I am two weeks into the moving process, my first impression of the Hubitat is excellent, I have to migrate almost 100 devices, and it has been a lot of work. First I have to find the manual on the internet, show how to reset to factory settings, and then add to Hubitat, but it is worth the sacrifice, the perception I have that now the devices respond better, and of course my biggest problem with S2 devices that did not work on the Vera, now they all work on Hubitat. I won't even talk about Zigbee which never worked on the Vera.

          The biggest work I am having is adjusting about 80 routines I have in MSR, I don't use anything in the hub, even a simple rule of opening a door and turning on a light I am using MSR. I am doing this to ensure that the hub is as light as possible. When deleting from Vera, I have to search in MSR where I used the device and adjust for the new one in Hubitat. Now there is a good thing, over time I have improved my rules, so in this device tuning revision, I have made improvements and optimizations.

          @Alan_F 's comment about the community is also important, they have a collection of discussions that help a lot in the first steps, I find it hard to search for things, but when I find it, it has been useful in understanding the installation of devices, or APP that can help.

          Now there are some critical points about Hubitat in my opinion:

          • The Z-wave antenna power is lower than the Vera, and this forced me to have repeaters, which did not exist before;
          • In another thread, I comment on the lack of control over device failure. In the Vera if a device does not respond in a certain time, there is a failure indication, in Hubitat it seems that it is an APP, I have not reached this point yet;
          • I am already missing @toggledbits 's Switchboard Plugin, it seems that there is also an APP to do this, but again, you have to look in the community;
          • The dashboard out-of-the-box is very simple and practical, but you have to assemble everything, and the ease with which Vera already has everything ready is over, even with limitations, it at least facilitates the general management of devices. Maybe there is also an APP, I still have to find out;
          • Finally, it is not a big problem, but the automatic integration of MSR with Vera helps a lot. In Hubitat there is a publishing process that bothers me, I hope one-day @toggledbits can align with Hubitat people and have it straight.

          In summary, the change is in my opinion almost inevitable, there is work to be done, but so far I think the results have been good and the effort acceptable for the benefit of having more stability, better and more complete new device drives.

          Thanks.

          1 Reply Last reply
          0
          • PerHP Offline
            PerHP Offline
            PerH
            wrote on last edited by
            #5

            I went from VeraPlus to the combination openLuup(lead), Z-Way and Domoticz, with MSR for automation. Mostly because i was happy with the openluup interface, and there was good integration to Z-way, which is one of the best z-wave handlers i think. Haven't seen any other that match the "Expert" panel in z-way..

            Domoticz has a very good plugin for Zigate, and some other integrations like Tibber and Xiaomi vacuum. RFXtrx433 is hooked to openLuup directly for temperature sensors.

            Not the simplest path, but it's working very well! I could probably simplify this with i.e. Home assistant, but when i tried it, the zigbee pluigns weren't up to speed in my opinion.

            1 Reply Last reply
            1
            • S Offline
              S Offline
              sebby
              wrote on last edited by
              #6

              thanks all for the feedback. I will check out Hubitat and see how it does.

              1 Reply Last reply
              0
              • Black CatB Offline
                Black CatB Offline
                Black Cat
                wrote on last edited by
                #7

                I went for Homeseer, I liked you could run it local either on Windows or roll your own PC with 30 days to try it out.
                Horses for courses, what suits one doesn't suit the other.

                aka Zedrally

                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

                • Set Reaction > Script Action
                  therealdbT
                  therealdb
                  0
                  6
                  78

                • Wiring Samotech SM308-S into light fitting
                  akbooerA
                  akbooer
                  0
                  2
                  41

                • Errors after updating to MQTTController build 25139
                  toggledbitsT
                  toggledbits
                  0
                  6
                  72

                • 🎉 My very first MSR controller: OpenSprinkler
                  therealdbT
                  therealdb
                  5
                  13
                  631

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

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

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

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

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

                • Disaster recovery and virtualisation
                  CatmanV2C
                  CatmanV2
                  0
                  5
                  699

                • Remote access of Zwave stick from Z-wave server
                  CatmanV2C
                  CatmanV2
                  0
                  3
                  426
                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