Skip to content

Multi-System Reactor

870 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
    141 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
    143
    5 Votes
    143 Posts
    113k Views
    toggledbitsT
    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)
  • HTTP query failing after version 26177

    1
    2
    0 Votes
    1 Posts
    5 Views
    No one has replied
  • Mode Status NULL

    6
    2
    0 Votes
    6 Posts
    35 Views
    wmarcolinW
    It worked, my friend. I did a fresh install, restarted the VM, and now it's working perfectly. Thank you very much. A quick question: we used to open these topics in Mantis, but I no longer have access to it. Is it okay to continue here on the forum?
  • Telegram notification broke with latest update

    4
    1
    0 Votes
    4 Posts
    187 Views
    3
    I upgraded the docker to version latest-26177-be756a68. Unfortunately I am still not getting my Telegram alerts unless I put the Chat ID in the GUI. I don't know if it matters, but my chat_id starts with a "-". I think I have another chat ID that does not start/show as a negative ID. I can't test with that ID though.
  • OK to remove old json files?

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

    2
    1
    2 Votes
    2 Posts
    115 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
    322 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
    386 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
    160 Views
    toggledbitsT
    Got it. Next build... tomorrow, or Sunday at the latest.
  • Has ping command been removed?

    4
    1
    0 Votes
    4 Posts
    239 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
    300 Views
    tunnusT
    @toggledbits got it, thanks!
  • Integrations and 'Loaded'

    3
    0 Votes
    3 Posts
    165 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
    915 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
  • Upcoming Storage Change -- Got Back-ups?

    2
    3 Votes
    2 Posts
    452 Views
    toggledbitsT
    OK, everyone, it's almost time. Sorry for the long pause. Life takes over sometimes. The aforementioned updates will be in the next build, and I am working on wrapping everything up to get that build out later this week. Please make backups of your Reactor data as advised in the head post here. As I said then/there, I've been working with this for months now, with no issues, but my world is not your world or everyone else's world, so there's always the possibility I don't see or have an issue that you do. Prior to releasing this new build in the latest channel, the 26011 build will become the stable channel head. In addition to your backups, that gives you a relatively quick path (especially docker users) to get back onto 26011 if there's a showstopper. This build will also include unified room groups: DynamicGroupController will manage "rooms" (or areas or locations or whatever your hub calls them). If you have two different hubs with devices in the "Living Room," there will be one "Living Room" group with the combined set of devices. The per-controller room groups generated by VeraController and EzloController will be disabled by default, and existing room groups created by these controllers will be marked as dead entities (and eventually purged). If you already use DynamicGroupController to manually create your own room groups via configuration, you can either keep that (and disable DGC's new behavior, if you wish) or switch to DGC's version. An updated version of ZWaveJSController that supports this functionality will be released simultaneously with the core build.
  • Next Release?

    6
    0 Votes
    6 Posts
    674 Views
    CatmanV2C
    Just an update. Nothing apparent issue wise since my update yesterday C

Recent Topics