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. Help. Installing Reactor on Home Assistant.
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
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
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
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

Help. Installing Reactor on Home Assistant.

Scheduled Pinned Locked Moved Multi-System Reactor
33 Posts 6 Posters 6.2k Views 6 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.
  • A Offline
    A Offline
    alminsk
    wrote on last edited by
    #19

    Maybe I'm not choosing the right network?
    I have it like this now:

    image.png

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

      That volume binding doesn't look right to me. Again, I'm not a Portainer user, but I would think that the path /var/reactor would be mentioned as related to the binding, since this is what Reactor is using internally within the container. It looks like you may have copied something from the Home Assistant configuration, but that's not right. I bet the /mnt/data/supervisor/homeassistant directory does not even exist in your new VM, because Home Assistant is not installed in that VM. You can't copy-paste/borrow from the Home Assistant configuration and get a successful Reactor configuration; different products, different configuration requirements. The Reactor installation instructions for docker show in the examples a Reactor data directory simply created in a regular user home directory. This is what you want. That directory (e.g. /home/username/reactor) should be bound to /var/reactor in the container.

      Your network configuration is also suspect/incorrect. Again, it looks like you copied from Home Assistant's instructions, rather than using the Reactor instructions. The network mode is typically "host". If that doesn't work, you can try "bridge".

      Can any of the Portainer+Reactor users please chime in here with some help for this user? Screen shots would be helpful. @black-cat @Fanan @vezinpi ...

      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
      • A Offline
        A Offline
        alminsk
        wrote on last edited by
        #21

        I have created such a catologist. /mnt/data/supervisor/homeassistant

        I tried to install different networks

        "Can any of the Portainer+Reactor users please chime in here with some help for this user? Screen shots would be helpful. @black-cat @Fanan @vezinpi ..." - I would be very grateful to you.

        F 1 Reply Last reply
        0
        • A alminsk

          I have created such a catologist. /mnt/data/supervisor/homeassistant

          I tried to install different networks

          "Can any of the Portainer+Reactor users please chime in here with some help for this user? Screen shots would be helpful. @black-cat @Fanan @vezinpi ..." - I would be very grateful to you.

          F Offline
          F Offline
          Fanan
          wrote on last edited by Fanan
          #22

          @alminsk I use portainer succesfully and have the same volumes setting as you. I followed a guide from someone long time ago, and it's been a "do and forget" thing. I'm not a programmer, so I can't tell why somethings are as they are.

          My network setting are different:
          5fa9129a-9744-4731-8b50-3a8f50b2f6a7-image.png

          My setup is on a HA Blue (odroid n2+) and these values are also different:
          9fb11882-3563-4c17-9c16-fe6f563658e7-image.png

          Under Command & logging everything is the same except for the last line:
          8d6512e0-fc90-435e-a776-1257edd06599-image.png

          I hope this helps... As I wrote, I'm not the expert here, or know what every parameter means. Best of luck!
          /Fanan

          toggledbitsT 1 Reply Last reply
          1
          • F Fanan

            @alminsk I use portainer succesfully and have the same volumes setting as you. I followed a guide from someone long time ago, and it's been a "do and forget" thing. I'm not a programmer, so I can't tell why somethings are as they are.

            My network setting are different:
            5fa9129a-9744-4731-8b50-3a8f50b2f6a7-image.png

            My setup is on a HA Blue (odroid n2+) and these values are also different:
            9fb11882-3563-4c17-9c16-fe6f563658e7-image.png

            Under Command & logging everything is the same except for the last line:
            8d6512e0-fc90-435e-a776-1257edd06599-image.png

            I hope this helps... As I wrote, I'm not the expert here, or know what every parameter means. Best of luck!
            /Fanan

            toggledbitsT Offline
            toggledbitsT Offline
            toggledbits
            wrote on last edited by toggledbits
            #23

            @Fanan Unfortunately, at least one of those differences is incorrect for you. The NODE_PATH would be correct as @alminsk showed in his screen shots; it should be /opt/reactor:/opt/reactor/node_modules. If it is not this exact value, some features of Reactor will not function.

            The value of tag is not relevant.

            @alminsk In the face of all of this, I decided yesterday to make Portainer a supported environment, so I got it installed on a spare Pi, did a couple of Reactor installs, and wrote down the steps, here: https://reactor.toggledbits.com/docs/Installation-docker-portainer/

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

            F 1 Reply Last reply
            3
            • R Offline
              R Offline
              RogerO
              wrote on last edited by RogerO
              #24

              @toggledbits Hi Patrick,
              Looking at your Portainer doc, found a minor error I think. In second paragraph in first section you have "For most Linux most systems," . Doesn't make sense.

              Also, should "The stable branch builds have seen action for a while and are more... well... stable." Actually be "The stable branch builds have not seen action for a while and are more... well... stable.

              1 Reply Last reply
              1
              • toggledbitsT toggledbits

                @Fanan Unfortunately, at least one of those differences is incorrect for you. The NODE_PATH would be correct as @alminsk showed in his screen shots; it should be /opt/reactor:/opt/reactor/node_modules. If it is not this exact value, some features of Reactor will not function.

                The value of tag is not relevant.

                @alminsk In the face of all of this, I decided yesterday to make Portainer a supported environment, so I got it installed on a spare Pi, did a couple of Reactor installs, and wrote down the steps, here: https://reactor.toggledbits.com/docs/Installation-docker-portainer/

                F Offline
                F Offline
                Fanan
                wrote on last edited by
                #25

                @toggledbits Thanks! As I mentioned before; these things are like greek to me, so I'm very thankful for all assistance. I changed the NODE_PATH. Strange that it has worked as a charm so far!

                1 Reply Last reply
                0
                • A Offline
                  A Offline
                  alminsk
                  wrote on last edited by
                  #26

                  Excellent. Everything worked. Thank you so much for the excellent REACTOR. Thank you so much for your support.

                  1 Reply Last reply
                  1
                  • A Offline
                    A Offline
                    alminsk
                    wrote on last edited by
                    #27

                    Hello everyone. I ran into a problem: I can't save the rules.
                    Screenshot_1.png Screenshot_2.png

                    I assume that the problem is in the path of the user file. Created a directory along this path.

                    Screenshot_3.png

                    The Portainer starts the reactor container . But the rules are not saved.

                    1 Reply Last reply
                    0
                    • A Offline
                      A Offline
                      alminsk
                      wrote on last edited by
                      #28

                      I looked at the logs, everything is recorded well. The directory is specified correctly.

                      image.png

                      1 Reply Last reply
                      0
                      • A Offline
                        A Offline
                        alminsk
                        wrote on last edited by
                        #29

                        Everything worked. I don't understand what the reason is. The rules are saved.

                        1 Reply Last reply
                        0
                        • A Offline
                          A Offline
                          alminsk
                          wrote on last edited by
                          #30

                          Maybe I haven't figured out how to work with MSR yet. I used to work with Reactor in VeraPlus, but it works a little differently.

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

                            If the save button is faded green as shown in your screen shot, that means you have an error in your rule that you have to fix before saving. Your rule screen shot has everything collapsed/hidden; this is not helpful.

                            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
                            • A Offline
                              A Offline
                              alminsk
                              wrote on last edited by
                              #32

                              Thanks. I'm figuring it out a little bit. Yes, there really were mistakes.

                              G 1 Reply Last reply
                              0
                              • A alminsk

                                Thanks. I'm figuring it out a little bit. Yes, there really were mistakes.

                                G Offline
                                G Offline
                                gwp1
                                wrote on last edited by
                                #33

                                @alminsk Now that you've been working in MSR for a short while it's time to revisit the manual. You'll find things that may not have made sense or that you didn't see a use for now make much more sense.

                                Focus on how to understand the signs MSR is giving you to help you troubleshoot.

                                I, too, came from the Vera Reactor plugin. "Same but different" applies here - but in all good ways.

                                *Hubitat C-7 2.4.3.158
                                *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                                *HASS 2025.11.1
                                w/ HA Connect ZWA-2
                                FW: v1.1
                                SDK: v7.23.1

                                *Prod MSR in docker/portainer
                                MSR: latest-25323-d340b7d9
                                MQTTController: 25139
                                ZWave Controller: 25139

                                1 Reply Last reply
                                4
                                • toggledbitsT toggledbits locked this topic on
                                Reply
                                • Reply as topic
                                Log in to reply
                                • Oldest to Newest
                                • Newest to Oldest
                                • Most Votes


                                Recent Topics

                                • Is there a way to turn this section (image in post) off?
                                  toggledbitsT
                                  toggledbits
                                  0
                                  1
                                  17

                                • Device log?
                                  toggledbitsT
                                  toggledbits
                                  0
                                  2
                                  43

                                • Midnight crossing not working in date/time condition (build 25325)
                                  tunnusT
                                  tunnus
                                  0
                                  3
                                  43

                                • Error: Command timeout
                                  G
                                  gwp1
                                  0
                                  6
                                  131

                                • Reactor (Multi-System/Multi-Hub) Announcements
                                  toggledbitsT
                                  toggledbits
                                  5
                                  131
                                  74.9k

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

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

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

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

                                • Script action and custom timers
                                  toggledbitsT
                                  toggledbits
                                  0
                                  4
                                  204

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

                                • There is an alternative to homebridge-mqttthing
                                  akbooerA
                                  akbooer
                                  1
                                  2
                                  156
                                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