Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Issue with MSR UI becoming unresponsive
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
Device log?
G
@toggledbits is there a log that will show me what rule is turning on a specific device? I've got a switch that has been kicking on at 2200 ET for several nights now and the reactor.log doesn't have a thing in it that I can see on a device level (it being more rules-based).
Multi-System Reactor
Midnight crossing not working in date/time condition (build 25325)
tunnusT
Topic thumbnail image
Multi-System Reactor
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
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
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
Topic thumbnail image
Multi-System Reactor
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
Multi-System Reactor
Notice to Docker + ARM Users (RPi 3/4/5 and others)
toggledbitsT
This post does not apply to users of Intel/AMD-based systems. If you are using a Reactor image tagged latest-amd64 or stable-amd64, then this post does not apply to you. It also does not apply to bare-metal installs; it's for users of docker images on ARM-based systems only (principally Raspberry Pi hosts, but could be others). After January 15, 2026, I will no longer produce the aarch64-tagged docker image for Reactor. The ARM images will be arm64 for 64-bit operating systems, and armv7l for 32-bit operating systems. For those of you running a container from the aarch64 image today, this will be a relatively simple change: you just need to switch the image used for your docker container to a differently-tagged image. If you are using docker-compose, then this is a relatively simple matter of changing the image line in your docker-compose.yaml file and then stopping (docker-compose down) and restarting (docker-compose up -d) your Reactor daemon. But there's a catch... not all of you can safely just switch from the aarch64 image to the arm64 image. And, you can't just trust the output of uname -m, for example, because this exposes the CPU architecture, but not the word size of the OS running on that CPU. For Raspberry Pi systems, the transition to 64-bit operating systems was long (starting in 2016) and not always obvious — although there was a first "official" 64-bit OS for RPis in 2020, it did not become a default recommendation in the Raspberry Pi Imager until 2021, and then that was only the default for Pi 3/4 systems with >4GB RAM; it was 2022 before it was universally recommended for all 64-bit CPUs regardless of RAM size. Depending on when you first imaged your RPi system and what default you may have been offered/chosen, you could today easily have a 64-bit CPU Raspberry Pi running a 32-bit version of the operating system. Upgrades along the way would not change this; changing it to fully 64-bit requires a full reimage of the system. To establish if your OS is 64- or 32-bit, log in to your Pi and run: sudo dpkg-architecture -q DEB_HOST_ARCH. If the response is arm64 or aarch64, then you are running a 64-bit OS and you should use the arm64-tagged image. If it's anything else, you are running a 32-bit OS, and you should use the armv7l-tagged image. pi@rpi4-1:~ $ sudo dpkg-architecture -q DEB_HOST_ARCH armhf pi@rpi4-1:~ $ uname -m aarch64 pi@rpi4-1:~ $ In the example above, the uname command reports that the CPU is 64-bit architecture (aarch64), which is true for the host on which I ran these commands, but the DEB_HOST_ARCH value is armhf, indicating a 32-bit operating system. This system has to use the armv7l-tagged image. Other systems will have their own ways of determining the word size of the running OS. Since the majority of Reactor users running ARM systems are on Raspberry Pis, I am able to supply the above instructions, but if you happen to have a different ARM system, you'll need to do some web searching to figure out how to expose that information. Or, you can just try the arm64 image, and if it doesn't start up, try the armv7l image. Remember to always back up your system before making any changes. For everyone, please make this change as soon as possible, and if you have any trouble finding a working image, please (1) go back to the current aarch64 image; and (2) let me know in this thread along with as much detail about your host system as you can offer (including the output of the dpkg-architecture command mentioned above).
Multi-System Reactor
Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
M
Hi, I'm in the process of migrating from a Raspberry Pi 4 (ARMv7) to a Raspberry Pi 5 (ARMv8/aarch64), but I’ve run into an issue: there is no proper ARMv8/aarch64 image available. None of the existing images run on the Pi 5 - they all exit immediately with code 139 (segmentation fault), which typically indicates that the binaries inside the image are not compatible with the ARM64/aarch64 architecture used by the Pi 5. Would it be possible to publish a correct ARMv8/aarch64 (linux/arm64) image? Building one should be relatively straightforward using docker buildx with multi-arch support. For example, my own Node.js images are built this way: docker buildx build --push \ -t <localrepo>/<project>:<tag> \ --platform=linux/arm64,linux/amd64 \ --file ./apps/<project>/Dockerfile . This produces both the AMD64 and ARM64/v8 variants automatically. Also, as a side note, it may be best to avoid using Alpine as the base image for the ARM64 build, since musl-based builds often cause compatibility issues and unnecessary headaches. A glibc-based base image (e.g., Debian or Ubuntu) tends to work far more reliably on ARM64, especially for Node.js applications. @toggledbits - tagging you in case you missed this. Thanks, mgvra
Multi-System Reactor
Script action and custom timers
therealdbT
Sorry to write here without trying, but I’m flying today. Am I correct if i say that script action with alarm() makes it possible to execute a reaction in a given interval, lets say 15 seconds or 3.5 minutes? That sounds amazing, since I’ve used weird tricks, including a custom controller, just to do this.
Multi-System Reactor
Help resolve change in behaviour post update
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reactor w/HA 2025.11 error on set_datetime service call setting only time
CrilleC
@toggledbits Do you know if this is related to that PR or is it a change they made in 2025.11.1? [latest-25310]2025-11-11T13:16:24.319Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag with { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.320Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag action: { "type": "call_service", "service_data": { "date": (null), "time": "10:45", "datetime": (null), "timestamp": (null) }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_dag" } } [latest-25310]2025-11-11T13:16:24.321Z <HassController:ERR> HassController#hass request 1762866984320<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.321Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "10:45" }) on Entity#hass>input_datetime_vvb_dag failed! [latest-25310]2025-11-11T13:16:24.321Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"10:45","datetime":null,"timestamp":null},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_dag"},"id":1762866984320} [latest-25310]2025-11-11T13:16:24.322Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.322Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 0 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Engine#1 action args: { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 1 [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt with { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt action: { "type": "call_service", "service_data": { "date": (null), "time": "03:00", "datetime": (null), "timestamp": 0 }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_natt" } } [latest-25310]2025-11-11T13:16:24.324Z <HassController:ERR> HassController#hass request 1762866984323<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "03:00", "timestamp": 0 }) on Entity#hass>input_datetime_vvb_natt failed! [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"03:00","datetime":null,"timestamp":0},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_natt"},"id":1762866984323} [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.324Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 1 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <Engine:INFO> Engine#1 action args: { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 2 [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Sätt Schema VVB i Home Assistant<AKTIV> all actions completed.
Multi-System Reactor
Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
P
Hello, I currently have an office light (connected via a Leviton Zwave Dimmer switch) controlled from a Gen5 Aeotech Zwave switch installed on my Synology 720+ NAS. I run HA(2025.11.10) in a virtual machine from my NAS and Reactor on the container manager of the same NAS. Prior to updating to 25304 the rule I had set to turn the light on to a specific dimming value worked correctly. Now the rule appears to follow the decision tree, however the reaction does not trigger setting the dimming or turning on the office light? Strangely I can still turn the light on and off as well as dim it directly from HASS..? I have tried using the ''try this action'' button in the rules reaction setting and it will not control the light and does not throw an error flagÉ Please help, P.S Reactor has been rock steady for me over the last few years and I'm a big fan of this solution.
Multi-System Reactor
[Solved] alarm() in global expression throws error in log.
CrilleC
Topic thumbnail image
Multi-System Reactor
[Solved] Define function issue in latest-25304
CrilleC
Topic thumbnail image
Multi-System Reactor
No Upgrade Notification for Build 25308?
CatmanV2C
FWIW I'm no longer getting a notification from MSR that there's an update. Just thought I'd mention it C
Multi-System Reactor
Strange behavior in MSR latest-25304 with disabled groups in Reaction
therealdbT
Topic thumbnail image
Multi-System Reactor
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor

