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. Catch-all lights rule
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor

Catch-all lights rule

Scheduled Pinned Locked Moved Multi-System Reactor
7 Posts 2 Posters 454 Views 2 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.
  • G Offline
    G Offline
    gwp1
    wrote on last edited by gwp1
    #1

    Background: this is a Windows MSR install I've done for our local pool/amenity center just to run some fans and lights (not my daily driver at home). Install went perfectly fine.

    Scenario: I want the lights to go on when it's dark enough (even if during a storm, not just after sunset) so I'm using solarRadiation from my weather station to drive that Trigger. Easy stuff.

    Issue: sometimes, someone goes in the office and just starts flipping switches and the result can be lights turned on in the daytime or off at night. I'm trying to create a "catch-all" wherein if it is daytime and the lights somehow find their way ON, they will turn themselves back OFF.

    I have the following Reaction built:

    b30eab5b-5a14-4a3a-8c9a-47e3e7e53dc3-image.png

    I also have this Reaction for opposite, ie the lights find themselves turned off after dark and they will turn themselves back on:

    5c6946b1-297c-4eb1-9618-74820979df29-image.png

    Here are my two rules:

    288cba86-f941-4157-86d9-d8e7487905f7-image.png *NOTE that in my manual testing, ie I turn on the light switch at the incorrect time, when the solarRadiation level changes the Lights ON rule flags and shows as SET. On the next change of solarRadiation it goes back to reset again.

    My expectation is that Lights OFF rule should see the lights are on, the solarRadiation is above the set limit, and turn them off. Instead, every other run, the ON rule moves to SET and then reset again on the following run.

    Logs appear angry:

    [latest-25016]2025-01-26T22:03:31.696Z <Engine:INFO> Enqueueing "Lights ON<RESET>" (rule-m6e4ajh7:R)
