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. [MSR] reactor-mqtt-contrib package for additional MQTT templates
Home Assistant 2025.11.2 and latest-25315
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
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
[Reactor] Copy&Paste of Rules
therealdbT
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me. While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users. I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do. Just an idea
Multi-System Reactor

[MSR] reactor-mqtt-contrib package for additional MQTT templates

Scheduled Pinned Locked Moved Multi-System Reactor
46 Posts 4 Posters 10.0k Views 4 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.
  • CatmanV2C CatmanV2

    @gwp1
    TrackerID is CM
    DeviceID is catmaniphone
    UserID is my configured username for my Mosquito server (so should be your Hive username)

    Because all of my stuff is local I can see the messages being posted to the logs. Not sure if you can do that with your hive set up?

    At a guess you are not connecting to the Hive server. Does the iPhone app say 'connected'. Can you see Reactor getting messages from the Hive server?

    I'm not 100% sure that's the right location for the config file. I guess if you're running reactor from /home/reactor/Documents it's right though. Just an odd choice (although Windows is not my thing) !

    C

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

    @catmanv2 yep, configured the Hive user and password and is shows as “connected” in the iOS app. I’ve not found anywhere in their dashboard to verify messages being received into the broker. I’ve not seen anything come in from the broker to msr.

    I’m running a bare metal install on a RPi. Not a Linux expert so it ended up in an interesting folder structure but it works just fine so re-orging isn’t a priority.

    *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

    CatmanV2C 1 Reply Last reply
    0
    • G gwp1

      @catmanv2 yep, configured the Hive user and password and is shows as “connected” in the iOS app. I’ve not found anywhere in their dashboard to verify messages being received into the broker. I’ve not seen anything come in from the broker to msr.

      I’m running a bare metal install on a RPi. Not a Linux expert so it ended up in an interesting folder structure but it works just fine so re-orging isn’t a priority.

      CatmanV2C Offline
      CatmanV2C Offline
      CatmanV2
      wrote on last edited by CatmanV2
      #14

      @gwp1 That's a Linux setup?! 😉

      OK, can you read the log from reactor?

      Also, are you really sure that Reactor is able to connect to HiveMQ?

      C

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

      G 1 Reply Last reply
      0
      • CatmanV2C CatmanV2

        @gwp1 That's a Linux setup?! 😉

        OK, can you read the log from reactor?

        Also, are you really sure that Reactor is able to connect to HiveMQ?

        C

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

        @catmanv2 Back home now.

        This leads me to believe it's connected to Hive:
        7d4ead99-cc53-4bff-9929-ddd04bf3fea9-image.png

        I see nothing in the logs because a.) not entirely should what it would look like, and b.) there's nothing happening atm.

        *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
          #16

          Hmm, yes tough. I share your suspicion that it's Hive. No interest in firing up Mosquito on your Linux box? Takes about 10 minutes. OK there's an increase in your vulnerability but.....

          C

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

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

            The docs for MQTTController describe how to enable topic capture, so you can see if you are getting anything at all from Hive (this is probably preferable to turning up the log level in the log file for MQTTController). I'd suggest that as a start. See what, if anything, it's sending at all.

            Ref: https://reactor.toggledbits.com/docs/MQTTController/#troubleshooting-and-debugging

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

            G 1 Reply Last reply
            1
            • CatmanV2C CatmanV2

              I am now, thanks!
              All looking good

              C

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

              @catmanv2 I hope you’ll enjoy it as much as I am 🤣

              --
              On a mission to automate everything.

              My MS Reactor contrib
              My Luup Plug-ins

              1 Reply Last reply
              0
              • toggledbitsT toggledbits

                The docs for MQTTController describe how to enable topic capture, so you can see if you are getting anything at all from Hive (this is probably preferable to turning up the log level in the log file for MQTTController). I'd suggest that as a start. See what, if anything, it's sending at all.

                Ref: https://reactor.toggledbits.com/docs/MQTTController/#troubleshooting-and-debugging

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

                @toggledbits @CatmanV2 Unless I'm just not far enough thru coffee this morning, this is what I see in MSR's mqtt logs and it looks like it's data from my iPhone8 (which I fired up via wifi to use as a test phone.)

                2022-12-12T14:02:02.896Z "owntracks/msrmqtt/iphone8" {"_type":"location","acc":35,"alt":10,"batt":100,"bs":1,"conn":"o","inregions":["Home"],"inrids":["adf34c"],"lat":32.94714,"lon":-80.013836,"m":1,"p":101.826,"t":"u","tid":"i8","tst":1670853720,"vac":15}
                2022-12-12T14:02:02.998Z "owntracks/msrmqtt/iphone8" {"_type":"location","acc":10,"alt":10,"batt":100,"bs":1,"conn":"o","inregions":["Home"],"inrids":["adf34c"],"lat":32.946934,"lon":-80.013887,"m":1,"p":101.827,"tid":"i8","tst":1670853722,"vac":8,"vel":0}
                

                So why isn't this showing here:

                247de6bd-7caa-4f61-8ce1-0ae48666f4ec-image.png

                My entity config is:

                        owntracks_iphone8: #entity ID - must be unique
                          name: "iPhone8 location" # friendly name
                          prefix: "iphone8"
                          topic: "test_iphone"
                          uses_template: owntracks_sensor
                          homeRegionName: "Home"
                

                I feel like I'm just "this close" and I just don't have something aligned properly.

                *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
                • toggledbitsT Offline
                  toggledbitsT Offline
                  toggledbits
                  wrote on last edited by toggledbits
                  #20

                  Yes, your configuration of prefix and topic don't make a string that matches what is being received. Based on what it is coming in and how those fields template configuration are used, prefix should be msrmqtt and topic should be just iphone8.

                  Conspicuous give-away: your test_iphone value doesn't appear in the topic or payload of what you're receiving.

                  @therealdb this may need a bit more documentation, since the relevance of prefix and topic aren't immediately clear (at least, not to me) without looking at the template itself and seeing how they are used, and likely the phone configuration as well (i.e. describe how configuration fields on the phone may appear in the final event topic).

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

                  G therealdbT 2 Replies Last reply
                  1
                  • CatmanV2C Offline
                    CatmanV2C Offline
                    CatmanV2
                    wrote on last edited by
                    #21

                    I believe @toggledbits has it (unsurprisingly)

                    C

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

                    1 Reply Last reply
                    0
                    • toggledbitsT toggledbits

                      Yes, your configuration of prefix and topic don't make a string that matches what is being received. Based on what it is coming in and how those fields template configuration are used, prefix should be msrmqtt and topic should be just iphone8.

                      Conspicuous give-away: your test_iphone value doesn't appear in the topic or payload of what you're receiving.

                      @therealdb this may need a bit more documentation, since the relevance of prefix and topic aren't immediately clear (at least, not to me) without looking at the template itself and seeing how they are used, and likely the phone configuration as well (i.e. describe how configuration fields on the phone may appear in the final event topic).

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

                      @toggledbits I was just updating prefix when your response came in. Here's where I am now:

                            entities:
                              owntracks_iphone8: #entity ID - must be unique
                                name: "iPhone8 location" # friendly name
                                prefix: "msrmqtt"
                                topic: "iphone8"
                                uses_template: "owntracks_sensor"
                                homeRegionName: "Home"
                      

                      My template is in reactor/config/mqtt_templates which is where @therealdb directs. Do I need to modify the uses_template:?

                      *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
                        #23

                        I think the template is in the correct place. Let's see what happens when you restart Reactor

                        C

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

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

                          @gwp1 Are you getting an error that the template owntracks_sensor doesn't exist?

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

                          G 1 Reply Last reply
                          0
                          • toggledbitsT toggledbits

                            @gwp1 Are you getting an error that the template owntracks_sensor doesn't exist?

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

                            @toggledbits I am not receiving any errors.

                            08a4de13-3175-4d69-b492-4a98202b841f-image.png

                            Just not seeing anything populate the entity.

                            cef0bd91-1e63-4f77-ae2a-abb3d23ae390-image.png

                            Is it something to do with the entity name by any random chance?

                            *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

                            toggledbitsT 1 Reply Last reply
                            0
                            • G gwp1

                              @toggledbits I am not receiving any errors.

                              08a4de13-3175-4d69-b492-4a98202b841f-image.png

                              Just not seeing anything populate the entity.

                              cef0bd91-1e63-4f77-ae2a-abb3d23ae390-image.png

                              Is it something to do with the entity name by any random chance?

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

                              @gwp1 said in [MSR] reactor-mqtt-contrib package for additional MQTT templates:

                              @toggledbits I am not receiving any errors.

                              Then there's nothing wrong with uses_template.

                              I'll make the same comment/question to you that I made to @CatmanV2 earlier in this same thread: you're on the latest MQTTController, right?

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

                              G 1 Reply Last reply
                              0
                              • toggledbitsT toggledbits

                                @gwp1 said in [MSR] reactor-mqtt-contrib package for additional MQTT templates:

                                @toggledbits I am not receiving any errors.

                                Then there's nothing wrong with uses_template.

                                I'll make the same comment/question to you that I made to @CatmanV2 earlier in this same thread: you're on the latest MQTTController, right?

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

                                @toggledbits MQTTController-22326 (double-checked the CHANGELOG.md)

                                EDIT: ...which I now see is a version behind. You snuck one in on me. Updating to MQTTController-22340.

                                EDIT2: Nailed it.
                                8009852f-2527-46c2-a2da-508b073c5dec-image.png

                                *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

                                G CatmanV2C 2 Replies Last reply
                                1
                                • G gwp1

                                  @toggledbits MQTTController-22326 (double-checked the CHANGELOG.md)

                                  EDIT: ...which I now see is a version behind. You snuck one in on me. Updating to MQTTController-22340.

                                  EDIT2: Nailed it.
                                  8009852f-2527-46c2-a2da-508b073c5dec-image.png

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

                                  @toggledbits @therealdb @CatmanV2 Thank you all for your help here, this is a big step in my system. Really appreciate it!

                                  *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
                                  2
                                  • CatmanV2C Offline
                                    CatmanV2C Offline
                                    CatmanV2
                                    wrote on last edited by
                                    #29

                                    @therealdb what are your updates set to on the iPhone app? The data is going to be useful, but on 'Significant' I appear to be only getting updates on
                                    string and region which makes sense.
                                    I'm assuming that battery_power.level won't update more frequently unless the app is configured to 'Move'

                                    Has anyone done that? Does it kill the iPhone battery?

                                    Cheers

                                    C

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

                                    1 Reply Last reply
                                    0
                                    • G gwp1

                                      @toggledbits MQTTController-22326 (double-checked the CHANGELOG.md)

                                      EDIT: ...which I now see is a version behind. You snuck one in on me. Updating to MQTTController-22340.

                                      EDIT2: Nailed it.
                                      8009852f-2527-46c2-a2da-508b073c5dec-image.png

                                      CatmanV2C Offline
                                      CatmanV2C Offline
                                      CatmanV2
                                      wrote on last edited by
                                      #30

                                      @gwp1 how did you get the Driving Flag?

                                      Cheers

                                      C

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

                                      G 1 Reply Last reply
                                      0
                                      • CatmanV2C CatmanV2

                                        @gwp1 how did you get the Driving Flag?

                                        Cheers

                                        C

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

                                        @catmanv2 move translates to any movement your phone is making - increases accuracy but kills battery life. significant is defined by OwnTracks as "traveling a distance of at least 500 meters in 5 minutes" which lets the app nap and is much easier on the battery.

                                        Driving Flag is a virtual switch I created based on distance from Home. I believe I currently have it set to .1 mile so it trips as soon as I pull out of the neighborhood. I use it as a safety to the GPS reporting for when I'm not home. I have a second one called Driving Flag - Far Away that kicks in at two miles. This is for use when I'm obviously not just puttering about the neighborhood but going to be gone while. Can be used to trigger HVAC, etc.

                                        *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
                                        1
                                        • CatmanV2C Offline
                                          CatmanV2C Offline
                                          CatmanV2
                                          wrote on last edited by
                                          #32

                                          Cool, ta

                                          C

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

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


                                          Recent Topics

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

                                          • Reactor (Multi-System/Multi-Hub) Announcements
                                            toggledbitsT
                                            toggledbits
                                            5
                                            129
                                            73.4k

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

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

                                          • Script action and custom timers
                                            toggledbitsT
                                            toggledbits
                                            0
                                            4
                                            118

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

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

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

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

                                          • Shelly Wall Display XL
                                            akbooerA
                                            akbooer
                                            2
                                            9
                                            753

                                          • [Solved] alarm() in global expression throws error in log.
                                            toggledbitsT
                                            toggledbits
                                            0
                                            26
                                            708

                                          • [Solved] Define function issue in latest-25304
                                            CrilleC
                                            Crille
                                            0
                                            12
                                            444
                                          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