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.
CrilleC

Crille

@Crille
Next Release?
CatmanV2C
Morning. Do we have a roadmap for the next release, at all? I only ask as there's a breaking HA change and I have many packages now out of date. Cheers! C
Multi-System Reactor
Controller Z-Wave JS UI: "Location" attribute not visible in Reactor entities
N
Hi, I'm on Docker/NAs (latest-26011-c621bbc7) with Zwave js ui (last version). I have set the 'Location' for each device in the Z-Wave JS UI dashboard, I cannot find this information among the Entity Attributes in the Reactor. I tried and the result is an empty array []. It seems the 'Location' metadata from Z-Wave JS is not being mapped to a standard attribute in Reactor. Location is equale to Rooms for me. When comparing this to the Vera or Ezlo Controller, Reactor automatically creates Room Icons also in the Reactor Dashboard and places the various devices under those room categories. This is a very convenient way to keep the dashboard organized and quickly find lights to turn off with a click (especially when something isn't switched off as expected for me:) ). Is there a way to map the Z-Wave JS UI 'Location' attribute and a dashboard organization, just like it does with Vera/Ezlo? Thanks in advance for all the great tips you've shared
Multi-System Reactor
Do you Matter?
akbooerA
Is anyone using the Matter protocol to connect devices?
General Discussion
Variables not updating properly
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
VEC Virtual Switch Auto Off
S
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules. I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds). Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off? With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches. Thanks Reactor (Multi-hub) latest-26011-c621bbc7 VirtualEntityController v25356 Synology Docker
Multi-System Reactor
Changes operator does not always detect change
tunnusT
I've had similar problems before, but now this issue has resurfaced. Using build 26011 on Docker. As I copied one old rule as a "template" for a similar new rule, where I have multiple conditions using changes operator (from any to any, and with delay reset of 900), these conditions do not detect change in attributes. Even if I manually reset the rule, reset delay timers do not restart. If I do a new rule from scratch, and do not copy/import anything old, the same conditions work properly. Also, if I modify copied rule's conditions (put a random number to "from" & "to" fields), then save, and after that remove those modifications, rule begins to function normally. Just editing e.g. delay reset value does not do any good in this context. @toggledbits, I can DM logs & related rule files to you, if you just send me instructions.
Multi-System Reactor
Dynamic MQTT topics and parameters
M
Topic thumbnail image
Multi-System Reactor
Condition for trend
T
Topic thumbnail image
Multi-System Reactor
Struggling to setup my first Tasmota device and MQTT
cw-kidC
Topic thumbnail image
Multi-System Reactor
Raspberry Pi 4 dual RAM variant introduced to mitigate RAM price increases
toggledbitsT
Article here that may be of interest to some: https://www.cnx-software.com/2026/02/05/raspberry-pi-4-dual-ram-variant-introduced-to-mitigate-ram-price-increases-and-supply-challenges/
SBC
Existing Rule stopped working HTTP command fetching IP address from website
cw-kidC
Topic thumbnail image
Multi-System Reactor
Set reaction triggering wrong z-wave device
T
Topic thumbnail image
Multi-System Reactor
Can you run MSR on Home Assistant OS ?
cw-kidC
Looking at using Home Assistant for the first time, either on a Home Assistant Green, their own hardware or buying a cheap second hand mini PC. Sounds like Home Assistant OS is linux based using Docker for HA etc. Would I also be able to install things like MSR as well on their OS ? On the same box? Thanks.
Multi-System Reactor
RPi Alternative: Orange Pi 4 LTS (3GB RAM/16GB eMMC)
toggledbitsT
The last of four boards I'm trying in this batch is the Orange Pi 4 LTS. I purchased a 3GB RAM + 16GB eMMC model from Amazon for $83, making it the most costly of the four boards tried, but still well under my US$100 limit. This board is powered by a Rockchip RK3399-T processor, ARM-compatible with dual Cortex-A72 cores and quad Cortex-A53 cores at 1.6Ghz (1.8Ghz for the 4GB model); compare this to the RPi 3B+ with four Cortex-A53 and the RPi 4B with four Cortex-A72, this board is a hybrid that I would expect to stand in the performance middle between the two RPi models. It's available in 3GB and 4GB DDR4 RAM configurations, with and without 16GB eMMC storage. It has a MicroSDHC slot, gigabit Ethernet, WiFi and BT, two USB 2.0 type A ports, one USB 3.0 type C port, a mini PCIe ribbon-cable connector (requires add-on board for standard connector), two each RPi-compatible camera and LCD ports, HDMI type A, and can be powered (5VDC/3A) via USB-C or DC type C (3.8mm OD/1.1mm ID) jack (center-positive), an odd and perhaps unwelcome departure from the more common type A (5.5mm/2.1mm). A serial port for console/debug can be connected by using a (not included) USB-TTL adapter (3.3V) via pin headers like the Orange Pi Zero 2. The included dual-band antenna connects via U.FL connector to the board, so it's easy substituting for another if you prefer. The manufacturer recommends use of a heat sink (which was included in the box). A metal cooling case is also offered by the manufacturer (a bundle with the metal case and a power supply is sold on Amazon for $90 as of this writing). The Orange Pi 4 LTS is somewhat longer than the RPi 4B, and although the boards are the same width, the mounting hole placement is different both in length and (oddly) width. Between this and the differences in connector locations, neither board is a drop-in replacecment for the other and their respective cases are not interchangeable. The 26-pin header is a subset of the RPi 4B's 40-pin header, so some HATs for the RPi may work (although the mounting hole differences will make securing them "interesting"), and some HATs will surely not. Models with eMMC storage have an OS installed and boot immediately with SSH daemon running and ready for login. Mine was running Debian Bullseye, which would probably be fine for most users. It had clearly been on there a while, because it needed a lot of updates, but it's a current distro, so you're running out of the box with something that will last. A different OS can be installed by downloading an image (once again I chose Ubuntu Jammy) and writing it to a MicroSD card, then booting the system from the SD card. You can either leave the system in that state (running the OS from the SD card), or copy the OS from the SD card to the eMMC. The latter is done by a script; documentation for the process is best described in the downloadable PDF User Manual. This took about 10 minutes and went smoothly, and I was able to boot the system without the SD card after the process completed. I have lingering questions around the value of the eMMC storage. It's definitely faster than using MicroSD or USB-based storage (I got 311MB/s average on a 4GB write, compared to MicroSD performance around 15MB/s), but it would take a long-term test of this product to determine if the on-board eMMC option has the stamina to take the write counts typical of Linux systems, and if its wear-leveling and error correction are sufficient to assure a long, error-free life. Given the high premium apparently being paid for including eMMC on the board, it should be fast and durable, but only time and experience (perhaps painful) would tell the latter. A careful configuration with other Flash-friendly filesystems could be used to reduce wear, but this is an advanced configuration/cookbook topic and beyond the scope of this writing. This question is also not unique to eMMC — MicroSD cards are also known to fail with high write cycles, so the use of a "high endurance" product is recommended for any and all systems using MicroSD as primary storage. The board has Mini PCIe capability, and that may be a storage alternative, but read on... Also bear in mind that the eMMC storage is fixed-size forever; it cannot be expanded, and 16GB can run out pretty quickly these days. Users of MicroSD cards for primary storage can upgrade to bigger cards, but when users of eMMC primary storage outgrow it, the only choice is to add a MicroSD card or other "external" storage to the system, move part of the filesystem to it, and then manage both storage devices and deal with the limitations and risks of both. As I mentioned with the Orange Pi Zero 2, if you are going to use this board as a home automation controller/gateway or similar role, it should (IMO) have a battery-backed real time clock (RTC), and Orange Pi offers an add-on module that connects directly to the 26-pin header on the board. An available expansion board provides a standard Mini PCIe interface and SIM card slot (hmm...), but it connects to the main board via a short ribbon cable, and its mounting holes have no complement on the main board, so it seems like it would be a fragile dangly thing that's a nuisance to deal with. I want to like this board more, and it's very capable, but I'm concerned about value. The limited options for eMMC (16GB or none), the question mark of the eMMC's longevity vs cost, the strange DC power connector choice, the lack of 40-pin GPIO on a full-size (plus) board, the inconsistent hole placement, and the fragile Mini PCIe arrangement, are all "cons" that devalue this board in my view. The price point is clearly driven by the additional capabilities of the board (camera support, ports, six core CPU, extra RAM, on-board eMMC storage), but unfortunately, a great many of these features may not be useful for home automation, and therefore potentially a waste of money. In terms of overall value, I still believe the Libre "Le Potato" seems a better choice to me, and the Orange Pi Zero 2 (very) a close second, but I'll admit I'm focused on a particular application and your needs may be better suited to what this board offers than mine. Passmark Results: OrangePi 4 LTS Cortex-A72 (aarch64) 6 cores @ 1200 MHz | 2.9 GiB RAM Number of Processes: 6 | Test Iterations: 1 | Test Duration: Medium -------------------------------------------------------------------------- CPU Mark: 583 Integer Math 12037 Million Operations/s Floating Point Math 2542 Million Operations/s Prime Numbers 4.5 Million Primes/s Sorting 3141 Thousand Strings/s Encryption 153 MB/s Compression 4049 KB/s CPU Single Threaded 154 Million Operations/s Physics 80.5 Frames/s Extended Instructions (NEON) 244 Million Matrices/s Memory Mark: 498 Database Operations 551 Thousand Operations/s Memory Read Cached 2524 MB/s Memory Read Uncached 2602 MB/s Memory Write 3182 MB/s Available RAM 1947 Megabytes Memory Latency 119 Nanoseconds Memory Threaded 6243 MB/s --------------- eMMC storage write 311MB/s average for 4GB; MicroSD (Samsung 32GB class 10) storage write 15MB/s.
SBC
RPi Alternative: Orange Pi Zero 2 (1GB)
toggledbitsT
Topic thumbnail image
SBC
RPi Alternative: Libre Computer AML-S905X-CC "Le Potato" (2GB RAM)
toggledbitsT
With Raspberry Pi boards continuing to be relatively scarce, I've been trying a few alternatives to see what may be usable and good. I had previously written about the Jetson Nano 2GB, which is great, but a little pricey, so I'm trying to find sub-US$100 boards that will run Reactor. I've got four that I'm trying now, but one in particular goes right to work in the most predictable way and seems worth a mention immediately: the Libre Computer Board AML-S905X-CC 2GB (known as "Le Potato"). The form factor is very similar to that of the Raspberry Pi 3 B+, and has comparable CPU (ARM Cortex-A53, quad 64-bit cores at 1.5+GHz -- slightly higher clock speed). It's US$35 on Amazon and LoverPi in the (recommended) 2GB configuration, and easy to get. Startup is like RPi: download one of the available OS images (Ubuntu, Raspbian, Debian, ARMbian, etc.) from their site and write the image to a MicroSD card, insert into slot, power up, and off you go. I tried the Ubuntu 22.04 image first and it comes right up. No problem getting nodejs 18.12.1 installed and running (with Reactor). No WiFi on board, but I don't see that as a minus for use as a controller/hub (which should be hard-wired, IMO). The 40-pin GPIO connector is compatible with typical RPi HATs (PoE, breakouts, etc.). There is an available eMMC (solid state storage) module to use instead of MicroSD, which I would recommend for long-term use. It runs US$25 for 32GB (64GB and 128GB available). The module is scarcely larger than the chip it carries, and has the smallest board-to-board connector I've ever seen. Next up: ESPRESSObin 2GB (spoiler: it's... technical...)
SBC
HA and AI
CatmanV2C
Having hours of (actually quite fun) interaction with AI (Chat GPT) making up dashboards and sensors for HA. It's OK (well it's better than I am!) but it makes soooo many mistakes. Gets there in the end though, if you've half a clue (which I do half the time) C
Home Assistant
How to upgrade from an old version of MSR?
cw-kidC
Hello I haven't updated my installation of MSR in a very long time. Its a bare metal Linux install currently on version 24366-3de60836 I see the latest version is now latest-26011-c621bbc7 I assume I cannot just jump from a very old version to the latest version? Or can I? Thanks
Multi-System Reactor
This trigger no longer working - complaining about the operator needing changing
cw-kidC
Topic thumbnail image
Multi-System Reactor
About
Posts
354
Topics
39
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial
  • Do you Matter?
    CrilleC Crille

    Speaking of Matter and older Shelly (Gen 1 & 2) I found Matterbridge, very similar to Homebridge, paired it to Apple Home and installed matterbridge-shelly and as easy as that all my devices showed up in the Home app. Might be something for you @akbooer .
    Matterbridge offer other plugins like Zigbee2MQTT, Home Assistant and more, this makes me start thinking of moving away from Homebridge (and some MQTT) to Matterbridge and Matter, especially if a MatterController is eventually in the making.

    Because I'm Swedish IKEA is very close by and super cheap on "Matter over Thread" devices and my HomePod mini act as a Thread Border Router, I can say Matter starts to grow on me 🙂

    General Discussion
  • Do you Matter?
    CrilleC Crille

    I bought a new Sonoff device (ESP32) and flashed it with Tasmota v.15.3.0 and discovered it was possible to enable Matter (actually implemented in v.13.0).
    Tested it and as you say it was a very easy configuration. Having other thoughts about Matter now as there is no need for MQTT configuration in Homebridge, makes it a little bit smoother to add new devices.
    I still need to configure MQTT so Reactor picks it up though, @toggledbits any considerations of a MatterController?

    General Discussion
  • How to upgrade from an old version of MSR?
    CrilleC Crille

    For Zigbee I have an older Sonoff 3.0 USB Dongle Plus and Zigbee2MQTT running rock solid but if I were to replace it I would go for the Sonoff Dongle Max, looks pretty impressive and can be placed wherever there’s an ethernet port (or WiFi).

    Multi-System Reactor
  • [Solved] function isRuleEnabled() issue
    CrilleC Crille

    Never mind. I found the issue, this works as expected isRuleEnabled('rule-mj4xiyr8') where the rule id needs to be quoted with ' or ".
    Not obvious in the docs, my bad for not testing that first.

    Multi-System Reactor
  • [Solved] function isRuleEnabled() issue
    CrilleC Crille

    Wow, those were in fact really bad! Sorry for that.
    Rule id rule-mj4xiyr8 is in this case Enabled
    Rule expression:
    rule_expr.PNG Global expression:
    expr.PNG

    Multi-System Reactor
  • [Solved] function isRuleEnabled() issue
    CrilleC Crille

    Edit: Rule id needs to be quoted, e.g. isRuleEnabled( 'rule_id' )

    Bare metal 25325.

    I'm getting null in both global and local expressions for the function isRuleEnabled(). It doesn't matter if the rule is enabled or disabled. Let me know if you can't replicate and need logs at higher level or I'm doing something wrong.

    rule_expression.PNG expression.PNG

    
[latest-25325]2026-01-12T14:15:04.773Z <Rule:INFO> Laddning - Lastbalansering (rule-lj5kfvi6 in Funktioner) starting rule state evaluation; because timer-trigger Timer#rule-lj5kfvi6
[latest-25325]2026-01-12T14:15:07.348Z <Rule:NOTICE> rule-mkb8uytt (rule-mkb8uytt in Funktioner) configuration changed; reloading
[latest-25325]2026-01-12T14:15:07.349Z <Engine:INFO> Engine#1 rule Rule#rule-mkb8uytt changed; reloading and restarting it
[latest-25325]2026-01-12T14:15:07.349Z <Rule:NOTICE> rule-mkb8uytt (rule-mkb8uytt in Funktioner) stopping
[latest-25325]2026-01-12T14:15:07.350Z <Rule:NOTICE> rule-mkb8uytt (rule-mkb8uytt in Funktioner) stopped
[latest-25325]2026-01-12T14:15:07.350Z <Rule:NOTICE> rule-mkb8uytt (rule-mkb8uytt in Funktioner) starting
[latest-25325]2026-01-12T14:15:07.350Z <Rule:NOTICE> rule-mkb8uytt (rule-mkb8uytt in Funktioner) can't start -- rule is disabled
[latest-25325]2026-01-12T14:15:09.589Z <Rule:INFO> Ljusstyrka - Baksida (rule-kz3ygi32 in Ljusstyrka) starting rule state evaluation; because entity-changed Entity#mosquitto-mqtt>baksida
[latest-25325]2026-01-12T14:15:09.772Z <Rule:INFO> Laddning - Lastbalansering (rule-lj5kfvi6 in Funktioner) starting rule state evaluation; because expression-state-changed GlobalExpression#chargeAmps
[latest-25325]2026-01-12T14:15:09.773Z <Rule:INFO> Laddning - Återstarta om stoppad av lastbalansering (rule-m3yhrbvs in Funktioner) starting rule state evaluation; because expression-state-changed GlobalExpression#chargeAmps
[latest-25325]2026-01-12T14:15:09.787Z <Rule:INFO> Laddning - Lastbalansering (rule-lj5kfvi6 in Funktioner) starting rule state evaluation; because timer-trigger Timer#rule-lj5kfvi6
[latest-25325]2026-01-12T14:15:10.024Z <Rule:INFO> Laddning - Ladda bil (rule-mgb4e7bl in Funktioner) starting rule state evaluation; because timer-trigger Timer#rule-mgb4e7bl
[latest-25325]2026-01-12T14:15:10.025Z <Rule:INFO> Rule#rule-mgb4e7bl local values has_local_deps false has_object_deps true need_eval false
[latest-25325]2026-01-12T14:15:10.025Z <Rule:INFO> Rule#rule-mgb4e7bl local title has_local_deps false has_object_deps true need_eval false
[latest-25325]2026-01-12T14:15:10.025Z <Rule:INFO> Rule#rule-mgb4e7bl local text has_local_deps false has_object_deps true need_eval false
[latest-25325]2026-01-12T14:15:10.025Z <Rule:INFO> Rule#rule-mgb4e7bl local chargingTime has_local_deps true has_object_deps false need_eval true
[latest-25325]2026-01-12T14:15:10.025Z <Rule:INFO> Rule#rule-mgb4e7bl evaluating eligible local chargingTime
[latest-25325]2026-01-12T14:15:10.025Z <Rule:INFO> Rule#rule-mgb4e7bl local currentValues has_local_deps true has_object_deps false need_eval true
[latest-25325]2026-01-12T14:15:10.025Z <Rule:INFO> Rule#rule-mgb4e7bl evaluating eligible local currentValues
[latest-25325]2026-01-12T14:15:10.746Z <Rule:INFO> Ljusstyrka - Badrummet (rule-m23jno54 in Ljusstyrka) starting rule state evaluation; because entity-changed Entity#mosquitto-mqtt>badrummet
[latest-25325]2026-01-12T14:15:10.983Z <Rule:NOTICE> rule-mkb8uytt (rule-mkb8uytt in Funktioner) configuration changed; reloading
[latest-25325]2026-01-12T14:15:10.984Z <Engine:INFO> Engine#1 rule Rule#rule-mkb8uytt changed; reloading and restarting it
[latest-25325]2026-01-12T14:15:10.984Z <Rule:NOTICE> rule-mkb8uytt (rule-mkb8uytt in Funktioner) stopping
[latest-25325]2026-01-12T14:15:10.985Z <Rule:NOTICE> rule-mkb8uytt (rule-mkb8uytt in Funktioner) stopped
[latest-25325]2026-01-12T14:15:10.985Z <Rule:NOTICE> rule-mkb8uytt (rule-mkb8uytt in Funktioner) starting
[latest-25325]2026-01-12T14:15:10.986Z <Rule:INFO> rule-mkb8uytt (rule-mkb8uytt in Funktioner) starting rule state evaluation; because startup
[latest-25325]2026-01-12T14:15:10.986Z <Rule:INFO> Rule#rule-mkb8uytt initializing expressions: stage one - compile and dependency scan
[latest-25325]2026-01-12T14:15:10.987Z <Rule:INFO> Rule#rule-mkb8uytt initializing expressions: stage two - topological sort
[latest-25325]2026-01-12T14:15:10.987Z <Rule:INFO> Rule#rule-mkb8uytt initializing expressions: stage three - startup evaluation
[latest-25325]2026-01-12T14:15:10.987Z <Rule:INFO> Rule#rule-mkb8uytt evaluating eligible local test
[latest-25325]2026-01-12T14:15:10.989Z <Rule:INFO> rule-mkb8uytt (rule-mkb8uytt in Funktioner) started
[latest-25325]2026-01-12T14:15:14.787Z <Rule:INFO> Laddning - Lastbalansering (rule-lj5kfvi6 in Funktioner) starting rule state evaluation; because timer-trigger Timer#rule-lj5kfvi6
[latest-25325]2026-01-12T14:15:15.026Z <Rule:INFO> Varmvattenberedare (rule-mgffrozr in Funktioner) starting rule state evaluation; because timer-trigger Timer#rule-mgffrozr
    Multi-System Reactor
  • Logic Assistance: Exterior Lights on when Illuminance Below Threshold
    CrilleC Crille

    @CatmanV2 This is from my hallway and the sensor is placed near a light source so the level goes up when lights are on. This is to handle cloudy days and the hallway is a bit dark and needs artificial light but when the sun finds its way in, the lights turn off.

    Multi-System Reactor
  • Logic Assistance: Exterior Lights on when Illuminance Below Threshold
    CrilleC Crille

    I have a local variable as trigger for cases like this. When lightsOn is true the rule sets.
    lightsOn =

    do
