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. Fail safe condition for battery devices
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
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
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
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
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

Fail safe condition for battery devices

Scheduled Pinned Locked Moved Multi-System Reactor
29 Posts 3 Posters 3.1k 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.
  • T tamorgen

    Good morning,
    I'm trying to figure out if there is a way to evaluate if a command was completed and retry if it did not complete.

    I have 14 iBlinds 3.1 z-wave controllers in my home. 95% of the time, they work just fine. Occasionally, I'll get a blind that does not open on the first attempt. When I go into Home Assistant, and manually open or close the blind, it works.

    I have 3 reactions set up for each room. One to open, one to close, and one partial open for sun glare. Each of them is set up as below.

    5afc9924-4300-4718-9e23-8855c4a3a9fd-image.png

    The reactions are set up to wait for 5 seconds before going onto the next blind, so the z-wave network doesn't get overwhelmed.

    In addition, the set command to run the reactions has "Wait for completion" checked.

    3919fc06-c1f1-4c49-bf95-716028d18a27-image.png

    I also have a routine set up whenever a z-wave device reports as non-functional (dead), it'll get pinged to wake it up. This usually works to wake them up.

    16df4bff-c733-4ec2-a55c-c964238ada3b-image.png

    Appreciate any ideas to make this more reliable.

    I'm running:

    • Reactor latest-24190-bd310acc, Bare-metal on Fedora
    • WaveJSController [0.1.23326]
    • Home Assistant: 2024.7.0
    toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by toggledbits
    #2

    @tamorgen said in Fail safe condition for battery devices:

    Appreciate any ideas to make this more reliable.

    Have you considered using a "while" group? Here's a simple example in a Reaction. You can embellish on this for more reliability:

    6b887c6c-e42c-4d76-ac77-6b6f00078261-image.png

    The first action forces a refresh on the device, and the delay gives it a little time to settle. From there, the Repeat...While runs while the lock remains unlocked... it tries to lock the lock, and then waits a minute and will try again if the lock remains unlocked. You could add a refresh inside the loop as well.

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

    T 1 Reply Last reply
    0
    • toggledbitsT toggledbits

      @tamorgen said in Fail safe condition for battery devices:

      Appreciate any ideas to make this more reliable.

      Have you considered using a "while" group? Here's a simple example in a Reaction. You can embellish on this for more reliability:

      6b887c6c-e42c-4d76-ac77-6b6f00078261-image.png

      The first action forces a refresh on the device, and the delay gives it a little time to settle. From there, the Repeat...While runs while the lock remains unlocked... it tries to lock the lock, and then waits a minute and will try again if the lock remains unlocked. You could add a refresh inside the loop as well.

      T Offline
      T Offline
      tamorgen
      wrote on last edited by tamorgen
      #3

      @toggledbits
      Thanks Patrick. That's exactly what I was looking for. I didn't even know about that Repeat While condition....

      9060f80b-2ef0-498f-a9a9-77f32e67479f-image.png

      2 blinds down, 12 to go..... Oh, multiply by 3.... open, close, sun.

      This may take a while.

      1 Reply Last reply
      0
      • T Offline
        T Offline
        tamorgen
        wrote on last edited by
        #4

        Okay, I may have spoke to soon.... the first blind in the series keeps opening and closing when I run it.

        image.png

        The idea here.... the repeat while checks for the position.... If it does not equal 0 (range is 0-100), then it is open. The action is cover.close, and then delay for 10 seconds before going on to the next one.

        What could it be causing it to be stuck in the loop? I'm monitoring what it's doing, and the Current value: (number) changes between 0 and 50, whereas 50 being the open position.

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

          The iBlinds 3.x implementation in ZWaveJSController commands 99 for close, not 0. Try using position.set with 0 instead.

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

          T 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            The iBlinds 3.x implementation in ZWaveJSController commands 99 for close, not 0. Try using position.set with 0 instead.

            T Offline
            T Offline
            tamorgen
            wrote on last edited by tamorgen
            #6

            @toggledbits said in Fail safe condition for battery devices:

            The iBlinds 3.x implementation in ZWaveJSController commands 99 for close, not 0. Try using position.set with 0 instead.

            Not quite working either. Position 99 is Closed, down inside. Position 0 is Closed, up inside. The cover.open and cover.close commands work in my previous iteration. When I try and use the position.set command, I get unexpected results.

            Below is the corresponding Open version. When I set the position.set to 50, which is 50% (halfway between 0 & 99, so the blinds are flat and fully open, it set's the position to 99, not 50.

            8f628ae2-295d-44bd-891e-6e025afb7076-image.png

            If I use position.set to 1, the current value changes to 99, so for opening the blinds to that 50 value, position.set does not appear to be appropriate.

            ffab6c64-40fd-4027-9fab-010397715e4c-image.png

            iBlinds now uses the Window Covering command class and not the previously used multilevel switch window class, which works fine for roller blinds, but not horizontal blinds.

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

              Sorry, I erred... try using values in the range of 0 to 1 (so 50 = 0.5) for position.set.

              I would also be consistent and not use the extended attributes (x_zwave_values...), but rather position.value and/or cover.state.

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

              T 1 Reply Last reply
              0
              • toggledbitsT toggledbits

                Sorry, I erred... try using values in the range of 0 to 1 (so 50 = 0.5) for position.set.

                I would also be consistent and not use the extended attributes (x_zwave_values...), but rather position.value and/or cover.state.

                T Offline
                T Offline
                tamorgen
                wrote on last edited by
                #8

                @toggledbits said in Fail safe condition for battery devices:

                Sorry, I erred... try using values in the range of 0 to 1 (so 50 = 0.5) for position.set.

                I would also be consistent and not use the extended attributes (x_zwave_values...), but rather position.value and/or cover.state.

                That makes sense. The cover.state is a True/False value, so I'm not quite sure what that does.

                I've revised it, and I've extended the delay times out a bit. The first blind opens correctly, but the second one opens, and then closes itself again. I'm really perpelexed as to why.

                200c80a6-3a19-44b7-b025-88d33b22d4e9-image.png

                toggledbitsT 1 Reply Last reply
                0
                • T tamorgen

                  @toggledbits said in Fail safe condition for battery devices:

                  Sorry, I erred... try using values in the range of 0 to 1 (so 50 = 0.5) for position.set.

                  I would also be consistent and not use the extended attributes (x_zwave_values...), but rather position.value and/or cover.state.

                  That makes sense. The cover.state is a True/False value, so I'm not quite sure what that does.

                  I've revised it, and I've extended the delay times out a bit. The first blind opens correctly, but the second one opens, and then closes itself again. I'm really perpelexed as to why.

                  200c80a6-3a19-44b7-b025-88d33b22d4e9-image.png

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

                  @tamorgen said in Fail safe condition for battery devices:

                  That makes sense. The cover.state is a True/False value, so I'm not quite sure what that does.

                  Can you also post the full attributes for this device (using the Copy Attributes button)?

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

                  T 1 Reply Last reply
                  0
                  • toggledbitsT toggledbits

                    @tamorgen said in Fail safe condition for battery devices:

                    That makes sense. The cover.state is a True/False value, so I'm not quite sure what that does.

                    Can you also post the full attributes for this device (using the Copy Attributes button)?

                    T Offline
                    T Offline
                    tamorgen
                    wrote on last edited by toggledbits
                    #10

                    @toggledbits said in Fail safe condition for battery devices:

                    Can you also post the full attributes for this device (using the Copy Attributes button)?

                    Here you go:

                    battery_power.level=0.9
                    battery_power.since=1721846488511
                    cover.state=false
                    position.value=0
                    x_debug.dt={"entity_class":"Cover","match":"deviceClass.generic.key=17;deviceClass.specific.key=7","capabilities":["cover","toggle","position"],"primary_attribute":"cover.state","description":"Window Blind Controller","model":"iblinds V3","default_name":"Window Blind Controller","values":[{"valueId":"38:currentValue:","capabilities":{"cover":{"attributes":{"state":{"expr":"!(value == 0 || value >= 99)"}},"actions":{"open":{"valueId":"38:targetValue:","value":50},"close":{"valueId":"38:targetValue:","value":99},"stop":false}},"position":{"attributes":{"value":{"expr":"round( value / 99, 2 )"}},"actions":{"set":{"valueId":"38:targetValue","value":{"expr":"max( 0, min( 99, round( 100 * ( parameters.value ?# 0 ), 0 ) ) )"}},"increase":{"valueId":"38:targetValue","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) + ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}},"decrease":{"valueId":"38:targetValue","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) - ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}},"relative":{"valueId":"38:targetValue","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) + ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}}}},"toggle":{"actions":{"toggle":{"valueId":"38:targetValue:","value":{"expr":"entity.attributes.cover.state ? 99 : 50"}}}}}}],"manufacturerId":647,"productType":4,"productId":113}
                    x_zwave_values.Battery_isLow=false
                    x_zwave_values.Battery_level=90
                    x_zwave_values.Configuration_Close_Interval=15
                    x_zwave_values.Configuration_Default_ON_Value=50
                    x_zwave_values.Configuration_MC=1
                    x_zwave_values.Configuration_Maximum_Tilt_Level=null
                    x_zwave_values.Configuration_Minimum_Tilt_Level=null
                    x_zwave_values.Configuration_Movement_Duration=0
                    x_zwave_values.Configuration_Override_Response_to_ON_Command=null
                    x_zwave_values.Configuration_Remote_Calibration=1
                    x_zwave_values.Configuration_Reset_Button=0
                    x_zwave_values.Configuration_Reverse_Direction=0
                    x_zwave_values.Configuration_Send_Reports=0
                    x_zwave_values.Indicator_Node_Identify_3=0
                    x_zwave_values.Indicator_Node_Identify_4=0
                    x_zwave_values.Indicator_Node_Identify_5=0
                    x_zwave_values.Indicator_identify=null
                    x_zwave_values.Indicator_timeout=null
                    x_zwave_values.Indicator_value=null
                    x_zwave_values.Manufacturer_Specific_manufacturerId=647
                    x_zwave_values.Manufacturer_Specific_productId=114
                    x_zwave_values.Manufacturer_Specific_productType=4
                    x_zwave_values.Version_applicationBuildNumber=43707
                    x_zwave_values.Version_applicationFrameworkAPIVersion="3.12.1"
                    x_zwave_values.Version_applicationFrameworkBuildNumber=35
                    x_zwave_values.Version_applicationVersion="3.12.1"
                    x_zwave_values.Version_firmwareVersions=["3.12"]
                    x_zwave_values.Version_hardwareVersion=2
                    x_zwave_values.Version_hostInterfaceBuildNumber=0
                    x_zwave_values.Version_hostInterfaceVersion="unused"
                    x_zwave_values.Version_libraryType=3
                    x_zwave_values.Version_protocolVersion="7.12"
                    x_zwave_values.Version_sdkVersion="7.12.2"
                    x_zwave_values.Version_zWaveProtocolBuildNumber=35
                    x_zwave_values.Version_zWaveProtocolVersion="7.12.2"
                    x_zwave_values.Window_Covering_currentValue_23=0
                    x_zwave_values.Window_Covering_duration_23={"value":0,"unit":"seconds"}
                    x_zwave_values.Window_Covering_levelChangeDown_23=null
                    x_zwave_values.Window_Covering_levelChangeUp_23=null
                    x_zwave_values.Window_Covering_targetValue_23=0
                    zwave_device.capabilities=[106,112,114,128,134,135]
                    zwave_device.endpoint=0
                    zwave_device.failed=false
                    zwave_device.generic_class="Multilevel Switch"
                    zwave_device.impl_sig="23326:1:23260:1"
                    zwave_device.is_beaming=false
                    zwave_device.is_listening=false
                    zwave_device.is_routing=true
                    zwave_device.is_secure=true
                    zwave_device.manufacturer_info=[647,4,114]
                    zwave_device.max_data_rate=null
                    zwave_device.node_id=80
                    zwave_device.specific_class="Motor Control Class C"
                    zwave_device.status=4
                    zwave_device.status_text="alive"
                    zwave_device.version_info=[null,"3.12.1"]
                    
                    1 Reply Last reply
                    0
                    • toggledbitsT Offline
                      toggledbitsT Offline
                      toggledbits
                      wrote on last edited by
                      #11

                      So is it 80 or 81 that's not staying in the expected state?

                      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
                      • T Offline
                        T Offline
                        tamorgen
                        wrote on last edited by
                        #12

                        80, which is the second one

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

                          Can you command 80 from the Entities list using the same actions and values?

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

                          T 1 Reply Last reply
                          0
                          • toggledbitsT toggledbits

                            Can you command 80 from the Entities list using the same actions and values?

                            T Offline
                            T Offline
                            tamorgen
                            wrote on last edited by
                            #14

                            @toggledbits said in Fail safe condition for battery devices:

                            Can you command 80 from the Entities list using the same actions and values?

                            Yes, it opens to 50% using position.set .50

                            When I use the reaction, it does change to .5, but then changes back after 20 or 30 seconds.

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

                              Is there a rule that could be triggered by the shade moving that's still active?

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

                              T 1 Reply Last reply
                              0
                              • toggledbitsT toggledbits

                                Is there a rule that could be triggered by the shade moving that's still active?

                                T Offline
                                T Offline
                                tamorgen
                                wrote on last edited by tamorgen
                                #16

                                @toggledbits said in Fail safe condition for battery devices:

                                Is there a rule that could be triggered by the shade moving that's still active?

                                I don't believe so. I believe I would see other rules flashing active/green, were that to happen. If that was the case, manually doing it either through HA or through the entities tab, like you just had me do, would cause that reaction as well.

                                BTW, that was one of the first things I thought of. I had two separate reactor windows open, so I could monitor the Reactions tab, as well as the Blinds Rule Set rules simultaneously.

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

                                  Perhaps, but there's no command setting to closed in that reaction, either.

                                  Another way to look at this is to open a second tab for Reactor, and stay on the Status page with the Running Reactions widget displayed. If the blind closes after the Reaction has stopped running, that suggests the command to close it is coming from elsewhere.

                                  And of course, any time things don't look as expected, you should always be looking in the logs.

                                  Edit: based on your edit, I'd make sure all rules doing anything with blinds are disabled during this testing.

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

                                  toggledbitsT 1 Reply Last reply
                                  0
                                  • toggledbitsT toggledbits

                                    Perhaps, but there's no command setting to closed in that reaction, either.

                                    Another way to look at this is to open a second tab for Reactor, and stay on the Status page with the Running Reactions widget displayed. If the blind closes after the Reaction has stopped running, that suggests the command to close it is coming from elsewhere.

                                    And of course, any time things don't look as expected, you should always be looking in the logs.

                                    Edit: based on your edit, I'd make sure all rules doing anything with blinds are disabled during this testing.

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

                                    @toggledbits said in Fail safe condition for battery devices:

                                    Perhaps, but there's no command setting to closed in that reaction, either.

                                    WAIT -- WHAT'S THIS???

                                    6ddcbd6e-4043-42c4-b446-0e1fc7773f76-200c80a6-3a19-44b7-b025-88d33b22d4e9-image.png

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

                                    T 1 Reply Last reply
                                    0
                                    • toggledbitsT toggledbits

                                      @toggledbits said in Fail safe condition for battery devices:

                                      Perhaps, but there's no command setting to closed in that reaction, either.

                                      WAIT -- WHAT'S THIS???

                                      6ddcbd6e-4043-42c4-b446-0e1fc7773f76-200c80a6-3a19-44b7-b025-88d33b22d4e9-image.png

                                      T Offline
                                      T Offline
                                      tamorgen
                                      wrote on last edited by
                                      #19

                                      @toggledbits,

                                      That would be me dying of embarrassment. I'm not sure how that got there.

                                      Removed and surprise surprise, works fine.

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

                                        Whew! All good!

                                        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
                                        • G Offline
                                          G Offline
                                          gwp1
                                          wrote on last edited by
                                          #21

                                          Best thread ever given I have 13 iblinds and they get... cranky/fussy.

                                          I'm going to pile onto the "wait, I never knew about Repeat While - when was this added @toggledbits ?

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

                                          *HASS 2025.6.0
                                          w/ ZST10-700 fw 7.18.3

                                          *Prod MSR in docker/portainer
                                          MSR: latest-25139-fbd67abc
                                          MQTTController: 25139
                                          ZWave Controller: 25139

                                          T 1 Reply Last reply
                                          1
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Recent Topics

                                          • Gradually turn on lights.
                                            G
                                            gwp1
                                            0
                                            4
                                            204

                                          • Stop the MSR by an external switch on Hubitat.
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            1
                                            52

                                          • Error After Upgrade
                                            G
                                            gwp1
                                            0
                                            4
                                            130

                                          • Reset attribute value of entity in event handler
                                            R
                                            RHCPNG
                                            0
                                            5
                                            242

                                          • Need help figuring out how to delay a reset on reaction
                                            G
                                            gwp1
                                            0
                                            22
                                            986

                                          • Way to search for rules (rule state) in other rules
                                            T
                                            tamorgen
                                            0
                                            3
                                            123

                                          • Links to MSR from HA
                                            Tom_DT
                                            Tom_D
                                            0
                                            1
                                            112

                                          • Set Reaction > Script Action
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            11
                                            465

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

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

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

                                          • Advice reqeusted to migrate MSR from Bare Metal to Container
                                            T
                                            tamorgen
                                            0
                                            5
                                            290
                                          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