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. Preview of 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
Notice to Docker + ARM Users (RPi 3/4/5 and others)
toggledbitsT
This post does not apply to users of Intel/AMD-based systems. If you are using a Reactor image tagged latest-amd64 or stable-amd64, then this post does not apply to you. It also does not apply to bare-metal installs; it's for users of docker images on ARM-based systems only (principally Raspberry Pi hosts, but could be others). After January 15, 2026, I will no longer produce the aarch64-tagged docker image for Reactor. The ARM images will be arm64 for 64-bit operating systems, and armv7l for 32-bit operating systems. For those of you running a container from the aarch64 image today, this will be a relatively simple change: you just need to switch the image used for your docker container to a differently-tagged image. If you are using docker-compose, then this is a relatively simple matter of changing the image line in your docker-compose.yaml file and then stopping (docker-compose down) and restarting (docker-compose up -d) your Reactor daemon. But there's a catch... not all of you can safely just switch from the aarch64 image to the arm64 image. And, you can't just trust the output of uname -m, for example, because this exposes the CPU architecture, but not the word size of the OS running on that CPU. For Raspberry Pi systems, the transition to 64-bit operating systems was long (starting in 2016) and not always obvious — although there was a first "official" 64-bit OS for RPis in 2020, it did not become a default recommendation in the Raspberry Pi Imager until 2021, and then that was only the default for Pi 3/4 systems with >4GB RAM; it was 2022 before it was universally recommended for all 64-bit CPUs regardless of RAM size. Depending on when you first imaged your RPi system and what default you may have been offered/chosen, you could today easily have a 64-bit CPU Raspberry Pi running a 32-bit version of the operating system. Upgrades along the way would not change this; changing it to fully 64-bit requires a full reimage of the system. To establish if your OS is 64- or 32-bit, log in to your Pi and run: sudo dpkg-architecture -q DEB_HOST_ARCH. If the response is arm64 or aarch64, then you are running a 64-bit OS and you should use the arm64-tagged image. If it's anything else, you are running a 32-bit OS, and you should use the armv7l-tagged image. pi@rpi4-1:~ $ sudo dpkg-architecture -q DEB_HOST_ARCH armhf pi@rpi4-1:~ $ uname -m aarch64 pi@rpi4-1:~ $ In the example above, the uname command reports that the CPU is 64-bit architecture (aarch64), which is true for the host on which I ran these commands, but the DEB_HOST_ARCH value is armhf, indicating a 32-bit operating system. This system has to use the armv7l-tagged image. Other systems will have their own ways of determining the word size of the running OS. Since the majority of Reactor users running ARM systems are on Raspberry Pis, I am able to supply the above instructions, but if you happen to have a different ARM system, you'll need to do some web searching to figure out how to expose that information. Or, you can just try the arm64 image, and if it doesn't start up, try the armv7l image. Remember to always back up your system before making any changes. For everyone, please make this change as soon as possible, and if you have any trouble finding a working image, please (1) go back to the current aarch64 image; and (2) let me know in this thread along with as much detail about your host system as you can offer (including the output of the dpkg-architecture command mentioned above).
Multi-System Reactor
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 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

Preview of Multi-System Reactor

Scheduled Pinned Locked Moved Multi-System Reactor
58 Posts 11 Posters 10.0k Views 11 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.
  • LibraSunL Offline
    LibraSunL Offline
    LibraSun
    wrote on last edited by
    #31

    MSR USAGE QUESTION

    Is there a (straightforward) way to do Dev# substitution into the new way (e.g. getEntity( "vera>device_216" ).attributes.battery_power.level) that attribute values get referenced in MSR?
    Back on Reactor for Vera, I used to iterate over getstate( DeviceNum, "urn:micasaverde-com:serviceId:HaDevice1", "BatteryLevel" ) to derive the current battery levels on various devices. And I'd somewhat hate to have to hard-code or write out all of them by hand if I don't have to in MSR.

    1 Reply Last reply
    0
    • M Offline
      M Offline
      Matteburk
      wrote on last edited by
      #32

      @toggledbits
      Could you share a rule for one Room so we can see how it could look like with multipel reactions that has different conditions.
      I Don’t really understand how multipel reactions on diffrent conditions should look like. In Reactor it was easy to understand but in msr i Don’t get it..

      I really Wanja make more complicated automations but Iam stuck with one reaction...
      / Mattias

      T 1 Reply Last reply
      1
      • M Matteburk

        @toggledbits
        Could you share a rule for one Room so we can see how it could look like with multipel reactions that has different conditions.
        I Don’t really understand how multipel reactions on diffrent conditions should look like. In Reactor it was easy to understand but in msr i Don’t get it..

        I really Wanja make more complicated automations but Iam stuck with one reaction...
        / Mattias

        T Offline
        T Offline
        Tarkus
        wrote on last edited by
        #33

        @matteburk Did you do an import of your Vera reactor sensors? It is different in MSR but I compared the MSR imported rules vs Vera reactors and it helped me figure out what was going on.

        M 1 Reply Last reply
        1
        • toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by
          #34

          There are no reactions on groups in MSR. Reactor for Vera allowed you to create activities (its equivalent to reactions) on any group in your ReactorSensor.

          So, if you are creating a rule with subgroups in MSR, and you decide that the subgroup needs to perform some actions, you have export that subgroup to a Rule of its own. There is a button for that. If you click that button on a group (to the right of the group name), it will export the group to a Rule, and replace the group with a "Rule" condition for the new rule so the logic remains intact in the current rule.

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

          M 1 Reply Last reply
          1
          • toggledbitsT toggledbits

            There are no reactions on groups in MSR. Reactor for Vera allowed you to create activities (its equivalent to reactions) on any group in your ReactorSensor.

            So, if you are creating a rule with subgroups in MSR, and you decide that the subgroup needs to perform some actions, you have export that subgroup to a Rule of its own. There is a button for that. If you click that button on a group (to the right of the group name), it will export the group to a Rule, and replace the group with a "Rule" condition for the new rule so the logic remains intact in the current rule.

            M Offline
            M Offline
            Matteburk
            wrote on last edited by
            #35

            @toggledbits@toggledbits Ok Then I understand but I cant find the button... I have Button,rename and collapse and then som shaded row...
            Skärmavbild 2021-03-17 kl. 18.58.28.png

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

              Are you on 21075? Version number in the upper-right corner.

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

              M 2 Replies Last reply
              0
              • T Tarkus

                @matteburk Did you do an import of your Vera reactor sensors? It is different in MSR but I compared the MSR imported rules vs Vera reactors and it helped me figure out what was going on.

                M Offline
                M Offline
                Matteburk
                wrote on last edited by
                #37

                @tarkus I dont use reactor anymore on my Vera Plus... I Jumped the ship a year ago to hubitat..

                1 Reply Last reply
                0
                • toggledbitsT toggledbits

                  Are you on 21075? Version number in the upper-right corner.

                  M Offline
                  M Offline
                  Matteburk
                  wrote on last edited by
                  #38

                  @toggledbits yes... Sorry... will update asap My bad!

                  1 Reply Last reply
                  0
                  • toggledbitsT toggledbits

                    Are you on 21075? Version number in the upper-right corner.

                    M Offline
                    M Offline
                    Matteburk
                    wrote on last edited by
                    #39

                    @toggledbits On 21075 now and it works (button found) 🙂 Thanx! Lets rock on!

                    1 Reply Last reply
                    2
                    • LibraSunL Offline
                      LibraSunL Offline
                      LibraSun
                      wrote on last edited by LibraSun
                      #40

                      FEATURE REQUEST

                      Consider Including CallMeBot among the Notification classes, with the following parameters available for editing in notification.yaml:

                      base_url=http://api2.callmebot.com/start.php
                      source=vera
                      user=@<user_name>
                      text=<default_msg>
                      lang=en-US-Standard-C
                      rpt=2"
                      

                      Of course, the text parameter can be overridden in Reactions and probably should not have a default setting come to think of it. IIRC, usernames correspond to the user's Telegram account nickname.

                      1 Reply Last reply
                      1
                      • LibraSunL Offline
                        LibraSunL Offline
                        LibraSun
                        wrote on last edited by LibraSun
                        #41

                        Just finished porting ALL of my Reactor recipes over to MSR Rules, and feel very accomplished for having done so. Only took me about a week, which included a TON of A/B testing.

                        With very few exceptions, my workflows are working swiftly and as expected. Any obvious glitches I've reported using Bug Tracker.
                        And the remaining one or two head scratchers (notably me pressing a button on my NodOn Soft Remote and Vera frustratingly ignoring me!) deserve deeper exploration before I submit a trouble ticket.

                        The MSR learning curve has been refreshingly low, and I suspect it will be even for staunch PLEG users as well.

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

                          The Nodons are among the "scene controllers" that use non-standard variables (well, according to the UPnP device and service definitions). It seems that half of the scene controllers Vera supports use LastSceneID, and the half use either sl_SceneActivated/Deactivated or sl_CentralScene, and I've scene (see what I did there?) one case recently where a device uses both (the former consistently and the latter inconsistently). Vera doing Vera things.

                          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
                          1
                          • LibraSunL Offline
                            LibraSunL Offline
                            LibraSun
                            wrote on last edited by
                            #43

                            Delved deeper... turns out Vera had attempted to set a bogus Configuration Setting (device > details > Device Options)... Variable 1 = <empty> 😹

                            Deleted that, did Save Changes, and voilà... not only did sl_CentralScene, sl_CentralSceneAttr and sl_SceneActivated spring back to life...
                            ...so did the blinking LED in the center of the NodOn remote which, alas, had stopped working correctly last week. Guess how that's governed!? Yep, a Config Var (8, 1d, 3 IIRC).

                            Vera, Vera, Vera. Will your wonders never cease? Please? Pretty please?

                            1 Reply Last reply
                            0
                            • cw-kidC Offline
                              cw-kidC Offline
                              cw-kid
                              wrote on last edited by cw-kid
                              #44

                              Plus one for native CallMebot support. I am currently just sending a HTTP request.

                              Likewise for Telegram messenger push notifications, I am currently just sending a HTTP request.

                              Which is fine I guess, but anything that makes things easier for users is cool also.

                              1 Reply Last reply
                              0
                              • cw-kidC Offline
                                cw-kidC Offline
                                cw-kid
                                wrote on last edited by
                                #45

                                P.S. I really like the new Entity Attribute picker and search dialogue box.

                                Would of saved me a lot of time if we had it earlier but its definitely a big improvement.

                                1 Reply Last reply
                                3
                                • toggledbitsT Offline
                                  toggledbitsT Offline
                                  toggledbits
                                  wrote on last edited by
                                  #46

                                  CallMeBot will be in today's build.

                                  The Telegram plugin for Vera is supported through entity actions, no HTTP request needed.

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

                                  cw-kidC 1 Reply Last reply
                                  2
                                  • M Offline
                                    M Offline
                                    Matteburk
                                    wrote on last edited by
                                    #47

                                    @toggledbits Like Christmas for a kid the search entity function just popped up over night,when I woke up in a crispy Sunny Sweden it just was there.... Super great work P!

                                    1 Reply Last reply
                                    1
                                    • toggledbitsT toggledbits

                                      CallMeBot will be in today's build.

                                      The Telegram plugin for Vera is supported through entity actions, no HTTP request needed.

                                      cw-kidC Offline
                                      cw-kidC Offline
                                      cw-kid
                                      wrote on last edited by
                                      #48

                                      @toggledbits said in Preview of Multi-System Reactor:

                                      Telegram plugin for Vera

                                      I'm not using the Telegram plugin for Vera currently. Didn't see the point of installing another plugin, when I can just send a HTTP request directly to the Telegram API.

                                      1 Reply Last reply
                                      0
                                      • cw-kidC Offline
                                        cw-kidC Offline
                                        cw-kid
                                        wrote on last edited by
                                        #49

                                        Just tested the new CallMeBot integration which is working for me.

                                        5077d2a9-fdd2-433c-aa15-46f7d8570698-image.png

                                        In the notification.yaml file I just had to specify my username in the quotes:

                                        user: "@user_name"

                                        I also specified this language for proper English. 🇬🇧

                                        lang: "en-GB-Standard-A"

                                        And the number of repeats I wanted:

                                        rpt: "2"

                                        When I press the Play button on the "Set Reaction" in my test rule, my phone receives a phone call saying "This is a test" twice.

                                        My phone is Android Pie version 9. If anyone knows how to make this CallMeBot phone call ring out aloud even when my phone is in vibrate or silent mode I would really like to know how ?

                                        LibraSunL 1 Reply Last reply
                                        1
                                        • cw-kidC cw-kid

                                          Just tested the new CallMeBot integration which is working for me.

                                          5077d2a9-fdd2-433c-aa15-46f7d8570698-image.png

                                          In the notification.yaml file I just had to specify my username in the quotes:

                                          user: "@user_name"

                                          I also specified this language for proper English. 🇬🇧

                                          lang: "en-GB-Standard-A"

                                          And the number of repeats I wanted:

                                          rpt: "2"

                                          When I press the Play button on the "Set Reaction" in my test rule, my phone receives a phone call saying "This is a test" twice.

                                          My phone is Android Pie version 9. If anyone knows how to make this CallMeBot phone call ring out aloud even when my phone is in vibrate or silent mode I would really like to know how ?

                                          LibraSunL Offline
                                          LibraSunL Offline
                                          LibraSun
                                          wrote on last edited by LibraSun
                                          #50

                                          @cw-kid said in Preview of Multi-System Reactor:

                                          If anyone knows how to make this CallMeBot phone call ring out aloud even when my phone is in vibrate or silent mode I would really like to know how ?

                                          Sounds like a job for Tasker. Best Android phone automation tool around. Basically Reactor for Android!

                                          Among its many built-in variables is one for detecting the incoming phone number. That can become the basis for a "Profile" (trigger), which would run when CallMeBot phones you. And that profile can run a Task (reaction) which turns up your ringer volume and/or vibration.

                                          Tasker even resets (some) changed States (attributes) automatically once the Profile goes inactive (false).

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Recent Topics

                                          • Single protocol?
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            1
                                            13

                                          • Any thoughts on which is better
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            7
                                            114

                                          • Reactor Loading Screen Safari
                                            S
                                            SweetGenius
                                            0
                                            10
                                            135

                                          • Constraints states visually do not match actual
                                            S
                                            SweetGenius
                                            0
                                            3
                                            57

                                          • Oh the joy of pairing
                                            CatmanV2C
                                            CatmanV2
                                            2
                                            1
                                            40

                                          • HDMI oddness
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            1
                                            36

                                          • Home Assistant Connect ZWA-2 & ZBT-2
                                            therealdbT
                                            therealdb
                                            4
                                            14
                                            679

                                          • [MSR] Feature request: For Each action on arrays/groups
                                            therealdbT
                                            therealdb
                                            0
                                            7
                                            198

                                          • [Solved] Error: Command timeout
                                            toggledbitsT
                                            toggledbits
                                            0
                                            10
                                            509

                                          • Issue with MSR UI becoming unresponsive
                                            S
                                            sethlampman
                                            0
                                            7
                                            197

                                          • Date/time condition
                                            tunnusT
                                            tunnus
                                            0
                                            3
                                            140
                                          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