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. Support for 3rd party Vera plugins ?
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

Support for 3rd party Vera plugins ?

Scheduled Pinned Locked Moved Multi-System Reactor
39 Posts 5 Posters 8.4k Views 5 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.
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #24

    And here is a list of all the Harmony plugin service id functions

    1bbbfe55-6419-448a-aeeb-96f7f2349b62-image.png

    c5f05f9c-5baa-4af9-8fe7-b401dba86293-image.png

    1 Reply Last reply
    0
    • therealdbT Offline
      therealdbT Offline
      therealdb
      wrote on last edited by
      #25

      As @rigpapa said, he needs to map them.

      Since we're at it, I think both my VeraAlexa and VeraTelegram plug-ins are good candidate as a native MSR plug-in, since they could be written as node.js/bash script. Virtual HTTP Devices plug-in is using standard services, so we should be good.

      --
      On a mission to automate everything.

      My MS Reactor contrib
      My Luup Plug-ins

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

        Indeed.

        I'm not currently using your Telegram Vera plugin, I'm just sending out HTTP requests from Vera also now from MSR, to their Cloud API / my Telegram account.

        MSR Doesn't natively support Telegram messenger either by the looks of it.

        1 Reply Last reply
        0
        • therealdbT Offline
          therealdbT Offline
          therealdb
          wrote on last edited by
          #27

          And that’s ok if you want to send text only, but images/videos could be complex, since you need to send a file as well.

          --
          On a mission to automate everything.

          My MS Reactor contrib
          My Luup Plug-ins

          cw-kidC 1 Reply Last reply
          0
          • therealdbT therealdb

            And that’s ok if you want to send text only, but images/videos could be complex, since you need to send a file as well.

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

            @therealdb said in Support for 3rd party Vera plugins ?:

            but images/videos could be complex, since you need to send a file as well.

            Yeah I'm not doing that currently just text.

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

              Telegram plugin will be supported in 21055 (build later today). I am working on ALTHUE. Challenging since I don't own these devices.

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

              therealdbT 1 Reply Last reply
              0
              • toggledbitsT toggledbits

                Telegram plugin will be supported in 21055 (build later today). I am working on ALTHUE. Challenging since I don't own these devices.

                therealdbT Offline
                therealdbT Offline
                therealdb
                wrote on last edited by
                #30

                @toggledbits said in Support for 3rd party Vera plugins ?:

                Challenging since I don't own these devices.

                let me know if you need help. for ALTHue, I think an emulator (ie: HA-Bridge) could be enough.

                --
                On a mission to automate everything.

                My MS Reactor contrib
                My Luup Plug-ins

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

                  Would a device dump for the main AltHue device in Vera help ? Now I know how to do them.

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

                    I got all your stuff. That really helps. First pass support is in for 21055. Let's see how it goes.

                    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
                    • cw-kidC Offline
                      cw-kidC Offline
                      cw-kid
                      wrote on last edited by
                      #33

                      HARMONY SEND DEVICE COMMAND - CONFIRMED AS WORKING

                      I've tested sending a Device Command to an IR device via the Harmony hub in an MSR rule, see my note on the ticket here.

                      I can now see the Harmony plugin's ServiceID functions under an Entity Action in MSR, by selecting the Harmony Hub device.

                      81ece552-1c91-40f6-b021-604ec36194ff-image.png

                      I tried issuing a Device Command first, to turn on an Amplifier that runs the speaker in my Bathroom ceiling.

                      I used the Harmony plugin for Vera HTTP API with these commands to work out what information I needed. Or I could have looked in the Variables tab in Vera for this Harmony Hub device instead.

                      You can see here on the Vera forum about these HTTP commands.

                      List All Devices

                      (214 Is the Vera Device ID number of the Harmony Hub device)

                      http://VERA-IP/port_3480/data_request?id=lr_Harmony214&cmd=list_devices

                      In the results I found the device I wanted to send a command to.

                      { "Device": "Denon Mini System", "Manufacturer": "Denon", "ID": "70564644", "Model": "UDM31" }

                      So 70564644 is the devices ID number.

                      List All Commands of that device

                      http://VERA-IP/port_3480/data_request?id=lr_Harmony214&cmd=list_device_commands&cmdp1=70564644

                      In the results I then found the "Command" that I want to send from MSR, in this case its PowerToggle

                      [ { "Function": "Power", "Commands": [ { "Action": "PowerToggle", "Label": "Power Toggle" } ]

                      Duration is the length of time the Harmony Hub should blast the IR command I set this to 1

                      0021491d-babf-474c-8979-07806f75d508-image.png

                      My MSR rule here is linked / triggered by a virtual ON / OFF switch in Vera, so I also configured the "Reset Reaction" in the rule.

                      When I turn ON or OFF the "Bathroom Amplifier" virtual switch in Vera, the IR command "PowerToggle" is sent to the amplifier OK, so its working !

                      Today I will also test starting different Harmony Activities and Powering Off the Harmony Hub.

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

                        AltHue Plugin for Vera:

                        CONFIRMED AS WORKING - HUE SCENES

                        The ServiceID's are now exposed in an Entity Action in an MSR rule or Global Reaction.

                        You need to select the main AltHue device in your Entity Action, then select hue_scene from this list.

                        3ece807e-067a-482f-b6b0-fb292b8823cb-image.png

                        Go in to the AltHue main device in Vera UI7 web GUI and go in to the "Hue Scenes" area and find the scene in the list that you want to start in your MSR rule or Global Reaction.

                        Copy its ID number.

                        d961abcf-20cc-42f6-9b54-2f13702b66f0-image.png

                        Back in MSR edit the Entity Action and paste in the ID number.

                        ac481ffe-6a11-45cb-851f-e89e7ec00b49-image.png

                        When I ran my MSR Global Reaction, my hue scene is started and my lights are now in Arctic Aurora.

                        CONFIRMED AS WORKING - EFFECT COLORLOOP

                        Next I created another Global Reaction and tried starting the Effect ColorLoop

                        Choose the set_effect from the drop down list.

                        The child ID is the AltHue child device aka the light that you want the colorloop to be on.

                        and enter "colorloop" in the Effect field.

                        0b01caba-2889-4148-a67e-69f35369d7c2-image.png

                        When you run the Reaction, If the light is already turned ON the colorloop will start.

                        However if the light is turned off nothing will happen, so I added an action to turn on the light first then run the colorloop effect, which is working.

                        a20d30fe-a2e1-4534-95dc-d9d84ee82304-image.png

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

                          HARMONY POWER AND ACTIVITY STATUS - WORKING

                          If I use this HTTP command it lists all the Activities on my Lounge Harmony Hub.

                          http://VERA-IP/port_3480/data_request?id=lr_Harmony184&cmd=list_activities

                          { "status": "OK", "msg": "OK", "data": { "activities": [ { "ID": "27585584", "Activity": "ChromeCast Video" }, { "ID": "23834935", "Activity": "Media Center" }, { "ID": "23834936", "Activity": "XBOX" }, { "ID": "23864128", "Activity": "Wii-U" }, { "ID": "43190809", "Activity": "Nintendo Switch" }, { "ID": "23834933", "Activity": "Freeview" }, { "ID": "-1", "Activity": "PowerOff" }, { "ID": "42772934", "Activity": "Fire TV" }, { "ID": "36455394", "Activity": "ChromeCast Audio" }, { "ID": "42766865", "Activity": "BT TV" } ] }, "code": 200 }

                          In MSR I can see x_vera_plugin_harmony.activity_status ServiceID

                          When there are no activities running e.g. OFF the status returned is 0

                          And when I am in my Watch TV "BT TV" activity, the status is 2, so you should be able to work out which activity is what status number ?

                          Activities OFF - Status = 0

                          e716268a-4201-415d-9cbe-ec665c619628-image.png

                          Watch TV Activity - Status = 2

                          c60a6247-b893-47b5-9857-c4e22677d331-image.png

                          So I created a rule that when my Harmony hub is OFF then turn off some LED strip lights.

                          b1329efd-91e5-485e-8640-16a027c77d62-image.png

                          Alternatively there is a ServiceID called x_vera_plugin_harmony.power_status

                          It is FALSE when all my Harmony Activities are turned OFF, so we can potentially use this instead.

                          99b89c25-cde9-494a-9a14-c46da8230463-image.png

                          And finally I looked at x_vera_plugin_harmony.current_activity this will return the activity ID numbers.

                          I know -1 = Powered OFF so I could have used this also.

                          When my Harmony is in Watch TV activity "BT TV" its showing a number ID of 42766865 which is correct. If you look at my output at the start listing all the activities and their ID numbers.

                          3393fcea-4e87-4d73-b41a-1e029a902b15-image.png

                          So I could now create an MSR rule that does something only when I am in the Watch TV Harmony activity etc.

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

                            Thanks for the update. The detail really helps, too, as I've been pondering ways to gather "queryable" things to help smooth the user experience (e.g. list of activities).

                            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
                            • cw-kidC Offline
                              cw-kidC Offline
                              cw-kid
                              wrote on last edited by
                              #37

                              Yes that would be neat. The user wouldn't then have to do what I've just done and manually go looking up Activity numbers and matching them to the names of their activities.

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

                                I requested support for the Vera RGB Controller plugin, after that I'm all sorted I think, just looked at my installed plugins list on Vera and I can't see any others that I'd want or need MSR to be able to send commands to or monitor their status I don't think.

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

                                  CONFIRMED WORKING

                                  RGB Controller Plugin - Animations

                                  I use this plugin with Fibaro RGBW V1 modules, these modules have inbuilt LED animation routines.

                                  Animation - Fireplace - programId="6"

                                  Animation - Storm - programId="7"

                                  Animation - Rainbow - programId="8"

                                  Animation - Aurora - programId="9"

                                  Animation - LAPD - programId="10"

                                  Animation - Animation Off - programId="0"

                                  In the Entity Action you need to select the RGB Controller device of interest. Mine looks like this in Vera and is called "Kitchen - RGBW"

                                  c0c0ba70-a886-4f37-990f-5993dea78009-image.png

                                  You can then select x_vera_rgbcontroller_plugin.start_animation

                                  c5e3f21e-b1c8-4d0f-8109-7daf5fde1aec-image.png

                                  "speed" and "duration" fields I'm not sure about, never had to deal with those before in Vera / PLEG. I left them both at 0. The LED animations works OK anyway.

                                  Might have to look at the Fibaro RGBW user manual see what they say.

                                  Fireplace example:

                                  6e0c17a0-0ca8-460e-a65a-46e03404ab37-image.png

                                  Storm example:

                                  a0906648-62e0-481b-b86c-90dc0a7e4e5a-image.png

                                  Animation Off example:

                                  f5d51105-8952-4f69-b5d6-fc0d2e5275bf-image.png

                                  Be sure to change both the program_id field and the program_name field or it won't work.

                                  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

                                  • Single protocol?
                                    CatmanV2C
                                    CatmanV2
                                    0
                                    1
                                    11

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

                                  • Reactor Loading Screen Safari
                                    S
                                    SweetGenius
                                    0
                                    10
                                    133

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

                                  • 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
                                    508

                                  • 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