Issue with MSR UI becoming unresponsive

Scheduled Pinned Locked Moved Multi-System Reactor
7 Posts 2 Posters 43 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    sethlampman
    wrote last edited by
    #1

    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
    
    toggledbitsT 1 Reply Last reply
    0
    • toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote last edited by
      #2

      Don't worry about the OpenWeatherMap messages, that's just the occasional query failing, and Reactor will retry the query to get what it needs.

      Since it's UI side, the best thing to do is to press F12 or whatever key opens up the Developer Tools on the browser you are using. You can usually find it on the browser's menu with a little digging. From there, there is a console where there will be messages for the UI side of things, and just copy-paste that as you've done with the log entries. HTOP on the host... just for my own clarification, that to me means you are running it on the server side, and if it's the UI that's bogging down for some reason, I expect that to not tell us more. If you are on Windows, open Task Manager and look at the browser's performance stats and memory consumption. If Mac, I'm sure there's an equivalent tool.

      I would also be curious to hear if the problem resolves (even just temporarily) if you do a refresh on the browser.

      Please don't make any big changes (like moving off docker) — I'm almost 100% certain we will find this issue on the UI side and moving Reactor around won't matter, just make unnecessary work for you and a moving target for me. Stay with me, and we'll get to the bottom of this.

      1 Reply Last reply
      0
      • S Offline
        S Offline
        sethlampman
        wrote last edited by
        #3

        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

        1 Reply Last reply
        0
        • S Offline
          S Offline
          sethlampman
          wrote last edited by
          #4

          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
          
          1 Reply Last reply
          0
          • S Offline
            S Offline
            sethlampman
            wrote last edited by sethlampman
            #5

            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

            1 Reply Last reply
            0
            • S Offline
              S Offline
              sethlampman
              wrote last edited by
              #6

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

              1 Reply Last reply
              1
              • 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
                
                toggledbitsT Offline
                toggledbitsT Offline
                toggledbits
                wrote last edited by
                #7
                This post is deleted!
                1 Reply Last reply
                0
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                Recent Topics

                • Issue with MSR UI becoming unresponsive
                  S
                  sethlampman
                  0
                  7
                  43

                • Home Assistant Connect ZWA-2 & ZBT-2
                  PablaP
                  Pabla
                  2
                  4
                  96

                • Date/time condition
                  tunnusT
                  tunnus
                  0
                  3
                  74

                • Is there a way to turn this section (image in post) off?
                  toggledbitsT
                  toggledbits
                  0
                  1
                  60

                • Device log?
                  toggledbitsT
                  toggledbits
                  0
                  2
                  93

                • Midnight crossing not working in date/time condition (build 25325)
                  tunnusT
                  tunnus
                  0
                  3
                  103

                • Error: Command timeout
                  G
                  gwp1
                  0
                  6
                  219

                • Reactor (Multi-System/Multi-Hub) Announcements
                  toggledbitsT
                  toggledbits
                  5
                  131
                  75.6k

                • [Solved] Local expression in Rule does not evaluate as they used to do
                  CrilleC
                  Crille
                  0
                  5
                  306

                • Home Assistant 2025.11.2 and latest-25315
                  G
                  gwp1
                  0
                  6
                  313

                • Notice to Docker + ARM Users (RPi 3/4/5 and others)
                  toggledbitsT
                  toggledbits
                  1
                  1
                  121
                Powered by NodeBB | Contributors
                Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                • Login

                • Don't have an account? Register

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