Posts

• ---

  [Solved] function isRuleEnabled() issue
  T toggledbits

  Please post a readable screen shot. I don't know what or how this one got posted, but it's tiny and low resolution and I can't see clearly what's in it.

  Multi-System Reactor

• ---

  [Reactor] Problem with Global Reactions and groups
  T therealdb

  @toggledbits yes, fixed! thanks.

  Multi-System Reactor

• ---

  Possible feature request 2?
  C CatmanV2

  Oh! Damn! And thanks!

  C

  Multi-System Reactor

• ---

  [Reactor] Problem with Global Reactions and groups
  T toggledbits

  Try 26011

  Multi-System Reactor

• ---

  [Reactor] Problem with Global Reactions and groups
  T therealdb

  I have this Global Reaction doing some work around lights, based on the season:

  

  When I run it, both the lights in Summer and Winter groups are turned on. Very, very strange. I tried removing and adding the groups again, with no joy.

  I see these on the logs:

  [latest-25328]2026-01-11T18:23:11.847Z <Engine:CRIT> TypeError: this[_0x3c7c88(...)][_0x3c7c88(...)] is not a function [-]
  TypeError: this[_0x3c7c88(...)][_0x3c7c88(...)] is not a function
      at GlobalReactionPredicateContext.toString (/opt/reactor/server/lib/PredicateContext.js:87:126)
      at Logger.getLogger (/opt/reactor/server/lib/Logger.js:417:31)
      at new GlobalReactionPredicateContext (/opt/reactor/server/lib/GlobalReactionPredicateContext.js:62:93)
      at Engine._resume_reaction (/opt/reactor/server/lib/Engine.js:2136:55)
      at Engine._process_reaction_queue (/opt/reactor/server/lib/Engine.js:2031:133)
      at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
  [latest-25328]2026-01-11T18:23:12.155Z <Engine:CRIT> Engine#1 alarm() context is rule Rule#rule-mf29005p condition condmf29005q Script; timer ID will be alarm:rule:rule-mf29005p:cond:condmf29005q
  [latest-25328]2026-01-11T18:23:13.159Z <Engine:CRIT> Engine#1 alarm() context is rule Rule#rule-mf29005p condition condmf29005q Script; timer ID will be alarm:rule:rule-mf29005p:cond:condmf29005q
  [latest-25328]2026-01-11T18:23:14.376Z <Engine:CRIT> TypeError: this[_0x3c7c88(...)][_0x3c7c88(...)] is not a function [-]
  TypeError: this[_0x3c7c88(...)][_0x3c7c88(...)] is not a function
      at GlobalReactionPredicateContext.toString (/opt/reactor/server/lib/PredicateContext.js:87:126)
      at Logger.getLogger (/opt/reactor/server/lib/Logger.js:417:31)
      at new GlobalReactionPredicateContext (/opt/reactor/server/lib/GlobalReactionPredicateContext.js:62:93)
      at Engine._resume_reaction (/opt/reactor/server/lib/Engine.js:2136:55)
      at Engine._process_reaction_queue (/opt/reactor/server/lib/Engine.js:2031:133)
  

  Maybe some old format that was corrupted in the rule? @toggledbits

  Multi-System Reactor

• ---

  Reactor (Multi-System/Multi-Hub) Announcements
  T toggledbits

  Reaction build 26011

  USERS OF AARCH64-tagged DOCKER IMAGES: Per this earlier post, this build will likely be the last with the aarch64 tag. Please follow the post's guidance for changing to one of the newer tags appropriate for your hardware and OS (32-bit armv7l or 64-bit arm64).

  • Reactions UI: Fix update of display after copy in-place.
  • Don't store reaction history entries for sub-reactions
  • VirtualEntityController: better consistency in time-series configuration; update documentation.
  • Fix an error in date display of time range conditions within certain parameters.
  • HassController: Bless HA to 2026.1.0

  This is a "silent" release (it is not advertised in the Status page of Reactor).

  Multi-System Reactor announcements

• ---

  Reactor (Multi-System/Multi-Hub) Announcements
  T toggledbits

  Reactor build 25238

  • Rules/Date-Time: Fix a regression (in 25315) where a Date-Time between condition that crosses midnight may determine incorrect state if the Rule is reloaded (e.g. by editing it or a Reactor restart) in the period after midnight but before the end time.
  • Restarts on Win32 systems can now (finally) do a gradual, organized reload or shutdown.
  • HassController: Bless HA to 2025.11.3

  This is a "silent" release (it is not advertised in the Status page of Reactor)

  Multi-System Reactor announcements

• ---

  Possible feature request 2?
  T toggledbits

  @CatmanV2 said in Possible feature request 2?:

  Any chance of a 'bulk delete' option?

  Each Controller instance implements sys_system.purge_dead_entities action.

  This is also automatic for the Controller implementations I provide for entities that are older than 24 hours when the controller connects/reconnects.

  Multi-System Reactor

• ---

  Genuinely impressed with Zigbee and HA / Reactor
  C CatmanV2

  Well pretty much complete with the migration. I have one Fibaro smart module left which will be retired when my external Temperature / Humidity sensor arrives today, then the main and underfloor thermostats (which I will probably keep as response time is not really a major issue)

  There's a stack of virtual switches which trigger things like getting up and going to bed. I can replace those in HA (and probably will).

  C

  Zigbee

• ---

  Possible feature request 2?
  C CatmanV2

  Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks.

  Any chance of a 'bulk delete' option?

  No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices

  Cheers

  C

  Multi-System Reactor