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. Home Remote dashboard app and MSR HTTP API
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
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
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
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
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

Home Remote dashboard app and MSR HTTP API

Scheduled Pinned Locked Moved Multi-System Reactor
16 Posts 5 Posters 1.7k 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 cw-kid
    #1

    For those using the Home Remote dashboard app, this maybe of interest, Bill has just shown me how to more easily either create buttons on your own custom pages or "Scene" devices / tiles on Group pages, that when pressed will send out HTTP commands to MSR, to then run either a Global Reaction or a Rule Set that is triggered via a Global Expression value change.

    Apr 29, 2021

    Feature Request - Make it easier to create button to send HTTP requests

    Feature Request - Make it easier to create button to send HTTP requests

    I have managed to create two buttons that when pressed they send out a HTTP request. One button was an ON command and the other button was an OFF command. I followed the example here However for creating lots of buttons with this functionality I can see it being very difficult and a lot of hassle...

    Been wanting to be able to do this for a while now.

    This is a custom page with regular buttons, these two test buttons are initiating Global Reactions in MSR:

    e5146a4e-75a4-48a5-a286-aec93e550e4d-image.png

    This is a GROUP page with "Scene" tiles, these are initiating Rule Sets in MSR:

    edde011d-0542-4b7a-aef5-d2986cc27f81-image.png

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

      I recall from earlier Home Remote tutorials that you can round-trip device status pretty easily FROM the dashboard (you press a virtual button) TO Vera/other controller, which UPDATES Reactor/MSR (via entity status watches), then BACK to Home Remote (via MSR rule sending HTTP in this case), which UPDATES the dashboard (same button you initially pressed or any other receiving element).

      In light of that, have you attempted to create any "ganged" switches whereby turning ON/OFF A causes B, C, and D also to turn ON/OFF?

      That's always been a topic of interest for me -- all the more now that you've brought HTTP GET into the picture (since, for example, you can send/receive such commands with EventGhost running on a PC, which opens up lots of possibilities there...). It becomes a question of "Where to 'gang' them?"

      HR has internal logic, so it could theoretically happen there. MSR obviously has built-in logic. Vera can group or gang things together using the Switchboard plug-in, as one prime example. (Especially if you use the purpose-built "multi" switch type and use binary inputs to drive each toggle on/off!) And surely other options I'm not even thinking of at the moment.

      I'm eager to hear more about what you do with this type of construct.

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

        I am not using any of Home Remotes own internal scenes / logic, I couldn't see the point of that

        For me all logic should be done from one master controller which is MSR.

        Once I have moved my remaining Vera scenes that have logic (LUA code) to MSR then MSR will be doing everything. As you know I am no longer using PLEG.

        Home Remote for me is just that a dashboard remote control app.

        Home Remote is connected to my Vera Plus hub and Philips Hue Bridge, so all those devices and scenes I can control in the Home Remote dashboard.

        I am not grouping any lights really nothing to speak of other than my side table lamps.

        I have two in my lounge room for example and I created a "Master" virtual dimmer device in Vera and then a rule with an expression in MSR that groups the control of the two lamps.

        So when I turn On / Off or Dim the "Master" virtual dimmer device, then both real lamp devices follow suit etc.

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

          Now, here comes my essential question: How does Home Remote "know" to update its dashboard symbol for LIGHT A after you've tapped its button on the screen? Does it receive an update (via HTTP I presume) from Vera letting HA HR know that "It's on now"?

          I guess I could ask more simply, "How does HA HR stay 'in sync' with devices on Vera?"

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

            I don't know exactly how Bill is doing the Vera integration with Home Remote.

            However I do know he is using the SDATA output stream from Vera

            http://Vera-IP:3480/data_request?id=sdata
            

            So presumably it's the status of devices from SDATA, that updates the icons / states of the devices in the Home Remote GUI.

            As for control I assume he is using the Vera HTTP API (Luup Requests).

            As for what I am doing here creating buttons in Home Remote to run MSR actions (scenes), I don't really need any status feedback, they are just manually initiated scenes for basic things.

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

              The light icons update for Vera device objects.

              If I went to the wall switch and turned off the Lounge Main Light the icon and state of the device in the app would change to being OFF

              Screenshot_20210429_220156_com.thehomeremote.homeremote.jpg

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

                Okay, roger that, and thanks. It's great that HR (I think I called it HA for some odd reason earlier, sorry) and Vera "talk" that way. I'm now recalling that the lengthy tutorial I watched of his -- where the user had to essentially "code" all the feedback from actual devices -- involved a WiFi-connected amplifier. Unlike Vera, that device didn't "push" updates to HR in real time, so it had to be polled on every change.

                PablaP 1 Reply Last reply
                0
                • LibraSunL LibraSun

                  Okay, roger that, and thanks. It's great that HR (I think I called it HA for some odd reason earlier, sorry) and Vera "talk" that way. I'm now recalling that the lengthy tutorial I watched of his -- where the user had to essentially "code" all the feedback from actual devices -- involved a WiFi-connected amplifier. Unlike Vera, that device didn't "push" updates to HR in real time, so it had to be polled on every change.

                  PablaP Offline
                  PablaP Offline
                  Pabla
                  wrote on last edited by
                  #8

                  @librasun A lot of plugins have been integrated in the app where you no longer have to code anything really to control supported receivers etc. It's a pretty highly integrated app!

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

                    I am using Group pages in HR rather than building my own custom pages from a blank slate.

                    Group pages are auto generated for you. You just create a Windows Explorer folder like structure in the designer application, for your desired menu structure / layout and add Vera devices and scenes to them from the list it already imported.

                    Doing it that way I haven't needed to manually code anything for device Status feedback it just happens.

                    Have a look at my HR thread on the Vera forum, I covered the basic concept of using Group pages in HR.

                    Creating your own custom pages looks much more involved like what @Tarkus has done and his project looks amazing but beyond my skills I think.

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

                      This is how my dashboard looks

                      Nov 13, 2020

                      CW's Version 1.0 dashboard based on "Groups"

                      CW's Version 1.0 dashboard based on "Groups"

                      Hi Here is my first attempt at an Imperihome app dashboard replacement using Home Remote, I still have some small glitches and issues, but overall its finished ish… For reference here was my Imperihome dashboard. I have used the Groups pages, as that seemed like the quicker way to get up and...

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

                        Thanks, guys, this has me excited to try something with HR (or, later MSR's own Dashboard) which completely sidesteps Vera. Namely, creating "virtual devices" that live entirely on MSR (probably as Expressions at first, but conceivably as fully-blown Rules standing in place of virtual devices).

                        I'd love to have a Group page in Home Remote, where each square represents a corresponding entity on MSR. As @cw-kid proposes above, the back-and-forth could be wired up entirely via HTTP requests.

                        (My next question was going to be, "Does anyone have HR running in a Docker container?" I recall it runs on various platforms.)

                        cw-kidC T 2 Replies Last reply
                        1
                        • cw-kidC Offline
                          cw-kidC Offline
                          cw-kid
                          wrote on last edited by cw-kid
                          #12

                          Home Remote the designer application is Windows only. This is the application used to create your project.

                          The front end dashboard apps are Android, iOS and Windows.

                          Once you have created your project file you can publish it. I publish my project file to my internal ftp server then every mobile device phones and tablets look at that location for any new project file updates.

                          So the mobile apps just auto update to the latest version of my project when the app is launched on that device.

                          So no more running round to each mobile device to update it like with Imperihome.

                          No need for Docker.

                          1 Reply Last reply
                          1
                          • LibraSunL LibraSun

                            Thanks, guys, this has me excited to try something with HR (or, later MSR's own Dashboard) which completely sidesteps Vera. Namely, creating "virtual devices" that live entirely on MSR (probably as Expressions at first, but conceivably as fully-blown Rules standing in place of virtual devices).

                            I'd love to have a Group page in Home Remote, where each square represents a corresponding entity on MSR. As @cw-kid proposes above, the back-and-forth could be wired up entirely via HTTP requests.

                            (My next question was going to be, "Does anyone have HR running in a Docker container?" I recall it runs on various platforms.)

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

                            @librasun said in Home Remote dashboard app and MSR HTTP API:

                            Namely, creating "virtual devices" that live entirely on MSR (probably as Expressions at first, but conceivably as fully-blown Rules standing in place of virtual devices).

                            Your the expressions expert, I wouldn't know where to start! 😉

                            But virtual devices on MSR could be a good idea.

                            1 Reply Last reply
                            0
                            • LibraSunL LibraSun

                              Thanks, guys, this has me excited to try something with HR (or, later MSR's own Dashboard) which completely sidesteps Vera. Namely, creating "virtual devices" that live entirely on MSR (probably as Expressions at first, but conceivably as fully-blown Rules standing in place of virtual devices).

                              I'd love to have a Group page in Home Remote, where each square represents a corresponding entity on MSR. As @cw-kid proposes above, the back-and-forth could be wired up entirely via HTTP requests.

                              (My next question was going to be, "Does anyone have HR running in a Docker container?" I recall it runs on various platforms.)

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

                              @librasun here is a demo I put together on Home Remote utilizing my personal project. I also use MSR for a majority of the conditional logic. The demo runs about 9 minutes.

                              Home remote 3.0 Demo
                              MikeReadingtonM 1 Reply Last reply
                              3
                              • LibraSunL Offline
                                LibraSunL Offline
                                LibraSun
                                wrote on last edited by
                                #15

                                Awesome, will check it out! Meanwhile, here's @toggledbits ' official stance on "Virtual Devices on MSR".

                                1 Reply Last reply
                                0
                                • T Tarkus

                                  @librasun here is a demo I put together on Home Remote utilizing my personal project. I also use MSR for a majority of the conditional logic. The demo runs about 9 minutes.

                                  Home remote 3.0 Demo
                                  MikeReadingtonM Offline
                                  MikeReadingtonM Offline
                                  MikeReadington
                                  wrote on last edited by
                                  #16

                                  @tarkus very nice!

                                  Yep, I will be looking into this for sure.

                                  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

                                  • Error: Command timeout
                                    toggledbitsT
                                    toggledbits
                                    0
                                    4
                                    72

                                  • [Solved] Local expression in Rule does not evaluate as they used to do
                                    CrilleC
                                    Crille
                                    0
                                    5
                                    156

                                  • Reactor (Multi-System/Multi-Hub) Announcements
                                    toggledbitsT
                                    toggledbits
                                    5
                                    130
                                    74.3k

                                  • Home Assistant 2025.11.2 and latest-25315
                                    G
                                    gwp1
                                    0
                                    6
                                    187

                                  • Notice to Docker + ARM Users (RPi 3/4/5 and others)
                                    toggledbitsT
                                    toggledbits
                                    1
                                    1
                                    69

                                  • Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
                                    M
                                    mgvra
                                    1
                                    3
                                    165

                                  • Script action and custom timers
                                    toggledbitsT
                                    toggledbits
                                    0
                                    4
                                    175

                                  • Help resolve change in behaviour post update
                                    CatmanV2C
                                    CatmanV2
                                    0
                                    12
                                    474

                                  • There is an alternative to homebridge-mqttthing
                                    akbooerA
                                    akbooer
                                    1
                                    2
                                    142

                                  • Reactor w/HA 2025.11 error on set_datetime service call setting only time
                                    CrilleC
                                    Crille
                                    0
                                    6
                                    207

                                  • Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
                                    toggledbitsT
                                    toggledbits
                                    0
                                    17
                                    599

                                  • Shelly Wall Display XL
                                    akbooerA
                                    akbooer
                                    2
                                    9
                                    881
                                  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