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. What notification system is best?
[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
Rule Set UI bug - RESOLVED
3
Topic thumbnail image
Multi-System Reactor

What notification system is best?

Scheduled Pinned Locked Moved Multi-System Reactor
16 Posts 9 Posters 1.7k Views 9 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 Andr

    @therealdb said in What notification system is best?:

    Telegram here as well. I’ve deeply customized with a bot, pushing videos from my cams and accepting commands with wizards as well.

    Do you mean a "chatbot" that you can respond to? That sounds cool, could you give som example of what you use it for?

    Right now I struggle with Pushover. Can't find out why it doesn't work.😖
    From reactor.log:
    default:null Module NotifyPushover v21195
    Engine:ERR Engine#1 reaction re-kud4t99t step 0 notification (Pushover) failed: Error: Pushover user and token could not be determined

    From notification.yaml

      # Pushover
      Pushover:
        profiles:
          default:
            # description - A friendly description of this profile (for menus)
            description: Andre
            #
            # user - (required) user key from Pushover. Refer to the Reactor docs for
            #        the Notify action for info on how to get your user key.
            #user: u4cXXXXXXXXXXXXXXXXXXXXXtkv1d
            #
            # token - (required) token from Pushover site. Again, see the Reactor docs
            #         for info. This is the default token used for this profile if a
            #         token is not specified in the notification parameters.
            #token: amwXXXXXXXXXXXXXXXXXXXXXn7if
            #
            # default_device - (optional) name of the default device to receive not-
            #                  ifications. You can leave this blank, and the default
            #                  device will be whatever the Pushover API determines. If
            #                  set here, it's the default for this profile, when no
            #                  device is specified in the Notify action itself.
            #default_device: ""
            #
            # default_title - (optional) default notification title to use for this
            #                 profile. It will be used when no title is specified in
            #                 the Notify action. If no title is specified at all, the
            #                 system default title "Reactor" will be used.
            #default_title: "Reactor Notification"
    

    The Reaction
    568b81e0-3ad6-44b8-bd89-3ff26628429a-image.png

    I have tried to put user id & token between citation marks " "
    Same user id & token work from pushover site and when sending notification from Homeassistant.

    CrilleC Online
    CrilleC Online
    Crille
    wrote on last edited by
    #6

    @andr Remove the “#” in front of user id and token

    A 1 Reply Last reply
    1
    • CrilleC Crille

      @andr Remove the “#” in front of user id and token

      A Offline
      A Offline
      Andr
      wrote on last edited by
      #7

      @crille
      THANKS!!🙏🏼

      Now Pushover works.
      Time to take a look at that Telegrambot 🙂

      1 Reply Last reply
      1
      • CrilleC Online
        CrilleC Online
        Crille
        wrote on last edited by Crille
        #8

        I use pushover for all my notifications and have been doing so since 2013. A really good and stable service. Started using it before it became a subscription service so was upgraded to “free for life” when they introduced that.
        Telegram is looking very interesting though 🙂

        Edit: I see it’s a one-time fee per platform now, not a subscription.

        A 1 Reply Last reply
        0
        • CrilleC Crille

          I use pushover for all my notifications and have been doing so since 2013. A really good and stable service. Started using it before it became a subscription service so was upgraded to “free for life” when they introduced that.
          Telegram is looking very interesting though 🙂

          Edit: I see it’s a one-time fee per platform now, not a subscription.

          A Offline
          A Offline
          Andr
          wrote on last edited by
          #9

          @crille
          Yes, 5usd per platform. Not much to discuss if it is a good service.
          Will use the 30-day trial period for now to test it.

          But the telegram bot seems intresting, I got it up and running but i dont think i can manage to make good use of it.
          Me: Hey bot, heat up my car so its ready 07:45
          Bot: After consulting with MSR i found the outside temperature is -5 degrees, so I start the heater at 07:00.

          Thanks everyone for your thoughts, very helpful!

          tunnusT 1 Reply Last reply
          0
          • wmarcolinW Offline
            wmarcolinW Offline
            wmarcolin
            wrote on last edited by
            #10

            Telegram 🙂

            1 Reply Last reply
            0
            • A Andr

              @crille
              Yes, 5usd per platform. Not much to discuss if it is a good service.
              Will use the 30-day trial period for now to test it.

              But the telegram bot seems intresting, I got it up and running but i dont think i can manage to make good use of it.
              Me: Hey bot, heat up my car so its ready 07:45
              Bot: After consulting with MSR i found the outside temperature is -5 degrees, so I start the heater at 07:00.

              Thanks everyone for your thoughts, very helpful!

              tunnusT Offline
              tunnusT Offline
              tunnus
              wrote on last edited by
              #11

              @andr interactive bot might be a bit too much for starters, but Telegram is excellent in providing different status messages set up in MSR

              Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

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

                The chat bot is used to control lights and run scenes, if necessary. I’m still on my Vera but it’s decoupled, so this is the only way to interact when outside the house.

                I’ve also integrated my ECOVAC deebots, and opensprinkler. But we’re mainly using it to open doors and garage doors, since everything else is automated and we rarely mess with this stuff. But it was fun. It’s not parsing natural language, but it’s doable (part of my job is dedicated to this stuff, so this was a sort of research project for me back in the days).

                --
                On a mission to automate everything.

                My MS Reactor contrib
                My Luup Plug-ins

                PablaP 1 Reply Last reply
                0
                • G Offline
                  G Offline
                  gwp1
                  wrote on last edited by
                  #13

                  Dipped my toe with Prowl, saw Pushover and haven't looked back. I like the ability to "personalize" the notifications both textually and audibly.

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

                  *HASS 2025.11.1
                  w/ ZST10-700 fw 7.18.3

                  *Prod MSR in docker/portainer
                  MSR: latest-25310-dc2bb580
                  MQTTController: 25139
                  ZWave Controller: 25139

                  1 Reply Last reply
                  0
                  • CatmanV2C Offline
                    CatmanV2C Offline
                    CatmanV2
                    wrote on last edited by
                    #14

                    Telegram. Zero maintenance.

                    C

                    The Ex-Vera abuser know as CatmanV2.....

                    1 Reply Last reply
                    0
                    • therealdbT therealdb

                      The chat bot is used to control lights and run scenes, if necessary. I’m still on my Vera but it’s decoupled, so this is the only way to interact when outside the house.

                      I’ve also integrated my ECOVAC deebots, and opensprinkler. But we’re mainly using it to open doors and garage doors, since everything else is automated and we rarely mess with this stuff. But it was fun. It’s not parsing natural language, but it’s doable (part of my job is dedicated to this stuff, so this was a sort of research project for me back in the days).

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

                      @therealdb said in What notification system is best?:

                      The chat bot is used to control lights and run scenes, if necessary. I’m still on my Vera but it’s decoupled, so this is the only way to interact when outside the house.

                      I’ve also integrated my ECOVAC deebots, and opensprinkler. But we’re mainly using it to open doors and garage doors, since everything else is automated and we rarely mess with this stuff. But it was fun. It’s not parsing natural language, but it’s doable (part of my job is dedicated to this stuff, so this was a sort of research project for me back in the days).

                      This chat bot sounds interesting, if I am reading this correctly in the Telegram group chat you can basically tell the bot to do certain things that are preconfigured?

                      therealdbT 1 Reply Last reply
                      0
                      • PablaP Pabla

                        @therealdb said in What notification system is best?:

                        The chat bot is used to control lights and run scenes, if necessary. I’m still on my Vera but it’s decoupled, so this is the only way to interact when outside the house.

                        I’ve also integrated my ECOVAC deebots, and opensprinkler. But we’re mainly using it to open doors and garage doors, since everything else is automated and we rarely mess with this stuff. But it was fun. It’s not parsing natural language, but it’s doable (part of my job is dedicated to this stuff, so this was a sort of research project for me back in the days).

                        This chat bot sounds interesting, if I am reading this correctly in the Telegram group chat you can basically tell the bot to do certain things that are preconfigured?

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

                        @pabla yep. It’s not a product, but very specific to my needs, so I’ve not released it. I’ll see if I could post some screenshot to be of inspiration to others. AFAIK home assistant has something like this built in (or, maybe, it’s open hab)

                        --
                        On a mission to automate everything.

                        My MS Reactor contrib
                        My Luup Plug-ins

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


                        Recent Topics

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

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

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

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

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

                        • Script action and custom timers
                          toggledbitsT
                          toggledbits
                          0
                          4
                          158

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

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

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

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

                        • Shelly Wall Display XL
                          akbooerA
                          akbooer
                          2
                          9
                          836

                        • [Solved] alarm() in global expression throws error in log.
                          toggledbitsT
                          toggledbits
                          0
                          26
                          953
                        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