Skip to content

Multi-System Reactor

872 Topics 8.2k Posts
  • Deprecation Announcement: 32-bit ARM *docker* images

    Pinned until 8/1/27, 6:56 PM Locked
    1
    0 Votes
    1 Posts
    145 Views
    No one has replied
  • Category Topic Guide -- Read Before Posting

    Pinned Locked guidelines
    1
    8 Votes
    1 Posts
    1k Views
    No one has replied
  • Reactor (Multi-System/Multi-Hub) Announcements

    Pinned Locked announcements
    144
    5 Votes
    144 Posts
    114k Views
    toggledbitsT
    Nodejs v24.17 Not Compatible Users on bare-metal installs... a security fix in nodejs v24.17 inadvertently broke a dependency of Reactor. This version of nodejs is therefore not compatible with Reactor. If you are using it, please upgrade to v24.18.
  • [RESOLVED] Phantom device, “INFO” appears

    2
    1
    0 Votes
    2 Posts
    21 Views
    toggledbitsT
    That's a bug in Maker API... it's sending updates for a device that isn't enumerated for export. You can safely ignore those messages.
  • [RESOLVED] Mode Status NULL

    18
    2
    0 Votes
    18 Posts
    114 Views
    wmarcolinW
    Wow, what a headache. I don't know if this is also related to the Node.js issue, but I just added another scenario that I'm now seeing in the log—an INFO warning for a device that doesn't exist. I don't know if it's related. I'm going through the entire error log and reactor.log to see if I can spot anything else unusual in the information.
  • [RESOLVED] Telegram notification broke with latest update

    8
    1
    0 Votes
    8 Posts
    250 Views
    wmarcolinW
    Now that the log file has fewer errors (Node.js), I can see this log message appear—I'm not sure if it helps. [latest-26177]2026-06-28T23:20:20.829Z <NotifyTelegram:CRIT> Error: NotifyTelegram request failed [-] Error: NotifyTelegram request failed at NotifyTelegram.notify (/home/wilson/reactor/server/lib/NotifyTelegram.js:304:23) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async NotifyTelegram.sendNotification (/home/wilson/reactor/server/lib/Notifier.js:188:145) [latest-26177]2026-06-28T23:20:20.830Z <Engine:ERR> Engine#1 reaction rule-mevuuj8w:S step 3 notification (Telegram) failed: [Error] NotifyTelegram request failed [-] [latest-26177]2026-06-28T23:20:20.830Z <Engine:CRIT> Error: NotifyTelegram request failed [-] Error: NotifyTelegram request failed at NotifyTelegram.notify (/home/wilson/reactor/server/lib/NotifyTelegram.js:304:23) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async NotifyTelegram.sendNotification (/home/wilson/reactor/server/lib/Notifier.js:188:145) [latest-26177]2026-06-28T23:20:20.831Z <NotifyTelegram:ERR> NotifyTelegram failure response text: {"ok":false,"error_code":400,"description":"Bad Request: chat not found"}
  • [RESOLVED] HTTP query failing after version 26177

    3
    2
    0 Votes
    3 Posts
    40 Views
    wmarcolinW
    After updating Node.js, the query is working.
  • Question about the find function

    3
    1
    0 Votes
    3 Posts
    29 Views
    wmarcolinW
    Fantastic!! Another master class in knowledge—thank you. And I learned another function I didn't know about: slipt(). It's super useful—really great.
  • [Answered] OK to remove old json files?

    2
    1
    0 Votes
    2 Posts
    43 Views
    toggledbitsT
    Yes, you can remove the old ones.
  • Alexa for MSR, any interest?

    2
    1
    2 Votes
    2 Posts
    126 Views
    CatmanV2C
    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
  • [Solved] build 26150 - engine not starting

    8
    0 Votes
    8 Posts
    329 Views
    toggledbitsT
    @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.
  • http request action & digest auth

    7
    0 Votes
    7 Posts
    406 Views
    toggledbitsT
    I'll see what can be done later, but this comes from a package I use, not code of my own creation. Despite the bug discovered, if I abandon the external package, I lose years of testing against myriad servers in the wild, so it's a potentially costly trade-off that makes a lot of future work (and frustration, potentially).
  • Cloning actions in reactions does not work

    2
    0 Votes
    2 Posts
    224 Views
    toggledbitsT
    Got it. Next build... tomorrow, or Sunday at the latest.
  • Has ping command been removed?

    4
    1
    0 Votes
    4 Posts
    253 Views
    toggledbitsT
    OK. I've respun 26140 docker images with some additions to the underlying minimal OS. Grab the updated image for your container and you should have ping back.
  • ReferenceError with Home Assistant data & build 26140

    6
    1
    0 Votes
    6 Posts
    306 Views
    tunnusT
    @toggledbits got it, thanks!
  • Integrations and 'Loaded'

    3
    0 Votes
    3 Posts
    177 Views
    CatmanV2C
    Perfect! Thanks (again) C
  • Possible mismatch between binary_sensor in HA and MSR

    25
    0 Votes
    25 Posts
    1k Views
    CatmanV2C
    Thanks, installed and working. Although after the first restart there were some virtual switches in HA that were not being accurately reflected in MSR, but I restarted MSR again, and everything looks fine. Thanks again for your help. Next time I'll upload the logs to start with! C
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    9 Views
    No one has replied
  • 0 Votes
    19 Posts
    1k Views
    therealdbT
    @gwp1 I never had any doubt about @toggledbits
  • Reactor build 26116: empty group reaction

    18
    1 Votes
    18 Posts
    929 Views
    toggledbitsT
    OK. Please turn on log level 5 for that rule only. Run the rule to show the issue, and upload the entire Rule log file as well as reactor.log, the rule storage files (dval and json). Link for upload in your DMs

Recent Topics