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.
J

jsimmo

@jsimmo
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
Wiring Samotech SM308-S into light fitting
F
Hi Smart Home Community. I have used a Sonos inline WiFi switch to make one of my light fittings smart, but it requires a hard reset for WiFi changes, plus it isn't zigbee compatible, which means I can't use the Hue app to control it with the rest of the lights. To that end I bought a Samotech SM308-S as it is recommended as the better than the Sonos equivalent. I am however not exactly sure how to wire it in. The manual is available here Can anyone help me by clarifying which ports I need to use, and whether I should be using the live or switched live line for live etc. I will be keeping using standard switches for a while, although hope to upgrade to tap dials once I have all the fittings upgraded. Thanks
Hardware
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
Z-Wave Future....
DesTD
https://forum.z-wave.me/viewtopic.php?f=3417&t=36140 That's not a good thing I think Time to switch again?
Z-Wave.me
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
Disaster recovery and virtualisation
CatmanV2C
Following on from my last thread, some progress has been made over the weekend. With 18G of spanky RAM in my Synology DS224+. I've jumped into the murky world of virtualisation and already eliminated the need for two Raspberry Pi's from my system. Home Assistant: In theory they provide an OVA file which is supported by the Synology. I couldn't get it to work, however, so grabbed a copy of the .img file they supply, renamed it .iso and imported it as a VM. Restored from my full back up and that all seems fantastic. Minidnla Music server: Trivial. Grabbed a Debian .iso for Bookworm and copied that onto the NAS. Created a new machine which mirrored the specs of the Raspberry Pi, booted from the ISO then did an expert install. Once that was all stable with a basic core of stuff and networking, I've made a copy of that as a good base system. Then fired up minidnla on it, mounted my media and that's also woking. Not bad for a short weekend's work. Still not sure about the main NUC though. I'm thinking of buying a new USB stick so I can mess around getting it working on the Synology before I do anything drastic. Once that hurdle is sorted I'm torn between: Using a brand new install of Bookworm, re-installing Z-way server, OpenLuup, AltUI, MSR and HA bridge, then restoring across or Making an ISO of the current system, importing that and upgrading in place (which will be pretty risk free since I can snapshot everything before I make any changes.) Decisions, decisions. C
General Discussion
Remote access of Zwave stick from Z-wave server
CatmanV2C
Topic thumbnail image
Software
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
About
Posts
22
Topics
9
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • [SOLVED] MQTT Controller Not Toggling Sonoff Basic Correctly on Raspberry Pi 4B - Bare Metal (without Docker)
    J jsimmo

    Thanks very much. I specified it as you described and toggle works just fine now.

    I'll change the username and password and no, the template was not copied to the reactor.yaml file.

    I started out by following the docs (see below) on how to set it up but got a bit confused. It gives an example of setting up a Shelly, but then says to use the tasmota_generic_relay template. This is how I ended up with the 0 (from channel 0).

    Anyway all good now. Thanks again for the very quick reply. Looking forward to experimenting with MQTT and Tasmota to see if I can get improved reliability from my Sonoff devices.

    Easy Device Configuration - Using Existing Template
    As an example, let's say we have a Shelly1 configured with the topic shelly1_43DFD2 that is configured to operate as a single relay to operate a stairway light. To create an entity for this device, we can use the tasmota_generic_relay template. The template supports multiple relays, but since only one relay is configured in Tasmota, the published topics from the node will have a "unit number" (identifying which relay if more than one), so we'll specify no unit number by giving it an empty string:

    ...other stuff
    config: "mqtt://127.0.0.1:1883/"
    entities:
    shelly1_stairway:
    name: "Stairway Light"
    topic: shelly1_43DFD2
    uses_template: shelly_relay
    channel: 0

    Multi-System Reactor

  • [SOLVED] MQTT Controller Not Toggling Sonoff Basic Correctly on Raspberry Pi 4B - Bare Metal (without Docker)
    J jsimmo

    MSR is currently running the latest-21342

    I thought I would give MQTT controller a try for one of the many Sonoff devices I have in my home. My aim is to remove the HTTP Switch app in my Vera Plus and control all my devices from MSR using the MQTT controller.

    I have carried out the following steps:
    Flashed a new Sonoff Basic with Tasmota, configured it for MQTT and enabled it.
    Installed MQTT Controller on MSR and added the basic configuration in the reactor.yaml file and re-started reactor.
    The device is discovered in entities and when clicking on the attributes power_switch.on, power-switch.off, power-switch.set everything works just fine.
    The problem I have is with toggle. This always works to toggle the device ON but when toggled again does not turn it OFF.

    I've attached my reactor.yaml file and the template which it uses. Hopefully someone can shed some light on why it won't toggle OFF.

    Thanks

    5bba049f-3534-4ec3-8832-9ae042e1c807-ControllerConfig.JPG

    f23e0a8f-5728-4d03-ac5e-9f5769d78405-Template.JPG

    Multi-System Reactor

  • [SOLVED] Help required updating nodejs on Raspberry Pi 4B - Bare Metal (without Docker)
    J jsimmo

    I ran the install script again and nodejs is now updated to the latest version.
    pi@raspberrypi:~ $ node -v
    v16.13.0
    I also copied the reactor.service file as advised and MSR is working fine.

    Thanks for your help

    Multi-System Reactor

  • [SOLVED] Help required updating nodejs on Raspberry Pi 4B - Bare Metal (without Docker)
    J jsimmo

    I've recently updated to latest build 21332 and notice in the Readme file that I should update nodejs to 16.13.0 or higher before end of March. I've had a go at doing this, but think I've not done it correctly as I get the following responses in the terminal:

    pi@raspberrypi:~ $ node -v
    v14.17.0
    pi@raspberrypi:~ $ nodejs -v
    v16.13.0

    Is this correct? If not then what steps do I need to carry out to update nodejs properly.

    Any help from the group would be much appreciated.

    Multi-System Reactor

  • Not all options available when creating a new rule
    J jsimmo

    OK. It's all good now. I rebooted my system and all my icons are back and I'm able to access all the options now. Thanks for your help.

    Multi-System Reactor

  • Not all options available when creating a new rule
    J jsimmo

    @toggledbits

    No joy with that I'm afraid. This is the outcome of the update. Any clues here?

    pi@raspberrypi:~ $ cd ~/Documents/reactor
    pi@raspberrypi:~/Documents/reactor $ npm update --no-save
    npm WARN bootstrap@4.6.0 requires a peer of popper.js@^1.16.1 but none is installed. You must install peer dependencies yourself.

    • bootstrap-icons@1.5.0
    • jsdoc@3.6.7
    • influx@5.9.2
    • uuid@8.3.2
      added 25 packages from 23 contributors, updated 2 packages and audited 102 packages in 8.223s

    9 packages are looking for funding
    run npm fund for details

    found 1 moderate severity vulnerability
    run npm audit fix to fix them, or npm audit for details
    npm WARN bootstrap@4.6.0 requires a peer of popper.js@^1.16.1 but none is installed. You must install peer dependencies yourself.

    • diskusage-ng@1.0.2
      removed 25 packages, updated 1 package and audited 77 packages in 2.926s

    8 packages are looking for funding
    run npm fund for details

    found 1 moderate severity vulnerability
    run npm audit fix to fix them, or npm audit for details
    pi@raspberrypi:~/Documents/reactor $ sudo systemctl restart reactor

    Multi-System Reactor

  • Not all options available when creating a new rule
    J jsimmo

    @togglebits,

    Not sure when this happened, but now when I create a new rule I get the boxes open up for Triggers and Set Reaction only. Clicking in any of the Constraints, Reset Reaction or Expressions boxes does not expand them and allow me to enter anything.
    I'm getting round it for now by copying an existing rule which has Triggers, Set Reactions, Reset Reactions and Expressions in it and then modifying this to be my new rule.
    Any thoughts on how to make these boxes available again?

    MSR is installed on a Raspberry Pi 4B (8GB) - Bare Metal (without Docker) and is the latest-21228-05d7497

    dfc27b40-3b2a-488a-ac88-23f775f76d76-New Rule.JPG

    Multi-System Reactor

  • Version 1.0 Pre-release Discussion
    J jsimmo

    @sweetgenius said in Version 1.0 Pre-release Discussion:

    Would a Menu item for accessing the reactor log file or portion of the log be possible.Or ideally a way to monitor the log in real time from the GUI for troubleshooting?

    +1 for this.

    Multi-System Reactor

  • Local Expression not recognised after update to 21096
    J jsimmo

    @togglebits The following rule is one of two which have stopped working since updating to 21096. I guess they're easily fixed by changing the local expressions to global ones, but is this a bug or by design?

    Bye the way. Well pleased with how Alerts shows up the errors.

    Working Local Expression.JPG

    Alerts.JPG

    Non Working Local Expression.JPG

    Multi-System Reactor

  • Setting up Pushover in MSR
    J jsimmo

    Followed the guide and Pushover is now set up and working fine.

    Multi-System Reactor

  • Setting up Pushover in MSR
    J jsimmo

    Thanks. Should have known to look there. Will give it a try.

    Multi-System Reactor

  • Setting up Pushover in MSR
    J jsimmo

    Hi,

    I've been using Pushover in VeraAlerts, but now want to send my notifications from MSR.
    I see in the reactor config directory that the notification. yaml file includes Pushover, but is showing #TBD. Is this where I need to set up my Pushover user key etc. and if so what and how should the information be entered?

    Any help would be appreciated.

    Multi-System Reactor

  • PR #0000137: Expression Value Condition - Comparison not working
    J jsimmo

    @togglebits

    Just confirming that this working ok now since upgrade to 21081

    Many Thanks

    Multi-System Reactor

  • 0000075: Timeout Overflow Warning
    J jsimmo

    Patrick, Just confirming this is now working ok for me.👍

    Multi-System Reactor

  • Delays not working as expected
    J jsimmo

    Thanks for the fixes Patrick.

    I've now tried them on my test rules and both (PR#64 and 65) work fine. 👍

    I've also updated all my imported rules to use the "delay reset" on the "Follow" output mode. These are all working now with the added bonus of being able to monitor the delays counting down.

    Thanks again for the brilliant MSR.

    Multi-System Reactor

  • Delays not working as expected
    J jsimmo

    Ok, so this is how the rules for Delay1 and Delay 2 are now setup.

    Each rule works perfectly fine when run on its own. The problem I have now is when one runs at the same time as the other.

    To prevent any conflict, all my other rules in MSR are disabled, as are my Reactors in Vera.

    screenshot-192.168.0.56_8111-2021.02.27-00_32_14.png screenshot-192.168.0.56_8111-2021.02.27-00_33_11.png

    In the following screenshot, Delay 2 (20s) is started and shortly after Delay 1 (10s) is started. Delay 1 completes first and its associated lamp switches off. Then Delay 2 completes but its associated lamp remains on.
    What can't be seen in the screenshot is as well as the text being green for Delay 2 the whole box is also flashing green.
    Everything works ok, except the lamp does not switch off after Delay 2 completes.

    screenshot-192.168.0.56_8111-2021.02.27-01_37_12.png

    As can be seen from the logs, Delay 2 <Reset> does not occur.

    2021-02-27T01:31:12.388Z Engine:INFO Delay 1<SET> all actions completed.
    2021-02-27T01:31:29.320Z Rule:INFO Rule#rule-klmc7wxx (Delay 2) reset.
    2021-02-27T01:31:29.328Z Rule:INFO Rule#rule-klifbnfi (Delay 1) reset.
    2021-02-27T01:31:29.332Z Engine:INFO Enqueueing "Delay 2<RESET>" (rule-klmc7wxx:R)
    2021-02-27T01:31:29.333Z Engine:INFO Enqueueing "Delay 1<RESET>" (rule-klifbnfi:R)
    2021-02-27T01:31:29.334Z Engine:NOTICE Starting reaction Delay 2<RESET> [RuleReaction#rule-klmc7wxx:R]
    2021-02-27T01:31:29.336Z Engine:NOTICE Starting reaction Delay 1<RESET> [RuleReaction#rule-klifbnfi:R]
    2021-02-27T01:31:29.357Z Engine:NOTICE Resuming reaction Delay 2<RESET> from step 1
    2021-02-27T01:31:29.359Z Engine:INFO Delay 2<RESET> all actions completed.
    2021-02-27T01:31:29.431Z Engine:NOTICE Resuming reaction Delay 1<RESET> from step 1
    2021-02-27T01:31:29.433Z Engine:INFO Delay 1<RESET> all actions completed.
    2021-02-27T01:31:57.809Z Rule:NOTICE Rule#rule-klmc7wxx configuration changed; reloading
    2021-02-27T01:31:57.812Z Rule:NOTICE Rule#rule-klmc7wxx stopping rule
    2021-02-27T01:31:57.819Z Rule:NOTICE Rule Rule#rule-klmc7wxx stopped
    2021-02-27T01:31:57.820Z Rule:INFO Rule#rule-klmc7wxx (Delay 2) started
    2021-02-27T01:32:07.911Z Rule:INFO Rule#rule-klifbnfi (Delay 1) triggered!
    2021-02-27T01:32:07.915Z Engine:INFO Enqueueing "Delay 1<SET>" (rule-klifbnfi:S)
    2021-02-27T01:32:07.916Z Engine:NOTICE Starting reaction Delay 1<SET> [RuleReaction#rule-klifbnfi:S]
    2021-02-27T01:32:07.979Z Engine:NOTICE Resuming reaction Delay 1<SET> from step 1
    2021-02-27T01:32:07.980Z Engine:INFO Delay 1<SET> all actions completed.
    2021-02-27T01:32:24.901Z Rule:INFO Rule#rule-klifbnfi (Delay 1) reset.
    2021-02-27T01:32:24.905Z Engine:INFO Enqueueing "Delay 1<RESET>" (rule-klifbnfi:R)
    2021-02-27T01:32:24.906Z Engine:NOTICE Starting reaction Delay 1<RESET> [RuleReaction#rule-klifbnfi:R]
    2021-02-27T01:32:24.974Z Engine:NOTICE Resuming reaction Delay 1<RESET> from step 1
    2021-02-27T01:32:24.975Z Engine:INFO Delay 1<RESET> all actions completed.
    2021-02-27T01:32:29.114Z Rule:INFO Rule#rule-klmc7wxx (Delay 2) triggered!
    2021-02-27T01:32:29.124Z Engine:INFO Enqueueing "Delay 2<SET>" (rule-klmc7wxx:S)
    2021-02-27T01:32:29.125Z Engine:NOTICE Starting reaction Delay 2<SET> [RuleReaction#rule-klmc7wxx:S]
    2021-02-27T01:32:29.175Z Engine:NOTICE Resuming reaction Delay 2<SET> from step 1
    2021-02-27T01:32:29.176Z Engine:INFO Delay 2<SET> all actions completed.
    2021-02-27T01:32:34.920Z Rule:INFO Rule#rule-klifbnfi (Delay 1) triggered!
    2021-02-27T01:32:34.924Z Engine:INFO Enqueueing "Delay 1<SET>" (rule-klifbnfi:S)
    2021-02-27T01:32:34.926Z Engine:NOTICE Starting reaction Delay 1<SET> [RuleReaction#rule-klifbnfi:S]
    2021-02-27T01:32:34.973Z Engine:NOTICE Resuming reaction Delay 1<SET> from step 1
    2021-02-27T01:32:34.974Z Engine:INFO Delay 1<SET> all actions completed.
    2021-02-27T01:32:51.969Z Rule:INFO Rule#rule-klifbnfi (Delay 1) reset.
    2021-02-27T01:32:51.974Z Engine:INFO Enqueueing "Delay 1<RESET>" (rule-klifbnfi:R)
    2021-02-27T01:32:51.975Z Engine:NOTICE Starting reaction Delay 1<RESET> [RuleReaction#rule-klifbnfi:R]
    2021-02-27T01:32:52.047Z Engine:NOTICE Resuming reaction Delay 1<RESET> from step 1
    2021-02-27T01:32:52.049Z Engine:INFO Delay 1<RESET> all actions completed.

    Multi-System Reactor

  • Delays not working as expected
    J jsimmo

    That's great that you found it.

    I modified both my test rules to use the "delay reset" on the "Follow" output mode and changed the Set Reaction to switch the lights on and the Reset Reaction to switch them off again (much better way of doing it). Unfortunately, it hasn't fixed the problem, so I'm guessing the error you found affects this way of doing it as well. Will wait for the next daily build and test it again.

    Multi-System Reactor

  • Delays not working as expected
    J jsimmo

    Ok. Thanks for the explanation. You guessed right about how I want it to work. I'll try using "delay reset" on the "Follow" output mode instead.

    I was careful about how I did the test and have just carried it out again. There is nothing in the reset reactions of either rule and I made sure not re-activate the motion sensor associated with the 10 second rule after the 3 second pulse. I'm the only one in the house at the moment, so no-one else interfering with the test.
    It's always the case that the first timer does not end on time once the second timer is started.

    Multi-System Reactor

  • Delays not working as expected
    J jsimmo

    Not sure I understand what you mean by delay option. Is there something else I should be setting?

    e5d34a04-65eb-43d8-b112-012dfc12c6f2-image.png

    15e78d81-585a-4fd8-b50a-f868c55e11fa-image.png

    Multi-System Reactor

  • Delays not working as expected
    J jsimmo

    I seem to be having some issues with delays, so I set up a test as follows:

    38b96d15-e56b-4a53-bc55-861789e77194-image.png

    14bc4aab-ec56-46d3-b81d-04797f92eb74-image.png

    258343a3-e489-43ef-99d5-ae1a76b30ad2-image.png

    If the second rule is disabled, the first rule works as I expect - when motion is detected in the Hall, the Hall lamp switches on and then off again 10 seconds later.

    With both rules enabled - when motion is detected in the Hall the Hall lamp switches on, but then if motion is detected in the Dining room, the Dining room lamp switches on, but the Hall lamp does not switch off after the 10 seconds , but after the 30 seconds when both lamps switch off at the same time.

    Is this a bug, or just my understanding of how it should work?

    Multi-System Reactor
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved