Skip to content

Multi-System Reactor

877 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
    242 Views
    No one has replied
  • Category Topic Guide -- Read Before Posting

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

    Pinned Locked announcements
    147
    5 Votes
    147 Posts
    127k Views
    toggledbitsT
    Reactor build 26214 ALL USERS: This build is strictly to address a problem for bare-metal installs only running on nodejs v22.0 through v22.11. Use node -v to show your version, or look at the startup messages in reactor.log. If your nodejs is v22.12.0 or higher, or you are running a docker image, you do not need to update to this build. Workaround for module load problem in nodejs versions from 22.0 through 22.11. Only a bare-metal package is distributed for this build. The latest docker images are still build 26193.
  • 0 Votes
    1 Posts
    5 Views
    No one has replied
  • Upgrade Issues

    8
    2
    0 Votes
    8 Posts
    57 Views
    toggledbitsT
    I was able to find a workaround, so build 26214, which will be posted shortly for bare-metal only, should address the issue without any changes to your system (other than the Reactor package).
  • Logon screen timeout

    5
    0 Votes
    5 Posts
    170 Views
    G
    @toggledbits Damn you lol I'd just updated Brave a couple hours ago, then sat back lying in wait. I just now went to test it and it worked normally, I was logged out with the login screen visible. I thought "huh - musta been a Brave issue, well it's fixed now" - and then I saw both this post and the version change. Thank you, sir, as always!
  • [MSR] Copy&past of actions and/or drag&drop between set/reset

    9
    0 Votes
    9 Posts
    314 Views
    toggledbitsT
    Thanks for the inspiration!
  • Upgrade advice - upgrade from aarch64 to ARM64 image

    4
    0 Votes
    4 Posts
    183 Views
    toggledbitsT
    @Talisker said in Upgrade advice - upgrade from aarch64 to ARM64 image: What is confusing me a little is that the exemplar docker compose .yaml 'volumes:' file structure is a bit different to my current .yaml file. Will this cause a problem? The change in the newer file will be significant later, but no need to worry about it today. Make as few changes as possible. The only change you need to make here is from latest-aarch64 to latest-arm64.
  • Alexa for MSR, any interest?

    4
    1
    2 Votes
    4 Posts
    313 Views
    CatmanV2C
    @wmarcolin FWIW Home Assistant and Alexa Media Player can give you what you (and so much more) in about an hour's set up. C
  • [RESOLVED] Telegram notification broke with latest update

    11
    1
    0 Votes
    11 Posts
    772 Views
    CatmanV2C
    As ever, my thanks. Upgraded to 26177 and all is well! C
  • [RESOLVED] Phantom device, “INFO” appears

    2
    1
    0 Votes
    2 Posts
    167 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
    618 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] HTTP query failing after version 26177

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

    3
    1
    0 Votes
    3 Posts
    169 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
    183 Views
    toggledbitsT
    Yes, you can remove the old ones.
  • [Solved] build 26150 - engine not starting

    8
    0 Votes
    8 Posts
    526 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
    777 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
    387 Views
    toggledbitsT
    Got it. Next build... tomorrow, or Sunday at the latest.
  • Has ping command been removed?

    4
    1
    0 Votes
    4 Posts
    452 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
    438 Views
    tunnusT
    @toggledbits got it, thanks!

Recent Topics