lux = getEntity( "mosquitto-mqtt>rorelse_hallen" ).attributes.light_sensor.value,
lights = getEntity( "mosquitto-mqtt>hallen1" ).attributes.power_switch.state,
case
 when lux <= 17 : bool(true)
 when lights and lux >= 18 and lux <= 25 : bool(true)
 else bool(false)
end
done
    Multi-System Reactor
  • MQTT templates for ZIgbee scene controller, or a better way?
    CrilleC Crille

    You may take a look at the Reactor docs for Handling Home Assistant Events or build/modify your own MQTT template where you need to map all published actions to standard actions e.g. 1_single to single.

    Multi-System Reactor
  • [Solved] Local expression in Rule does not evaluate as they used to do
    CrilleC Crille

    Super, it now behaves as expected. Once again thank you!

    Multi-System Reactor
  • [Solved] Local expression in Rule does not evaluate as they used to do
    CrilleC Crille

    No change after restart, files uploaded.

    Multi-System Reactor
  • [Solved] Local expression in Rule does not evaluate as they used to do
    CrilleC Crille

    Edit: Solved in 25323.

    I experience some issues since local expressions changed behavior in some previous build.

    I've set up a test rule to verify my suspicions.
    local_expressions.PNG Previously this worked, when Reactor uptime changed all local expressions were evaluated but now only timeNow is updated and triggerNow does not change (even though it is dependent on timeNow), so the Rule never sets.
    I can work around the issue by getEntity(...uptime) in triggerNow, then the expression is evaluated and changes to true and the rule sets.

    Log from different test time:

    [latest-25321]2025-11-18T14:16:44.026Z <Rule:INFO> TEST - time in expression as trigger (rule-mi4ldhta in Funktioner) started
[latest-25321]2025-11-18T14:17:33.345Z <Rule:INFO> TEST - time in expression as trigger (rule-mi4ldhta in Funktioner) starting rule state evaluation; because entity-changed System#reactor_system>system
[latest-25321]2025-11-18T14:17:33.345Z <Rule:INFO> Rule#rule-mi4ldhta local triggerNow is a dependency of another variable
[latest-25321]2025-11-18T14:17:33.348Z <Rule:INFO> TEST - time in expression as trigger (rule-mi4ldhta in Funktioner) starting rule state evaluation; because entity-changed System#reactor_system>system
[latest-25321]2025-11-18T14:17:33.348Z <Rule:INFO> Rule#rule-mi4ldhta local triggerNow is a dependency of another variable
[latest-25321]2025-11-18T14:17:33.350Z <Rule:INFO> TEST - time in expression as trigger (rule-mi4ldhta in Funktioner) starting rule state evaluation; because entity-changed System#reactor_system>system
[latest-25321]2025-11-18T14:17:33.350Z <Rule:INFO> Rule#rule-mi4ldhta local triggerNow is a dependency of another variable
[latest-25321]2025-11-18T14:17:33.354Z <Rule:INFO> TEST - time in expression as trigger (rule-mi4ldhta in Funktioner) starting rule state evaluation; because entity-changed System#reactor_system>system
[latest-25321]2025-11-18T14:17:33.355Z <Rule:INFO> Rule#rule-mi4ldhta local triggerNow is a dependency of another variable
[latest-25321]2025-11-18T14:17:38.345Z <Rule:INFO> TEST - time in expression as trigger (rule-mi4ldhta in Funktioner) starting rule state evaluation; because timer-trigger Timer#rule-mi4ldhta
[latest-25321]2025-11-18T14:17:38.345Z <Rule:INFO> Rule#rule-mi4ldhta local triggerNow is a dependency of another variable

    Is this the expected behavior?

    Bare metal, latest-25321

    Multi-System Reactor
  • Home Assistant 2025.11.2 and latest-25315
    CrilleC Crille

    Yes, solved. Thank you! Next time I will remember to do a manual backup of HASS before upgrading 🙂

    Multi-System Reactor
  • Home Assistant 2025.11.2 and latest-25315
    CrilleC Crille

    Heads up!
    It might be just my system or it might be a good idea to wait for HASSController to bless 2025.11.2 before you update HASS.
    @toggledbits can you confirm?

    2025112.PNG

    [latest-25315]2025-11-17T14:05:05.818Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.1.180:8123/api/websocket
