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
Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
M
Hi, I'm in the process of migrating from a Raspberry Pi 4 (ARMv7) to a Raspberry Pi 5 (ARMv8/aarch64), but I’ve run into an issue: there is no proper ARMv8/aarch64 image available. None of the existing images run on the Pi 5 - they all exit immediately with code 139 (segmentation fault), which typically indicates that the binaries inside the image are not compatible with the ARM64/aarch64 architecture used by the Pi 5. Would it be possible to publish a correct ARMv8/aarch64 (linux/arm64) image? Building one should be relatively straightforward using docker buildx with multi-arch support. For example, my own Node.js images are built this way: docker buildx build --push \ -t <localrepo>/<project>:<tag> \ --platform=linux/arm64,linux/amd64 \ --file ./apps/<project>/Dockerfile . This produces both the AMD64 and ARM64/v8 variants automatically. Also, as a side note, it may be best to avoid using Alpine as the base image for the ARM64 build, since musl-based builds often cause compatibility issues and unnecessary headaches. A glibc-based base image (e.g., Debian or Ubuntu) tends to work far more reliably on ARM64, especially for Node.js applications. @toggledbits - tagging you in case you missed this. Thanks, mgvra
Multi-System Reactor
Script action and custom timers
therealdbT
Sorry to write here without trying, but I’m flying today. Am I correct if i say that script action with alarm() makes it possible to execute a reaction in a given interval, lets say 15 seconds or 3.5 minutes? That sounds amazing, since I’ve used weird tricks, including a custom controller, just to do this.
Multi-System Reactor
Help resolve change in behaviour post update
CatmanV2C
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 w/HA 2025.11 error on set_datetime service call setting only time
CrilleC
@toggledbits Do you know if this is related to that PR or is it a change they made in 2025.11.1? [latest-25310]2025-11-11T13:16:24.319Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag with { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.320Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag action: { "type": "call_service", "service_data": { "date": (null), "time": "10:45", "datetime": (null), "timestamp": (null) }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_dag" } } [latest-25310]2025-11-11T13:16:24.321Z <HassController:ERR> HassController#hass request 1762866984320<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.321Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "10:45" }) on Entity#hass>input_datetime_vvb_dag failed! [latest-25310]2025-11-11T13:16:24.321Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"10:45","datetime":null,"timestamp":null},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_dag"},"id":1762866984320} [latest-25310]2025-11-11T13:16:24.322Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.322Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 0 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Engine#1 action args: { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 1 [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt with { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt action: { "type": "call_service", "service_data": { "date": (null), "time": "03:00", "datetime": (null), "timestamp": 0 }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_natt" } } [latest-25310]2025-11-11T13:16:24.324Z <HassController:ERR> HassController#hass request 1762866984323<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "03:00", "timestamp": 0 }) on Entity#hass>input_datetime_vvb_natt failed! [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"03:00","datetime":null,"timestamp":0},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_natt"},"id":1762866984323} [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.324Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 1 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <Engine:INFO> Engine#1 action args: { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 2 [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Sätt Schema VVB i Home Assistant<AKTIV> all actions completed.
Multi-System Reactor
Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
P
Hello, I currently have an office light (connected via a Leviton Zwave Dimmer switch) controlled from a Gen5 Aeotech Zwave switch installed on my Synology 720+ NAS. I run HA(2025.11.10) in a virtual machine from my NAS and Reactor on the container manager of the same NAS. Prior to updating to 25304 the rule I had set to turn the light on to a specific dimming value worked correctly. Now the rule appears to follow the decision tree, however the reaction does not trigger setting the dimming or turning on the office light? Strangely I can still turn the light on and off as well as dim it directly from HASS..? I have tried using the ''try this action'' button in the rules reaction setting and it will not control the light and does not throw an error flagÉ Please help, P.S Reactor has been rock steady for me over the last few years and I'm a big fan of this solution.
Multi-System Reactor
[Solved] alarm() in global expression throws error in log.
CrilleC
Topic thumbnail image
Multi-System Reactor
[Solved] Define function issue in latest-25304
CrilleC
Topic thumbnail image
Multi-System Reactor
No Upgrade Notification for Build 25308?
CatmanV2C
FWIW I'm no longer getting a notification from MSR that there's an update. Just thought I'd mention it C
Multi-System Reactor
Strange behavior in MSR latest-25304 with disabled groups in Reaction
therealdbT
Topic thumbnail image
Multi-System Reactor
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Handling Dead Entities and Renamed Entities
PablaP
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down. I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor). My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only). Anyway, here's my reactor-mqtt-contrib package: https://github.com/dbochicchio/reactor-mqtt-contrib Simply download yaml files (everything or just the ones you need) and you're good to go. I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them. The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression. Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
Multi-System Reactor
HA 2025.9.4 Supported Yet?
CatmanV2C
Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off Cheers C
Multi-System Reactor
Rule Set UI bug - RESOLVED
3
Topic thumbnail image
Multi-System Reactor
[Reactor] Copy&Paste of Rules
therealdbT
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me. While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users. I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do. Just an idea
Multi-System Reactor
[Reactor] Help with scene controller cycling logic
therealdbT
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically. That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button. Example: Light 1 ON → OFF, then Light 2 ON → OFF. The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule. Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor

Issue with HTTP API

Scheduled Pinned Locked Moved Multi-System Reactor
8 Posts 2 Posters 791 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

                  • Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
                    M
                    mgvra
                    1
                    3
                    66
                  • Script action and custom timers
                    toggledbitsT
                    toggledbits
                    0
                    4
                    85
                  • Help resolve change in behaviour post update
                    CatmanV2C
                    CatmanV2
                    0
                    12
                    244
                  • Reactor (Multi-System/Multi-Hub) Announcements
                    CatmanV2C
                    CatmanV2
                    5
                    128
                    72.9k
                  • There is an alternative to homebridge-mqttthing
                    akbooerA
                    akbooer
                    1
                    2
                    87
                  • Reactor w/HA 2025.11 error on set_datetime service call setting only time
                    CrilleC
                    Crille
                    0
                    6
                    91
                  • Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
                    toggledbitsT
                    toggledbits
                    0
                    17
                    310
                  • Shelly Wall Display XL
                    akbooerA
                    akbooer
                    2
                    9
                    699
                  • [Solved] alarm() in global expression throws error in log.
                    toggledbitsT
                    toggledbits
                    0
                    26
                    537
                  • [Solved] Define function issue in latest-25304
                    CrilleC
                    Crille
                    0
                    12
                    384
                  • No Upgrade Notification for Build 25308?
                    toggledbitsT
                    toggledbits
                    0
                    2
                    90
                  • Strange behavior in MSR latest-25304 with disabled groups in Reaction
                    toggledbitsT
                    toggledbits
                    0
                    2
                    131
                  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