[latest-25016]2025-01-26T22:03:31.712Z <Engine:NOTICE> Starting reaction Lights ON<RESET> (rule-m6e4ajh7:R)
[latest-25016]2025-01-26T22:03:31.713Z <Engine:INFO> Lights ON<RESET> all actions completed.
[latest-25016]2025-01-26T22:03:42.565Z <wsapi:INFO> client "127.0.0.1#3" closed, code=1001, reason=
[latest-25016]2025-01-26T22:03:42.753Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/lang
[latest-25016]2025-01-26T22:03:42.754Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/lang from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/lang ACL (#7): [Object]{ "url": "/api/v1/lang", "allow": true, "index": 7 }
[latest-25016]2025-01-26T22:03:42.790Z <wsapi:INFO> wsapi: connection from ::ffff:127.0.0.1
[latest-25016]2025-01-26T22:03:42.839Z <wsapi:INFO> [WSAPI]wsapi#1 client "127.0.0.1#6" authorized
[latest-25016]2025-01-26T22:03:43.353Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/systime
[latest-25016]2025-01-26T22:03:43.353Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/systime from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/systime ACL (#5): [Object]{ "url": "/api/v1/systime", "allow": true, "index": 5 }
[latest-25016]2025-01-26T22:03:48.146Z <wsapi:INFO> client "127.0.0.1#6" closed, code=1001, reason=
[latest-25016]2025-01-26T22:03:48.308Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/lang
[latest-25016]2025-01-26T22:03:48.309Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/lang from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/lang ACL (#7): [Object]{ "url": "/api/v1/lang", "allow": true, "index": 7 }
[latest-25016]2025-01-26T22:03:48.346Z <wsapi:INFO> wsapi: connection from ::ffff:127.0.0.1
[latest-25016]2025-01-26T22:03:48.390Z <wsapi:INFO> [WSAPI]wsapi#1 client "127.0.0.1#7" authorized
[latest-25016]2025-01-26T22:03:49.412Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/systime
[latest-25016]2025-01-26T22:03:49.413Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/systime from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/systime ACL (#5): [Object]{ "url": "/api/v1/systime", "allow": true, "index": 5 }
[latest-25016]2025-01-26T22:03:52.734Z <wsapi:INFO> client "127.0.0.1#7" closed, code=1001, reason=
[latest-25016]2025-01-26T22:03:52.891Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/lang
[latest-25016]2025-01-26T22:03:52.892Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/lang from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/lang ACL (#7): [Object]{ "url": "/api/v1/lang", "allow": true, "index": 7 }
[latest-25016]2025-01-26T22:03:52.925Z <wsapi:INFO> wsapi: connection from ::ffff:127.0.0.1
[latest-25016]2025-01-26T22:03:52.965Z <wsapi:INFO> [WSAPI]wsapi#1 client "127.0.0.1#8" authorized
[latest-25016]2025-01-26T22:03:54.383Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/systime
[latest-25016]2025-01-26T22:03:54.384Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/systime from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/systime ACL (#5): [Object]{ "url": "/api/v1/systime", "allow": true, "index": 5 }
[latest-25016]2025-01-26T22:04:01.590Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" }
[latest-25016]2025-01-26T22:04:39.646Z <Rule:INFO> Lights OFF (rule-m6e33ja3 in Atrium Lights) evaluated; rule state transition from RESET to SET!
[latest-25016]2025-01-26T22:04:39.656Z <Rule:INFO> Lights ON (rule-m6e4ajh7 in Atrium Lights) evaluated; rule state transition from RESET to SET!
[latest-25016]2025-01-26T22:04:39.663Z <Engine:INFO> Enqueueing "Lights OFF<SET>" (rule-m6e33ja3:S)
[latest-25016]2025-01-26T22:04:39.665Z <Engine:INFO> Enqueueing "Lights ON<SET>" (rule-m6e4ajh7:S)
[latest-25016]2025-01-26T22:04:39.668Z <Engine:NOTICE> Starting reaction Lights OFF<SET> (rule-m6e33ja3:S)
[latest-25016]2025-01-26T22:04:39.669Z <Engine:NOTICE> Starting reaction Lights ON<SET> (rule-m6e4ajh7:S)
[latest-25016]2025-01-26T22:04:39.669Z <Engine:INFO> Lights ON<SET> all actions completed.
[latest-25016]2025-01-26T22:04:39.675Z <Rule:INFO> Lights OFF (rule-m6e33ja3 in Atrium Lights) evaluated; rule state transition from SET to RESET!
[latest-25016]2025-01-26T22:04:39.680Z <Engine:NOTICE> ReactionHistory: no entry for
[latest-25016]2025-01-26T22:04:39.683Z <Engine:NOTICE> [Engine]Engine#1 entry 256 reaction rule-m6e33ja3:S-1q2f1j0p: [Error] terminated [parent terminating]
[latest-25016]2025-01-26T22:04:39.683Z <Engine:CRIT> Error: terminated [parent terminating]
Error: terminated
    at Engine._process_reaction_queue (C:\Users\Jalan\msr\reactor\server\lib\Engine.js:1644:47)
[latest-25016]2025-01-26T22:04:39.699Z <Engine:NOTICE> [Engine]Engine#1 entry 254 reaction rule-m6e33ja3:S: [Error] terminated [preempted by rule state change]
[latest-25016]2025-01-26T22:04:39.699Z <Engine:CRIT> Error: terminated [preempted by rule state change]
Error: terminated
    at Engine._process_reaction_queue (C:\Users\Jalan\msr\reactor\server\lib\Engine.js:1644:47)
[latest-25016]2025-01-26T22:04:39.700Z <Engine:INFO> Enqueueing "Lights OFF<RESET>" (rule-m6e33ja3:R)
[latest-25016]2025-01-26T22:04:39.704Z <Engine:NOTICE> Starting reaction Lights OFF<RESET> (rule-m6e33ja3:R)
[latest-25016]2025-01-26T22:04:39.705Z <Engine:INFO> Lights OFF<RESET> all actions completed.
[latest-25016]2025-01-26T22:05:48.822Z <Rule:INFO> Lights ON (rule-m6e4ajh7 in Atrium Lights) evaluated; rule state transition from SET to RESET!
[latest-25016]2025-01-26T22:05:48.831Z <Engine:INFO> Enqueueing "Lights ON<RESET>" (rule-m6e4ajh7:R)
[latest-25016]2025-01-26T22:05:48.847Z <Engine:NOTICE> Starting reaction Lights ON<RESET> (rule-m6e4ajh7:R)
[latest-25016]2025-01-26T22:05:48.847Z <Engine:INFO> Lights ON<RESET> all actions completed.

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

    *HASS 2025.3.4
    w/ ZST10-700 fw 7.18.3

    *Prod MSR in docker/portainer
    MSR: latest-25082-3c348de6
    MQTTController: 24257
    ZWave Controller: 25082

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

      You're not showing your RESET reactions for either rule.

      Edit: by the way, neither rule is looking at the lights, so when you say things like "the lights find themselves turned off after dark and they will turn themselves back on" and "wherein if it is daytime and the lights somehow find their way ON, they will turn themselves back OFF", you're not showing anything that literally does that. It would only happen by accident if/when solarRadiation changes, because that's the only thing you are looking at.

      Logs aren't angry at all. One message is missing a piece of data, but other than that, this looks as expected. Are you forgetting that the changes operator with no terminal values is just a pulse? So the rule(s) would be expected to set and reset very quickly, which it appears they are doing. It also appears that at least the "Lights OFF" rule has something in the reset reaction, so when the rule resets, the running set reaction will be stopped before it finishes (or maybe even before it starts), and the reset will be run. That's documented behavior. If you don't want your set reaction to be pre-empted, your reset reaction has to be completely empty, not even a comment.

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

      G 2 Replies Last reply
      0
      • toggledbitsT toggledbits

        You're not showing your RESET reactions for either rule.

        Edit: by the way, neither rule is looking at the lights, so when you say things like "the lights find themselves turned off after dark and they will turn themselves back on" and "wherein if it is daytime and the lights somehow find their way ON, they will turn themselves back OFF", you're not showing anything that literally does that. It would only happen by accident if/when solarRadiation changes, because that's the only thing you are looking at.

        Logs aren't angry at all. One message is missing a piece of data, but other than that, this looks as expected. Are you forgetting that the changes operator with no terminal values is just a pulse? So the rule(s) would be expected to set and reset very quickly, which it appears they are doing. It also appears that at least the "Lights OFF" rule has something in the reset reaction, so when the rule resets, the running set reaction will be stopped before it finishes (or maybe even before it starts), and the reset will be run. That's documented behavior. If you don't want your set reaction to be pre-empted, your reset reaction has to be completely empty, not even a comment.

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

        @toggledbits Interesting. Once upon a time you told me to add even a random comment as a placeholder for reset reaction if I had no actually reset action. That's what is in each of these.

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

        *HASS 2025.3.4
        w/ ZST10-700 fw 7.18.3

        *Prod MSR in docker/portainer
        MSR: latest-25082-3c348de6
        MQTTController: 24257
        ZWave Controller: 25082

        toggledbitsT 1 Reply Last reply
        0
        • toggledbitsT toggledbits

          You're not showing your RESET reactions for either rule.

          Edit: by the way, neither rule is looking at the lights, so when you say things like "the lights find themselves turned off after dark and they will turn themselves back on" and "wherein if it is daytime and the lights somehow find their way ON, they will turn themselves back OFF", you're not showing anything that literally does that. It would only happen by accident if/when solarRadiation changes, because that's the only thing you are looking at.

          Logs aren't angry at all. One message is missing a piece of data, but other than that, this looks as expected. Are you forgetting that the changes operator with no terminal values is just a pulse? So the rule(s) would be expected to set and reset very quickly, which it appears they are doing. It also appears that at least the "Lights OFF" rule has something in the reset reaction, so when the rule resets, the running set reaction will be stopped before it finishes (or maybe even before it starts), and the reset will be run. That's documented behavior. If you don't want your set reaction to be pre-empted, your reset reaction has to be completely empty, not even a comment.

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

          @toggledbits I did, however, deconstruct and reconstruct the Catch-All rule last night.

          16c862f3-89a9-46ee-8f36-0f80c068996d-image.png

          99108e45-e9f2-4abc-989f-0868a9a37545-image.png 95e6c0ee-65d0-4f37-9c14-bf0955cc32f3-image.png

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

          *HASS 2025.3.4
          w/ ZST10-700 fw 7.18.3

          *Prod MSR in docker/portainer
          MSR: latest-25082-3c348de6
          MQTTController: 24257
          ZWave Controller: 25082

          G 1 Reply Last reply
          0
          • G gwp1

            @toggledbits I did, however, deconstruct and reconstruct the Catch-All rule last night.

            16c862f3-89a9-46ee-8f36-0f80c068996d-image.png

            99108e45-e9f2-4abc-989f-0868a9a37545-image.png 95e6c0ee-65d0-4f37-9c14-bf0955cc32f3-image.png

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

            And then I tried a different approach...

            c5337edc-4416-4b76-957a-358f249d7efa-image.png 3fb6d0a8-5865-414a-a866-111ce6992831-image.png

            This may be another case of me making things more complicated than they need to be...

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

            *HASS 2025.3.4
            w/ ZST10-700 fw 7.18.3

            *Prod MSR in docker/portainer
            MSR: latest-25082-3c348de6
            MQTTController: 24257
            ZWave Controller: 25082

            1 Reply Last reply
            0
            • G gwp1

              @toggledbits Interesting. Once upon a time you told me to add even a random comment as a placeholder for reset reaction if I had no actually reset action. That's what is in each of these.

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

              @gwp1 said in Catch-all lights rule:

              Once upon a time you told me to add even a random comment as a placeholder for reset reaction if I had no actually reset action. That's what is in each of these.

              I'm pretty sure there was more context to that advice. Go find it. Let's have a look.

              @gwp1 said in Catch-all lights rule:

              This may be another case of me making things more complicated than they need to be...

              Yeah, not what I would chose.

              Why not something like this:

              1. Make a rule that detects if any of the controlled lights is on (i.e. an OR group when there are multiple devices). I'll call it "Any Light On"
              2. Your "Lights ON" rule is (AND group, with sustained for 300 seconds option):
                • solarRadiation < 14
                • Rule "Any Light On" is FALSE
              3. Your "Lights OFF" rule is (AND group, with sustained for 300 seconds option):
                • solarRadiation >= 14
                • Rule "Any Light On" is TRUE

              The SET reactions for each should be obvious (run your ON or OFF reaction). The RESET reactions should be (completely) empty.

              The "sustained for 300 seconds" will provide 5 minutes of hysteresis:

              • Once it gets dark enough and has been that way for 5 minutes with no lights on, it will turn the lights on;
              • Once it gets light enough and has been that way for 5 minutes with lights on, it will turn them off;
              • If it's dark and the lights are turned off, they will turn back on in 5 minutes. If you want that faster, reduce the sustain period on "Lights ON"
              • If it's light and the lights are turned on, they will stay on for 5 minutes, then get turned off. Adjust "Lights OFF" sustain to suit.

              This is pretty much exactly how my kitchen undercabinet strips are controlled (motion sensing and house mode are also part of it, but not applicable here).

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

              G 1 Reply Last reply
              0
              • toggledbitsT toggledbits

                @gwp1 said in Catch-all lights rule:

                Once upon a time you told me to add even a random comment as a placeholder for reset reaction if I had no actually reset action. That's what is in each of these.

                I'm pretty sure there was more context to that advice. Go find it. Let's have a look.

                @gwp1 said in Catch-all lights rule:

                This may be another case of me making things more complicated than they need to be...

                Yeah, not what I would chose.

                Why not something like this:

                1. Make a rule that detects if any of the controlled lights is on (i.e. an OR group when there are multiple devices). I'll call it "Any Light On"
                2. Your "Lights ON" rule is (AND group, with sustained for 300 seconds option):
                  • solarRadiation < 14
                  • Rule "Any Light On" is FALSE
                3. Your "Lights OFF" rule is (AND group, with sustained for 300 seconds option):
                  • solarRadiation >= 14
                  • Rule "Any Light On" is TRUE

                The SET reactions for each should be obvious (run your ON or OFF reaction). The RESET reactions should be (completely) empty.

                The "sustained for 300 seconds" will provide 5 minutes of hysteresis:

                • Once it gets dark enough and has been that way for 5 minutes with no lights on, it will turn the lights on;
                • Once it gets light enough and has been that way for 5 minutes with lights on, it will turn them off;
                • If it's dark and the lights are turned off, they will turn back on in 5 minutes. If you want that faster, reduce the sustain period on "Lights ON"
                • If it's light and the lights are turned on, they will stay on for 5 minutes, then get turned off. Adjust "Lights OFF" sustain to suit.

                This is pretty much exactly how my kitchen undercabinet strips are controlled (motion sensing and house mode are also part of it, but not applicable here).

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

                @toggledbits sorry for the delay, day job has a rude habit of interfering in fun.

                This solution worked perfectly for this need. It's actually quite similar to how I control the outdoor garden fountain, HVAC, and some other things. As usual, I tried to over-complicate things.

                EDIT: in fact, I find I am using this EXACT method for my outdoor LIFX lights. sigh

                I am still looking for that context. Will provide when I locate it.

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

                *HASS 2025.3.4
                w/ ZST10-700 fw 7.18.3

                *Prod MSR in docker/portainer
                MSR: latest-25082-3c348de6
                MQTTController: 24257
                ZWave Controller: 25082

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

                Recent Topics

                • Set Reaction > Script Action
                  therealdbT
                  therealdb
                  0
                  6
                  79
                • Wiring Samotech SM308-S into light fitting
                  akbooerA
                  akbooer
                  0
                  2
                  41
                • Errors after updating to MQTTController build 25139
                  toggledbitsT
                  toggledbits
                  0
                  6
                  72
                • 🎉 My very first MSR controller: OpenSprinkler
                  therealdbT
                  therealdb
                  5
                  13
                  631
                • Advice reqeusted to migrate MSR from Bare Metal to Container
                  T
                  tamorgen
                  0
                  5
                  94
                • Reactor (Multi-System/Multi-Hub) Announcements
                  toggledbitsT
                  toggledbits
                  5
                  122
                  37.3k
                • Z-Wave Future....
                  CatmanV2C
                  CatmanV2
                  0
                  5
                  176
                • Can´t restart or upgrade/deploy MSR
                  toggledbitsT
                  toggledbits
                  0
                  4
                  133
                • [Solved] Limit HA Entity in MSR
                  wmarcolinW
                  wmarcolin
                  0
                  7
                  261
                • Disaster recovery and virtualisation
                  CatmanV2C
                  CatmanV2
                  0
                  5
                  699
                • Remote access of Zwave stick from Z-wave server
                  CatmanV2C
                  CatmanV2
                  0
                  3
                  427
                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