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. Rule to detect failed devices on an Ezlo hub?
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
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
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
[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

Rule to detect failed devices on an Ezlo hub?

Scheduled Pinned Locked Moved Multi-System Reactor
8 Posts 3 Posters 384 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.
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #1

    Hi

    Does anyone have an expression to detect failed devices on an Ezlo hub?

    This is how we did it for a Vera hub here.

    Thanks

    1 Reply Last reply
    0
    • cw-kidC Offline
      cw-kidC Offline
      cw-kid
      wrote on last edited by cw-kid
      #2

      This is a currently failed device on my Ezlo Plus

      battery_power.level=1
      battery_power.since=1648664932056
      humidity_sensor.units="%"
      humidity_sensor.value=65.9700012207031
      x_ezlo_device.battery_powered=true
      x_ezlo_device.category="humidity"
      x_ezlo_device.manufacturer="CentraLite"
      x_ezlo_device.model="3310-G"
      x_ezlo_device.parent=""
      x_ezlo_device.reachable=false
      x_ezlo_device.ready=true
      x_ezlo_device.room="61f08bdc123e431284c13fbc"
      x_ezlo_device.status="idle"
      x_ezlo_device.subcategory=""
      x_ezlo_device.type_id="CentraLite_3310-G"
      x_ezlo_item.battery=100
      x_ezlo_item.humidity=65.9700012207031
      x_ezlo_object.id="61f0bbbf123e4312a1900a18"
      Capabilities: battery_power, humidity_sensor, x_ezlo_device, x_ezlo_item, x_ezlo_object
      Actions: x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check
      

      x_ezlo_device.reachable=false

      Its a Zigbee device if that makes any difference.

      CrilleC 1 Reply Last reply
      0
      • cw-kidC cw-kid

        This is a currently failed device on my Ezlo Plus

        battery_power.level=1
        battery_power.since=1648664932056
        humidity_sensor.units="%"
        humidity_sensor.value=65.9700012207031
        x_ezlo_device.battery_powered=true
        x_ezlo_device.category="humidity"
        x_ezlo_device.manufacturer="CentraLite"
        x_ezlo_device.model="3310-G"
        x_ezlo_device.parent=""
        x_ezlo_device.reachable=false
        x_ezlo_device.ready=true
        x_ezlo_device.room="61f08bdc123e431284c13fbc"
        x_ezlo_device.status="idle"
        x_ezlo_device.subcategory=""
        x_ezlo_device.type_id="CentraLite_3310-G"
        x_ezlo_item.battery=100
        x_ezlo_item.humidity=65.9700012207031
        x_ezlo_object.id="61f0bbbf123e4312a1900a18"
        Capabilities: battery_power, humidity_sensor, x_ezlo_device, x_ezlo_item, x_ezlo_object
        Actions: x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check
        

        x_ezlo_device.reachable=false

        Its a Zigbee device if that makes any difference.

        CrilleC Offline
        CrilleC Offline
        Crille
        wrote on last edited by Crille
        #3

        @cw-kid I'm doing it like this. There may be better ways but this works for me.

        I have a dynamic group for unreachable devices.

         - id: groups
           name: Dynamic Group Controller
           enable: true
           implementation: DynamicGroupController
           config:
             groups:
               "UnreachableEzloDevices":
                 name: Ezlo Devices Not Responding
                 select:
                   - include_controller: ezlo
                   - include_capability: x_ezlo_device
                 filter_expression: entity.attributes.x_ezlo_device.reachable != true
        

        Then a global expression for the devices.

        global_expression_ezlo.PNG

        In the rule I have this setup.
        trigger1.PNG trigger2.PNG

        reaction.PNG

        local_expressions.PNG

        The global variable prevEzloDevicesNotResponding is set to keep track of number of devices that are unreachable.
        The local variable Send is used to only send a notification if the number of unreachable devices is increasing or is back to zero, since after a reboot of the controller, all Zigbee devices is marked as unreachable until physically power toggled and I don't need a notification of a decreased array every time a device is reachable again until they all are.

        Hope this gives you some ideas.

        cw-kidC 1 Reply Last reply
        0
        • CrilleC Crille

          @cw-kid I'm doing it like this. There may be better ways but this works for me.

          I have a dynamic group for unreachable devices.

           - id: groups
             name: Dynamic Group Controller
             enable: true
             implementation: DynamicGroupController
             config:
               groups:
                 "UnreachableEzloDevices":
                   name: Ezlo Devices Not Responding
                   select:
                     - include_controller: ezlo
                     - include_capability: x_ezlo_device
                   filter_expression: entity.attributes.x_ezlo_device.reachable != true
          

          Then a global expression for the devices.

          global_expression_ezlo.PNG

          In the rule I have this setup.
          trigger1.PNG trigger2.PNG

          reaction.PNG

          local_expressions.PNG

          The global variable prevEzloDevicesNotResponding is set to keep track of number of devices that are unreachable.
          The local variable Send is used to only send a notification if the number of unreachable devices is increasing or is back to zero, since after a reboot of the controller, all Zigbee devices is marked as unreachable until physically power toggled and I don't need a notification of a decreased array every time a device is reachable again until they all are.

          Hope this gives you some ideas.

          cw-kidC Offline
          cw-kidC Offline
          cw-kid
          wrote on last edited by
          #4

          @crille

          Thanks for the detailed information.

          However after adding the group in to my reactor.yaml file MSR no longer starts or runs.

          My controller is called Ezlo_Plus

          0d6e11fc-7bbb-4b1f-9871-f5e8e098f5af-image.png

          I've tried both "Ezlo_Plus" and "ezlo_plus"

          - id: groups
              name: Dynamic Group Controller
              enable: true
              implementation: DynamicGroupController
              config:
                groups:
                  "UnreachableEzloDevices":
                    name: Ezlo Devices Not Responding
                    select:
                      - include_controller: Ezlo_Plus
                      - include_capability: x_ezlo_device
                    filter_expression: entity.attributes.x_ezlo_device.reachable != true
          

          Does it matter where abouts in the reactor.yaml file you add this code? I just added it in the Controllers section after my last "enabled" controller .

          Thanks.

          CrilleC 1 Reply Last reply
          0
          • cw-kidC Offline
            cw-kidC Offline
            cw-kid
            wrote on last edited by
            #5

            Alternatively doing it the "old" way without using a Dynamic Group these two expressions seem to work and are correctly returning the names of the two currently failed devices on my Ezlo Plus Controller:

            3c25519b-ed40-4b46-bf1f-cb2076b5f6c1-image.png

            FailedEzlo:

            each id in matchEntities( { capability: 'x_ezlo_device' } ):
                         ( getEntity(id)?.attributes.x_ezlo_device.reachable ) !=true ? id : null
            

            FailedNamesEzlo:

            join( each id in FailedEzlo: getEntity(id)?.name ?? id, ", " )
            
            1 Reply Last reply
            0
            • cw-kidC cw-kid

              @crille

              Thanks for the detailed information.

              However after adding the group in to my reactor.yaml file MSR no longer starts or runs.

              My controller is called Ezlo_Plus

              0d6e11fc-7bbb-4b1f-9871-f5e8e098f5af-image.png

              I've tried both "Ezlo_Plus" and "ezlo_plus"

              - id: groups
                  name: Dynamic Group Controller
                  enable: true
                  implementation: DynamicGroupController
                  config:
                    groups:
                      "UnreachableEzloDevices":
                        name: Ezlo Devices Not Responding
                        select:
                          - include_controller: Ezlo_Plus
                          - include_capability: x_ezlo_device
                        filter_expression: entity.attributes.x_ezlo_device.reachable != true
              

              Does it matter where abouts in the reactor.yaml file you add this code? I just added it in the Controllers section after my last "enabled" controller .

              Thanks.

              CrilleC Offline
              CrilleC Offline
              Crille
              wrote on last edited by Crille
              #6

              @cw-kid The indentation of the groups controller was off in my post. I've corrected it. Please try again with correct indentation and your Reactor should start.
              The groups controller is in the right place in your config and include_controller should be the id of the Ezlo Plus controller.

              cw-kidC 1 Reply Last reply
              1
              • CrilleC Crille

                @cw-kid The indentation of the groups controller was off in my post. I've corrected it. Please try again with correct indentation and your Reactor should start.
                The groups controller is in the right place in your config and include_controller should be the id of the Ezlo Plus controller.

                cw-kidC Offline
                cw-kidC Offline
                cw-kid
                wrote on last edited by
                #7

                @crille

                Great thanks I will try it again.

                I've not used Dynamic Groups before either, so you are giving me a good tutorial !

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

                  Any time you edit a config file and then Reactor doesn't start, you've likely corrupted the file. There's a troubleshooting section for startup in the documentation that will help you look at the logs (yes, once again, go look at the logs), and there are tools like https://yamlchecker.com that will also help you find errors, and there's this handy YAML editor https://onlineyamltools.com/edit-yaml

                  Edit: I wanted to add here that I routinely break my config files, so as fluent as I consider myself to be with YAML (begrudgingly, I'll admit), it's just touchy and mistakes are easy to make. I am working on a graphical editor for settings in the background, but it's a huge undertaking and a bit of an "all or nothing" deal, so it's got a long road ahead of it (or, really, I do).

                  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
                  3
                  • toggledbitsT toggledbits locked this topic on
                  Reply
                  • Reply as topic
                  Log in to reply
                  • Oldest to Newest
                  • Newest to Oldest
                  • Most Votes


                  Recent Topics

                  • Errors after updating to MQTTController build 25139
                    toggledbitsT
                    toggledbits
                    0
                    2
                    9

                  • Set Reaction > Script Action
                    toggledbitsT
                    toggledbits
                    0
                    4
                    25

                  • Wiring Samotech SM308-S into light fitting
                    F
                    Freemanator
                    0
                    1
                    9

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

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

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

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

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

                  • Disaster recovery and virtualisation
                    CatmanV2C
                    CatmanV2
                    0
                    5
                    688

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

                  • Organizing/ structuring rule sets and rules
                    G
                    gwp1
                    0
                    5
                    396
                  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