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

sethlampman

@sethlampman
Existing Rule stopped working HTTP command fetching IP address from website
cw-kidC
Topic thumbnail image
Multi-System Reactor
Raspberry Pi 4 dual RAM variant introduced to mitigate RAM price increases
toggledbitsT
Article here that may be of interest to some: https://www.cnx-software.com/2026/02/05/raspberry-pi-4-dual-ram-variant-introduced-to-mitigate-ram-price-increases-and-supply-challenges/
SBC
Condition for trend
T
Topic thumbnail image
Multi-System Reactor
Set reaction triggering wrong z-wave device
T
Topic thumbnail image
Multi-System Reactor
Can you run MSR on Home Assistant OS ?
cw-kidC
Looking at using Home Assistant for the first time, either on a Home Assistant Green, their own hardware or buying a cheap second hand mini PC. Sounds like Home Assistant OS is linux based using Docker for HA etc. Would I also be able to install things like MSR as well on their OS ? On the same box? Thanks.
Multi-System Reactor
RPi Alternative: Orange Pi 4 LTS (3GB RAM/16GB eMMC)
toggledbitsT
The last of four boards I'm trying in this batch is the Orange Pi 4 LTS. I purchased a 3GB RAM + 16GB eMMC model from Amazon for $83, making it the most costly of the four boards tried, but still well under my US$100 limit. This board is powered by a Rockchip RK3399-T processor, ARM-compatible with dual Cortex-A72 cores and quad Cortex-A53 cores at 1.6Ghz (1.8Ghz for the 4GB model); compare this to the RPi 3B+ with four Cortex-A53 and the RPi 4B with four Cortex-A72, this board is a hybrid that I would expect to stand in the performance middle between the two RPi models. It's available in 3GB and 4GB DDR4 RAM configurations, with and without 16GB eMMC storage. It has a MicroSDHC slot, gigabit Ethernet, WiFi and BT, two USB 2.0 type A ports, one USB 3.0 type C port, a mini PCIe ribbon-cable connector (requires add-on board for standard connector), two each RPi-compatible camera and LCD ports, HDMI type A, and can be powered (5VDC/3A) via USB-C or DC type C (3.8mm OD/1.1mm ID) jack (center-positive), an odd and perhaps unwelcome departure from the more common type A (5.5mm/2.1mm). A serial port for console/debug can be connected by using a (not included) USB-TTL adapter (3.3V) via pin headers like the Orange Pi Zero 2. The included dual-band antenna connects via U.FL connector to the board, so it's easy substituting for another if you prefer. The manufacturer recommends use of a heat sink (which was included in the box). A metal cooling case is also offered by the manufacturer (a bundle with the metal case and a power supply is sold on Amazon for $90 as of this writing). The Orange Pi 4 LTS is somewhat longer than the RPi 4B, and although the boards are the same width, the mounting hole placement is different both in length and (oddly) width. Between this and the differences in connector locations, neither board is a drop-in replacecment for the other and their respective cases are not interchangeable. The 26-pin header is a subset of the RPi 4B's 40-pin header, so some HATs for the RPi may work (although the mounting hole differences will make securing them "interesting"), and some HATs will surely not. Models with eMMC storage have an OS installed and boot immediately with SSH daemon running and ready for login. Mine was running Debian Bullseye, which would probably be fine for most users. It had clearly been on there a while, because it needed a lot of updates, but it's a current distro, so you're running out of the box with something that will last. A different OS can be installed by downloading an image (once again I chose Ubuntu Jammy) and writing it to a MicroSD card, then booting the system from the SD card. You can either leave the system in that state (running the OS from the SD card), or copy the OS from the SD card to the eMMC. The latter is done by a script; documentation for the process is best described in the downloadable PDF User Manual. This took about 10 minutes and went smoothly, and I was able to boot the system without the SD card after the process completed. I have lingering questions around the value of the eMMC storage. It's definitely faster than using MicroSD or USB-based storage (I got 311MB/s average on a 4GB write, compared to MicroSD performance around 15MB/s), but it would take a long-term test of this product to determine if the on-board eMMC option has the stamina to take the write counts typical of Linux systems, and if its wear-leveling and error correction are sufficient to assure a long, error-free life. Given the high premium apparently being paid for including eMMC on the board, it should be fast and durable, but only time and experience (perhaps painful) would tell the latter. A careful configuration with other Flash-friendly filesystems could be used to reduce wear, but this is an advanced configuration/cookbook topic and beyond the scope of this writing. This question is also not unique to eMMC — MicroSD cards are also known to fail with high write cycles, so the use of a "high endurance" product is recommended for any and all systems using MicroSD as primary storage. The board has Mini PCIe capability, and that may be a storage alternative, but read on... Also bear in mind that the eMMC storage is fixed-size forever; it cannot be expanded, and 16GB can run out pretty quickly these days. Users of MicroSD cards for primary storage can upgrade to bigger cards, but when users of eMMC primary storage outgrow it, the only choice is to add a MicroSD card or other "external" storage to the system, move part of the filesystem to it, and then manage both storage devices and deal with the limitations and risks of both. As I mentioned with the Orange Pi Zero 2, if you are going to use this board as a home automation controller/gateway or similar role, it should (IMO) have a battery-backed real time clock (RTC), and Orange Pi offers an add-on module that connects directly to the 26-pin header on the board. An available expansion board provides a standard Mini PCIe interface and SIM card slot (hmm...), but it connects to the main board via a short ribbon cable, and its mounting holes have no complement on the main board, so it seems like it would be a fragile dangly thing that's a nuisance to deal with. I want to like this board more, and it's very capable, but I'm concerned about value. The limited options for eMMC (16GB or none), the question mark of the eMMC's longevity vs cost, the strange DC power connector choice, the lack of 40-pin GPIO on a full-size (plus) board, the inconsistent hole placement, and the fragile Mini PCIe arrangement, are all "cons" that devalue this board in my view. The price point is clearly driven by the additional capabilities of the board (camera support, ports, six core CPU, extra RAM, on-board eMMC storage), but unfortunately, a great many of these features may not be useful for home automation, and therefore potentially a waste of money. In terms of overall value, I still believe the Libre "Le Potato" seems a better choice to me, and the Orange Pi Zero 2 (very) a close second, but I'll admit I'm focused on a particular application and your needs may be better suited to what this board offers than mine. Passmark Results: OrangePi 4 LTS Cortex-A72 (aarch64) 6 cores @ 1200 MHz | 2.9 GiB RAM Number of Processes: 6 | Test Iterations: 1 | Test Duration: Medium -------------------------------------------------------------------------- CPU Mark: 583 Integer Math 12037 Million Operations/s Floating Point Math 2542 Million Operations/s Prime Numbers 4.5 Million Primes/s Sorting 3141 Thousand Strings/s Encryption 153 MB/s Compression 4049 KB/s CPU Single Threaded 154 Million Operations/s Physics 80.5 Frames/s Extended Instructions (NEON) 244 Million Matrices/s Memory Mark: 498 Database Operations 551 Thousand Operations/s Memory Read Cached 2524 MB/s Memory Read Uncached 2602 MB/s Memory Write 3182 MB/s Available RAM 1947 Megabytes Memory Latency 119 Nanoseconds Memory Threaded 6243 MB/s --------------- eMMC storage write 311MB/s average for 4GB; MicroSD (Samsung 32GB class 10) storage write 15MB/s.
SBC
RPi Alternative: Orange Pi Zero 2 (1GB)
toggledbitsT
Topic thumbnail image
SBC
RPi Alternative: Libre Computer AML-S905X-CC "Le Potato" (2GB RAM)
toggledbitsT
With Raspberry Pi boards continuing to be relatively scarce, I've been trying a few alternatives to see what may be usable and good. I had previously written about the Jetson Nano 2GB, which is great, but a little pricey, so I'm trying to find sub-US$100 boards that will run Reactor. I've got four that I'm trying now, but one in particular goes right to work in the most predictable way and seems worth a mention immediately: the Libre Computer Board AML-S905X-CC 2GB (known as "Le Potato"). The form factor is very similar to that of the Raspberry Pi 3 B+, and has comparable CPU (ARM Cortex-A53, quad 64-bit cores at 1.5+GHz -- slightly higher clock speed). It's US$35 on Amazon and LoverPi in the (recommended) 2GB configuration, and easy to get. Startup is like RPi: download one of the available OS images (Ubuntu, Raspbian, Debian, ARMbian, etc.) from their site and write the image to a MicroSD card, insert into slot, power up, and off you go. I tried the Ubuntu 22.04 image first and it comes right up. No problem getting nodejs 18.12.1 installed and running (with Reactor). No WiFi on board, but I don't see that as a minus for use as a controller/hub (which should be hard-wired, IMO). The 40-pin GPIO connector is compatible with typical RPi HATs (PoE, breakouts, etc.). There is an available eMMC (solid state storage) module to use instead of MicroSD, which I would recommend for long-term use. It runs US$25 for 32GB (64GB and 128GB available). The module is scarcely larger than the chip it carries, and has the smallest board-to-board connector I've ever seen. Next up: ESPRESSObin 2GB (spoiler: it's... technical...)
SBC
HA and AI
CatmanV2C
Having hours of (actually quite fun) interaction with AI (Chat GPT) making up dashboards and sensors for HA. It's OK (well it's better than I am!) but it makes soooo many mistakes. Gets there in the end though, if you've half a clue (which I do half the time) C
Home Assistant
How to upgrade from an old version of MSR?
cw-kidC
Hello I haven't updated my installation of MSR in a very long time. Its a bare metal Linux install currently on version 24366-3de60836 I see the latest version is now latest-26011-c621bbc7 I assume I cannot just jump from a very old version to the latest version? Or can I? Thanks
Multi-System Reactor
This trigger no longer working - complaining about the operator needing changing
cw-kidC
Topic thumbnail image
Multi-System Reactor
Self test
CatmanV2C
Having been messing around with some stuff I worked a way to self trigger some tests that I wanted to do on the HA <> MSR integration This got me wondering if there's an entity that changes state / is exposed when a configured controller goes off line? I can't see one but thought it might be hidden or something? Cheers C
Multi-System Reactor
Access control - allowing anonymous user to dashboard
tunnusT
Using build 25328 and having the following users.yaml configuration: users: # This section defines your valid users. admin: ******* groups: # This section defines your user groups. Optionally, it defines application # and API access restrictions (ACLs) for the group. Users may belong to # more than one group. Again, no required or special groups here. admin_group: users: - admin applications: true # special form allows access to ALL applications guests: users: "*" applications: - dashboard api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin_group allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: true session: timeout: 7200 # (seconds) rolling: true # activity extends timeout when true # If log_acls is true, the selected ACL for every API access is logged. log_acls: true # If debug_acls is true, even more information about ACL selection is logged. debug_acls: true My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
Multi-System Reactor
VEC Virtual Switch Auto Off
S
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules. I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds). Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off? With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches. Thanks Reactor (Multi-hub) latest-26011-c621bbc7 VirtualEntityController v25356 Synology Docker
Multi-System Reactor
Upcoming Storage Change -- Got Back-ups?
toggledbitsT
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future. In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level. Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way. I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption. A few other things to know: If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc. Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy). The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON. You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach). The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case. This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change. This thread is open for any questions or concerns.
Multi-System Reactor
Oddness in Copy/Move of Reactions
G
Topic thumbnail image
Multi-System Reactor
[Solved] function isRuleEnabled() issue
CrilleC
Topic thumbnail image
Multi-System Reactor
[Reactor] Problem with Global Reactions and groups
therealdbT
Topic thumbnail image
Multi-System Reactor
Possible feature request 2?
CatmanV2C
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks. Any chance of a 'bulk delete' option? No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices Cheers C
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
About
Posts
16
Topics
7
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial
  • Issue with MSR UI becoming unresponsive
    S sethlampman

    sorry for all the replies here but.. I deleted the device trackers and they all just reappear. They are coming from HA even though I have removed Opnsense integration. So I added this to my reactor.yaml

    
      filter_entity:
        - "/^device_tracker_/"

    Deleted the tracker jsons, restarted docker and the problem is 100% resolved. I am now trying to figure out how to get rid of these in HA. very annoying....

    Multi-System Reactor
  • Issue with MSR UI becoming unresponsive
    S sethlampman

    Also I literally have over 1000 of these, could that be causing an issue? The only think I can think of is I enabled Opnsense data gathering in Home assistant (i've since disabled). I dont mind deleting them but right now it appears as if I have to do it one by one which would be tedious.

    edit I found them in /storage/entities/hass and there were 50k of them. I deleted and going to see if that had any bearing on this.

    image.png

    Multi-System Reactor
  • Issue with MSR UI becoming unresponsive
    S sethlampman

    just for Sh*t's and giggles, I tried doing a restore on a non docker bare metal environment and you are 100% right, the issues followed. Back to the original env... Is there a way to disable live search? that would help a lot I'm guessing. I start typing and the ui is very responsive. Then I start pressing the backspace key and the live search responds until i get to 1 letter and then she freezes for 30 seconds to a minute or longer. Thinking back I used to have this issue while trying to manage MSR on my phone browser sometimes. I would just move to a computer browser and all would be fine. would the logs be helpful? I posted all that I could, for some reason I cannot upload a file

    [latest-25328]2025-12-01T18:03:50.905Z <Rule:INFO> Closed - Right Shade - L (rule-grp13yiveal in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10161
[latest-25328]2025-12-01T18:03:50.905Z <Rule:INFO> Open - Right Shade - L (rule-grp13yjkbak in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10161
[latest-25328]2025-12-01T18:03:50.905Z <Rule:INFO> Shades - Center Open (rule-94 in Sunroom) starting rule state evaluation; because entity-changed Cover#vera>device_10165, entity-changed Cover#vera>device_10441
[latest-25328]2025-12-01T18:03:50.906Z <Rule:INFO> Shades - Center Closed (rule-98 in Sunroom) starting rule state evaluation; because entity-changed Cover#vera>device_10165, entity-changed Cover#vera>device_10167, entity-changed Cover#vera>device_10441
[latest-25328]2025-12-01T18:03:50.907Z <Rule:INFO> Shades - Center Right Shade Partially Closed (rule-m29j3nwf in Sunroom) starting rule state evaluation; because entity-changed Cover#vera>device_10165, entity-changed Cover#vera>device_10167, entity-changed Cover#vera>device_10441
[latest-25328]2025-12-01T18:03:50.909Z <Rule:INFO> Closed - Center Shade - CL (rule-grp13x7waga in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10165
[latest-25328]2025-12-01T18:03:50.909Z <Rule:INFO> Open - Center Shade - CL (rule-grp13x8479w in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10165
[latest-25328]2025-12-01T18:03:50.909Z <Rule:INFO> Closed - Center Shade - R (rule-grp13x7yauz in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10167
[latest-25328]2025-12-01T18:03:50.909Z <Rule:INFO> Open - Center Shade - R (rule-grp13x86vl5 in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10167
[latest-25328]2025-12-01T18:03:50.909Z <Rule:INFO> Left Shades Open (rule-91 in Sunroom) starting rule state evaluation; because entity-changed Cover#vera>device_10444, entity-changed Cover#vera>device_10160, entity-changed Cover#vera>device_10451
[latest-25328]2025-12-01T18:03:50.910Z <Rule:INFO> Closed - Left Shade - L (rule-grp13x60f0y in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10444
[latest-25328]2025-12-01T18:03:50.911Z <Rule:INFO> Open - Left Shade - L (rule-grp13x7bvkl in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10444
[latest-25328]2025-12-01T18:03:50.911Z <Rule:INFO> Closed - Right Shade - R (rule-grp13yjieiy in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10445
[latest-25328]2025-12-01T18:03:50.911Z <Rule:INFO> Open - Right Shade - R (rule-grp13yjnsd4 in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10445
[latest-25328]2025-12-01T18:03:50.911Z <Rule:INFO> BI ~Global~ Profile Night @ Civil Dusk (rule-grp1indyjrw in Security - Blue Iris) starting rule state evaluation; because entity-changed SecuritySensor#vera>device_10237
[latest-25328]2025-12-01T18:03:50.911Z <Rule:INFO> MBR - Minimote - Button 1 - All Lights On + Temp XMAS (rule-grpx8pim5l in MBR Lighting) starting rule state evaluation; because entity-changed Entity#vera>device_10024
[latest-25328]2025-12-01T18:03:50.912Z <Rule:INFO> MBR - Minimote - Button 2 - MBR Dim + Temp XMAS (rule-ljuf4mxu in MBR Lighting) starting rule state evaluation; because entity-changed Entity#vera>device_10024
[latest-25328]2025-12-01T18:03:50.912Z <Rule:INFO> MBR - Minimote - Button 3 - MBR Off + Security Lighting + Temp XMAS (rule-ljuf65hu in MBR Lighting) starting rule state evaluation; because entity-changed Entity#vera>device_10024
[latest-25328]2025-12-01T18:03:50.912Z <Rule:INFO> MBR - Minimote - Button 4 - Really DIM + Temp XMAS (rule-grpxen1h3w in MBR Lighting) starting rule state evaluation; because entity-changed Entity#vera>device_10024
[latest-25328]2025-12-01T18:03:50.912Z <Rule:INFO> Kitchen Minimote - Button 1 tap - Downstairs On (rule-grpxan4n87 in Kitchen) starting rule state evaluation; because entity-changed Entity#vera>device_10036
[latest-25328]2025-12-01T18:03:50.912Z <Rule:INFO> Kitchen Minimote - Button 2 tap - Dim Downstairs (rule-grpxanakbk in Kitchen) starting rule state evaluation; because entity-changed Entity#vera>device_10036
[latest-25328]2025-12-01T18:03:50.913Z <Rule:INFO> Kitchen Minimote - Button 3 tap - Kitchen On (rule-grpxam8jfz in Kitchen) starting rule state evaluation; because entity-changed Entity#vera>device_10036
[latest-25328]2025-12-01T18:03:50.913Z <Rule:INFO> Kitchen Minimote - Button 3 hold - Kitchen On Bright (rule-m0hnaif4 in Kitchen) starting rule state evaluation; because entity-changed Entity#vera>device_10036
[latest-25328]2025-12-01T18:03:50.913Z <Rule:INFO> Kitchen Minimote - Button 4 tap - Kitchen Off (rule-grpxam8lmi in Kitchen) starting rule state evaluation; because entity-changed Entity#vera>device_10036
[latest-25328]2025-12-01T18:03:50.913Z <Rule:INFO> Kitchen Minimote - Button 4 hold - Kitchen Evening (rule-m0ki8muh in Kitchen) starting rule state evaluation; because entity-changed Entity#vera>device_10036
[latest-25328]2025-12-01T18:03:50.913Z <Rule:INFO> Minimote - Button 1 tap - Brenda's Office ON (rule-ls2drjuo in Brendas Office) starting rule state evaluation; because entity-changed Entity#vera>device_10056
[latest-25328]2025-12-01T18:03:50.914Z <Rule:INFO> Minimote - Button 2 tap - Brenda's Office OFF (rule-ls2drnb6 in Brendas Office) starting rule state evaluation; because entity-changed Entity#vera>device_10056
[latest-25328]2025-12-01T18:03:50.914Z <Rule:INFO> Minimote - Button 3 tap - Brenda's Office Med Dim (rule-ls2drtzw in Brendas Office) starting rule state evaluation; because entity-changed Entity#vera>device_10056
[latest-25328]2025-12-01T18:03:50.915Z <Rule:INFO> Minimote - Button 4 tap - Brenda's Office Very Dim (rule-ls2drxo1 in Brendas Office) starting rule state evaluation; because entity-changed Entity#vera>device_10056
[latest-25328]2025-12-01T18:03:50.915Z <Rule:INFO> Garage Worklight ON - Motion (rule-lss1u12y in Garage) starting rule state evaluation; because entity-changed SecuritySensor#vera>device_10365
[latest-25328]2025-12-01T18:03:50.915Z <Rule:INFO> Garage Light ON - Interior Door, External garage door, PIR (rule-lrn2n18a in Garage) starting rule state evaluation; because entity-changed SecuritySensor#vera>device_10365
[latest-25328]2025-12-01T18:03:50.915Z <Rule:INFO> Garage Light OFF - No Motion for 10min (rule-lrn2i4ih in Garage) starting rule state evaluation; because entity-changed SecuritySensor#vera>device_10365
[latest-25328]2025-12-01T18:03:50.916Z <Rule:INFO> BI ~Garage Cameras Motion ON - No Motion inside Garage (rule-lr5yb2a0 in Security - Blue Iris) starting rule state evaluation; because entity-changed SecuritySensor#vera>device_10365
[latest-25328]2025-12-01T18:03:50.916Z <Rule:INFO> BL - Minimote - Button 1 - Bedtime (no company) + Temp XMAS (rule-grpxacwh5h in MBR Lighting) starting rule state evaluation; because entity-changed Entity#vera>device_10134
[latest-25328]2025-12-01T18:03:50.916Z <Rule:INFO> BL - Minimote - Button 2 - MBR Dim + Temp XMAS (rule-grpxadoh2y in MBR Lighting) starting rule state evaluation; because entity-changed Entity#vera>device_10134
[latest-25328]2025-12-01T18:03:50.916Z <Rule:INFO> BL - Minimote - Button 3 - MBR Off + Safety Lighting + Temp XMAS (rule-grpxaduapm in MBR Lighting) starting rule state evaluation; because entity-changed Entity#vera>device_10134
[latest-25328]2025-12-01T18:03:50.917Z <Rule:INFO> BL - Minimote - Button 4 - Bedroom Really Dim + Temp XMAS (rule-grpxady4ip in MBR Lighting) starting rule state evaluation; because entity-changed Entity#vera>device_10134
[latest-25328]2025-12-01T18:03:50.917Z <Rule:INFO> Remote - Button 1 ON // Left Shades Open (rule-grpy7qw8qm in Sunroom) starting rule state evaluation; because entity-changed Entity#vera>device_10150
[latest-25328]2025-12-01T18:03:50.917Z <Rule:INFO> Remote - Button 1 OFF // Left Shades Closed (rule-grpy7qxwc8 in Sunroom) starting rule state evaluation; because entity-changed Entity#vera>device_10150
[latest-25328]2025-12-01T18:03:50.917Z <Rule:INFO> Remote - Button 2 ON // Center Shades Open (rule-grpyegg15i in Sunroom) starting rule state evaluation; because entity-changed Entity#vera>device_10150
[latest-25328]2025-12-01T18:03:50.918Z <Rule:INFO> Remote - Button 2 OFF // Center Shades Closed (rule-grpyeghilp in Sunroom) starting rule state evaluation; because entity-changed Entity#vera>device_10150
[latest-25328]2025-12-01T18:03:50.918Z <Rule:INFO> Remote - Button 3 ON // Right Shades Open (rule-grpyegkz7s in Sunroom) starting rule state evaluation; because entity-changed Entity#vera>device_10150
[latest-25328]2025-12-01T18:03:50.918Z <Rule:INFO> Remote - Button 3 OFF // Right Shades Closed (rule-grpyegmlme in Sunroom) starting rule state evaluation; because entity-changed Entity#vera>device_10150
[latest-25328]2025-12-01T18:03:50.918Z <Rule:INFO> Remote - Button 4 ON // Landsdcape Lights On (rule-grpy6ykcsl in Sunroom) starting rule state evaluation; because entity-changed Entity#vera>device_10150
[latest-25328]2025-12-01T18:03:50.918Z <Rule:INFO> Remote - Button 4 OFF // Landscape Lights Off (rule-grpy6ykenn in Sunroom) starting rule state evaluation; because entity-changed Entity#vera>device_10150
[latest-25328]2025-12-01T18:03:50.918Z <Rule:INFO> Closed - Left Shade - R (rule-grp13x75942 in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10160
[latest-25328]2025-12-01T18:03:50.919Z <Rule:INFO> Open - Left Shade - R (rule-grp13x7hjq0 in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10160
[latest-25328]2025-12-01T18:03:50.919Z <Rule:INFO> Closed - Center Shade - L (rule-grp13x7rd3o in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10441
[latest-25328]2025-12-01T18:03:50.919Z <Rule:INFO> Open - Center Shade - L (rule-grp13x82q9h in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10441
[latest-25328]2025-12-01T18:03:50.919Z <Rule:INFO> Closed - Left Shade - C (rule-grp13x66th4 in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10451
[latest-25328]2025-12-01T18:03:50.919Z <Rule:INFO> Open - Left Shade - C (rule-grp13x7fsdh in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10451
[latest-25328]2025-12-01T18:03:50.919Z <Rule:INFO> Rule#rule-lo4s7vnz rule state evaluation(s) pending, will start after release of semaphore
[latest-25328]2025-12-01T18:03:50.919Z <Rule:INFO> Rule#rule-l3p3k82u rule state evaluation(s) pending, will start after release of semaphore
[latest-25328]2025-12-01T18:03:50.919Z <Rule:INFO> Rule#rule-mb3xi9ku rule state evaluation(s) pending, will start after release of semaphore
[latest-25328]2025-12-01T18:03:50.920Z <Rule:INFO> Rule#rule-101 rule state evaluation(s) pending, will start after release of semaphore
[latest-25328]2025-12-01T18:03:50.920Z <Rule:INFO> Rule#rule-l1totlyh rule state evaluation(s) pending, will start after release of semaphore
[latest-25328]2025-12-01T18:03:50.920Z <Rule:INFO> Rule#rule-94 rule state evaluation(s) pending, will start after release of semaphore
[latest-25328]2025-12-01T18:03:50.920Z <Rule:INFO> Rule#rule-98 rule state evaluation(s) pending, will start after release of semaphore
[latest-25328]2025-12-01T18:03:50.920Z <Rule:INFO> Rule#rule-m29j3nwf rule state evaluation(s) pending, will start after release of semaphore
[latest-25328]2025-12-01T18:03:50.920Z <Rule:INFO> Rule#rule-91 rule state evaluation(s) pending, will start after release of semaphore
[latest-25328]2025-12-01T18:03:50.920Z <Rule:INFO> Pool - Camera IR ON // Sunroom Shades Closed (rule-lo4s7vnz in Security) starting rule state evaluation
[latest-25328]2025-12-01T18:03:50.921Z <Rule:INFO> Shades - Right Open (rule-l3p3k82u in Sunroom) starting rule state evaluation
[latest-25328]2025-12-01T18:03:50.922Z <Rule:INFO> Shades - Right Open - 8AM (rule-mb3xi9ku in Sunroom) starting rule state evaluation
[latest-25328]2025-12-01T18:03:50.922Z <Rule:INFO> Shades - Right Closed (rule-101 in Sunroom) starting rule state evaluation
[latest-25328]2025-12-01T18:03:50.923Z <Rule:INFO> Landscape - Lighting Off // Sunroom shades closed late evening (rule-l1totlyh in Outside) starting rule state evaluation
[latest-25328]2025-12-01T18:03:50.924Z <Rule:INFO> Shades - Center Open (rule-94 in Sunroom) starting rule state evaluation
[latest-25328]2025-12-01T18:03:50.925Z <Rule:INFO> Shades - Center Closed (rule-98 in Sunroom) starting rule state evaluation
[latest-25328]2025-12-01T18:03:50.926Z <Rule:INFO> Shades - Center Right Shade Partially Closed (rule-m29j3nwf in Sunroom) starting rule state evaluation
[latest-25328]2025-12-01T18:03:50.927Z <Rule:INFO> Left Shades Open (rule-91 in Sunroom) starting rule state evaluation
[latest-25328]2025-12-01T18:03:54.220Z <Rule:INFO> Seths Office Minimote - Button 1 tap - Lights ON (rule-lhb27vur in Seth's Office) starting rule state evaluation; because entity-changed Entity#vera>device_10051
[latest-25328]2025-12-01T18:03:54.220Z <Rule:INFO> Seths Office Minimote - Button 2 tap - All OFF (rule-grpxf30nws in Seth's Office) starting rule state evaluation; because entity-changed Entity#vera>device_10051
[latest-25328]2025-12-01T18:03:54.221Z <Rule:INFO> Seths Office Minimote - Button 3 tap - DIM (rule-grpxf30pf6 in Seth's Office) starting rule state evaluation; because entity-changed Entity#vera>device_10051
[latest-25328]2025-12-01T18:03:54.221Z <Rule:INFO> Pool - Camera IR ON // Sunroom Shades Closed (rule-lo4s7vnz in Security) starting rule state evaluation; because entity-changed Cover#vera>device_10336, entity-changed Cover#vera>device_10161, entity-changed Cover#vera>device_10165, entity-changed Cover#vera>device_10167, entity-changed Cover#vera>device_10444, entity-changed Cover#vera>device_10445, entity-changed Cover#vera>device_10160, entity-changed Cover#vera>device_10441, entity-changed Cover#vera>device_10451
[latest-25328]2025-12-01T18:03:54.222Z <Rule:INFO> Shades - Right Open (rule-l3p3k82u in Sunroom) starting rule state evaluation; because entity-changed Cover#vera>device_10336, entity-changed Cover#vera>device_10161, entity-changed Cover#vera>device_10445
[latest-25328]2025-12-01T18:03:54.224Z <Rule:INFO> Shades - Right Open - 8AM (rule-mb3xi9ku in Sunroom) starting rule state evaluation; because entity-changed Cover#vera>device_10336, entity-changed Cover#vera>device_10161, entity-changed Cover#vera>device_10445
[latest-25328]2025-12-01T18:03:54.225Z <Rule:INFO> Shades - Right Closed (rule-101 in Sunroom) starting rule state evaluation; because entity-changed Cover#vera>device_10336, entity-changed Cover#vera>device_10161, entity-changed Cover#vera>device_10445
[latest-25328]2025-12-01T18:03:54.226Z <Rule:INFO> Closed - Right Shade - C (rule-grp13yjgb9b in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10336
[latest-25328]2025-12-01T18:03:54.227Z <Rule:INFO> Open - Right Shade - C (rule-grp13yjm4dq in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10336
[latest-25328]2025-12-01T18:03:54.227Z <Rule:INFO> Landscape - Lighting Off // Sunroom shades closed late evening (rule-l1totlyh in Outside) starting rule state evaluation; because entity-changed Cover#vera>device_10336, entity-changed Cover#vera>device_10161, entity-changed Cover#vera>device_10165, entity-changed Cover#vera>device_10167, entity-changed Cover#vera>device_10444, entity-changed Cover#vera>device_10445, entity-changed Cover#vera>device_10160, entity-changed Cover#vera>device_10441, entity-changed Cover#vera>device_10451
[latest-25328]2025-12-01T18:03:54.227Z <Rule:INFO> Closed - Right Shade - L (rule-grp13yiveal in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10161
[latest-25328]2025-12-01T18:03:54.228Z <Rule:INFO> Open - Right Shade - L (rule-grp13yjkbak in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10161
[latest-25328]2025-12-01T18:03:54.229Z <Rule:INFO> Shades - Center Open (rule-94 in Sunroom) starting rule state evaluation; because entity-changed Cover#vera>device_10165, entity-changed Cover#vera>device_10441
[latest-25328]2025-12-01T18:03:54.230Z <Rule:INFO> Shades - Center Closed (rule-98 in Sunroom) starting rule state evaluation; because entity-changed Cover#vera>device_10165, entity-changed Cover#vera>device_10167, entity-changed Cover#vera>device_10441
[latest-25328]2025-12-01T18:03:54.232Z <Rule:INFO> Shades - Center Right Shade Partially Closed (rule-m29j3nwf in Sunroom) starting rule state evaluation; because entity-changed Cover#vera>device_10165, entity-changed Cover#vera>device_10167, entity-changed Cover#vera>device_10441
[latest-25328]2025-12-01T18:03:54.233Z <Rule:INFO> Closed - Center Shade - CL (rule-grp13x7waga in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10165
[latest-25328]2025-12-01T18:03:54.234Z <Rule:INFO> Open - Center Shade - CL (rule-grp13x8479w in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10165
[latest-25328]2025-12-01T18:03:54.234Z <Rule:INFO> Closed - Center Shade - R (rule-grp13x7yauz in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10167
[latest-25328]2025-12-01T18:03:54.234Z <Rule:INFO> Open - Center Shade - R (rule-grp13x86vl5 in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10167
[latest-25328]2025-12-01T18:03:54.235Z <Rule:INFO> Left Shades Open (rule-91 in Sunroom) starting rule state evaluation; because entity-changed Cover#vera>device_10444, entity-changed Cover#vera>device_10160, entity-changed Cover#vera>device_10451
[latest-25328]2025-12-01T18:03:54.236Z <Rule:INFO> Closed - Left Shade - L (rule-grp13x60f0y in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10444
[latest-25328]2025-12-01T18:03:54.237Z <Rule:INFO> Open - Left Shade - L (rule-grp13x7bvkl in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10444
[latest-25328]2025-12-01T18:03:54.237Z <Rule:INFO> Closed - Right Shade - R (rule-grp13yjieiy in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10445
[latest-25328]2025-12-01T18:03:54.237Z <Rule:INFO> Open - Right Shade - R (rule-grp13yjnsd4 in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10445
[latest-25328]2025-12-01T18:03:54.237Z <Rule:INFO> BI ~Global~ Profile Night @ Civil Dusk (rule-grp1indyjrw in Security - Blue Iris) starting rule state evaluation; because entity-changed SecuritySensor#vera>device_10237
[latest-25328]2025-12-01T18:03:54.237Z <Rule:INFO> MBR - Minimote - Button 1 - All Lights On + Temp XMAS (rule-grpx8pim5l in MBR Lighting) starting rule state evaluation; because entity-changed Entity#vera>device_10024
[latest-25328]2025-12-01T18:03:54.238Z <Rule:INFO> MBR - Minimote - Button 2 - MBR Dim + Temp XMAS (rule-ljuf4mxu in MBR Lighting) starting rule state evaluation; because entity-changed Entity#vera>device_10024
[latest-25328]2025-12-01T18:03:54.238Z <Rule:INFO> MBR - Minimote - Button 3 - MBR Off + Security Lighting + Temp XMAS (rule-ljuf65hu in MBR Lighting) starting rule state evaluation; because entity-changed Entity#vera>device_10024
[latest-25328]2025-12-01T18:03:54.238Z <Rule:INFO> MBR - Minimote - Button 4 - Really DIM + Temp XMAS (rule-grpxen1h3w in MBR Lighting) starting rule state evaluation; because entity-changed Entity#vera>device_10024
[latest-25328]2025-12-01T18:03:54.239Z <Rule:INFO> Kitchen Minimote - Button 1 tap - Downstairs On (rule-grpxan4n87 in Kitchen) starting rule state evaluation; because entity-changed Entity#vera>device_10036
[latest-25328]2025-12-01T18:03:54.239Z <Rule:INFO> Kitchen Minimote - Button 2 tap - Dim Downstairs (rule-grpxanakbk in Kitchen) starting rule state evaluation; because entity-changed Entity#vera>device_10036
[latest-25328]2025-12-01T18:03:54.239Z <Rule:INFO> Kitchen Minimote - Button 3 tap - Kitchen On (rule-grpxam8jfz in Kitchen) starting rule state evaluation; because entity-changed Entity#vera>device_10036
[latest-25328]2025-12-01T18:03:54.239Z <Rule:INFO> Kitchen Minimote - Button 3 hold - Kitchen On Bright (rule-m0hnaif4 in Kitchen) starting rule state evaluation; because entity-changed Entity#vera>device_10036
[latest-25328]2025-12-01T18:03:54.240Z <Rule:INFO> Kitchen Minimote - Button 4 tap - Kitchen Off (rule-grpxam8lmi in Kitchen) starting rule state evaluation; because entity-changed Entity#vera>device_10036
[latest-25328]2025-12-01T18:03:54.240Z <Rule:INFO> Kitchen Minimote - Button 4 hold - Kitchen Evening (rule-m0ki8muh in Kitchen) starting rule state evaluation; because entity-changed Entity#vera>device_10036
[latest-25328]2025-12-01T18:03:54.240Z <Rule:INFO> Minimote - Button 1 tap - Brenda's Office ON (rule-ls2drjuo in Brendas Office) starting rule state evaluation; because entity-changed Entity#vera>device_10056
[latest-25328]2025-12-01T18:03:54.241Z <Rule:INFO> Minimote - Button 2 tap - Brenda's Office OFF (rule-ls2drnb6 in Brendas Office) starting rule state evaluation; because entity-changed Entity#vera>device_10056
[latest-25328]2025-12-01T18:03:54.241Z <Rule:INFO> Minimote - Button 3 tap - Brenda's Office Med Dim (rule-ls2drtzw in Brendas Office) starting rule state evaluation; because entity-changed Entity#vera>device_10056
[latest-25328]2025-12-01T18:03:54.241Z <Rule:INFO> Minimote - Button 4 tap - Brenda's Office Very Dim (rule-ls2drxo1 in Brendas Office) starting rule state evaluation; because entity-changed Entity#vera>device_10056
[latest-25328]2025-12-01T18:03:54.241Z <Rule:INFO> Garage Worklight ON - Motion (rule-lss1u12y in Garage) starting rule state evaluation; because entity-changed SecuritySensor#vera>device_10365
[latest-25328]2025-12-01T18:03:54.242Z <Rule:INFO> Garage Light ON - Interior Door, External garage door, PIR (rule-lrn2n18a in Garage) starting rule state evaluation; because entity-changed SecuritySensor#vera>device_10365
[latest-25328]2025-12-01T18:03:54.243Z <Rule:INFO> Garage Light OFF - No Motion for 10min (rule-lrn2i4ih in Garage) starting rule state evaluation; because entity-changed SecuritySensor#vera>device_10365
[latest-25328]2025-12-01T18:03:54.243Z <Rule:INFO> BI ~Garage Cameras Motion ON - No Motion inside Garage (rule-lr5yb2a0 in Security - Blue Iris) starting rule state evaluation; because entity-changed SecuritySensor#vera>device_10365
[latest-25328]2025-12-01T18:03:54.243Z <Rule:INFO> BL - Minimote - Button 1 - Bedtime (no company) + Temp XMAS (rule-grpxacwh5h in MBR Lighting) starting rule state evaluation; because entity-changed Entity#vera>device_10134
[latest-25328]2025-12-01T18:03:54.243Z <Rule:INFO> BL - Minimote - Button 2 - MBR Dim + Temp XMAS (rule-grpxadoh2y in MBR Lighting) starting rule state evaluation; because entity-changed Entity#vera>device_10134
[latest-25328]2025-12-01T18:03:54.244Z <Rule:INFO> BL - Minimote - Button 3 - MBR Off + Safety Lighting + Temp XMAS (rule-grpxaduapm in MBR Lighting) starting rule state evaluation; because entity-changed Entity#vera>device_10134
[latest-25328]2025-12-01T18:03:54.244Z <Rule:INFO> BL - Minimote - Button 4 - Bedroom Really Dim + Temp XMAS (rule-grpxady4ip in MBR Lighting) starting rule state evaluation; because entity-changed Entity#vera>device_10134
[latest-25328]2025-12-01T18:03:54.244Z <Rule:INFO> Remote - Button 1 ON // Left Shades Open (rule-grpy7qw8qm in Sunroom) starting rule state evaluation; because entity-changed Entity#vera>device_10150
[latest-25328]2025-12-01T18:03:54.244Z <Rule:INFO> Remote - Button 1 OFF // Left Shades Closed (rule-grpy7qxwc8 in Sunroom) starting rule state evaluation; because entity-changed Entity#vera>device_10150
[latest-25328]2025-12-01T18:03:54.245Z <Rule:INFO> Remote - Button 2 ON // Center Shades Open (rule-grpyegg15i in Sunroom) starting rule state evaluation; because entity-changed Entity#vera>device_10150
[latest-25328]2025-12-01T18:03:54.245Z <Rule:INFO> Remote - Button 2 OFF // Center Shades Closed (rule-grpyeghilp in Sunroom) starting rule state evaluation; because entity-changed Entity#vera>device_10150
[latest-25328]2025-12-01T18:03:54.245Z <Rule:INFO> Remote - Button 3 ON // Right Shades Open (rule-grpyegkz7s in Sunroom) starting rule state evaluation; because entity-changed Entity#vera>device_10150
[latest-25328]2025-12-01T18:03:54.246Z <Rule:INFO> Remote - Button 3 OFF // Right Shades Closed (rule-grpyegmlme in Sunroom) starting rule state evaluation; because entity-changed Entity#vera>device_10150
[latest-25328]2025-12-01T18:03:54.246Z <Rule:INFO> Remote - Button 4 ON // Landsdcape Lights On (rule-grpy6ykcsl in Sunroom) starting rule state evaluation; because entity-changed Entity#vera>device_10150
[latest-25328]2025-12-01T18:03:54.246Z <Rule:INFO> Remote - Button 4 OFF // Landscape Lights Off (rule-grpy6ykenn in Sunroom) starting rule state evaluation; because entity-changed Entity#vera>device_10150
[latest-25328]2025-12-01T18:03:54.246Z <Rule:INFO> Closed - Left Shade - R (rule-grp13x75942 in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10160
[latest-25328]2025-12-01T18:03:54.246Z <Rule:INFO> Open - Left Shade - R (rule-grp13x7hjq0 in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10160
[latest-25328]2025-12-01T18:03:54.247Z <Rule:INFO> Closed - Center Shade - L (rule-grp13x7rd3o in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10441
[latest-25328]2025-12-01T18:03:54.247Z <Rule:INFO> Open - Center Shade - L (rule-grp13x82q9h in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10441
[latest-25328]2025-12-01T18:03:54.247Z <Rule:INFO> Closed - Left Shade - C (rule-grp13x66th4 in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10451
[latest-25328]2025-12-01T18:03:54.247Z <Rule:INFO> Open - Left Shade - C (rule-grp13x7fsdh in Sunroom Shade Watchdog) starting rule state evaluation; because entity-changed Cover#vera>device_10451
[latest-25328]2025-12-01T18:03:54.247Z <Rule:INFO> Rule#rule-lo4s7vnz rule state evaluation(s) pending, will start after release of semaphore
[latest-25328]2025-12-01T18:03:54.248Z <Rule:INFO> Rule#rule-l3p3k82u rule state evaluation(s) pending, will start after release of semaphore
[latest-25328]2025-12-01T18:03:54.248Z <Rule:INFO> Rule#rule-mb3xi9ku rule state evaluation(s) pending, will start after release of semaphore
[latest-25328]2025-12-01T18:03:54.248Z <Rule:INFO> Rule#rule-101 rule state evaluation(s) pending, will start after release of semaphore
[latest-25328]2025-12-01T18:03:54.248Z <Rule:INFO> Rule#rule-l1totlyh rule state evaluation(s) pending, will start after release of semaphore
[latest-25328]2025-12-01T18:03:54.248Z <Rule:INFO> Rule#rule-94 rule state evaluation(s) pending, will start after release of semaphore
[latest-25328]2025-12-01T18:03:54.248Z <Rule:INFO> Rule#rule-98 rule state evaluation(s) pending, will start after release of semaphore
[latest-25328]2025-12-01T18:03:54.248Z <Rule:INFO> Rule#rule-m29j3nwf rule state evaluation(s) pending, will start after release of semaphore
[latest-25328]2025-12-01T18:03:54.248Z <Rule:INFO> Rule#rule-91 rule state evaluation(s) pending, will start after release of semaphore
[latest-25328]2025-12-01T18:03:54.248Z <Rule:INFO> Pool - Camera IR ON // Sunroom Shades Closed (rule-lo4s7vnz in Security) starting rule state evaluation
[latest-25328]2025-12-01T18:03:54.249Z <Rule:INFO> Shades - Right Open (rule-l3p3k82u in Sunroom) starting rule state evaluation
[latest-25328]2025-12-01T18:03:54.251Z <Rule:INFO> Shades - Right Open - 8AM (rule-mb3xi9ku in Sunroom) starting rule state evaluation
[latest-25328]2025-12-01T18:03:54.252Z <Rule:INFO> Shades - Right Closed (rule-101 in Sunroom) starting rule state evaluation
[latest-25328]2025-12-01T18:03:54.254Z <Rule:INFO> Landscape - Lighting Off // Sunroom shades closed late evening (rule-l1totlyh in Outside) starting rule state evaluation
[latest-25328]2025-12-01T18:03:54.254Z <Rule:INFO> Shades - Center Open (rule-94 in Sunroom) starting rule state evaluation
[latest-25328]2025-12-01T18:03:54.257Z <Rule:INFO> Shades - Center Closed (rule-98 in Sunroom) starting rule state evaluation
[latest-25328]2025-12-01T18:03:54.258Z <Rule:INFO> Shades - Center Right Shade Partially Closed (rule-m29j3nwf in Sunroom) starting rule state evaluation
[latest-25328]2025-12-01T18:03:54.260Z <Rule:INFO> Left Shades Open (rule-91 in Sunroom) starting rule state evaluation
[latest-25328]2025-12-01T18:03:54.430Z <Rule:INFO> Turn On House Lights After Dark (rule-grptyruxy6 in House Auto Lighting) starting rule state evaluation; because expression-state-changed GlobalExpression#SRAdjustedLuxLevelR
[latest-25328]2025-12-01T18:03:54.431Z <Rule:INFO> Shades - Right Open (rule-l3p3k82u in Sunroom) starting rule state evaluation; because expression-state-changed GlobalExpression#SRAdjustedLuxLevelR
[latest-25328]2025-12-01T18:03:54.433Z <Rule:INFO> Shades - Right Closed (rule-101 in Sunroom) starting rule state evaluation; because entity-changed ValueSensor#hass>sensor_sr_right_shade_4in1_illuminance
[latest-25328]2025-12-01T18:03:54.435Z <Rule:INFO> Landscape - Lighting On // Shade LUX below 100 (rule-l1tnl5yf in Outside) starting rule state evaluation; because entity-changed ValueSensor#hass>sensor_sr_right_shade_4in1_illuminance
[latest-25328]2025-12-01T18:03:55.783Z <Rule:INFO> Turn On House Lights After Dark (rule-grptyruxy6 in House Auto Lighting) starting rule state evaluation; because expression-state-changed GlobalExpression#SRAdjustedLuxLevelR
[latest-25328]2025-12-01T18:03:55.783Z <Rule:INFO> Shades - Right Open (rule-l3p3k82u in Sunroom) starting rule state evaluation; because expression-state-changed GlobalExpression#SRAdjustedLuxLevelR
[latest-25328]2025-12-01T18:03:55.785Z <Rule:INFO> Shades - Right Closed (rule-101 in Sunroom) starting rule state evaluation; because entity-changed ValueSensor#hass>sensor_sr_right_shade_4in1_illuminance
[latest-25328]2025-12-01T18:03:55.787Z <Rule:INFO> Landscape - Lighting On // Shade LUX below 100 (rule-l1tnl5yf in Outside) starting rule state evaluation; because entity-changed ValueSensor#hass>sensor_sr_right_shade_4in1_illuminance
    Multi-System Reactor
  • Issue with MSR UI becoming unresponsive
    S sethlampman

    thanks, The only console error I see while recreating the issue is:
    ClientAPI.js:957 API: ignoring unsupported message
    MessageEvent {isTrusted: true, data: '{"type":"goodbye","reason":"missed ping(s)"}', origin: 'ws://192.168.12.37:8111', lastEventId: '', source: null, …}
    isTrusted
    :
    true
    bubbles
    :
    false
    cancelBubble
    :
    false
    cancelable
    :
    false
    composed
    :
    false
    currentTarget
    :
    WebSocket {url: 'ws://192.168.12.37:8111/wsapi', readyState: 3, bufferedAmount: 0, onopen: ƒ, onerror: ƒ, …}
    data
    :
    "{"type":"goodbye","reason":"missed ping(s)"}"
    defaultPrevented
    :
    false
    eventPhase
    :
    0
    lastEventId
    :
    ""
    origin
    :
    "ws://192.168.12.37:8111"
    ports
    :
    []
    returnValue
    :
    true
    source
    :
    null
    srcElement
    :
    WebSocket {url: 'ws://192.168.12.37:8111/wsapi', readyState: 3, bufferedAmount: 0, onopen: ƒ, onerror: ƒ, …}
    target
    :
    WebSocket {url: 'ws://192.168.12.37:8111/wsapi', readyState: 3, bufferedAmount: 0, onopen: ƒ, onerror: ƒ, …}
    timeStamp
    :
    85696
    type
    :
    "message"
    userActivation
    :
    null
    [[Prototype]]
    :
    MessageEvent

    Multi-System Reactor
  • Issue with MSR UI becoming unresponsive
    S sethlampman

    I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all.

    From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only.
    Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again...

    Installation method
Home Assistant Container
Core
2025.7.3
Frontend
20250702.3

    nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR

    Any help would be greatly appreciated

    Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config

NODE_PATH /opt/reactor:/opt/reactor/node_modules
[latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node
[latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined)
[latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage
[latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules
[latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300
[latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141
[latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8
[latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US
[latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM"
[latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326
[latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312
[latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141
[latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279
[latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314
[latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251
[latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253
[latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318
[latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283
[latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141
[latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258
[latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328
[latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323
[latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292
[latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325
[latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328
[latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328
[latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138
[latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141
[latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325
[latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268
[latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323
[latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092
[latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason:  [-]
FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: 
    at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11)
   at ClientRequest.emit (node:events:508:28)
    at ClientRequest.emit (node:domain:489:12)
    at emitErrorEvent (node:_http_client:108:11)
    at TLSSocket.socketErrorListener (node:_http_client:575:5)
    at TLSSocket.emit (node:events:508:28)
    at TLSSocket.emit (node:domain:489:12)
    at emitErrorNT (node:internal/streams/destroy:170:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at processTicksAndRejections (node:internal/process/task_queues:89:21
    Multi-System Reactor
  • Have reactor shut off a light with no motion unless I turned it on manually
    S sethlampman

    So I have a strange one here and I don't know if there is a way to do this or not. I have blue iris triggering a vera virtual switch when AI detects motion on my front porch. Reactor then triggers the light, this works perfect. I want to shut the light off when there is no motion, this also works perfect. What I am having am issue with is when someone turns on the light manually I don't want it to turn off after motion is detected. Example: we are expecting a pizza so we turn on the porch light. 5 min later amazon delivers a package, trips motion. 10 min later Reactor is going to turn off the light. If I manually turn on the light before motion is detected I do not want reactor to turn it off. For the life of me I cannot figure the logic out. Does anyone have any ideas?

    Multi-System Reactor
  • Help with controlling Hue lights through Home Assistant & Reactor
    S sethlampman

    @toggledbits thanks that works great (the workaround). One slight typo though, you have script instead of scene in the graphic.

    Multi-System Reactor
  • Help with controlling Hue lights through Home Assistant & Reactor
    S sethlampman

    Ok so I am trying to do something that I think is simple but apparently not LOL. I want to turn a hue light on yellow when a condition is met. Basically we have really high humidity here in the evenings. When the garage door is open and the humidity is over 60% then I want my hue garage door light to be yellow. If below 60% then I want it to be white. This is simple enough.

    Here is my problem. I cannot find anyway to control the hue color directly from Reactor. There is an x_hass_light.turn_on function but it doesn't do anything when you define a color.

    No problem, I will create a scene in Home Assistant and set my color there, then call that scene from Reactor. (Not elegant, but will work). Created a scene, works great and sets my color the way I want it.

    I go back into Reactor -> Entity Action -> Garage Door Yellow (scene name) and then there is this annoying little box that requires a selection when there is no selection available. There is nothing for me to select and I cannot save because it is expecting input.
    784eafef-6c29-4b78-816c-006a81e41564-image.png

    Can anyone give me some advice on how to accomplish what I am trying to do? I would like a way to do this 100% in reactor (set the light to a color of my choosing) but I am OK with a workaround by using HA scenes. I just need it to work without asking me for a section input that isnt there.

    My next step is to create a virtual switch in Vera, then create a an automation in HA that will trigger my color. Then use Reactor to trigger the virtual switch... I think that is kludge and will likely confuse me months later when I go to edit a rule and forget this workflow...

    Multi-System Reactor
  • Issue with yellow triangles next to rules
    S sethlampman

    Here is the crazy thing. The sensor values were stale, I changed a value in the rule and then saved it. Now there isn't an exclamation point and the sensor value is updating as well. Almost like it was stuck after the upgrade?

    Multi-System Reactor
  • Issue with yellow triangles next to rules
    S sethlampman

    So I upgraded to the latest docker version of Reactor. Now I notice that some of my rules have a yellow triangle before them. I hovered over it but I don't see any explanation as to why. I searched the docs and the forum but I can't figure out why it is showing. If I go into the rule I don't see any errors. Any ideas?

    d5f4c6c5-fd2b-430f-ba72-abc6e09a2b9e-image.png

    Multi-System Reactor
  • Expressions in MQTT Payload?
    S sethlampman

    OK I dont know what happened. I tried it again and it worked??? SMH...

    Multi-System Reactor
  • Expressions in MQTT Payload?
    S sethlampman

    I'm trying to send a video overlay to BlueIris. BI is receving my MQTT Message and it is writing it to a Macro but it doesnt appear that I can use expressions in MQTT Payloads with Reactor?

    418a3dc6-8b4d-424c-b12c-25fbf38fa826-image.png

    Output from BlueIris (no expression data):
    af933278-2ffe-4796-bf5f-c48283bc4025-image.png

    I figured a workaround by using HTTP GET but I just wondered if I am doing something wrong with getting expression variables to work with MQTT.

    This works with BlueIris:
    4b8a4968-9aea-4299-9899-a3f7f9381a13-image.png

    BlueIris returns actual expression data:
    c1e99f79-0510-4acc-8a1a-52f48022a15d-image.png

    Multi-System Reactor
  • Disk Warning on Multisystem Reactor
    S sethlampman

    Thanks that was it. For some reason Home Assistant was configured with Debug logging on and the log file was 267GB on a 512gb drive. SMH...

    Multi-System Reactor
  • Disk Warning on Multisystem Reactor
    S sethlampman

    334ccd7a-9499-4dea-8a4a-2347609dce62-image.png

    For the life of me I cannot figure this out.
    when I run the du -hs command (from the host) for the mapped volume I get 25M
    (/home/seth/ReactorConfig maps to /var/reactor)

    Inside the container I ran du -hs for each of the folders that the ui is complaining about
    /opt/reactor = 71.2M
    /var/reactor/storage = 2.9M
    /var/reactor/logs = 17.6M

    If I run df on the docker container I get this. Disk space is not critical
    1f5d230c-0792-468b-b3b7-9f45e31581c5-image.png

    What gives?

    Multi-System Reactor
  • Home Assistant Script, Reaction requires seclection that isnt there
    S sethlampman

    Thanks! I got the scripts working now so I have a way, although ugly as it is.. I did setup MQTT in reactor but the documentation has me very confused. I don't know how to create a template or anything like that. I basically just want to be able to publish a value that I specify to aqualinkd/Filter_Pump/RPM/set. Is there an easy way to make that work?

    Multi-System Reactor
  • Home Assistant Script, Reaction requires seclection that isnt there
    S sethlampman

    I'm trying to create some automation so I can control my pool variable speed pump from reactor rather than iAqualink (which sucks). My controller is MQTT enabled so I created several scripts for my desired speeds. (I know reactor has MQTT ability but honestly I read the docs and could not make much sense of it and since I already have it set up in Home Assistant, I figured I would just leverage that instead)

    So I created all of my scripts and tested them, they worked perfectly. The I created a rule in reactor and set running the script as the action. The problem is that reactor is telling me that I have to make a selection. I try to click the dropdown and there is nothing to select. I cant save the rule, the only option is to exit.

    9e0a3147-5058-4893-9860-2f0d759dfe3c-image.png

    Here is my script in Home Assistant. Any advice on how to get this to work? If I am looking at this the wrong way I am open to suggestions (I would rather be able to call a specific action and specify a speed value but I cannot figure out how to do that). Thanks in advance.

    bfc7ba89-70a5-47d3-a111-0c2927ac3c73-image.png

    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