Posts

• ---

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

  Reactor build 26177

  • Notify via Telegram: fix application of default chat_id when not specified on individual notification action.
  • Hubitat: fix an error in handling data POST from MakerAPI (affects house modes, HSM)
  Multi-System Reactor announcements

• ---

  Mode Status NULL
  T toggledbits

  I think I know what this is... fix coming soon...

  Edit: by the way... always look at the log files.

  Multi-System Reactor

• ---

  Telegram notification broke with latest update
  T toggledbits

  OK. Fix coming soon...

  Multi-System Reactor

• ---

  OK to remove old json files?
  T toggledbits

  Yes, you can remove the old ones.

  Multi-System Reactor

• ---

  Alexa for MSR, any interest?
  C CatmanV2

  I think this makes sense if you're starting afresh. Personally I've exposed my devices from MSR via HA Bridge and it works really well for me

  Multi-System Reactor

• ---

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

  Reactor build 26174

  IF YOU ARE UPGRADING FROM A REACTOR BUILD EARLIER THAN 26116, PLEASE READ THE RELEASE NOTES FOR THAT BUILD. THERE WERE IMPORTANT CHANGES MADE ON THAT BUILD THAT MAY AFFECT HOW YOU BACK UP AND RESTORE REACTOR DATA.

  NOTE TO DEVELOPERS: An upcoming build of Reactor will be published after code base conversion to ES modules. Current Reactor core modules are CommonJS (CJS). Many dependent packages are only getting new features in their ESM versions (i.e. the world is moving to ESMs), so Reactor must follow. Instructions for converting your Reactor Controller and Plugin subclasses are published in the Building Controllers page of the Reactor documentation (under Developer Info). If you send me a DM in this community, I can send you an early release of ESM Reactor for your development and testing. This 26174 build is still CJS-based, so your conversion applies only to that future Reactor release and beyond.

  • Entities list: fix a bug in entity filtering where a group filter would be ignored when an entity's name matched the name filter (both should be enforced).
  • Hubitat: Fixed a problem where a scene controller button would report tapped at every Reactor startup.
  • HTTP API: A new endpoint /api/v1/notify has been added so that external applications can use Reactor's configured notifiers to send messages. docs
  • VirtualEntityController: New ping-driven binary sensor reflects the (ICMP) reachability of a target network host. see docs
  • VirtualEntityController: Virtual entities may now be added to system room/location groups by including room: <string> in the virtual entity configuration.
  • HassController: Bless HA to 2026.6.4
  Multi-System Reactor announcements

• ---

  Deprecation Announcement: 32-bit ARM *docker* images
  T toggledbits

  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.

  Multi-System Reactor

• ---

  [Solved] build 26150 - engine not starting
  T toggledbits

  @gwp1 said in [Solved] build 26150 - engine not starting:

  @toggledbits I checked, rechecked, RErechecked and couldn't find any issue with that YAML.

  Upload it to me, I'd like to take a look.

  @gwp1 said in [Solved] build 26150 - engine not starting:

  So... my question NOW is: why did it run fine until this build? That logging has been there for several weeks.

  No idea. But, having once gotten a clean startup, it now has a last known good version of that config file, so whatever it's not happy with won't prevent startup in future.

  Multi-System Reactor

• ---

  [Solved] build 26150 - engine not starting
  T toggledbits

  Did you read the log entries? Pretty strong starting point there...

  The logs are showing that your logging.yaml has an unrecoverable error. First, check to make sure you have only spaces, no tabs, for indenting.

  If that's not it, indent the - type: file line two spaces, as well as the keep, level, and recycle lines that follow it.

  Multi-System Reactor

• ---

  [Solved] build 26150 - engine not starting
  T toggledbits

  Huh. I'm running the 26150 amd64 container with no issue... sure would be nice to have logs. If you go for them, startup is where it's at, and you may need to look at the container syslog if an error is being thrown before the logger is up and running. Some early message get written to the console, and that usually ends up directed to the system logs.

  Multi-System Reactor