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).
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
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.
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.
@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.
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.
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).
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
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
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically.
That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button.
Example: Light 1 ON → OFF, then Light 2 ON → OFF.
The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule.
Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Entity is not visible
-
Trying my damndest to follow the guidelines......
Reactor latest-22274-24dfd72c
Intel NUC Debian BullseyeUsing an online YAML editor I have managed to create a reactor.yaml with an entity that allows Reactor to start (no idea why vi seems to break the yaml)
- id: mqqt enabled: true implementation: MQTTController name: Mosquito config: source: "mqtt://192.168.70.249:8883/" username: xxxx password: xxxx entities: catman_iphone: name: "Catman Phone" topic: FCEB043-B975-490E-B051-198473F6A504 uses_template: owntracks_in_region region: "Home"My expectation is that this would create a binary sensor. I can see no such sensor.
Reactor log:
[latest-22274]2022-10-09T15:13:55.580Z <app:null> Reactor latest-22274-24dfd72c starting on v16.15.0 [latest-22274]2022-10-09T15:13:55.581Z <app:INFO> Process ID 10567; docker false; platform linux/x64 #1 SMP Debian 4.19.235-1 (2022-03-17); locale en_GB.UTF-8 [latest-22274]2022-10-09T15:13:55.581Z <app:INFO> Basedir /home/catman/reactor; data in /home/catman/reactor/storage [latest-22274]2022-10-09T15:13:55.581Z <app:INFO> NODE_PATH=/home/catman/reactor [latest-22274]2022-10-09T15:13:55.583Z <app:INFO> Configured locale (undefined); selected locale(s) en_GB.UTF-8 [latest-22274]2022-10-09T15:13:55.601Z <app:INFO> Loaded locale en-US [latest-22274]2022-10-09T15:13:55.612Z <Capabilities:null> Module Capabilities v22250 [latest-22274]2022-10-09T15:13:55.659Z <Plugin:null> Module Plugin v21186 [latest-22274]2022-10-09T15:13:55.663Z <TimerBroker:null> Module TimerBroker v22263 [latest-22274]2022-10-09T15:13:55.665Z <default:INFO> Module Entity v22258 [latest-22274]2022-10-09T15:13:55.667Z <Controller:null> Module Controller v22266 [latest-22274]2022-10-09T15:13:55.668Z <default:null> Module Structure v22123 [latest-22274]2022-10-09T15:13:55.675Z <default:null> Module Ruleset v21096 [latest-22274]2022-10-09T15:13:55.675Z <default:null> Module Rulesets v21096 [latest-22274]2022-10-09T15:13:55.680Z <GlobalExpression:null> Module GlobalExpression v21333 [latest-22274]2022-10-09T15:13:55.697Z <Predicate:null> Module Predicate v22271 [latest-22274]2022-10-09T15:13:55.699Z <AlertManager:null> Module AlertManager v22117 [latest-22274]2022-10-09T15:13:55.701Z <default:null> Module Rule v22265 [latest-22274]2022-10-09T15:13:55.704Z <GlobalReaction:null> Module GlobalReaction v21333 [latest-22274]2022-10-09T15:13:55.705Z <default:null> Module Engine v22266 [latest-22274]2022-10-09T15:13:55.705Z <default:null> Module httpapi v22248 [latest-22274]2022-10-09T15:13:55.717Z <default:null> Module wsapi v22104 [latest-22274]2022-10-09T15:13:55.719Z <app:NOTICE> Starting Structure... [latest-22274]2022-10-09T15:13:55.723Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping [latest-22274]2022-10-09T15:13:55.727Z <Structure:INFO> Structure#1 loading controller interface vera (VeraController) [latest-22274]2022-10-09T15:13:55.762Z <TaskQueue:null> Module TaskQueue 21351 [latest-22274]2022-10-09T15:13:55.763Z <VeraController:null> Module VeraController v22258 [latest-22274]2022-10-09T15:13:55.866Z <Structure:INFO> Structure#1 loading controller interface mqqt (MQTTController) [latest-22274]2022-10-09T15:13:55.869Z <MQTTController:null> Module MQTTController v22144 [latest-22274]2022-10-09T15:13:55.930Z <MQTTController:INFO> instance topic ident is mqqt [latest-22274]2022-10-09T15:13:55.933Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController) [latest-22274]2022-10-09T15:13:55.938Z <DynamicGroupController:null> Module DynamicGroupController v22123 [latest-22274]2022-10-09T15:13:55.941Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [latest-22274]2022-10-09T15:13:55.944Z <SystemController:null> Module SystemController v22257 [latest-22274]2022-10-09T15:13:55.946Z <Structure:INFO> Starting controller VeraController#vera [latest-22274]2022-10-09T15:13:55.947Z <VeraController:NOTICE> VeraController#vera starting [latest-22274]2022-10-09T15:13:55.985Z <VeraController:INFO> VeraController#vera loaded mapping ver 22257 rev 3 format 1 notice (none) [latest-22274]2022-10-09T15:13:55.990Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute members [latest-22274]2022-10-09T15:13:55.990Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute empty [latest-22274]2022-10-09T15:13:56.000Z <Structure:INFO> Starting controller MQTTController#mqqt [latest-22274]2022-10-09T15:13:56.001Z <MQTTController:NOTICE> Connecting to broker mqtt://192.168.70.249:8883/ [latest-22274]2022-10-09T15:13:56.036Z <Structure:INFO> Starting controller DynamicGroupController#groups [latest-22274]2022-10-09T15:13:56.041Z <DynamicGroupController:NOTICE> Controller DynamicGroupController#groups is now online. [latest-22274]2022-10-09T15:13:56.041Z <Structure:INFO> Starting controller SystemController#reactor_system [latest-22274]2022-10-09T15:13:56.043Z <SystemController:NOTICE> Controller SystemController#reactor_system is now online. [latest-22274]2022-10-09T15:13:56.081Z <app:NOTICE> Starting HTTP server and API... [latest-22274]2022-10-09T15:13:56.083Z <httpapi:NOTICE> Starting HTTP API v1 22248 on http://192.168.70.2Anyone comment on what I've done wrong?
TIA
C
The Ex-Vera abuser know as CatmanV2.....
-
Trying my damndest to follow the guidelines......
Reactor latest-22274-24dfd72c
Intel NUC Debian BullseyeUsing an online YAML editor I have managed to create a reactor.yaml with an entity that allows Reactor to start (no idea why vi seems to break the yaml)
- id: mqqt enabled: true implementation: MQTTController name: Mosquito config: source: "mqtt://192.168.70.249:8883/" username: xxxx password: xxxx entities: catman_iphone: name: "Catman Phone" topic: FCEB043-B975-490E-B051-198473F6A504 uses_template: owntracks_in_region region: "Home"My expectation is that this would create a binary sensor. I can see no such sensor.
Reactor log:
[latest-22274]2022-10-09T15:13:55.580Z <app:null> Reactor latest-22274-24dfd72c starting on v16.15.0 [latest-22274]2022-10-09T15:13:55.581Z <app:INFO> Process ID 10567; docker false; platform linux/x64 #1 SMP Debian 4.19.235-1 (2022-03-17); locale en_GB.UTF-8 [latest-22274]2022-10-09T15:13:55.581Z <app:INFO> Basedir /home/catman/reactor; data in /home/catman/reactor/storage [latest-22274]2022-10-09T15:13:55.581Z <app:INFO> NODE_PATH=/home/catman/reactor [latest-22274]2022-10-09T15:13:55.583Z <app:INFO> Configured locale (undefined); selected locale(s) en_GB.UTF-8 [latest-22274]2022-10-09T15:13:55.601Z <app:INFO> Loaded locale en-US [latest-22274]2022-10-09T15:13:55.612Z <Capabilities:null> Module Capabilities v22250 [latest-22274]2022-10-09T15:13:55.659Z <Plugin:null> Module Plugin v21186 [latest-22274]2022-10-09T15:13:55.663Z <TimerBroker:null> Module TimerBroker v22263 [latest-22274]2022-10-09T15:13:55.665Z <default:INFO> Module Entity v22258 [latest-22274]2022-10-09T15:13:55.667Z <Controller:null> Module Controller v22266 [latest-22274]2022-10-09T15:13:55.668Z <default:null> Module Structure v22123 [latest-22274]2022-10-09T15:13:55.675Z <default:null> Module Ruleset v21096 [latest-22274]2022-10-09T15:13:55.675Z <default:null> Module Rulesets v21096 [latest-22274]2022-10-09T15:13:55.680Z <GlobalExpression:null> Module GlobalExpression v21333 [latest-22274]2022-10-09T15:13:55.697Z <Predicate:null> Module Predicate v22271 [latest-22274]2022-10-09T15:13:55.699Z <AlertManager:null> Module AlertManager v22117 [latest-22274]2022-10-09T15:13:55.701Z <default:null> Module Rule v22265 [latest-22274]2022-10-09T15:13:55.704Z <GlobalReaction:null> Module GlobalReaction v21333 [latest-22274]2022-10-09T15:13:55.705Z <default:null> Module Engine v22266 [latest-22274]2022-10-09T15:13:55.705Z <default:null> Module httpapi v22248 [latest-22274]2022-10-09T15:13:55.717Z <default:null> Module wsapi v22104 [latest-22274]2022-10-09T15:13:55.719Z <app:NOTICE> Starting Structure... [latest-22274]2022-10-09T15:13:55.723Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping [latest-22274]2022-10-09T15:13:55.727Z <Structure:INFO> Structure#1 loading controller interface vera (VeraController) [latest-22274]2022-10-09T15:13:55.762Z <TaskQueue:null> Module TaskQueue 21351 [latest-22274]2022-10-09T15:13:55.763Z <VeraController:null> Module VeraController v22258 [latest-22274]2022-10-09T15:13:55.866Z <Structure:INFO> Structure#1 loading controller interface mqqt (MQTTController) [latest-22274]2022-10-09T15:13:55.869Z <MQTTController:null> Module MQTTController v22144 [latest-22274]2022-10-09T15:13:55.930Z <MQTTController:INFO> instance topic ident is mqqt [latest-22274]2022-10-09T15:13:55.933Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController) [latest-22274]2022-10-09T15:13:55.938Z <DynamicGroupController:null> Module DynamicGroupController v22123 [latest-22274]2022-10-09T15:13:55.941Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [latest-22274]2022-10-09T15:13:55.944Z <SystemController:null> Module SystemController v22257 [latest-22274]2022-10-09T15:13:55.946Z <Structure:INFO> Starting controller VeraController#vera [latest-22274]2022-10-09T15:13:55.947Z <VeraController:NOTICE> VeraController#vera starting [latest-22274]2022-10-09T15:13:55.985Z <VeraController:INFO> VeraController#vera loaded mapping ver 22257 rev 3 format 1 notice (none) [latest-22274]2022-10-09T15:13:55.990Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute members [latest-22274]2022-10-09T15:13:55.990Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute empty [latest-22274]2022-10-09T15:13:56.000Z <Structure:INFO> Starting controller MQTTController#mqqt [latest-22274]2022-10-09T15:13:56.001Z <MQTTController:NOTICE> Connecting to broker mqtt://192.168.70.249:8883/ [latest-22274]2022-10-09T15:13:56.036Z <Structure:INFO> Starting controller DynamicGroupController#groups [latest-22274]2022-10-09T15:13:56.041Z <DynamicGroupController:NOTICE> Controller DynamicGroupController#groups is now online. [latest-22274]2022-10-09T15:13:56.041Z <Structure:INFO> Starting controller SystemController#reactor_system [latest-22274]2022-10-09T15:13:56.043Z <SystemController:NOTICE> Controller SystemController#reactor_system is now online. [latest-22274]2022-10-09T15:13:56.081Z <app:NOTICE> Starting HTTP server and API... [latest-22274]2022-10-09T15:13:56.083Z <httpapi:NOTICE> Starting HTTP API v1 22248 on http://192.168.70.2Anyone comment on what I've done wrong?
TIA
C
@catmanv2 said in Entity is not visible:
Trying my damndest to follow the guidelines
This is a solid performance.
no idea why vi seems to break the yaml
If i had to guess, you're indenting with tabs rather than spaces. That would be the first thing I'd look at. No tabs allowed.
My expectation is that this would create a binary sensor. I can see no such sensor
Easy, at least at the first level: your
entitiessection is at the same indent level asconfig. Theentitiessection is part ofconfig, so it should be indented underneath it.entities:and all of the lines that follow as part of it should be indented two more spaces. As you have it, MQTTController can't even see that section, and that would explain why you're not getting an entity created.Should be:
- id: mqqt enabled: true implementation: MQTTController name: Mosquito config: source: "mqtt://192.168.70.249:8883/" username: xxxx password: xxxx entities: catman_iphone: ...Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@catmanv2 said in Entity is not visible:
Trying my damndest to follow the guidelines
This is a solid performance.
no idea why vi seems to break the yaml
If i had to guess, you're indenting with tabs rather than spaces. That would be the first thing I'd look at. No tabs allowed.
My expectation is that this would create a binary sensor. I can see no such sensor
Easy, at least at the first level: your
entitiessection is at the same indent level asconfig. Theentitiessection is part ofconfig, so it should be indented underneath it.entities:and all of the lines that follow as part of it should be indented two more spaces. As you have it, MQTTController can't even see that section, and that would explain why you're not getting an entity created.Should be:
- id: mqqt enabled: true implementation: MQTTController name: Mosquito config: source: "mqtt://192.168.70.249:8883/" username: xxxx password: xxxx entities: catman_iphone: ...@toggledbits said in Entity is not visible:
If i had to guess, you're indenting with tabs rather than spaces. That would be the first thing I'd look at. No tabs allowed.
Thanks. I promise I'm not not but I'll just do it in a browser for now
- id: mqqt enabled: true implementation: MQTTController name: Mosquito config: source: "mqtt://192.168.70.249:8883/" username: xxxx password: xxxx entities: catman_iphone: name: "Catman Phone" topic: catmaniphone uses_template: owntracks_in_region region: "Home"Everything starts fine. I've hard refreshed the browser.
Still can't find any entity in either the entities screen or if I try to use 'it' in a rule.
Clearly I've still done something idiotic, and there's an error in here, but damned if I know what it means?
[latest-22274]2022-10-09T17:45:15.492Z <Structure:INFO> Starting controller MQTTController#mqqt [latest-22274]2022-10-09T17:45:15.493Z <Structure:INFO> Starting controller DynamicGroupController#groups [latest-22274]2022-10-09T17:45:15.496Z <DynamicGroupController:NOTICE> Controller DynamicGroupController#groups is now online. [latest-22274]2022-10-09T17:45:15.496Z <Structure:INFO> Starting controller SystemController#reactor_system [latest-22274]2022-10-09T17:45:15.498Z <SystemController:NOTICE> Controller SystemController#reactor_system is now online. [latest-22274]2022-10-09T17:45:15.538Z <Structure:ERR> Structure#1 controller mqqt failed to start: [TypeError]TypeError: Cannot read properties of null (reading 'uses_template') [latest-22274]2022-10-09T17:45:15.538Z <Structure:CRIT> TypeError: Cannot read properties of null (reading 'uses_template') TypeError: Cannot read properties of null (reading 'uses_template') at MQTTController.start (/home/catman/reactor/ext/MQTTController/MQTTController.js:73:21) at Structure.start (/home/catman/reactor/server/lib/Structure.js:346:56) [latest-22274]2022-10-09T17:45:15.538Z <MQTTController:NOTICE> MQTTController#mqqt stopping, sending LWT [latest-22274]2022-10-09T17:45:15.539Z <MQTTController:NOTICE> MQTTController#mqqt stopping [latest-22274]2022-10-09T17:45:15.540Z <app:NOTICE> Starting HTTP server and API... [latest-22274]2022-10-09T17:45:15.542Z <httpapi:NOTICE> Starting HTTP API v1 22248 on http://192.168.70.249:8111 [latest-22274]2022-10-09T17:45:15.545Z <app:NOTICE> Starting Reaction Engine... [latest-22274]2022-10-09T17:45:15.545Z <Engine:INFO> Reaction Engine startingCheers
<edit> per the other thread I've also edited the DeviceID to catmaniphone on the phone and in the reactor.yaml. The log remains the same.
C
-
OK. I just noticed one more error... if I had included more sample data in my last example to you, I would have noticed it earlier...
All together now...
entities:must be indented two spaces fromconfig:(as per my last post), but also everything aftercatman_iphone:should be indented two spaces from that...- id: mqqt enabled: true implementation: MQTTController name: Mosquito config: source: "mqtt://192.168.70.249:8883/" username: xxxx password: xxxx entities: catman_iphone: name: "Catman Phone" topic: catmaniphone uses_template: owntracks_in_region region: "Home"General rule of thumb... if the
:is the last character on the line, everything below it will need to be indented. -
I shall try to remember, thanks!
So I have this:
- id: mqqt enabled: true implementation: MQTTController name: Mosquito config: source: "mqtt://192.168.70.249:8883/" username: xxxxx password: xxxxx entities: catman_iphone: name: "Catman Phone" topic: catmaniphone uses_template: owntracks_in_region region: "Home2"And in the logs:
[latest-22274]2022-10-09T20:45:55.083Z <app:null> Reactor latest-22274-24dfd72c starting on v16.15.0 [latest-22274]2022-10-09T20:45:55.084Z <app:INFO> Process ID 24110; docker false; platform linux/x64 #1 SMP Debian 4.19.235-1 (2022-03-17); locale en_GB.UTF-8 [latest-22274]2022-10-09T20:45:55.084Z <app:INFO> Basedir /home/catman/reactor; data in /home/catman/reactor/storage [latest-22274]2022-10-09T20:45:55.084Z <app:INFO> NODE_PATH=/home/catman/reactor [latest-22274]2022-10-09T20:45:55.086Z <app:INFO> Configured locale (undefined); selected locale(s) en_GB.UTF-8 [latest-22274]2022-10-09T20:45:55.105Z <app:INFO> Loaded locale en-US [latest-22274]2022-10-09T20:45:55.113Z <Capabilities:null> Module Capabilities v22250 [latest-22274]2022-10-09T20:45:55.160Z <Plugin:null> Module Plugin v21186 [latest-22274]2022-10-09T20:45:55.164Z <TimerBroker:null> Module TimerBroker v22263 [latest-22274]2022-10-09T20:45:55.166Z <default:INFO> Module Entity v22258 [latest-22274]2022-10-09T20:45:55.168Z <Controller:null> Module Controller v22266 [latest-22274]2022-10-09T20:45:55.169Z <default:null> Module Structure v22123 [latest-22274]2022-10-09T20:45:55.176Z <default:null> Module Ruleset v21096 [latest-22274]2022-10-09T20:45:55.176Z <default:null> Module Rulesets v21096 [latest-22274]2022-10-09T20:45:55.181Z <GlobalExpression:null> Module GlobalExpression v21333 [latest-22274]2022-10-09T20:45:55.194Z <Predicate:null> Module Predicate v22271 [latest-22274]2022-10-09T20:45:55.197Z <AlertManager:null> Module AlertManager v22117 [latest-22274]2022-10-09T20:45:55.198Z <default:null> Module Rule v22265 [latest-22274]2022-10-09T20:45:55.201Z <GlobalReaction:null> Module GlobalReaction v21333 [latest-22274]2022-10-09T20:45:55.202Z <default:null> Module Engine v22266 [latest-22274]2022-10-09T20:45:55.202Z <default:null> Module httpapi v22248 [latest-22274]2022-10-09T20:45:55.214Z <default:null> Module wsapi v22104 [latest-22274]2022-10-09T20:45:55.215Z <app:NOTICE> Starting Structure... [latest-22274]2022-10-09T20:45:55.218Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping [latest-22274]2022-10-09T20:45:55.221Z <Structure:INFO> Structure#1 loading controller interface vera (VeraController) [latest-22274]2022-10-09T20:45:55.258Z <TaskQueue:null> Module TaskQueue 21351 [latest-22274]2022-10-09T20:45:55.259Z <VeraController:null> Module VeraController v22258 [latest-22274]2022-10-09T20:45:55.362Z <Structure:INFO> Structure#1 loading controller interface mqqt (MQTTController) [latest-22274]2022-10-09T20:45:55.366Z <MQTTController:null> Module MQTTController v22144 [latest-22274]2022-10-09T20:45:55.422Z <MQTTController:INFO> instance topic ident is mqqt [latest-22274]2022-10-09T20:45:55.425Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController) [latest-22274]2022-10-09T20:45:55.429Z <DynamicGroupController:null> Module DynamicGroupController v22123 [latest-22274]2022-10-09T20:45:55.432Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [latest-22274]2022-10-09T20:45:55.435Z <SystemController:null> Module SystemController v22257 [latest-22274]2022-10-09T20:45:55.438Z <Structure:INFO> Starting controller VeraController#vera [latest-22274]2022-10-09T20:45:55.438Z <VeraController:NOTICE> VeraController#vera starting [latest-22274]2022-10-09T20:45:55.477Z <VeraController:INFO> VeraController#vera loaded mapping ver 22257 rev 3 format 1 notice (none) [latest-22274]2022-10-09T20:45:55.482Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute members [latest-22274]2022-10-09T20:45:55.482Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute empty [latest-22274]2022-10-09T20:45:55.492Z <Structure:INFO> Starting controller MQTTController#mqqt [latest-22274]2022-10-09T20:45:55.492Z <MQTTController:ERR> MQTTController#mqqt entity catman_iphone uses_template=owntracks_in_region, template not defined [latest-22274]2022-10-09T20:45:55.493Z <MQTTController:NOTICE> Connecting to broker mqtt://192.168.70.249:8883/ [latest-22274]2022-10-09T20:45:55.527Z <Structure:INFO> Starting controller DynamicGroupController#groups [latest-22274]2022-10-09T20:45:55.533Z <DynamicGroupController:NOTICE> Controller DynamicGroupController#groups is now online. [latest-22274]2022-10-09T20:45:55.533Z <Structure:INFO> Starting controller SystemController#reactor_system [latest-22274]2022-10-09T20:45:55.535Z <SystemController:NOTICE> Controller SystemController#reactor_system is now online. [latest-22274]2022-10-09T20:45:55.574Z <app:NOTICE> Starting HTTP server and API... [latest-22274]2022-10-09T20:45:55.576Z <httpapi:NOTICE> Starting HTTP API v1 22248 on http://192.168.70.249:8111 [latest-22274]2022-10-09T20:45:55.579Z <app:NOTICE> Starting Reaction Engine... [latest-22274]2022-10-09T20:45:55.579Z <Engine:INFO> Reaction Engine startingStill no device. Thanks
C
-
You need at least version 22260 of MQTTController
-
T toggledbits locked this topic on
