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

basai

@basai
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
18
Topics
6
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Runtime error latest-24366 when Create New Reaction
    B basai

    Confirming that 25016 has indeed resolved the error.

    Thank you !!

    Multi-System Reactor

  • Runtime error latest-24366 when Create New Reaction
    B basai

    @toggledbits Howdy, the error is as I posted and doesn't show that information. I took the instructions not to upload a screen shot too literally I suppose, apologies.

    Here is what it looks like on my end on Safari, and Firefox in OS X Sequoia.

    Screenshot 2025-01-17 at 11.09.04 AM.png

    Thanks,
    -bh

    Multi-System Reactor

  • Runtime error latest-24366 when Create New Reaction
    B basai

    Reactor (Multi-hub) latest-24366-3de60836
    Running on Proxmox 8 VM
    Ubuntu 22.04.5 LTS
    Docker version 27.5.0, build a187fa5
    Docker Compose version v2.32.3
    Browsers being used on Mac OS Sequoia: Safari, Firefox also occurs with Safari on iPhone 16 Pro 18.2.1

    This occurs on two different instances of MSR running at two different locations having the same environment detailed above.

    When I select "Reactions->Create Reaction" I get an error window with a red “Runtime Error:” banner. Note that I can edit and save existing Reactions

    —-------------------<SNIP>————————————
    Runtime Error:

    @http://192.168.119.137:8111/reactor/en-US/lib/js/reactor-ui-reactions.js:445:34

    You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.
    ---------------------</SNIP>————————

    apt update, apt upgrade, reboot have been performed as well as
    docker system prune -a
    docker compose down
    docker compose up -d

    Many thanks in advance,
    -bh

    Multi-System Reactor

  • MSR SMTP Notifications fail - <wsapi:CRIT> Error: Engine has not been started
    B basai

    That was likely it now that you mention it. I did have a problem awhile back where I fat fingered a 2:00AM cron job that was supposed to trim backup files to only keep the last x days of *.tar.gz files which filled the partition. I bet the file date reflects when that happened 🙂

    Thanks again for the help and clarifying. Take care,
    -bh

    Multi-System Reactor

  • MSR SMTP Notifications fail - <wsapi:CRIT> Error: Engine has not been started
    B basai

    Thanks for the input.

    I'm not sure if deleting this zero length file was the right thing to do or not but it fixed the problem, the engine starts now and SMTP works.

    From the log:
    [latest-23218]2023-08-21T20:55:09.695Z <IndividualFileStrategy:ERR> [IndividualFileStrategy][IndividualFileStrategy#/var/reactor/storage/states] failed to read cs-rule-lbhys108 in /var/reactor/storage/states/cs-rule-lbhys108.json: 
    

    So basically the file /var/reactor/storage/states/cs-rule-lbhys108.json had a file length of "0"
    -rwx------ 1 501 staff 0 Jul 20 02:00 cs-rule-lbhys108.json

    I moved the file in question to a tmp directory, restarted reactor, the engine started and SMTP works now.

    Question:
    Was moving / effectively deleting this file from reactors view a bad thing to do that will cause future problems and is there anything else that need to do other than getting rid of that zero length file?

    Thanks,
    -bh

    Multi-System Reactor

  • MSR SMTP Notifications fail - <wsapi:CRIT> Error: Engine has not been started
    B basai

    MSR Version: latest-23218
    Running as Docker Container : Docker version 24.0.5, build ced0996
    OS: Linux 15BPMSR1 6.1.26-05272-g26c406245a2c #1 SMP PREEMPT_DYNAMIC Thu Apr 27 10:15:40 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

    SMTP notifications had been working fine and I am unsure exactly what action(s) stopped it from working.

    I have verified that the SMTP server configured in notifications.yml is working properly.

    To duplicate the problem I am forcing an SMTP email notification using the set reaction play button, the reactor.log shows the following errors:

    [latest-23218]2023-08-21T14:23:22.462Z <wsapi:ERR> [WSAPI]wsapi#1 can't queue reaction rule-lgxmrba4:S: [Error] Engine has not been started [-]
    [latest-23218]2023-08-21T14:23:22.463Z <wsapi:CRIT> Error: Engine has not been started [-]
    Error: Engine has not been started
        at Engine.queueReaction (/opt/reactor/server/lib/Engine.js:1494:46)
        at WSAPI.clientMessage (/opt/reactor/server/wsapi/wsapi.js:782:64)
        at WebSocket.<anonymous> (/opt/reactor/server/wsapi/wsapi.js:301:157)
        at WebSocket.emit (node:events:527:28)
        at WebSocket.emit (node:domain:475:12)
        at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1068:20)
        at Receiver.emit (node:events:527:28)
        at Receiver.emit (node:domain:475:12)
        at Receiver.dataMessage (/opt/reactor/node_modules/ws/lib/receiver.js:517:14)
        at Receiver.getData (/opt/reactor/node_modules/ws/lib/receiver.js:435:17)
    
    

    I have tried:

    OS level: apt udate and apt upgrade and reboot

    docker pull toggledbits/reactor:latest-aarch64
    latest-aarch64: Pulling from toggledbits/reactor
    Digest: sha256:d8a019d457c9fef61f7c3e6908db1f1d0a2d14b6f7c5e9d4fc536c791503d152
    Status: Image is up to date for toggledbits/reactor:latest-aarch64
    docker.io/toggledbits/reactor:latest-aarch64
    

    docker stop reactor
    docker start reactor

    docker compose down
    docker compose up -d

    To no avail.

    I feel like I'm missing something obvious but can't put my finger on it.

    Thank you in advance for any guidance.
    -bh

    Multi-System Reactor

  • Smart bed sensor
    B basai

    I think this would be an interesting sensor to have. I’m guessing you are sensing pressure / weight and returning a numeric value based on that vs a simple open / close. The reason being you is that you would need a base (empty bed) value in order to make decisions whether someone / thing is in bed or not or how many are in bed for that matter. The second reason is that beds have different numbers of legs depending on the type of bed and therefore weight distribution comes into the picture, so sensing pressure or weight vs open / close seems like it would give you more options and even interest from other markets.

    Meaning, if this is a pressure / weight type sensor it could have other applications as well expanding your market. For example, I have a salt tank that holds a few hundred pounds of salt for my water treatment system. I could record the initial numeric values at different levels and use that information to know when it is low and needs more salt. I would be interested in doing that.

    Just my $.02

    Take care and good luck.

    -bh

    General Discussion

  • Is latest-22337 in DockerHub?
    B basai

    Howdy,

    Has anyone successfully installed 22337 via Docker Hub?

    I'm currently running latest-22310 on Qnap NAS 5.0.0.1986

    My usual method which is normally successful, is that in the Qnap CLI I run a docker pull (stdout below of what I got for 22337):

    >basai ~]$ docker pull toggledbits/reactor:latest-amd64
    > latest-amd64: Pulling from toggledbits/reactor
    > 8663204ce13b: Already exists 
    > 8c392e9e905c: Already exists 
    > 36ce72f2f129: Already exists 
    > 2e8529c47e46: Already exists 
    > 26c2865d7fe4: Pull complete 
    > b45a2cf2a065: Pull complete 
    > ac02d13d40de: Pull complete 
    > 2bd82a6d3d8c: Pull complete 
    > Digest: sha256:a192e403200a62664cec40f40f61499218ac9a0cae3b8ed8390f87679505105d
    > Status: Downloaded newer image for toggledbits/reactor:latest-amd64
    > docker.io/toggledbits/reactor:latest-amd64
    

    But when I go into the Qnap's container station (part of my usual process) and search for reactor and do the install for 'latest-amd64' it installs latest-22310 and not latest-22337.

    Sanity checking before I go down the path of chasing down Qnap and/or Container Station problems.

    TIA
    -b

    Multi-System Reactor

  • What am I missing with this rule not setting?
    B basai

    I'm not exactly sure here trying to follow the logic, but since you are using constraints, could that be the reason? Meaning, there is a section in the manual that talks about constraints eg: "Unlike triggers, changes in the conditions of constraints do not cause the rule to set or unset. They are only used as filter to allow or prevent the rule from setting."

    Multi-System Reactor

  • 🎉 My very first MSR controller: OpenSprinkler
    B basai

    Happy Birthday !! Also, thanks for doing this. Take care, -b

    Multi-System Reactor

  • Can a rule be used to disable other rules?
    B basai

    Thank you all for your responses, you are an awesome bunch in this group and I have what I was looking for.

    Essentially toggling a rule as active or inactive can only be done manually, so I wasn't going crazy because this was something I could do in the Vera Reactor to another Reactor 🙂

    I have been using toggles in HAAS to toggle a state which I include as a 'constraint' within multiple MSR rules which works.

    What I was looking for is more of a 'kill switch’ to completely disable a rule or set of rules for reasons that come up from time to time where I manually disable them so there is no chance of them running. Not a show stopper by any means.

    Thanks again,
    -b

    Multi-System Reactor

  • Can a rule be used to disable other rules?
    B basai

    Howdy,

    My goal is to have a rule that when triggered will disable other certain pre-defined rule sets, but I can't seem to find a way to do it in MSR. Is it possible?

    In the MSR UI, rule sets are toggled manually to be enabled (green) and disabled (red). I would like to do this from within a rule.

    Running MSR version latest-22274-24dfd72c

    TIA,
    -bh

    Multi-System Reactor

  • MSR Set Reaction not working anymore
    B basai

    Howdy, Honestly I didn’t really think this was an MSR Set Reaction pandemic and was more than likely a locally induced error of some sort.

    This is fixed now based on something you said in your last reply suspecting an update problem which pulled me out of a loop and put me on the right path.

    Summary: Upgrading to latest-22274 fixed the problem but QNAP’s Container Station using the Docker Hub Tab would only download and install latest-22179. Not sure if this is a QNAP bug or feature.

    Detail: For the benefit of any QNAP NAS users out there I’ll explain.

    Using QNAP NAS’s Container Station, searching for “reactor” in the “Docker Hub” tab I would select "latest-amd64”, but it would only install latest-22179 and not the actual latest-22274. Picking up the NAS and shaking it a few times, turning it off and on again, or putting more quarters in it didn't help.

    In the past I didn’t find a need to do the following since I believe Container Station should be doing this all by self, and if not, user error on my part.

    So to fix this I ssh’d to the QNAP NAS CLI and ran.

    docker pull toggledbits/reactor:latest-amd64
    

    Which returned the following, I was feeling optimistic seeing the "pull completes' "

    [basai@basai ~]$ docker pull toggledbits/reactor:latest-amd64
    latest-amd64: Pulling from toggledbits/reactor
    8663204ce13b: Already exists 
    8c392e9e905c: Already exists 
    36ce72f2f129: Already exists 
    2e8529c47e46: Already exists 
    26c2865d7fe4: Pull complete 
    b45a2cf2a065: Pull complete 
    ac02d13d40de: Pull complete 
    2bd82a6d3d8c: Pull complete 
    Digest: sha256:a192e403200a62664cec40f40f61499218ac9a0cae3b8ed8390f87679505105d
    Status: Downloaded newer image for toggledbits/reactor:latest-amd64
    docker.io/toggledbits/reactor:latest-amd64
    [basai@basai ~]$
    

    After this completed, now when I went to create a new docker by going into container station, searching for “reactor” in the “Docker Hub Tab” and selected “latest-amd64” it correctly installed latest-22274 and also pre-populated the NODE_PATH variable correctly which wasn’t happening before.

    Problem solved and MSR is working as expected again.

    Thanks you for your help, MSR Rocks!
    -bh

    Multi-System Reactor

  • MSR Set Reaction not working anymore
    B basai

    @toggledbits

    Apologies for the confusion.

    I was trying to indicate, although poorly, that I did install 'latest' at first which didn't correct the problem and then opted to go with 'stable' thinking that was the better choice.

    As far as the MSR Set Reaction using haas vs vera per my report, I was testing both and neither worked when the rule is triggered, however the light does turn off when I manually select the play button next to the Set Reaction Rule for either the set haas or vera case. Unfortunately I neglected to reflect that correctly in my report and hence the mismatch / confusion

    HTH
    -bh

    Multi-System Reactor

  • MSR Set Reaction not working anymore
    B basai

    Iron: QNAP NAS
    Running MSR and HAAS on Docker (QNAP Container Station)
    Reactor (Multi-hub) stable-22203-81a2f3cc
    Home Assistant Core 2022.6.7
    Vera 1.7.5186 (7.31)
    Config files are stored in shared volumes on the NAS.
    Office light in example is joined to Vera-Plus

    Hello all,

    I decided to upgrade MSR to latest-amd64. It wasn’t until afterwards that I noticed all rulesets broken. So unfortunately I’m not sure if this was already broken before or I broke it after upgrading. Yes poor judgement on my part for being complacent.

    Never the less, this is broken globally across all rulesets, even though I can see the triggers change to “True” (Turn green).

    For this example, I have a boolean helper toggle in HAAS called “TV MODE HAAS SW”.

    When toggled ‘on’, MSR should turn my Vera office light OFF and it doesn’t, but if I manually select the play button to the right of the line in the Set Reaction, it executes properly and turns off the Vera office light.

    The MSR Rule does not have any Constraints set.

    I can see in MSR it recognizes the state changes yet doesn’t execute the “Set Reaction”.

    Any help greatly appreciated.

    Log files from reactor.log and screen shots to follow:

    Reactor.log when toggling the haas helper, Set Reaction doesn’t execute.

    [stable-22203]2022-10-02T21:21:34.799Z <Rule:INFO> TV MODE ON (Rule#rule-l2hvuz8r) starting evaluation; because entity-changed Entity#hass>input_boolean_tv_mode
    [stable-22203]2022-10-02T21:21:34.800Z <Rule:INFO> TV MODE ON (Rule#rule-l2hvuz8r) evaluated; rule state transition from RESET to SET!
    [stable-22203]2022-10-02T21:21:34.819Z <Rule:INFO> TV MODE ON (Rule#rule-l2hvuz8r) evaluation complete
    [stable-22203]2022-10-02T21:21:34.820Z <Engine:INFO> Enqueueing "TV MODE ON<SET>" (rule-l2hvuz8r:S)
    [stable-22203]2022-10-02T21:21:34.835Z <Engine:NOTICE> Starting reaction TV MODE ON<SET> (rule-l2hvuz8r:S)
    [stable-22203]2022-10-02T21:21:34.835Z <Engine:INFO> TV MODE ON<SET> all actions completed.
    

    Reactor.log when manually triggering the Set Reaction with the play button which correctly turns off the light

    [stable-22203]2022-10-02T21:23:25.035Z <HassController:null> HassController#hass: sending payload for power_switch.off on Entity#hass>light_office_86 action: [Object]{ "type": "call_service", "service_data": { "entity_id": "light.office_86" }, "domain": "homeassistant", "service": "turn_off" }
    

    When toggled ON
    toggled_on.png

    Rule config screen
    tv_mode_config.png

    Multi-System Reactor

  • git hub docker container not available?
    B basai

    It may be that you need to pull "latest-[flavor]" and not just "latest" eg: latest-amd64 etc. dependent on the image specific to your installation type.
    -bh

    Multi-System Reactor

  • Is a global timestamp expression possible ?
    B basai

    @toggledbits Thank you for the reply and solution.

    What confused me was that as an expression created within a Rule it worked fine, but now that I read your reply I see why, this was a "Doh!" on my part, I hadn't thought of it like that.

    Thanks again!,
    -b

    Multi-System Reactor

  • Is a global timestamp expression possible ?
    B basai

    I’ve looked and can’t find the answer which concerns me that the answer is obvious and thats why I can't find the answer to this.

    I’m new to MSR and this is my first post, so please bare with me 🙂

    What I’m trying to do is have a global expression that contains the current time so I can use it in Global reactions as well as Rulesets as part of my syslog messages.

    Example of what I’m experiencing:
    In Expressions, create a global expression: gMyTOD = strftime("%T %D”)
    In Rulesets, in a rule, create a local expression: MyTOD = strftime("%T %D”)

    In that same rule create a Notify type of Syslog.
    Set syslog message to: gMyTOD time is ${{gMyTOD}} and MyTOD time is ${{MyTOD}}
    Trigger the rule.

    The result is that the local expression (MyTOD) contains the correct time but the global expression (gMyTOD) does not update and reflects the wrong time in the final syslog message.

    Is there a different approach I should be using?

    Thank you in advance for any insight.

    -bh

    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