[latest-25315]2025-11-17T14:05:05.820Z <HassController:NOTICE> HassController#hass connected, starting protocol
[latest-25315]2025-11-17T14:05:05.821Z <HassController:INFO> HassController#hass successful authentication with ws://192.168.1.180:8123; fetching initial data...
[latest-25315]2025-11-17T14:05:05.822Z <HassController:INFO> HassController#hass HA reports version "2025.11.2" location Hem timezone Europe/Stockholm state RUNNING safe_mode false
[latest-25315]2025-11-17T14:05:05.822Z <HassController:ERR> HassController#hass error while attempting config dump: [TypeError] Cannot read properties of undefined (reading 'tag') [-]
[latest-25315]2025-11-17T14:05:05.823Z <HassController:ERR> HassController#hass failed to complete startup: [TypeError] Cannot read properties of undefined (reading 'tag') [-]
[latest-25315]2025-11-17T14:05:05.823Z <HassController:CRIT> TypeError: Cannot read properties of undefined (reading 'tag') [-]
TypeError: Cannot read properties of undefined (reading 'tag')
    at /home/homebridge/reactor/server/lib/AlertManager.js:141:144
    at Array.findIndex (<anonymous>)
    at AlertManager.addAlert (/home/homebridge/reactor/server/lib/AlertManager.js:141:114)
    at /home/homebridge/reactor/server/lib/HassController.js:1464:367
    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
