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.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. SiteSensor migration
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
[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
[Solved] DynamicGroupController updating members issue
CrilleC
Edit: Solved in latest-26221. Bare-metal latest-26193 I have this group: "OKforLarm": name: OK för Larm select: - include_controller: vera - include_capability: door_sensor filter_expression: entity.attributes.door_sensor.state It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
Multi-System Reactor

SiteSensor migration

Scheduled Pinned Locked Moved Multi-System Reactor
22 Posts 4 Posters 7.5k Views 4 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G gwp1

    This is a very timely thread as I'm starting to explore how to migrate two Site Sensors (one pulls weather data from Ambient API, the other pulls weather data from OpenWxMap API) to feed my HVAC needs.

    Disclaimer: I have near zero KB regarding expressions let along how they work in MSR. I'll be watching this thread closely.

    tunnusT Offline
    tunnusT Offline
    tunnus
    wrote on last edited by
    #6

    @gwp1 you are probably better off with this post than what's here, but feel free to follow also this discussion 🙂

    Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Zigbee2MQTT & ZWA-2

    1 Reply Last reply
    0
    • toggledbitsT toggledbits

      If g_temp_var is not changing, changes is never going to fire. But g_UplinkResponse is changing.

      Edit: to try to clarify more, it's a chicken and egg problem. g_temp_var will not be updated until it is referenced by a running rule, but the rule only runs when g_temp_var is changed. So without something external causing g_temp_var to change, the rule will never run and call for g_temp_var to be updated. If you check g_UplinkResponse for changes, but use g_temp_var everywhere else in the rule, you should get the behavior you are looking for, because g_UplinkResponse is changed externally by another rule on an interval, so that will stimulate the run of the rule to evaluate everything else needed.

      tunnusT Offline
      tunnusT Offline
      tunnus
      wrote on last edited by
      #7

      @toggledbits okay, now I have this test rule set up:

      Screenshot 2021-09-12 at 2.31.02.png

      Situation remains the same, global expression(s) is not changing 😞

      Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Zigbee2MQTT & ZWA-2

      1 Reply Last reply
      0
      • toggledbitsT Offline
        toggledbitsT Offline
        toggledbits
        wrote on last edited by toggledbits
        #8

        I can't tell from the timestamps, but given that they're similar, did the value actually change? No hit if the value doesn't actually change.

        By the way, how are you determining if there was a change or not? I mean, how do you know it's not changing. Does something happen when the conditions are met (is there a Reaction that does something?)?

        Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

        tunnusT 1 Reply Last reply
        0
        • toggledbitsT toggledbits

          I can't tell from the timestamps, but given that they're similar, did the value actually change? No hit if the value doesn't actually change.

          By the way, how are you determining if there was a change or not? I mean, how do you know it's not changing. Does something happen when the conditions are met (is there a Reaction that does something?)?

          tunnusT Offline
          tunnusT Offline
          tunnus
          wrote on last edited by
          #9

          @toggledbits I know it's supposed to be something else as I can monitor the same values via a couple of different means (an app for instance).

          But as I wrote before, if I use local expressions, values are as they should be:

          Screenshot 2021-09-12 at 3.02.34.png

          Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Zigbee2MQTT & ZWA-2

          toggledbitsT 1 Reply Last reply
          0
          • tunnusT tunnus

            @toggledbits I know it's supposed to be something else as I can monitor the same values via a couple of different means (an app for instance).

            But as I wrote before, if I use local expressions, values are as they should be:

            Screenshot 2021-09-12 at 3.02.34.png

            toggledbitsT Offline
            toggledbitsT Offline
            toggledbits
            wrote on last edited by toggledbits
            #10

            @tunnus Well, I'm not getting a clear picture here from the little bits and pieces you're posting, so I set up a little test environment of my own where I have an HTTP request run, set a global variable, and have a rule with a condition that goes true when the global changes with a reaction that sends an alert notification that the variable has changed. I get the notification every time I run the HTTP request.

            Here's the rule:

            b897854e-0377-4d07-8f98-9be318276661-image.png

            And the variables:

            a5d579cb-3480-43fb-b94e-f81f4089a461-image.png 212872b0-6d58-44d7-ac06-2ead76c78192-image.png

            Here's the reaction I can run manually to make a request and store the result in the global variable. The API function I'm calling returns a timestamp (with milliseconds), so every request is pretty much guaranteed to give me a different response from the last.

            5de7eca4-b637-4764-8de3-662dee90061e-image.png

            This seems to model what you're telling me you want to do, and it works fine.

            Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

            tunnusT wmarcolinW 3 Replies Last reply
            0
            • toggledbitsT toggledbits

              @tunnus Well, I'm not getting a clear picture here from the little bits and pieces you're posting, so I set up a little test environment of my own where I have an HTTP request run, set a global variable, and have a rule with a condition that goes true when the global changes with a reaction that sends an alert notification that the variable has changed. I get the notification every time I run the HTTP request.

              Here's the rule:

              b897854e-0377-4d07-8f98-9be318276661-image.png

              And the variables:

              a5d579cb-3480-43fb-b94e-f81f4089a461-image.png 212872b0-6d58-44d7-ac06-2ead76c78192-image.png

              Here's the reaction I can run manually to make a request and store the result in the global variable. The API function I'm calling returns a timestamp (with milliseconds), so every request is pretty much guaranteed to give me a different response from the last.

              5de7eca4-b637-4764-8de3-662dee90061e-image.png

              This seems to model what you're telling me you want to do, and it works fine.

              tunnusT Offline
              tunnusT Offline
              tunnus
              wrote on last edited by tunnus
              #11

              @toggledbits sorry, I tried to depict the problem in the first post as well as I could.

              But yes, your test case models my case and now I'm baffled. I'll try to setup my test from a scratch and see what happens...

              EDIT: replicated this case, no change. Local variables work nicely, but global expressions won’t update. Patrick, any logs I could provide to solve this?

              Only difference I could think of (between my and your test setup) is that if response structures (array etc) differ just enough and code handles local & global expressions a bit differently.

              Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Zigbee2MQTT & ZWA-2

              1 Reply Last reply
              0
              • toggledbitsT Offline
                toggledbitsT Offline
                toggledbits
                wrote on last edited by
                #12

                The key here is that the response to the HTTP request has to change. If it doesn't, then the changes isn't going to work, and nothing will trigger the rule to evaluate and cause the other global variables to be updated. Remember that changes requires an actual change of the value, not just a fetch of the value and setting it (again) to what's already there... no change, no changes.

                Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                tunnusT 1 Reply Last reply
                0
                • toggledbitsT toggledbits

                  The key here is that the response to the HTTP request has to change. If it doesn't, then the changes isn't going to work, and nothing will trigger the rule to evaluate and cause the other global variables to be updated. Remember that changes requires an actual change of the value, not just a fetch of the value and setting it (again) to what's already there... no change, no changes.

                  tunnusT Offline
                  tunnusT Offline
                  tunnus
                  wrote on last edited by tunnus
                  #13

                  @toggledbits what's strange here is that I only change this:

                  Screenshot 2021-09-13 at 12.19.22.png

                  to this:

                  Screenshot 2021-09-13 at 12.14.40.png

                  or vice versa, URL & other settings remain the same, local expression works, changes are immediately detected. And yes, response is really changing.

                  Here's the most current test rule:

                  Screenshot 2021-09-13 at 12.19.55.png

                  (at the time of the screenshot, "-111.0" was the correct value)

                  The only time I get an updated/correct value (for the global expression) is when a global variable/expression is initialized (when it is empty), after that it remains the same.

                  Maybe this problem is unique to my setup.

                  Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Zigbee2MQTT & ZWA-2

                  1 Reply Last reply
                  0
                  • tunnusT Offline
                    tunnusT Offline
                    tunnus
                    wrote on last edited by tunnus
                    #14

                    @LibraSun, @cw-kid & others, could you test if you can replicate this error I'm experiencing?

                    EDIT: I have another rule querying the same API, for a bit different values and that works fine even with global expressions, so reproducing the same error might prove to be difficult...

                    Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Zigbee2MQTT & ZWA-2

                    1 Reply Last reply
                    0
                    • toggledbitsT toggledbits

                      @tunnus Well, I'm not getting a clear picture here from the little bits and pieces you're posting, so I set up a little test environment of my own where I have an HTTP request run, set a global variable, and have a rule with a condition that goes true when the global changes with a reaction that sends an alert notification that the variable has changed. I get the notification every time I run the HTTP request.

                      Here's the rule:

                      b897854e-0377-4d07-8f98-9be318276661-image.png

                      And the variables:

                      a5d579cb-3480-43fb-b94e-f81f4089a461-image.png 212872b0-6d58-44d7-ac06-2ead76c78192-image.png

                      Here's the reaction I can run manually to make a request and store the result in the global variable. The API function I'm calling returns a timestamp (with milliseconds), so every request is pretty much guaranteed to give me a different response from the last.

                      5de7eca4-b637-4764-8de3-662dee90061e-image.png

                      This seems to model what you're telling me you want to do, and it works fine.

                      wmarcolinW Offline
                      wmarcolinW Offline
                      wmarcolin
                      wrote on last edited by
                      #15

                      @toggledbits, in your test proposal, when the HTTP Request fails, an error is generated and thus an Alert is displayed on the dashboard. Since this is an under-control situation, is it possible to inhibit this alert?

                      1 Reply Last reply
                      0
                      • toggledbitsT Offline
                        toggledbitsT Offline
                        toggledbits
                        wrote on last edited by
                        #16

                        Depends on how you're doing the implementation. What's the error that's generated?

                        Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                        wmarcolinW 1 Reply Last reply
                        0
                        • toggledbitsT toggledbits

                          Depends on how you're doing the implementation. What's the error that's generated?

                          wmarcolinW Offline
                          wmarcolinW Offline
                          wmarcolin
                          wrote on last edited by
                          #17

                          @toggledbits I am referring to this error alert, generated when I interrupt the internet access, automatically the HTTP GET will fail, which is expected and I will give the necessary treatment. But I would like to not have this alert in the status dashboard, because as I mention it would be an expected problem, I don't need the alert.

                          9e58b432-8e2a-4f54-8f76-d62db5c049ec-image.png

                          Now of course this is no big problem, just exploring more possibilities.

                          1 Reply Last reply
                          0
                          • toggledbitsT toggledbits

                            @tunnus Well, I'm not getting a clear picture here from the little bits and pieces you're posting, so I set up a little test environment of my own where I have an HTTP request run, set a global variable, and have a rule with a condition that goes true when the global changes with a reaction that sends an alert notification that the variable has changed. I get the notification every time I run the HTTP request.

                            Here's the rule:

                            b897854e-0377-4d07-8f98-9be318276661-image.png

                            And the variables:

                            a5d579cb-3480-43fb-b94e-f81f4089a461-image.png 212872b0-6d58-44d7-ac06-2ead76c78192-image.png

                            Here's the reaction I can run manually to make a request and store the result in the global variable. The API function I'm calling returns a timestamp (with milliseconds), so every request is pretty much guaranteed to give me a different response from the last.

                            5de7eca4-b637-4764-8de3-662dee90061e-image.png

                            This seems to model what you're telling me you want to do, and it works fine.

                            tunnusT Offline
                            tunnusT Offline
                            tunnus
                            wrote on last edited by tunnus
                            #18

                            @toggledbits if you'd be willing to troubleshoot this issue further, I could provide you the whole response to this http request? But where is that response stored on the filesystem?

                            What seems to happen is that if my global expression/variable is empty, fresh data is initially stored to that, but subsequent queries are "ignored", data is not replaced.

                            In the log I can see new/fresh values, but for some reason this new data is not used:

                            2021-10-01T14:04:00.321Z <Rule:5:Rule.js:997> Rule#rule-ktc09w2v._evaluate() trigger state now false (was false)
                            2021-10-01T14:04:00.323Z <Rule:5:Rule.js:999> Rule#rule-ktc09w2v._evaluate() constraints state true
                            2021-10-01T14:04:00.325Z <Rule:5:Rule.js:1008> Rule#rule-ktc09w2v rule state now false, changed no
                            2021-10-01T14:04:00.548Z <Engine:INFO> Engine#1 reaction Nibe uplink SiteSensor<SET> step 0 HTTP request to https://192.168.XXXX:8443/rest/items?tags=nibe2vera&recursive=false succeeded (200 OK)
                            2021-10-01T14:04:00.552Z <Engine:5:Engine.js:1547> Engine#1 response type application/json
                            2021-10-01T14:04:00.556Z <Engine:5:Engine.js:1169> Engine#1 global set variable g_UplinkTest = (object) [ { "link": "https://192.168.XXXX:8443/rest/items/NibeRESTAPI_Control_HotWaterBoost", "state": "0", "stateDescription": { "pattern": "%.0f", "readOnly": false, "options": [  ] }, "commandDescription": { "commandOptions": [ { "command": "0", "label": "Off" }, { "command": "1", "label": "3h" }, { "command": "2", "label": "6h" }, { "command": "3", "label": "12h" }, { "command": "4", "label": "One time" } ] }, "editable": true, "type": "Number", "name": "NibeRESTAPI_Control_HotWaterBoost", "label": "Hot water boost", "tags": [ "nibe2vera" ], "groupNames": [  ] }, { "link": "https://192.168.XXXX:8443/rest/items/NibeRESTAPI_Status_DegreeMinutes", "state": "-54.3", "stateDescription": { "pattern": "%.0f", "readOnly": true, "options": [  ] }, "editable": true, "type": "Number", "name": "NibeRESTAPI_Status_DegreeMinutes", "label": "Degree Minutes", "tags": [ "nibe2vera" ], "groupNames": [  ] }, { "link": "https://192.168.XXXX:8443/rest/items/NibeRESTAPI_Ventilation_FanSpeed", "state": "72.0", "stateDescription": { "pattern": "%.0f", "readOnly": true, "options": [  ] }, "editable": true, "type": "Number", "name": "NibeRESTAPI_Ventilation_FanSpeed", "label": "Fan Speed", "tags": [ "nibe2vera" ], "groupNames": [  ] }, { "link": "https://192.168.XXXX:8443/rest/items/NibeRESTAPI_Addition_Blocked", "state": "ON", "stateDescription": { "readOnly": true, "options": [  ] }, "editable": true, "type": "Switch", "name": "NibeRESTAPI_Addition_Blocked", "label": "Blocked", "tags": [ "nibe2vera" ], "groupNames": [  ] }, { "link": "https://192.168.XXXX:8443/rest/items/NibeRESTAPI_CprInfoEp14_CurrentComprFrequency", "state": "20.0 Hz", "stateDescription": { "pattern": "%.0f", "readOnly": true, "options": [  ] }, "editable": true, "type": "Number:Frequency", "name": "NibeRESTAPI_CprInfoEp14_CurrentComprFrequency", "label": "Compr. Frequency", "tags": [ "nibe2vera" ], "groupNames": [  ] }, { "link": "https://192.168.XXXX:8443/rest/items/NibeRESTAPI_Status_OutdoorTemp", "state": "10.9 °C", "stateDescription": { "pattern": "%.0f", "readOnly": true, "options": [  ] }, "editable": true, "type": "Number:Temperature", "name": "NibeRESTAPI_Status_OutdoorTemp", "label": "Outdoor Temp.", "tags": [ "nibe2vera" ], "groupNames": [  ] }, { "link": "https://192.168.XXXX:8443/rest/items/NibeRESTAPI_Status_AlarmInfo", "state": "NULL", "stateDescription": { "pattern": "%s", "readOnly": true, "options": [  ] }, "editable": true, "type": "String", "name": "NibeRESTAPI_Status_AlarmInfo", "label": "Alarm Info", "tags": [ "nibe2vera" ], "groupNames": [  ] }, { "link": "https://192.168.XXXX:8443/rest/items/NibeRESTAPI_Status_HotWaterTop", "state": "46.3 °C", "stateDescription": { "pattern": "%.0f", "readOnly": true, "options": [  ] }, "editable": true, "type": "Number:Temperature", "name": "NibeRESTAPI_Status_HotWaterTop", "label": "Hot Water Top", "tags": [ "nibe2vera" ], "groupNames": [  ] } ]
                            2021-10-01T14:04:02.173Z <Engine:5:Engine.js:1367> _process_reaction_queue() wake-up!
                            2021-10-01T14:04:02.200Z <Engine:5:Engine.js:1328> _process_reaction_queue() running task 1179 { "tid": 1179, "id": "rule-kt9u8aur:S", "rule": "rule-kt9u8aur", "__reaction": [RuleReaction#rule-kt9u8aur:S], "next_step": 2, "status": 0, "ts": 1633097040135, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise], "attempts": 1 }
                            2021-10-01T14:04:02.201Z <Engine:NOTICE> Resuming reaction Nibe uplink SiteSensor<SET> (rule-kt9u8aur:S) from step 2
                            2021-10-01T14:04:02.204Z <Engine:5:Engine.js:1537> Engine#1 request header accept: application/json
                            2021-10-01T14:04:02.205Z <Engine:5:Engine.js:1539> Engine#1 reaction rule-kt9u8aur:S step 2 request url https://192.168.XXXX:8443/rest/items?tags=nibe2vera2&recursive=false data { "method": "GET", "timeout": 15000, "size": 8192, "agent": [object Object], "headers": [object Headers] }
                            2021-10-01T14:04:02.208Z <Engine:INFO> Nibe uplink SiteSensor<SET> all actions completed.
                            2021-10-01T14:04:02.209Z <Engine:5:Engine.js:1332> _process_reaction_queue() task returned, new status -1; task 1179
                            2021-10-01T14:04:02.212Z <Engine:5:Engine.js:1367> _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting
                            

                            (and then it continues with another http request in the same reaction, 2 s delay in between)

                            Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Zigbee2MQTT & ZWA-2

                            toggledbitsT 1 Reply Last reply
                            0
                            • tunnusT tunnus

                              @toggledbits if you'd be willing to troubleshoot this issue further, I could provide you the whole response to this http request? But where is that response stored on the filesystem?

                              What seems to happen is that if my global expression/variable is empty, fresh data is initially stored to that, but subsequent queries are "ignored", data is not replaced.

                              In the log I can see new/fresh values, but for some reason this new data is not used:

                              2021-10-01T14:04:00.321Z <Rule:5:Rule.js:997> Rule#rule-ktc09w2v._evaluate() trigger state now false (was false)
                              2021-10-01T14:04:00.323Z <Rule:5:Rule.js:999> Rule#rule-ktc09w2v._evaluate() constraints state true
                              2021-10-01T14:04:00.325Z <Rule:5:Rule.js:1008> Rule#rule-ktc09w2v rule state now false, changed no
                              2021-10-01T14:04:00.548Z <Engine:INFO> Engine#1 reaction Nibe uplink SiteSensor<SET> step 0 HTTP request to https://192.168.XXXX:8443/rest/items?tags=nibe2vera&recursive=false succeeded (200 OK)
                              2021-10-01T14:04:00.552Z <Engine:5:Engine.js:1547> Engine#1 response type application/json
                              2021-10-01T14:04:00.556Z <Engine:5:Engine.js:1169> Engine#1 global set variable g_UplinkTest = (object) [ { "link": "https://192.168.XXXX:8443/rest/items/NibeRESTAPI_Control_HotWaterBoost", "state": "0", "stateDescription": { "pattern": "%.0f", "readOnly": false, "options": [  ] }, "commandDescription": { "commandOptions": [ { "command": "0", "label": "Off" }, { "command": "1", "label": "3h" }, { "command": "2", "label": "6h" }, { "command": "3", "label": "12h" }, { "command": "4", "label": "One time" } ] }, "editable": true, "type": "Number", "name": "NibeRESTAPI_Control_HotWaterBoost", "label": "Hot water boost", "tags": [ "nibe2vera" ], "groupNames": [  ] }, { "link": "https://192.168.XXXX:8443/rest/items/NibeRESTAPI_Status_DegreeMinutes", "state": "-54.3", "stateDescription": { "pattern": "%.0f", "readOnly": true, "options": [  ] }, "editable": true, "type": "Number", "name": "NibeRESTAPI_Status_DegreeMinutes", "label": "Degree Minutes", "tags": [ "nibe2vera" ], "groupNames": [  ] }, { "link": "https://192.168.XXXX:8443/rest/items/NibeRESTAPI_Ventilation_FanSpeed", "state": "72.0", "stateDescription": { "pattern": "%.0f", "readOnly": true, "options": [  ] }, "editable": true, "type": "Number", "name": "NibeRESTAPI_Ventilation_FanSpeed", "label": "Fan Speed", "tags": [ "nibe2vera" ], "groupNames": [  ] }, { "link": "https://192.168.XXXX:8443/rest/items/NibeRESTAPI_Addition_Blocked", "state": "ON", "stateDescription": { "readOnly": true, "options": [  ] }, "editable": true, "type": "Switch", "name": "NibeRESTAPI_Addition_Blocked", "label": "Blocked", "tags": [ "nibe2vera" ], "groupNames": [  ] }, { "link": "https://192.168.XXXX:8443/rest/items/NibeRESTAPI_CprInfoEp14_CurrentComprFrequency", "state": "20.0 Hz", "stateDescription": { "pattern": "%.0f", "readOnly": true, "options": [  ] }, "editable": true, "type": "Number:Frequency", "name": "NibeRESTAPI_CprInfoEp14_CurrentComprFrequency", "label": "Compr. Frequency", "tags": [ "nibe2vera" ], "groupNames": [  ] }, { "link": "https://192.168.XXXX:8443/rest/items/NibeRESTAPI_Status_OutdoorTemp", "state": "10.9 °C", "stateDescription": { "pattern": "%.0f", "readOnly": true, "options": [  ] }, "editable": true, "type": "Number:Temperature", "name": "NibeRESTAPI_Status_OutdoorTemp", "label": "Outdoor Temp.", "tags": [ "nibe2vera" ], "groupNames": [  ] }, { "link": "https://192.168.XXXX:8443/rest/items/NibeRESTAPI_Status_AlarmInfo", "state": "NULL", "stateDescription": { "pattern": "%s", "readOnly": true, "options": [  ] }, "editable": true, "type": "String", "name": "NibeRESTAPI_Status_AlarmInfo", "label": "Alarm Info", "tags": [ "nibe2vera" ], "groupNames": [  ] }, { "link": "https://192.168.XXXX:8443/rest/items/NibeRESTAPI_Status_HotWaterTop", "state": "46.3 °C", "stateDescription": { "pattern": "%.0f", "readOnly": true, "options": [  ] }, "editable": true, "type": "Number:Temperature", "name": "NibeRESTAPI_Status_HotWaterTop", "label": "Hot Water Top", "tags": [ "nibe2vera" ], "groupNames": [  ] } ]
                              2021-10-01T14:04:02.173Z <Engine:5:Engine.js:1367> _process_reaction_queue() wake-up!
                              2021-10-01T14:04:02.200Z <Engine:5:Engine.js:1328> _process_reaction_queue() running task 1179 { "tid": 1179, "id": "rule-kt9u8aur:S", "rule": "rule-kt9u8aur", "__reaction": [RuleReaction#rule-kt9u8aur:S], "next_step": 2, "status": 0, "ts": 1633097040135, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise], "attempts": 1 }
                              2021-10-01T14:04:02.201Z <Engine:NOTICE> Resuming reaction Nibe uplink SiteSensor<SET> (rule-kt9u8aur:S) from step 2
                              2021-10-01T14:04:02.204Z <Engine:5:Engine.js:1537> Engine#1 request header accept: application/json
                              2021-10-01T14:04:02.205Z <Engine:5:Engine.js:1539> Engine#1 reaction rule-kt9u8aur:S step 2 request url https://192.168.XXXX:8443/rest/items?tags=nibe2vera2&recursive=false data { "method": "GET", "timeout": 15000, "size": 8192, "agent": [object Object], "headers": [object Headers] }
                              2021-10-01T14:04:02.208Z <Engine:INFO> Nibe uplink SiteSensor<SET> all actions completed.
                              2021-10-01T14:04:02.209Z <Engine:5:Engine.js:1332> _process_reaction_queue() task returned, new status -1; task 1179
                              2021-10-01T14:04:02.212Z <Engine:5:Engine.js:1367> _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting
                              

                              (and then it continues with another http request in the same reaction, 2 s delay in between)

                              toggledbitsT Offline
                              toggledbitsT Offline
                              toggledbits
                              wrote on last edited by
                              #19

                              @tunnus said in SiteSensor migration:

                              What seems to happen is that if my global expression/variable is empty, fresh data is initially stored to that, but subsequent queries are "ignored", data is not replaced.
                              In the log I can see new/fresh values, but for some reason this new data is not used

                              You're going to have to describe this in more detail.

                              Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                              tunnusT 1 Reply Last reply
                              0
                              • toggledbitsT toggledbits

                                @tunnus said in SiteSensor migration:

                                What seems to happen is that if my global expression/variable is empty, fresh data is initially stored to that, but subsequent queries are "ignored", data is not replaced.
                                In the log I can see new/fresh values, but for some reason this new data is not used

                                You're going to have to describe this in more detail.

                                tunnusT Offline
                                tunnusT Offline
                                tunnus
                                wrote on last edited by
                                #20

                                @toggledbits I'll PM you relevant logs

                                Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Zigbee2MQTT & ZWA-2

                                1 Reply Last reply
                                0
                                • toggledbitsT Offline
                                  toggledbitsT Offline
                                  toggledbits
                                  wrote on last edited by
                                  #21

                                  Make sure you test with 21275 first.

                                  Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                                  tunnusT 1 Reply Last reply
                                  0
                                  • toggledbitsT toggledbits

                                    Make sure you test with 21275 first.

                                    tunnusT Offline
                                    tunnusT Offline
                                    tunnus
                                    wrote on last edited by
                                    #22

                                    @toggledbits will do

                                    Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Zigbee2MQTT & ZWA-2

                                    1 Reply Last reply
                                    0
                                    • toggledbitsT toggledbits locked this topic on
                                    Reply
                                    • Reply as topic
                                    Log in to reply
                                    • Oldest to Newest
                                    • Newest to Oldest
                                    • Most Votes


                                    Recent Topics

                                    • UI not loading after upgrading to 26318
                                      tunnusT
                                      tunnus
                                      0
                                      3
                                      57

                                    • [Resolved] Hubitat upgrade 2.5.3.123 may have broken login
                                      toggledbitsT
                                      toggledbits
                                      0
                                      8
                                      262

                                    • Reactor (Multi-System/Multi-Hub) Announcements
                                      toggledbitsT
                                      toggledbits
                                      5
                                      153
                                      162.9k

                                    • Reactor Inspect - a small read-only helper panel for MSR
                                      G
                                      gwp1
                                      2
                                      8
                                      599

                                    • Reverse proxy & API ACL
                                      tunnusT
                                      tunnus
                                      0
                                      9
                                      490

                                    • MFA
                                      T
                                      tamorgen
                                      0
                                      28
                                      1.4k

                                    • Grouped devices
                                      G
                                      gwp1
                                      0
                                      3
                                      193

                                    • Login protections
                                      toggledbitsT
                                      toggledbits
                                      0
                                      2
                                      236

                                    • Reactor Build 26284 stuck at Loading Reactor UI
                                      T
                                      tamorgen
                                      0
                                      16
                                      1.8k

                                    • MSR with reverse proxy
                                      tunnusT
                                      tunnus
                                      0
                                      12
                                      893

                                    • Missing attribute after upgrade
                                      3
                                      3rdStng
                                      0
                                      3
                                      690

                                    • Use of Google Gemini as an MSR and Hubitat configuration aid
                                      therealdbT
                                      therealdb
                                      0
                                      2
                                      326
                                    Powered by NodeBB | Contributors
                                    Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                                    • Login

                                    • Don't have an account? Register

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