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
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor
Device log?
G
@toggledbits is there a log that will show me what rule is turning on a specific device? I've got a switch that has been kicking on at 2200 ET for several nights now and the reactor.log doesn't have a thing in it that I can see on a device level (it being more rules-based).
Multi-System Reactor
Midnight crossing not working in date/time condition (build 25325)
tunnusT
Topic thumbnail image
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
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
Topic thumbnail image
Multi-System Reactor
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
Multi-System Reactor
Notice to Docker + ARM Users (RPi 3/4/5 and others)
toggledbitsT
This post does not apply to users of Intel/AMD-based systems. If you are using a Reactor image tagged latest-amd64 or stable-amd64, then this post does not apply to you. It also does not apply to bare-metal installs; it's for users of docker images on ARM-based systems only (principally Raspberry Pi hosts, but could be others). After January 15, 2026, I will no longer produce the aarch64-tagged docker image for Reactor. The ARM images will be arm64 for 64-bit operating systems, and armv7l for 32-bit operating systems. For those of you running a container from the aarch64 image today, this will be a relatively simple change: you just need to switch the image used for your docker container to a differently-tagged image. If you are using docker-compose, then this is a relatively simple matter of changing the image line in your docker-compose.yaml file and then stopping (docker-compose down) and restarting (docker-compose up -d) your Reactor daemon. But there's a catch... not all of you can safely just switch from the aarch64 image to the arm64 image. And, you can't just trust the output of uname -m, for example, because this exposes the CPU architecture, but not the word size of the OS running on that CPU. For Raspberry Pi systems, the transition to 64-bit operating systems was long (starting in 2016) and not always obvious — although there was a first "official" 64-bit OS for RPis in 2020, it did not become a default recommendation in the Raspberry Pi Imager until 2021, and then that was only the default for Pi 3/4 systems with >4GB RAM; it was 2022 before it was universally recommended for all 64-bit CPUs regardless of RAM size. Depending on when you first imaged your RPi system and what default you may have been offered/chosen, you could today easily have a 64-bit CPU Raspberry Pi running a 32-bit version of the operating system. Upgrades along the way would not change this; changing it to fully 64-bit requires a full reimage of the system. To establish if your OS is 64- or 32-bit, log in to your Pi and run: sudo dpkg-architecture -q DEB_HOST_ARCH. If the response is arm64 or aarch64, then you are running a 64-bit OS and you should use the arm64-tagged image. If it's anything else, you are running a 32-bit OS, and you should use the armv7l-tagged image. pi@rpi4-1:~ $ sudo dpkg-architecture -q DEB_HOST_ARCH armhf pi@rpi4-1:~ $ uname -m aarch64 pi@rpi4-1:~ $ In the example above, the uname command reports that the CPU is 64-bit architecture (aarch64), which is true for the host on which I ran these commands, but the DEB_HOST_ARCH value is armhf, indicating a 32-bit operating system. This system has to use the armv7l-tagged image. Other systems will have their own ways of determining the word size of the running OS. Since the majority of Reactor users running ARM systems are on Raspberry Pis, I am able to supply the above instructions, but if you happen to have a different ARM system, you'll need to do some web searching to figure out how to expose that information. Or, you can just try the arm64 image, and if it doesn't start up, try the armv7l image. Remember to always back up your system before making any changes. For everyone, please make this change as soon as possible, and if you have any trouble finding a working image, please (1) go back to the current aarch64 image; and (2) let me know in this thread along with as much detail about your host system as you can offer (including the output of the dpkg-architecture command mentioned above).
Multi-System Reactor
Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
M
Hi, I'm in the process of migrating from a Raspberry Pi 4 (ARMv7) to a Raspberry Pi 5 (ARMv8/aarch64), but I’ve run into an issue: there is no proper ARMv8/aarch64 image available. None of the existing images run on the Pi 5 - they all exit immediately with code 139 (segmentation fault), which typically indicates that the binaries inside the image are not compatible with the ARM64/aarch64 architecture used by the Pi 5. Would it be possible to publish a correct ARMv8/aarch64 (linux/arm64) image? Building one should be relatively straightforward using docker buildx with multi-arch support. For example, my own Node.js images are built this way: docker buildx build --push \ -t <localrepo>/<project>:<tag> \ --platform=linux/arm64,linux/amd64 \ --file ./apps/<project>/Dockerfile . This produces both the AMD64 and ARM64/v8 variants automatically. Also, as a side note, it may be best to avoid using Alpine as the base image for the ARM64 build, since musl-based builds often cause compatibility issues and unnecessary headaches. A glibc-based base image (e.g., Debian or Ubuntu) tends to work far more reliably on ARM64, especially for Node.js applications. @toggledbits - tagging you in case you missed this. Thanks, mgvra
Multi-System Reactor
Script action and custom timers
therealdbT
Sorry to write here without trying, but I’m flying today. Am I correct if i say that script action with alarm() makes it possible to execute a reaction in a given interval, lets say 15 seconds or 3.5 minutes? That sounds amazing, since I’ve used weird tricks, including a custom controller, just to do this.
Multi-System Reactor
Help resolve change in behaviour post update
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reactor w/HA 2025.11 error on set_datetime service call setting only time
CrilleC
@toggledbits Do you know if this is related to that PR or is it a change they made in 2025.11.1? [latest-25310]2025-11-11T13:16:24.319Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag with { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.320Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag action: { "type": "call_service", "service_data": { "date": (null), "time": "10:45", "datetime": (null), "timestamp": (null) }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_dag" } } [latest-25310]2025-11-11T13:16:24.321Z <HassController:ERR> HassController#hass request 1762866984320<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.321Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "10:45" }) on Entity#hass>input_datetime_vvb_dag failed! [latest-25310]2025-11-11T13:16:24.321Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"10:45","datetime":null,"timestamp":null},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_dag"},"id":1762866984320} [latest-25310]2025-11-11T13:16:24.322Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.322Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 0 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Engine#1 action args: { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 1 [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt with { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt action: { "type": "call_service", "service_data": { "date": (null), "time": "03:00", "datetime": (null), "timestamp": 0 }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_natt" } } [latest-25310]2025-11-11T13:16:24.324Z <HassController:ERR> HassController#hass request 1762866984323<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "03:00", "timestamp": 0 }) on Entity#hass>input_datetime_vvb_natt failed! [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"03:00","datetime":null,"timestamp":0},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_natt"},"id":1762866984323} [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.324Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 1 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <Engine:INFO> Engine#1 action args: { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 2 [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Sätt Schema VVB i Home Assistant<AKTIV> all actions completed.
Multi-System Reactor
Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
P
Hello, I currently have an office light (connected via a Leviton Zwave Dimmer switch) controlled from a Gen5 Aeotech Zwave switch installed on my Synology 720+ NAS. I run HA(2025.11.10) in a virtual machine from my NAS and Reactor on the container manager of the same NAS. Prior to updating to 25304 the rule I had set to turn the light on to a specific dimming value worked correctly. Now the rule appears to follow the decision tree, however the reaction does not trigger setting the dimming or turning on the office light? Strangely I can still turn the light on and off as well as dim it directly from HASS..? I have tried using the ''try this action'' button in the rules reaction setting and it will not control the light and does not throw an error flagÉ Please help, P.S Reactor has been rock steady for me over the last few years and I'm a big fan of this solution.
Multi-System Reactor
[Solved] alarm() in global expression throws error in log.
CrilleC
Topic thumbnail image
Multi-System Reactor
[Solved] Define function issue in latest-25304
CrilleC
Topic thumbnail image
Multi-System Reactor
No Upgrade Notification for Build 25308?
CatmanV2C
FWIW I'm no longer getting a notification from MSR that there's an update. Just thought I'd mention it C
Multi-System Reactor

Fail safe condition for battery devices

Scheduled Pinned Locked Moved Multi-System Reactor
29 Posts 3 Posters 5.6k 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.3.171
                                          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                                          *HASS 2025.12.2
                                          w/ HA Connect ZWA-2
                                          FW: v1.1
                                          SDK: v7.23.1

                                          *Prod MSR in docker/portainer
                                          MSR: latest-25328-b2ed1365
                                          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

                                          • Single protocol?
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            1
                                            11

                                          • Any thoughts on which is better
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            7
                                            112

                                          • Reactor Loading Screen Safari
                                            S
                                            SweetGenius
                                            0
                                            10
                                            133

                                          • Constraints states visually do not match actual
                                            S
                                            SweetGenius
                                            0
                                            3
                                            56

                                          • Oh the joy of pairing
                                            CatmanV2C
                                            CatmanV2
                                            2
                                            1
                                            40

                                          • HDMI oddness
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            1
                                            36

                                          • Home Assistant Connect ZWA-2 & ZBT-2
                                            therealdbT
                                            therealdb
                                            4
                                            14
                                            679

                                          • [MSR] Feature request: For Each action on arrays/groups
                                            therealdbT
                                            therealdb
                                            0
                                            7
                                            198

                                          • [Solved] Error: Command timeout
                                            toggledbitsT
                                            toggledbits
                                            0
                                            10
                                            508

                                          • Issue with MSR UI becoming unresponsive
                                            S
                                            sethlampman
                                            0
                                            7
                                            197

                                          • Date/time condition
                                            tunnusT
                                            tunnus
                                            0
                                            3
                                            140
                                          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