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.
P

powisquare

@powisquare
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
76
Topics
9
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Z-way token Expiration
    P powisquare

    All good - much appreciated.

    Zway Bridge

  • openLuup: MQTT server
    P powisquare

    Sorry - my bad. Device that's working does not have a password. I'll have another go.

    Boom - all working

    openLuup

  • openLuup: MQTT server
    P powisquare

    Yes I have - on all of them. I seem to recall, when setting up the first one, that openLuup recognised a button press. Perhaps that's how it worked. These sensors wake up on an hourly basis, but when you wake them up manually they are awake for a minute or so (it seems).

    openLuup

  • openLuup: MQTT server
    P powisquare

    Should have looked first ! Red highlights a win here; am seeing this ... (is there a proper way of copying and pasting?)

    2021-06-12 11:10:01.904 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=492370363&Timeout=60&MinimumDelay=1500&_=1623492371898 HTTP/1.1 tcp{client}: 0x1e96db0
    2021-06-12 11:10:19.108 openLuup.io.server:: MQTT:1883 connection from 192.168.1.156 tcp{client}: 0x1d97790
    2021-06-12 11:10:19.152 openLuup.mqtt:: shellyht-E01A8B SUBSCRIBE to shellies/command tcp{client}: 0x1d97790
    2021-06-12 11:10:19.153 openLuup.mqtt:: shellyht-E01A8B SUBSCRIBE to shellies/shellyht-E01A8B/command tcp{client}: 0x1d97790
    2021-06-12 11:10:19.156 luup.shelly:83: New Shelly announced: shellyht-E01A8B
    2021-06-12 11:10:19.279 openLuup.context_switch:: ERROR: [dev #83] ./openLuup/client.lua:96: missing realm or nonce in received WWW-Authenticate header
    2021-06-12 11:10:19.280 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/announce : ./openLuup/client.lua:96: missing realm or nonce in received WWW-Authenticate header
    2021-06-12 11:10:19.393 openLuup.server:: request completed (1891 bytes, 1 chunks, 17488 ms) tcp{client}: 0x1e96db0

    openLuup

  • Z-way token Expiration
    P powisquare

    Updated openLuup to v. 21.6.8 yesterday. I notice the z-way bridge has lost connection. and requires login. When I go to device/actions there is no way to enter credentials - only a login button.

    Zway Bridge

  • openLuup: MQTT server
    P powisquare

    The first Shelly I tried worked with the bridge created and device created in the Shellies room. The next ones also appear in openLuup/Servers/Received Connections list but don't appear as devices. Have I missed a step?

    openLuup

  • openLuup: MQTT server
    P powisquare

    OMG. Genius. Many thanks indeed! Note to self - for Shelly .. Internet & Security/Advanced - Developer Settings/Enable MQTT

    openLuup

  • openLuup: MQTT server
    P powisquare

    Will I need to set ports or do anything in Lua Startup still?

    openLuup

  • openLuup: MQTT server
    P powisquare

    Hi guys - just received some Shelly H & Ts. Is there any documentation on how to connect these to mqtt (in novice speak 🙂)? Have read the thread but am getting slightly confused - do I need just the openluup mqtt server or another plugin also?

    openLuup

  • ubiquiti breach
    P powisquare

    Did you ever get a certificate on to your controller? Would love to get Let's Encrypt on but I wonder if they are making it difficult so people go for their cloud solution.

    General Discussion

  • Secure/Horstmann thermostat/zway
    P powisquare

    Not using the button - don't really know what it does.

    Hardware

  • Secure/Horstmann thermostat/zway
    P powisquare

    Thanks, only difference is Brand; I have Horstman (Secure), all versions and command classes are the same. I get the same error using openLuup interface too. Think this is the part where setpoint is accepted. Do you use the button for anything?

    [2021-03-22 09:05:40.517] [D] [zway] SETDATA devices.42.data.lastReceived = 0 (0x00000000)
    [2021-03-22 09:05:40.517] [I] [zway] Node 42:0 CC Wakeup: Wakeup notification
    [2021-03-22 09:05:40.517] [D] [zway] SETDATA devices.42.instances.0.commandClasses.132.data.lastWakeup = 1616403940 (0x60585de4)
    [2021-03-22 09:05:40.518] [D] [zway] SETDATA devices.42.data.isAwake = True
    [2021-03-22 09:05:40.518] [D] [zway] SETDATA devices.42.data.lastSendInternal = **********
    [2021-03-22 09:05:40.518] [D] [zway] SETDATA devices.42.data.lastNonceGet = 47091702 (0x02ce8ff6)
    [2021-03-22 09:05:40.518] [D] [zway] Running wakeup handler for node 42
    [2021-03-22 09:05:40.518] [D] [zway] SETDATA devices.42.instances.0.commandClasses.132.data.lastSleep = 1616403940 (0x60585de4)
    [2021-03-22 09:05:40.518] [I] [zway] Node 42:0 CC Wakeup: Send node to sleep
    [2021-03-22 09:05:40.518] [I] [zway] Adding job: Wakeup Sleep
    [2021-03-22 09:05:40.518] [D] [zway] SENDING (cb 0xfc): ( 01 0D 00 13 2A 06 43 01 01 22 00 6E 05 FC 3B )
    [2021-03-22 09:05:40.525] [D] [zway] RECEIVED ACK
    [2021-03-22 09:05:40.527] [D] [zway] RECEIVED: ( 01 04 01 13 01 E8 )
    [2021-03-22 09:05:40.528] [D] [zway] SENT ACK
    [2021-03-22 09:05:40.528] [D] [zway] Delivered to Z-Wave stack
    [2021-03-22 09:05:40.548] [D] [zway] RECEIVED: ( 01 18 00 13 FC 00 00 02 00 B0 7F 7F 7F 7F 01 01 03 00 00 00 00 02 01 00 00 BA )
    [2021-03-22 09:05:40.548] [D] [zway] SENT ACK
    [2021-03-22 09:05:40.548] [I] [zway] Job 0x13 (ThermostatSetPoint Set): Delivered
    [2021-03-22 09:05:40.549] [D] [zway] SendData Response with callback 0xfc received: received by recipient
    [2021-03-22 09:05:40.549] [D] [zway] SETDATA devices.42.data.lastSendInternal = **********
    [2021-03-22 09:05:40.549] [D] [zway] SETDATA devices.42.data.lastSend = 47092706 (0x02ce93e2)
    [2021-03-22 09:05:40.549] [D] [zway] Job 0x13 (ThermostatSetPoint Set): success
    [2021-03-22 09:05:40.549] [I] [zway] Removing job: ThermostatSetPoint Set

    Hardware

  • Secure/Horstmann thermostat/zway
    P powisquare

    Thanks - yes from zway basic interface.

    Hardware

  • Secure/Horstmann thermostat/zway
    P powisquare

    Seems to be working fine except I get an error notification via email 'Error during perform command execution: Error: Invalid argument' every time setpoint is changed from controller. Also does anyone know if the 'Button' child is useful?

    [2021-03-22 09:00:03.113] [I] [core] --- ZWayVDev_zway_42-0-67-1 performCommand processing: {"0":"exact","1":{"level":"11"}}
    [2021-03-22 09:00:03.113] [D] [zway] SETDATA devices.42.instances.0.commandClasses.67.data.1.setVal = 11.000000
    [2021-03-22 09:00:03.114] [I] [zway] Adding job: ThermostatSetPoint Set
    [2021-03-22 09:00:03.114] [I] [zway] Adding job: ThermostatSetPoint Get
    [2021-03-22 09:00:03.114] [I] [zway] Node 42:0 CC ThermostatMode: Thermostat Mode 1 is not supported by device (modemask 0x0)
    [2021-03-22 09:00:03.117] [I] [core] Notification: error (module): Error during perform command execution: Error: Invalid argument
    [2021-03-22 09:00:03.125] [I] [core] Error: Invalid argument
    at Error (native)
    at t_vDev.(anonymous function).self.controller.devices.create.handler (automation/modules/ZWave/index.js:5540:62)
    at .extend.performCommand (automation/classes/VirtualDevice.js:365:25)
    at ZAutomationAPIWebRequest.
    .extend.performVDevCommandFunc (automation/ZAutomationAPIProvider.js:442:51)
    at ZAutomationAPIWebRequest.handlerFunc (automation/ZAutomationAPIProvider.js:3976:30)
    at ZAutomationAPIWebRequest.ZAutomationWebRequest.handleRequest (automation/WebserverRequestRouter.js:250:35)
    at automation/WebserverRequestRouter.js:32:29
    at WebServer.document_root (automation/Webserver.js:40:31)
    [2021-03-22 09:00:03.130] [I] [core] HK: updated ZWayVDev_zway_42-0-67-1
    [2021-03-22 09:00:03.137] [D] [zway] RECEIVED: ( 01 18 00 13 F0 00 00 05 01 C4 7F 7F 7F 7F 00 00 03 2E 00 00 00 03 01 00 00 EB )

    Hardware

  • Why Migrate to Z-way from vera and how?
    P powisquare

    +1 for zway 🙂

    Zway Bridge

  • altUI
    P powisquare

    May well be different machines, differing firmwares. Frustrating nevertheless. Here's a stab at displaying variables.

    varaibles1.jpg

    Vera/openLuup plugins

  • altUI
    P powisquare

    Thanks - will have to try tomorrow - can't risk sending vera in to a tiz with guests staying.

    Vera/openLuup plugins

  • altUI
    P powisquare

    Can i set them to (0,0) as the (5,1) misbehaves?

    Vera/openLuup plugins

  • altUI
    P powisquare

    Sorry I was conflating issues. I have (a) two thermostats on separate veras that have different jsons and (b) one of those thermostats is shown above has the same json as another thermostat (on zway) but different functionality. Kinda got that muddled.

    Vera/openLuup plugins

  • altUI
    P powisquare

    Seems odd that it's two different jsons for the same thermostat on separate veras. Perhaps the issue is inherently an altui one anyway. When I use the up down arrows for temp setpoint it starts from the cooling setting ie in this case 0 so its a lot of clicking to get to 20.

    thermostat.jpg

    The same model thermostat paired to zway displays and behaves correctly with no cooling temps.

    TRthermostat.jpg

    But they have the same json?

    thermostatattributes.jpg

    Vera/openLuup plugins
  • Login

  • Don't have an account? Register

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