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. Issue with HTTP API
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor
Device log?
G
@toggledbits is there a log that will show me what rule is turning on a specific device? I've got a switch that has been kicking on at 2200 ET for several nights now and the reactor.log doesn't have a thing in it that I can see on a device level (it being more rules-based).
Multi-System Reactor
Midnight crossing not working in date/time condition (build 25325)
tunnusT
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
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
Topic thumbnail image
Multi-System Reactor
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
Multi-System Reactor

Issue with HTTP API

Scheduled Pinned Locked Moved Multi-System Reactor
8 Posts 2 Posters 962 Views 2 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.
  • E Offline
    E Offline
    eonnet
    wrote on last edited by
    #1

    Hello @toggledbits I have a strange issue with the HTTP request that i send to Reactor.
    I have two reactors one on a Unraid server and one on Ubuntu server installed as a docker, when i send http get request to the Unraid server to control home assistant entity everything is going ok, but when i send the same request to the ubuntu modified accordingly it says "Request failed" but when i try to run reaction via http request it works.

    When i go to entities and try to control the entity manually its working.

    Any idea's?

    Best regards

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

      First, you need to show your work (per the posting guidelines). That means showing the reactions, and the requests, and the responses to the requests, and describe how you are making the requests (curl, etc.-- what is the "it" that is giving you "Request failed"). If the requests are being made in Reactor, what is being logged?

      Second, I find this statement contradictory, and it needs clarification:

      when i send the same request to the ubuntu modified accordingly it says "Request failed" but when i try to run reaction via http request it works.

      Please update your original post.

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

      1 Reply Last reply
      0
      • E Offline
        E Offline
        eonnet
        wrote on last edited by eonnet
        #3

        Hello @toggledbits im trying to control reactor from external source, for this example i'm using web browser.

        (this is example for the docker installation on ubuntu server)
        When i hit a web page http://192.168.0.39:8111/api/v1/entity/hass_container>climate_vivax/perform/hvac_heating_unit.set_setpoint?setpoint=26
        i get a response
        'Request failed'
        and the action is not executed

        When i hit a web page http://192.168.0.39:8111/api/v1/reaction/re-lb1bejbo/run
        i get response
        {"status":true,"message":"Vivax Off started"}
        and the action is executed

        On the unraid server docker installation when i hit http://192.168.0.81:8111/api/v1/entity/hass>climate_vivax/perform/hvac_heating_unit.set_setpoint?setpoint=26
        i recieve a response
        {"status":true,"message":"Performed hvac_heating_unit.set_setpoint on Thermostat#hass>climate_vivax"}
        and the action is executed

        when i hit http://eonnet.duckdns.org:8112/api/v1/entity/hass>climate_vivax/perform/hvac_control.set_mode?mode=off
        i recieve a response
        {"status":true,"message":"Performed hvac_control.set_mode on Thermostat#hass>climate_vivax"}
        and the action is executed.

        Best regards

        1 Reply Last reply
        0
        • E Offline
          E Offline
          eonnet
          wrote on last edited by
          #4

          I tried tonight with curl and postman i get the same response
          request failed
          no further info.... this is only happening when i try to make a request to entity.

          I also tried to make a reaction with the http request to reactor and the response is:
          Reaction "re-lb2sork5" (re-lb2sork5) step 1 http request failed
          Error: HTTP request failed: 400 Bad Request

          I hope this gives you more info

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

            What did you find in the reactor.log file?

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

            E 1 Reply Last reply
            0
            • toggledbitsT toggledbits

              What did you find in the reactor.log file?

              E Offline
              E Offline
              eonnet
              wrote on last edited by eonnet
              #6

              @toggledbits here is the log

              [latest-22328]2022-11-30T19:58:30.832Z httpapi:ERR httpapi: perform hvac_heating_unit.set_setpoint on Thermostat#hass>climate_vivax failed: [TypeError]Typ>
              [latest-22328]2022-11-30T19:58:30.834Z httpapi:CRIT TypeError: Type mismatch on config reactor.engine.monitored_entities, expecting array, got object
              TypeError: Type mismatch on config reactor.engine.monitored_entities, expecting array, got object
              at Configuration.getConfig (/opt/reactor/server/lib/Configuration.js:163:23)
              at Function.getConfig (/opt/reactor/server/lib/Configuration.js:151:82)
              at HTTPAPI._handlePerformRequest (/opt/reactor/server/lib/httpapi.js:834:56)
              at /opt/reactor/server/lib/httpapi.js:396:61
              at Layer.handle [as handle_request] (/opt/reactor/node_modules/express/lib/router/layer.js:95:5)
              at next (/opt/reactor/node_modules/express/lib/router/route.js:144:13)
              at Route.dispatch (/opt/reactor/node_modules/express/lib/router/route.js:114:3)
              at Layer.handle [as handle_request] (/opt/reactor/node_modules/express/lib/router/layer.js:95:5)
              at /opt/reactor/node_modules/express/lib/router/index.js:284:15
              at param (/opt/reactor/node_modules/express/lib/router/index.js:365:14)

              and another on with different request

              [latest-22328]2022-11-30T20:02:22.335Z httpapi:ERR httpapi: perform hvac_control.set_mode on Thermostat#hass>climate_vivax failed: [TypeError]TypeError: T>
              [latest-22328]2022-11-30T20:02:22.336Z httpapi:CRIT TypeError: Type mismatch on config reactor.engine.monitored_entities, expecting array, got object
              TypeError: Type mismatch on config reactor.engine.monitored_entities, expecting array, got object
              at Configuration.getConfig (/opt/reactor/server/lib/Configuration.js:163:23)
              at Function.getConfig (/opt/reactor/server/lib/Configuration.js:151:82)
              at HTTPAPI._handlePerformRequest (/opt/reactor/server/lib/httpapi.js:834:56)
              at /opt/reactor/server/lib/httpapi.js:396:61
              at Layer.handle [as handle_request] (/opt/reactor/node_modules/express/lib/router/layer.js:95:5)
              at next (/opt/reactor/node_modules/express/lib/router/route.js:144:13)
              at Route.dispatch (/opt/reactor/node_modules/express/lib/router/route.js:114:3)
              at Layer.handle [as handle_request] (/opt/reactor/node_modules/express/lib/router/layer.js:95:5)
              at /opt/reactor/node_modules/express/lib/router/index.js:284:15
              at param (/opt/reactor/node_modules/express/lib/router/index.js:365:14)

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

                OK. It looks like you've formatted your monitored_entities configuration incorrectly on that Reactor install. That seems to be the error. Either remove that section, or review the documentation and get it fixed.

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

                1 Reply Last reply
                0
                • E Offline
                  E Offline
                  eonnet
                  wrote on last edited by
                  #8

                  @toggledbits yes that was the problem, thanks on the fix.

                  Best regards

                  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

                  • Copying a global reaction
                    toggledbitsT
                    toggledbits
                    0
                    3
                    78

                  • [HowTo] Using HABridge with Reactor
                    CatmanV2C
                    CatmanV2
                    0
                    9
                    385

                  • [Reactor] Bug when sending MQTT boolean payloads
                    toggledbitsT
                    toggledbits
                    0
                    4
                    130

                  • Genuinely impressed with Zigbee and HA / Reactor
                    therealdbT
                    therealdb
                    1
                    8
                    298

                  • Difficulty defining repeating annual period
                    G
                    gwp1
                    0
                    5
                    97

                  • Need help with sequence
                    therealdbT
                    therealdb
                    0
                    3
                    61

                  • Possible feature request?
                    therealdbT
                    therealdb
                    0
                    5
                    161

                  • Logic Assistance: Exterior Lights on when Illuminance Below Threshold
                    CatmanV2C
                    CatmanV2
                    0
                    11
                    338

                  • Time series documentation
                    tunnusT
                    tunnus
                    0
                    11
                    389

                  • MQTT templates for ZIgbee scene controller, or a better way?
                    CatmanV2C
                    CatmanV2
                    0
                    3
                    158

                  • Reset a delay
                    CatmanV2C
                    CatmanV2
                    0
                    8
                    219
                  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