[latest-25315]2025-11-17T14:05:05.825Z <HassController:NOTICE> HassController#hass websocket closing, 1000
    Multi-System Reactor
  • Reactor w/HA 2025.11 error on set_datetime service call setting only time
    CrilleC Crille

    Sounds good, thank you for your work!

    Multi-System Reactor
  • Reactor w/HA 2025.11 error on set_datetime service call setting only time
    CrilleC Crille

    OK, thanks. Strange because it works in developer tools for me...
    date_time.PNG

    Multi-System Reactor
  • There is an alternative to homebridge-mqttthing
    CrilleC Crille

    Just throwing out a general hint to the people running Homebridge and MQTT.

    Homebridge MQTT-Thing hasn't been updated in almost 2 years and it falls behind on compatibility with the development of Homebridge.

    I was looking for a replacement and found Homebridge Easy MQTT and I think it's a good replacement for MQTT-Thing. I particularly find Easy MQTT Value tranformers easier to to understand and use compared to MQTT-Thing Apply function.

    It took a while to migrate everything but I'm pleased and can recommend.

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

    @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
  • [Solved] alarm() in global expression throws error in log.
    CrilleC Crille

    Yes sir, your magic has worked for sure!
    No more errors, thank you very much.

    Multi-System Reactor
  • Login
  • Don't have an account? Register
  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved