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
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
Genuinely impressed with Zigbee and HA / Reactor
CatmanV2C
Just for the record, in case anyone is following, I'm really rather impressed. I have installed one of these: https://www.amazon.co.uk/dp/B0B6P22YJC?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 That's connected (physically) to the VM running on my Synology, with a 2m USB extension. The same host also runs Openluup, Mosquito, HA Bridge. Yesterday I installed Zigbee2mqtt. That was a bit of a PITA but mostly because of ports and permissions. Once up and running, and the correct boxes ticked, immediately visible in Home Assistant via the MQTT integration, and thence into Reactor I've only got two devices. I bought the cheapest sensor I could find, which is a door sensor. Dead easy to add to ZIgbee2mqtt and again, immediately visible in HA. https://www.amazon.co.uk/dp/B0FPQLWRW1?ref=ppx_yo2ov_dt_b_fed_asin_title The dongle is on the top floor of the house, and I wanted the sensor on the back door (just about as far apart as it's possible to get short of going into the garage) When I moved the sensor downstairs it dropped out pretty instantly (which wasn't a huge surprise) so quick bit of research found out that smart plugs will act as routers so... https://www.amazon.co.uk/dp/B0FDQDPGBB?ref=ppx_yo2ov_dt_b_fed_asin_title Took me about 30 seconds to connect. Updated the name. Instantly visible in Reactor with the new name pushed over from Zigbee2mqtt. And lo, the door sensor now has a signal of 140 and works as far as I can tell perfectly and instantly (unlike my z-wave one). A few more of those will be purchased and used to replace the Tuya wifi cloud devices and the (continually failing) Z-wave plugs (yeah, they were TKB so....) Commended to the house. Thanks for everyone that got me on the right lines. C
Zigbee
Tuya Wifi to Tasmota flashing
CatmanV2C
Just popping this in here in case it's helpful to anyone else later. I've got several Tuya Wifi sockets that I'm getting rid of / replacing. Looking at which ones, if any, can be flashed to Tasmota: https://www.amazon.co.uk/dp/B09Y212TCK?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 Are NOT flashable C
Zigbee
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Zigbee2mqtt installed! sytemctl not happy :(
CatmanV2C
Hello oh great ones. After a couple of hours messing with ports and permissions I have Zigbee2mqtt installed and running on my virtual pi Can connect to the front end and everything Odd one though, simply cannot get systemctl to work and the error is, well, unhelpful. The service file is this: [Unit] Description=zigbee2mqtt After=network.target [Service] Environment=NODE_ENV=production Type=notify ExecStart=/usr/local/bin/node index.js WorkingDirectory=/opt/zigbee2mqtt StandardOutput=inherit # Or use StandardOutput=null if you don't want Zigbee2MQTT messages filling syslog, for more options see systemd.exec(5) StandardError=inherit WatchdogSec=10s Restart=always RestartSec=10s User=pi [Install] WantedBy=multi-user.target Straight out of the docs with the change to point to my local node install (which we know works as it's the same as the very fine Reactor is using. Running manually pnpm start in /opt/zigbee2mqtt works fine However: catman@openluup:/etc/systemd/system$ sudo systemctl start zigbee2mqtt.service Job for zigbee2mqtt.service failed because the control process exited with error code. See "systemctl status zigbee2mqtt.service" and "journalctl -xe" for details. Which I have catman@openluup:/etc/systemd/system$ sudo systemctl status zigbee2mqtt.service ● zigbee2mqtt.service - zigbee2mqtt Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; disabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Tue 2025-12-16 12:32:42 GMT; 4s ago Process: 3093 ExecStart=/usr/local/bin/node index.js (code=exited, status=217/USER) Main PID: 3093 (code=exited, status=217/USER) and -- A start job for unit zigbee2mqtt.service has begun execution. -- -- The job identifier is 17477. Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed to determine user credentials: No such process Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed at step USER spawning /usr/local/bin/node: No such process -- Subject: Process /usr/local/bin/node could not be executed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The process /usr/local/bin/node could not be executed and failed. -- -- The error number returned by this process is ERRNO. Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=217/USER -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStart= process belonging to unit zigbee2mqtt.service has exited. -- -- The process' exit code is 'exited' and its exit status is 217. Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit zigbee2mqtt.service has entered the 'failed' state with result 'exit-code'. Dec 16 12:35:16 openluup systemd[1]: Failed to start zigbee2mqtt. -- Subject: A start job for unit zigbee2mqtt.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit zigbee2mqtt.service has finished with a failure. Which strikes me as very odd. Any blindingly obvious things I'm missing? TIA! C
Zigbee
Any thoughts on which is better
CatmanV2C
Obviously a quiet forum, but perhaps it's time I'm looking at rolling Zigbee into my system, in large part for the Aqara FP300 presence sensors which seem to finally provide a solution to if the wasp is actually in the box. My current set up is as follows: One Debian VM on Synology NAS running: Z-wave Server Open Luup Multi system reactor HA bridge Mosquito MQQT broker This machine has a UZB Z-wave stick connected via the USB port on the NAS Another HAOS VM on the same NAS running HAOS I've got some older Z-wave stuff that I keep around until it fails. I have some Tuya stuff integrated in HA My thought was to get either a SMLIGHT SLZB-06M or an Aqara Hub M2 Integrate them via Zigbee2MQQT (running on the Debian machine) and then expose them in HA so I can continue to automate in MSR. Thoughts on which of those devices wold be preferable long term. Both are POE capable which is good. It also appears I could add a USB dongle to the NAS and expose it to the HAOS machine. Any thoughts from the assembled experts here? TIA C
Zigbee
Single protocol?
CatmanV2C
Another question to the hive mind. Prompted by the fact that I lost yet another z-wave device over the weekend due to a power issue. It looks like z-way server is reporting another device failed (although it's working fine) and message queue is far too long IMHO. Also the failed device has been removed in the expert interface, but still there in the 'normal' one. Sigh. Currently I have z-wave, Tuya, thinking about Zigbee.... Does anyone use one single protocol for everything? Right now I'm feeling that as the z-wave stuff dies, I'm just gonna replace it with something else.... C
General Discussion
HDMI oddness
CatmanV2C
Not really Smart Home stuff, but going to ask as we have smart people... Bear with me on this one. Asking here because of the font of knowledge! For many eek years I have had a Virgin V6 box and a Raspberry Pi running Kodi connected to my TV through a cheap *** HDMI switch. It all worked beautifully but the absolutely critical thing was that the TV remote passed the signals back to the Pi to allow remote control of Kodi. Couple of changes of late: Installed a soundbar on the TV using the ARC (audio return channel). That then turns the soundbar on and off when the TV turns on and off and the TV volume control controls the soundbar volume direct. Everything continues to work Upgraded the software of the Tivo box to Virgin 360. This is literally software only. You get sent a snacky new Bluetooth remote hit 'upgrade' on the screen and off it goes. Now, things are not playing well. Typically when I turn on to watch Kodi the soundbar comes on (as it should) but the TV either puts out sound through its own speakers and the soundbar, or just the soundbar. It's not possible to control the volume of the soundbar through the TV. Also it's not longer possible to control Kodi using the TV remote. If I turn the TV360 box off, i.e. power it down, before turning on to watch Kodi, everything is fine. This makes little to no sense to me. My assumption is that the cheap *** HDMI switch is getting something from the TV360 connection that it didn't used to get when the software was Tivo and that's screwing up the HDMI communications. I'm upgrading the switch to something a little less chap, but wondered if anyone could validate my theory at all? TIA C
General Discussion
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
Oh the joy of pairing
CatmanV2C
When I remember the old days Just added a new Tuya plug (OK so it's cloud) Start to finish, visible in HA and MSR < 30 seconds... C
Vera
Home Assistant Connect ZWA-2 & ZBT-2
therealdbT
Topic thumbnail image
Hardware
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor
Is there a way to turn this section (image in post) off?
toggledbitsT
Topic thumbnail image
Comments & Feedback
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