@toggledbits thanks for the new features, I love them!
T
therealdb
@therealdb
Love openLuup - it just keeps working perfectly.
I started looking at trying to add a gen4 Shelly device to the Shelly plugin via L_ShellyBridge.lua. The plugin is a little uncooked (no rudeness intended), so a bit of a rabbit hole for me.
All of a sudden no console pages available in either Firefox or Chrome. AltUI works perfectly and all the log files indicate no errors. openLuup still running everything works as it should - just no console pages.
I possibly screwed something up but any recently changes files show no problems. The original/ backup of L_ShellyBridge.lua was reinstated but still no console.
Bit stumped on this one. Not sure how to debug. Any ideas?
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.
Hey @toggledbits
One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets.
#1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth.
Both will be appreciated, but I understand the technical challenges. Thanks!
I'm currently on version 26011. I understand that the aarch64 image is no longer supported. So, I therefore need to update to the ARM64 image. Can anyone possibly suggest how I update my docker compose.yaml file (see below). Ideally I'd like to keep my existing reactions etc. rather than start from scratch.
# Multi-System Reactor template docker-compose.yml (version 22160)
#
# Change the lines indicated by "DO"...
#
services:
reactor:
container_name: reactor
environment:
# DO change the TZ: line to set your local time zone.
# See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
TZ: GB
#
# DO NOT change this path. Your directory location is in "source" below.
REACTOR_DATA_PREFIX: /var/reactor
# DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4)
image: toggledbits/reactor:latest-aarch64
restart: "always"
expose:
- 8111
ports:
- 8111:8111
volumes:
# DO change the /home/username/reactor below to the directory you created for
# your local data; DO NOT change the /var/reactor part
- /home/pi/docker/reactor:/var/reactor
- /etc/localtime:/etc/localtime:ro
tmpfs: /tmp
It appears that Ezlo is going to new levels of paid subscription for cloud services supporting Vera hubs. I have to congratulate them. It will soon be 8 years since Ezlo acquired Vera, and despite their purported financial and "intellectual" capital, they have to date not produced a viable full replacement for Vera. Now they are going to charge extra for services for a platform that they stopped updating years ago.
If you know anyone who hasn't yet fully moved on from Captain Ahab's White Whale Chase, please remind them that my Decouple project is still up on Github to decouple a Vera Plus/Secure/Edge from Vera/Ezlo's cloud services. Veras have been said to misbehave when they can't reach the mother ship.
I have also written my first new Vera plugin in... six years? more?... the AlertPushover project will send Vera hub alerts to Pushover, so you can still get messages generated by your Vera hub without paying for Ezlo's cloud service. It's crude but functional (i.e. better than nothing/worth every penny paid).
These two projects won't replace the functionality of their cloud service and app for those who need those things. But any that don't, this may help bridge the gap. Hopefully these stragglers who have waited so long and been disappointed so often will get the idea that it's time to move on.
If you are using the armv7l docker image, the OpenJS Foundation that publishes node is no longer producing 32-bit builds as of v24. That means the last supported LTS version of node for armv7l is v22, which will go End-of-Life in May 2027.
Therefore, the Reactor armv7l image is now deprecated and will only be produced until node v22 goes EOL, and I will not publish armv7l images beyond that date.
If you are running an RPi 3 or earlier with Reactor, you are on this image, and will need to upgrade hardware to a 64-bit model and use the arm64 image. If you need help getting it done, ask in this category.
@toggledbits I pulled the image (well, Watchtower did) and within minutes the whole system went offline.
The log looks like it ends with 26143.
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mkahsmgf/26qq82mw-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lqyfljfi/22f8on0t-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lsb61rw8/24oenqi2-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/rule-lrh58he0:S-1c00gfib-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1c00dylr-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1nam9w5u-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miuh2qqi/22ls4lql-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1vj8sdfc-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1qanz01x-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/24lq19p6-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mk0o8iox/23oy468y-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miscg2h3/rule-miscg2h3:S-22gmbq1c-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrfjke/238p0old-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-m7ccsso5/re-m7ccsso5-1r0myjxa-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/19nl9wq2-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3xk9t-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3vv5m-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/re-ln7j2nqp-22mx9lzd-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/22mx87c8-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-licneppy/1mzwe7ht-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ml3194ih/25jqt1j4-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrg7kf/227hshak-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13ua1p95-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13uagam7-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x4cbv-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x2fyl-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-lscjrws1/238p5c22-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lbwr0jvq/1xkczf03-cons
[latest-26143]2026-05-31T15:23:44.547Z <Structure:NOTICE> Structure Structure#1 stopped
[latest-26143]2026-05-31T15:23:44.547Z <app:NOTICE> Closing APIs...
[latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: closing...
[latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: disconnecting from "192.168.1.23#82" (1001 service closing)
[latest-26143]2026-05-31T15:23:44.548Z <httpapi:NOTICE> HTTP API closing...
[latest-26143]2026-05-31T15:23:44.549Z <wsapi:NOTICE> wsapi: server closed
[latest-26143]2026-05-31T15:23:44.549Z <httpapi:INFO> HTTP server closed.
[latest-26143]2026-05-31T15:23:44.549Z <app:NOTICE> Stopping timers...
[latest-26143]2026-05-31T15:23:44.551Z <app:null> Shutdown complete, process ID 1
[latest-26143]2026-05-31T15:23:44.551Z <app:null> Closing logs...
[latest-26143]2026-05-31T15:23:44.551Z <default:null> Closing log
I can SSH to the VM. Alas, I do not have the previous image for 26143 as I'm a little too quick sometimes on housekeeping.
Today marks another milestone in my Home Automation journey.
After tripping the main breaker once, and shedding more blood than is normally recommended, the underfloor heating (which was the last Z-wave device on my system) has been replaced with a Zigbee one.
Edited reactor.conf
Disabled z-way-server
Disabled Openluup
Z-wave is no more....
C
Posts
-
[MSR] Copy&past of actions and/or drag&drop between set/reset -
[MSR] Copy&past of actions and/or drag&drop between set/resetWhat about support for right click on items? We could definitely move some stuff there. I see some potential in an advanced UI, since we're all power users, after all. Thanks for the consideration!
-
[MSR] Copy&past of actions and/or drag&drop between set/reset@toggledbits I know. But with 200+ rules and no search box, it's very difficult to find the current set actions I'm working on and I have to save it first to get the current status. Header is not sticky and saving means multiple scrolls and lost of focus. Plus, I'm speaking about copy/pasting the single action/group here.
Imagine this. I want to copy an action doing an mqtt message, and paste to another rule (or in the reset). So, real copy/paste like in normal apps. This should be doable with some local storage and a couple of buttons.
-
[MSR] Copy&past of actions and/or drag&drop between set/resetHey @toggledbits
One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets.
#1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth.
Both will be appreciated, but I understand the technical challenges. Thanks!
-
Ezlo Paid Subscription for Vera Cloud ServicesOh boy. They even sent some invoices, as "courtesy previews". People are entertained in the old place...
If you need a way to quickly migrate from Vera to Home Assistant Zwave key, read here:
https://smarthome.community/topic/1590/how-to-migrate-from-vera-to-zwave-me-and-then-zwavejs-in-2024I used Zwave.me as an intermediate step, but I think anything on Zwave series 500 should work.
-
Possible mismatch between binary_sensor in HA and MSRI don’t know if setting to null it’s better for reactor. @toggledbits here is the best source of truth.
-
Possible mismatch between binary_sensor in HA and MSR -
Possible mismatch between binary_sensor in HA and MSRIt may. I have similar behavior with other Template sensors being 0/null/off at boot.
As a defensive measure, I always make the condition to be sustained for at least 10 secs and/or avoid them being evaluated when ha has been restarted for the last 20 secs.
I rarely use ha templates, so my experience is anecdotal.
-
[Solved] Rulesets with multiple groups in Set Reaction not working post-26116@gwp1 I never had any doubt about @toggledbits
-
[Solved] Rulesets with multiple groups in Set Reaction not working post-26116@toggledbits the one with the rules.
-
[Solved] Rulesets with multiple groups in Set Reaction not working post-26116it fixed a couple for me, so definitely working! thanks!
PS: is it safe to delete the json files in the folder?
-
Reactor build 26116: empty group reaction@toggledbits unfortunately, this is still occurring with the new build. here's the log:
Reactor Support Report - Outdoor Lights Sunset Logic
1) Dev instrumentation context before event
[latest-26127]2026-05-07T18:06:07.950Z <Engine:INFO> Engine#1 performing startup eval of global partymode [latest-26127]2026-05-07T18:07:09.232Z <Rule:NOTICE> Lights-Outdoor-On-Sunset (rule-kwulsxqu in Lights-Outdoor) configuration changed; reloading [latest-26127]2026-05-07T18:07:09.232Z <Engine:INFO> Engine#1 rule Rule#rule-kwulsxqu changed; reloading and restarting it2) Sunset rule starts and enters No vacation
[latest-26127]2026-05-07T18:07:37.303Z <Engine:INFO> Enqueueing "Lights-Outdoor-On-Sunset<SET>" (rule-kwulsxqu:S) [latest-26127]2026-05-07T18:07:37.307Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-Sunset<SET> (rule-kwulsxqu:S) [latest-26127]2026-05-07T18:07:37.310Z <Rule:INFO> Rule#rule-kwulsxqu evaluating reaction group constraints No vacation (rule-kwulsxqu:S-159bdlwb-cons) [latest-26127]2026-05-07T18:07:37.319Z <Rule:INFO> Rule#rule-kwulsxqu reaction group No vacation (rule-kwulsxqu:S-159bdlwb-cons) constraints result=true3) Party Mode OFF evaluated true and executed
[latest-26127]2026-05-07T18:07:37.334Z <Rule:INFO> Rule#rule-kwulsxqu evaluating reaction group constraints Party Mode: OFF (rule-kwulsxqu:S-sjf1np7-cons) [latest-26127]2026-05-07T18:07:37.337Z <Rule:INFO> Rule#rule-kwulsxqu reaction group Party Mode: OFF (rule-kwulsxqu:S-sjf1np7-cons) constraints result=true [latest-26127]2026-05-07T18:07:37.353Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-Sunset<SET>/No vacation/Party Mode: OFF (rule-kwulsxqu:S-sjf1np7)4) Party Mode ON also evaluated true in same flow
[latest-26127]2026-05-07T18:08:17.332Z <Rule:INFO> Rule#rule-kwulsxqu evaluating reaction group constraints Party Mode: ON (rule-kwulsxqu:S-sjf1np7-cons) [latest-26127]2026-05-07T18:08:17.334Z <Rule:INFO> Rule#rule-kwulsxqu reaction group Party Mode: ON (rule-kwulsxqu:S-sjf1np7-cons) constraints result=true [latest-26127]2026-05-07T18:08:17.358Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-Sunset<SET>/No vacation/Party Mode: ON (rule-kwulsxqu:S-je98j75)5) Follow-up party path triggers On-All scene
[latest-26127]2026-05-07T18:08:22.377Z <Engine:INFO> Enqueueing "Lights-Outdoor-On-PartyMode<SET>" (rule-kwulj21d:S) [latest-26127]2026-05-07T18:08:22.508Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-PartyMode<SET> (rule-kwulj21d:S) [latest-26127]2026-05-07T18:08:22.525Z <Engine:INFO> Enqueueing "G-Lights-Outdoor-On-All" (re-kwueqcud)6) Same top-level run also executes Vacation branch
[latest-26127]2026-05-07T18:08:22.585Z <Rule:INFO> Rule#rule-kwulsxqu evaluating reaction group constraints Vacation (rule-kwulsxqu:S-159bdlwb-cons) [latest-26127]2026-05-07T18:08:22.586Z <Rule:INFO> Rule#rule-kwulsxqu reaction group Vacation (rule-kwulsxqu:S-159bdlwb-cons) constraints result=true [latest-26127]2026-05-07T18:08:22.603Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-Sunset<SET>/Vacation (rule-kwulsxqu:S-159bdlwb)Dev Instrumentation Lines (Most Relevant)
These are the strongest lines showing the engine handling multiple conflicting groups as
true:[latest-26127]2026-05-07T18:07:37.320Z <Engine:INFO> Engine#1 reaction rule-kwulsxqu:S handling group No vacation (rule-kwulsxqu:S-159bd6va) constraints result state true [latest-26127]2026-05-07T18:07:37.339Z <Engine:INFO> Engine#1 reaction rule-kwulsxqu:S-159bd6va handling group Party Mode: OFF (rule-kwulsxqu:S-sjf1np7) constraints result state true [latest-26127]2026-05-07T18:08:17.334Z <Engine:INFO> Engine#1 reaction rule-kwulsxqu:S-159bd6va handling group Party Mode: ON (rule-kwulsxqu:S-je98j75) constraints result state true [latest-26127]2026-05-07T18:08:22.587Z <Engine:INFO> Engine#1 reaction rule-kwulsxqu:S handling group Vacation (rule-kwulsxqu:S-159bdlwb) constraints result state trueAdditional Context
[latest-26127]2026-05-07T18:08:22.553Z <Engine:INFO> Engine#1 perform x_mqtt.publish ... topic "dbdomoticz/cmd/sceniclightsprogram" ... by reaction Lights-Outdoor-On-Sunset<SET>/No vacation [latest-26127]2026-05-07T18:08:22.372Z <Rule:INFO> Rule#rule-l20ceesq re-evaluating local variable close for dependency notification from GlobalExpression#scenefrommqtt [latest-26127]2026-05-07T18:08:22.374Z <Rule:INFO> Rule#rule-l3jpxetn re-evaluating local variable allup for dependency notification from GlobalExpression#scenefrommqtt -
Reactor build 26116: empty group reaction@toggledbits maybe it's related, but right now I have a similar problem.
Given these groups:
in this case, all are called.
Forum extract - Party Mode false but both branches executed Source: .vs/.tmp/logs/reactor.log Date: 2026-05-05 === A) Sunset flow where both Party Mode OFF and Party Mode ON run === [latest-26120]2026-05-05T18:16:00.192Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-Sunset<SET>/No vacation (rule-kwulsxqu:S-159bd6va) [latest-26120]2026-05-05T18:16:00.206Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-Sunset<SET>/No vacation/Party Mode: OFF (rule-kwulsxqu:S-sjf1np7) [latest-26120]2026-05-05T18:16:00.207Z <Engine:INFO> Lights-Outdoor-On-Sunset<SET>/No vacation/Party Mode: OFF all actions completed. [latest-26120]2026-05-05T18:16:00.207Z <Engine:INFO> Enqueueing "G-Lights-Outdoor-On-Sunset" (re-kwulrhc7) [latest-26120]2026-05-05T18:16:00.243Z <Engine:NOTICE> Starting reaction G-Lights-Outdoor-On-Sunset (re-kwulrhc7) [latest-26120]2026-05-05T18:16:00.244Z <Engine:INFO> Engine#1 perform power_switch.on on Switch#zwavejs>89-2 with { } by reaction G-Lights-Outdoor-On-Sunset (re-kwulrhc7) step 2 [latest-26120]2026-05-05T18:16:00.248Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-Sunset<SET>/No vacation/Party Mode: ON (rule-kwulsxqu:S-je98j75) [latest-26120]2026-05-05T18:16:00.249Z <Engine:NOTICE> Lights-Outdoor-On-Sunset<SET>/No vacation/Party Mode: ON delaying until 1778004965249<5/5/2026, 8:16:05 PM> === B) Party Mode ON continuation triggers PartyMode and On-All scenes === [latest-26120]2026-05-05T18:16:05.250Z <Engine:INFO> Resuming reaction Lights-Outdoor-On-Sunset<SET>/No vacation/Party Mode: ON (rule-kwulsxqu:S-je98j75) from step 2 [latest-26120]2026-05-05T18:16:05.251Z <Engine:INFO> Lights-Outdoor-On-Sunset<SET>/No vacation/Party Mode: ON all actions completed. [latest-26120]2026-05-05T18:16:05.251Z <Engine:INFO> Enqueueing "Lights-Outdoor-On-PartyMode<SET>" (rule-kwulj21d:S) [latest-26120]2026-05-05T18:16:05.271Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-PartyMode<SET> (rule-kwulj21d:S) [latest-26120]2026-05-05T18:16:05.271Z <Engine:INFO> Lights-Outdoor-On-PartyMode<SET> all actions completed. [latest-26120]2026-05-05T18:16:05.288Z <Engine:INFO> Enqueueing "G-Lights-Outdoor-On-All" (re-kwueqcud) [latest-26120]2026-05-05T18:16:05.303Z <Engine:NOTICE> Starting reaction G-Lights-Outdoor-On-All (re-kwueqcud) [latest-26120]2026-05-05T18:16:05.304Z <Engine:INFO> Engine#1 perform power_switch.on on Switch#zwavejs>169-1 with { } by reaction G-Lights-Outdoor-On-All (re-kwueqcud) step 2 === C) Same Sunset rule run also enters Vacation branch === [latest-26120]2026-05-05T18:16:05.343Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-Sunset<SET>/Vacation (rule-kwulsxqu:S-159bdlwb) [latest-26120]2026-05-05T18:16:05.343Z <Engine:INFO> Engine#1 perform power_switch.on on Switch#zwavejs>70-1 with { } by reaction Lights-Outdoor-On-Sunset<SET>/Vacation (rule-kwulsxqu:S-159bdlwb) step 1 === D) Later retrigger (18:19) of G-Lights-Outdoor-On-Sunset === [latest-26120]2026-05-05T18:19:27.156Z <Engine:INFO> Enqueueing "G-Lights-Outdoor-On-Sunset" (re-kwulrhc7) [latest-26120]2026-05-05T18:19:27.160Z <Engine:NOTICE> Starting reaction G-Lights-Outdoor-On-Sunset (re-kwulrhc7) [latest-26120]2026-05-05T18:19:27.161Z <Engine:INFO> Engine#1 perform power_switch.on on Switch#zwavejs>89-2 with { } by reaction G-Lights-Outdoor-On-Sunset (re-kwulrhc7) step 2 [latest-26120]2026-05-05T18:19:27.597Z <Engine:NOTICE> Starting reaction G-Lights-Outdoor-On-Sunset/Green Mode (re-kwulrhc7-vxmf6qa) [latest-26120]2026-05-05T18:19:27.598Z <Engine:INFO> Engine#1 perform power_switch.on on Switch#zwavejs>89-1 with { } by reaction G-Lights-Outdoor-On-Sunset/Green Mode (re-kwulrhc7-vxmf6qa) step 1 [latest-26120]2026-05-05T18:19:28.007Z <Engine:INFO> Engine#1 perform power_switch.on on Switch#zwavejs>70-1 with { } by reaction G-Lights-Outdoor-On-Sunset/Green Mode (re-kwulrhc7-vxmf6qa) step 2 [latest-26120]2026-05-05T18:19:28.104Z <Engine:NOTICE> Starting reaction G-Lights-Outdoor-On-Sunset/Terrazzo (re-kwulrhc7-v80fyx6) [latest-26120]2026-05-05T18:19:28.105Z <Engine:INFO> Engine#1 perform power_switch.on on Switch#zwavejs>85-1 with { } by reaction G-Lights-Outdoor-On-Sunset/Terrazzo (re-kwulrhc7-v80fyx6) step 1 === E) MQTT scene-related reevaluations nearby (possible retrigger context) === [latest-26120]2026-05-05T18:19:28.174Z <Rule:INFO> Rule#rule-l20ceesq re-evaluating local variable close for dependency notification from GlobalExpression#scenefrommqtt [latest-26120]2026-05-05T18:19:28.175Z <Rule:INFO> Rule#rule-l3jpxetn re-evaluating local variable allup for dependency notification from GlobalExpression#scenefrommqtt [latest-26120]2026-05-05T18:19:28.270Z <Rule:INFO> Tasks-MQTT-ResetScene (rule-l2vqcz3z in System Tasks) starting rule state evaluation; because predicate-state-changed Predicate#rule-l2vqcz3z/trig [latest-26120]2026-05-05T18:19:28.271Z <Rule:INFO> Tasks-MQTT-ResetScene (rule-l2vqcz3z in System Tasks) evaluated; rule state transition from RESET to 'SET'this rule group is inside another rule group.
-
Reactor build 26116: empty group reaction@toggledbits all good now. no need to apologize, thanks for your hard work!
-
Reactor build 26116: empty group reactionto be honest, I cannot edit any rule at the moment... every one fails with this message.
-
Reactor build 26116: empty group reaction@toggledbits so, build 26120 has now a strange side effect: when I try to add a comment to an empty constraint list, the infamous "fix erros before saving" banner appears and I cannot make it to go away, no matter what constraints I add to the group. Thanks.
-
Reactor build 26116: empty group reaction@toggledbits fair enough. I’ve analyzed more than 100 rules and I fixed a bunch of them manually. I’ll update my second system with next build.
Thanks!
-
Reactor build 26116: empty group reaction -
Reactor build 26116: empty group reactionI have a couple of rules that has group reactions with empty conditions. I notice, in particular on one that's called every 5 secs, that it was not working. I added an empty comment as condition and it started working again.
I don't know if saving was enough to "reset" it, but I'm reporting anyway. No errors in the logs, but the MQTT message was not published, so I had an easy path to check the rule.
I have others like these, but not easy to test. @toggledbits maybe some stuck status data? (I restarted a couple of times after the last update). Thanks.
-
Dynamic MQTT topics and parametersVery cool. And I thought my wall panel was cool
if I were you, I'll just build a custom capability and have just one device doing the work per panel. 45 properties/actions per device are totally acceptable imho.
Unfortunately, AFAIK, at the moment the only dynamic part accepted in topics is substitutions from config. I think @toggledbits will need to specifically support this new option in order to work.
