Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
T

Trexx

@Trexx
UI not loading after upgrading to 26318
tunnusT
Sorry for a hasty post, will update some details later, but the scenario is that I managed to type a wrong password for too many times and had the following users.yaml section: authtrack: max_attempts: 4 within_minutes: 180 # 180 minutes = 3 hrs block_expiration_minutes: 10080 # 7 days At this time I used build 26298. Then noticed there's a new build with a bypass blocking feature (and yes, it said it won't remove existing block). Anyway, went ahead and upgraded to 26318, but the problem now is that UI is not loading at all (page does not answer). This also means that I cannot use "http://reactor_host:port/diag/clear_authtrack?askauth" command to clear the block (or use any other source IP for login). Docker container stays up & running and does not exit. I'll try to dig up some logs, but anything that I could immediately try out (could I delete a particular file for example)? EDIT: some logs [latest-26318]2026-11-17T20:42:32.337Z <Rule:INFO> MSR startup (rule-lculfnhm in Miscellaneous) started [latest-26318]2026-11-17T20:42:32.343Z <httpapi:NOTICE> httpapi#1 HTTP server listening on :::8111 [latest-26318]2026-11-17T20:42:32.347Z <httpapi:INFO> httpapi#1 local docs found in /opt/reactor/docs/html; setting up static service [latest-26318]2026-11-17T20:42:32.354Z <app:NOTICE> Starting WSAPI... [latest-26318]2026-11-17T20:42:32.355Z <wsapi:NOTICE> wsapi: starting version 26298 protocol [latest-26318]2026-11-17T20:42:32.523Z <Engine:INFO> Engine#1 master timer tick, local time "17/11/2026 22:42:32" (TZ offset 120 mins from UTC) [latest-26318]2026-11-17T20:42:32.542Z <Engine:NOTICE> Starting reaction MSR startup<SET> (rule-lculfnhm:S) [latest-26318]2026-11-17T20:42:32.545Z <Notifier:null> Module Notifier v26186 [latest-26318]2026-11-17T20:42:32.545Z <Engine:INFO> MSR startup<SET> all actions completed. [latest-26318]2026-11-17T20:42:32.557Z <Rule:INFO> Rule#rule-lculfnhm reaction rule-lculfnhm:S completed [latest-26318]2026-11-17T20:42:32.558Z <default:null> Module NotifyTelegram v26177
Multi-System Reactor
[Resolved] Hubitat upgrade 2.5.3.123 may have broken login
3
Topic thumbnail image
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Reactor Inspect - a small read-only helper panel for MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Reverse proxy & API ACL
tunnusT
I'm trying to allow anonymous access from a local network to /api/v1/log, but the problem now with the reverse proxy configuration is that this access is open via proxy to the internet. At least I wasn't able to configure ACL so that only an access from a local network would be permitted. reactor.yaml: baseurl: "http://192.168.1.12:8111" proxy_baseurl: "https://external.com:30000" trusted_proxy: "192.168.1.12" Local traffic would originate from 192.168.1.0/24 network. Synology is acting as a reverse proxy and hosting MSR as a docker container (which has its own network and IP 172.18.0.5). MSR build is latest-26298-fbb75fb8 users.yaml: - url: "/api/v1/log" method: "GET" source_ip: 172.18.0.0/24 allow: true Using the above ACL works, but it enables access via proxy also. If I use source_ip: 192.168.1.0/24, then it doesn't work either locally or remotely. So I'm kinda lost what should I use as source_ip in this case?
Multi-System Reactor
MFA
T
Topic thumbnail image
Multi-System Reactor
Grouped devices
G
I've seen many of you using Dynamic Group Controller. I'm using it myself for monitoring device battery levels. I've read and re-read the Dynamic Group Controller docs and still cannot come to an answer for my question so let me paint my scenario: I've migrated from EchoSpeaks in Hubitat ('cause borked and seemingly unmaintained) to Alexa Devices in Home Assistant ('cause not borked in 2026.11.0) to be able to send TTS to my Echo devices. In EchoSpeaks I could create groups. Sweet. In Alexa Devices I don't seem to be able to do so. As such, my thought was "wait - isn't there a way in MSR?" Is this an effective scenario that Dynamic Group Controller can be used for?
Multi-System Reactor
Login protections
tunnusT
Topic thumbnail image
Multi-System Reactor
Reactor Build 26284 stuck at Loading Reactor UI
T
Topic thumbnail image
Multi-System Reactor
MSR with reverse proxy
tunnusT
I'm trying to use MSR via reserve proxy in Synology DSM, but MSR page does not load https://<public ip>:30000/reactor/en-US/ At the same time logging page loads normally https://<public ip>:30000/api/v1/log I thought maybe authentication was messing it up, but there was no deny entries in the log, and also disabling authentication did not make any difference. For this use case VPN is not an option (that works, but as said not an option for this particular use case). Any ideas what could cause this? MSR build latest-26242-28d69aa8, Chrome browser
Multi-System Reactor
Missing attribute after upgrade
3
Topic thumbnail image
Multi-System Reactor
Use of Google Gemini as an MSR and Hubitat configuration aid
R
I may be late to the AI party on this, but I recently ran into difficulty installing and configuring the Nexia Thermostat Manager on my Hubitat C8 Pro. Hoping for some immediate help I performed a Google search on my problem. I was a bit surprised to see Gemini jump into assist. Gemini walked me through the steps to clean up the failed install, followed by a script for successful installation and configuration. I would not have expected Gemini to "know" this much about Hubitat. Next I sought assistance MSR with the Entity Actions needed to set up the desired controls. I was unclear which of the attribute fields I should to set the cooling an heating temperatures. Once again, Gemini came back not with just a link to a possible explanation, but an easy to follow explanation instead. Once again, I did not expect Gemini to provide such detailed assistance with MSR. Gemini will be a key tool in my HA toolkit in the future.
How-To
[MSR] Native fan capabilty
therealdbT
Nothing more to add. I see we have hvac_blower, but, anyway, maybe a native fan on the same assumptions of the fan from HASS could be reasonable. I have a couple of them. ie, this is from ESPHome via HASS. x_hass.domain="fan" x_hass.entity_id="fan.kitchen_seashell_hood_ventilation_fan" x_hass.floor_id=null x_hass.services=["fan","esphome"] x_hass.source="esphome" x_hass.state="off" x_hass_attr.friendly_name="Seashell Hood Ventilation Fan" x_hass_attr.percentage=50 x_hass_attr.percentage_step=25 x_hass_attr.preset_mode="" x_hass_attr.preset_modes=[] x_hass_attr.supported_features=49 Thanks.
Multi-System Reactor
[MSR] Rule do not fire
therealdbT
Topic thumbnail image
Multi-System Reactor
Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart
N
Build: latest-26221-b25bb3e3, Docker on Synology. Hi, I have a Rule whose Trigger/Constraints reference other Rules via Rule State ... is TRUE. At some point it stops firing. Expanding the rule's condition tree in the UI shows every Trigger and Constraint condition green/TRUE — confirmed live by walking into the room and watching Motion go true in real time. Rule History shows no new SET, just old reset entries. Tried, on the same rule, same evening: recreating the trigger conditions with fresh IDs, recreating the constraint conditions with fresh IDs (flat and wrapped in a new Group — wrapping in a Group produced one SET, but it didn't reproduce on repeat attempts with the same structure), and finally a full container restart with a verified-correct saved rule. Still no SET, even with a fresh live motion event right after the restart. Separately, I found that this rule (and its 10 per-room clones) share identical internal condition/group IDs with each other — leftover from a batch clone done months ago, never regenerated. Not sure if that's related, since fixing the IDs didn't reliably fix the symptom either. Has anyone seen a Rule State condition show TRUE in the UI without the Rule ever producing a SET, surviving a clean restart? Thanks in advance
Multi-System Reactor
DynamicGroupController and attributes
therealdbT
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group. First of all, I think I found a typo in the doc: primary_attribute: "binary_sensor.state" primary_attribute_value: | d = false; each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d, d I think the correct code snippet is d = false, All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
Multi-System Reactor
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Multi-System Reactor
Ooops - Deleted Reactor Ex Machina II
R
I accidentally deleted Reactor Ex Machina II (REM II) from my Reactor rules. I tried to recover it by deleting the .json and .dval in the Rules subdirectory and then recreating it from Togglebits original posting, but that did not work. Does anyone know how to recover REM ll ?
Multi-System Reactor
Bail out of failed reaction?
T
Topic thumbnail image
Multi-System Reactor
Arming Envisalink panel from MSR
T
Topic thumbnail image
Multi-System Reactor
About
Posts
27
Topics
2
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    T Trexx

    I received the new USB dongle from e-bay seller. Shows US frequency in Zwave SW (5.27 release) and connected into OZWD in Home Assistant fine. Was able to successfully pair a Fibaro Dongle with it (which I couldn't get anything to pair with old dongle). So I think we have a winner 🙂

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    T Trexx

    I was having issues where using OZWD I would try and add a node (inclusion) and it wouldn't register the device even if was almost on top of it.. so that eventually led me there.

    I looked on the sticker on the dongle which claims it is the US version (ZMEUUZB1).

    In Z-way app, it shows EU and only options that appear to be for the ZMEEUZB version (EU) dongle for changing frequency.

    I tried changing frequency via shell script to US, which says it does, but Z-way still showed EU even after that.

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    T Trexx

    I think I figured out part of my problem... in looking closer at the controller information in SmartHome app, it looks like I got an EU version instead of a US version of the dongle so it was on the wrong frequencies. I am sending it back to Amazon and re-ordered the chip off of your recommended eBay seller.

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    T Trexx

    At this point it isn't worth the headache and time to potentially solve this. The "all" access token which used to work on v3.06 to be able to access via the gui the firmware downgrade option doesn't work anymore. I initially thought it was related to upgrading to v3.10 of SmartHome so I rolled back, but still it didn't work. Looks like they shut that one down.

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    T Trexx

    To which version of UZB are you thinking? And yes I have been on the QNAP forums for many years 🙂

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    T Trexx

    Yup... file still there.

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    T Trexx

    Tried 7.29, reset to factory, restore backup config w/zwave. All came up good, failed on dongle.restore (luup) phase. Tried doing a touch "dongle.restore.go" and reboot even.. no go.

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    T Trexx

    I was able to piece together the URL structure to download the mt621 versions of 7.31 (current), 7.30 & 7.29. Which do you want to target.

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    T Trexx

    @rafale77 Which Vera FW version are you thinking and do you have a link to it 🙂

    Which zwave-me version would I need to be on to to test that portion?

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    T Trexx

    I have been having to manually delete the dongle.restore file

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    T Trexx

    @rafale77 Yup... dongle.restore never got changed and dongle.dumps's all accounted for (see below)

    root@MiOS_50013148:~# ls -al /etc/cmh/dongle*
    -rw-r--r--    1 root     root         16383 Aug 22 20:26 /etc/cmh/dongle.6.1.dump.0
    -rw-r--r--    1 root     root         16383 Aug 22 20:26 /etc/cmh/dongle.6.1.dump.1
    -rw-r--r--    1 root     root         16383 Aug 22 20:25 /etc/cmh/dongle.6.1.dump.2
    -rw-r--r--    1 root     root         16383 Aug 22 20:25 /etc/cmh/dongle.6.1.dump.3
    -rw-r--r--    1 root     root         16383 Aug 20 14:05 /etc/cmh/dongle.6.1.dump.4
    -rw-r--r--    1 root     root         16383 Aug 20 13:57 /etc/cmh/dongle.6.1.dump.5
    

    If you wanted, I could send you a dump file so you could try flashing it via ZMESerialUpdater to see if that even works 🙂

    As for the onboard restore, I assume I still have to remap the to the internal /dev/ttyS0 first prior to those commands.

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    T Trexx

    @rafale77

    Here you go.

    Screen Shot 2020-08-27 at 7.29.34 PM.png

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    T Trexx

    Correct... in /etc/cmh

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    T Trexx

    Yup.. the dongle.restore file was still there.

    I tried Luup.reload(), Z-wave engine restart, and via Device > Advanced > New Service > Reload Engine. No go for any of them causing the dongle.restore to delete and create the dongle.restore.go file.

    As for user_data.json files... those are now showing as .lzo files btw if under /etc/cmh

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    T Trexx

    I re-ran the testing today. Step 6 is where things are breaking. I did the touch dongle.restore command, reloaded luup, etc. The dongle.restore.go file never appears.

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    T Trexx

    In googling, it looks like one way to do a Luup reload is the following in UI7 via Apps > Develop Apps

     luup.reload()
    

    @rafale77 That might be something you want to add to your directions for users who are not as deep into the weeds as you are 🙂

    Another option is via ALTUI > MISC > Reload Luup Engine

    Vera

  • Vera account suspended for a 1000 years
    T Trexx

    Well that was quick/painless :). Thanks BlackCat!

    @DesT - One other thing that would be handy is for code blocks to have a 'click - copy to clipboard' function. Unless I just missed that somehow as well 🙂

    Vera

  • Vera account suspended for a 1000 years
    T Trexx

    @DesT - A dark mode theme would be nice, and support for DiscourseHub 🙂

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    T Trexx

    So ... I am trying to do the following:

    Current setup:
    Vera Plus (1.7.4955) Zwave only -> HASSIO VM (full control via Vera Integration)

    Future Target:
    HASSIO VM (leveraging zwave.me UZB1 dongle via USB)

    I have done the following so far:

    • Updated UZB1 dongle (via RPi SmartHome) to latest 5.39 Firmware

    I followed the following steps to try and migrate my existing Z-Wave NW (currently on Vera) onto the UZB1 dongle following the steps listed here:

    Migrate from Vera to Z-way

    Problem:

    • Steps 1-3: went fine (although the dumps are labeled as dongle.6.1.dump.x)

    • Step 4: went fine and the UZB1 was recognized as it should be (per dmesg)

    • Step 5: updating the port to /dev/ttyACM0 went fine, although I didn't see any indication of luup reload (or a save button for that matter when updating the port mapping)

    • Step 6: I did the touch for dongle.restore, but wasn't sure where to trigger a luup reload (I assumed it was Z-Wave Settings > Advanced > Reload Engine). I believe I got an error message when trying to do that step

    • Step 7: verify dongle.restore.go I don't recall being in the directions when I was going the test, but I rebooted

    • Post Reboot: None of my previous z-wave devices were listed. I also checked dmesg via ssh and noticed the following items:

    [ 4.328000] Unsupported Device!
    [ 4.328000] Vendor=658 ProdID=200
    [ 4.328000] Manufacturer= Product=
    

    I saw that item a couple times which almost seems like Vera is blocking the UZB1 or at least complaining about it.

    I ended up switching the Z-Wave back to the embedded controller, and restoring configuration from backup.

    Any suggestions what I did wrong??

    Vera

  • UZB/RaZberry Firmwares - Update
    T Trexx

    Thanks Rafale77 for your patience/help. Now I have to jump over to your GitHub page/directions for copying my existing ZWave NW from Vera onto the ZWay.Me and get the existing security key 🙂

    Z-Wave.me
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved