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.
C
Crille
@Crille
Using build 25328 and having the following users.yaml configuration:
users:
# This section defines your valid users.
admin: *******
groups:
# This section defines your user groups. Optionally, it defines application
# and API access restrictions (ACLs) for the group. Users may belong to
# more than one group. Again, no required or special groups here.
admin_group:
users:
- admin
applications: true # special form allows access to ALL applications
guests:
users: "*"
applications:
- dashboard
api_acls:
# This ACL allows users in the "admin" group to access the API
- url: "/api"
group: admin_group
allow: true
log: true
# This ACL allows anyone/thing to access the /api/v1/alive API endpoint
- url: "/api/v1/alive"
allow: true
session:
timeout: 7200 # (seconds)
rolling: true # activity extends timeout when true
# If log_acls is true, the selected ACL for every API access is logged.
log_acls: true
# If debug_acls is true, even more information about ACL selection is logged.
debug_acls: true
My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
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
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future.
In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level.
Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way.
I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption.
A few other things to know:
If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc.
Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy).
The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON.
You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach).
The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case.
This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change.
This thread is open for any questions or concerns.
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks.
Any chance of a 'bulk delete' option?
No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices
Cheers
C
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.
Just for the record, in case anyone is following, I'm really rather impressed.
I have installed one of these:
https://www.amazon.co.uk/dp/B0B6P22YJC?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1
That's connected (physically) to the VM running on my Synology, with a 2m USB extension.
The same host also runs Openluup, Mosquito, HA Bridge.
Yesterday I installed Zigbee2mqtt. That was a bit of a PITA but mostly because of ports and permissions.
Once up and running, and the correct boxes ticked, immediately visible in Home Assistant via the MQTT integration, and thence into Reactor
I've only got two devices. I bought the cheapest sensor I could find, which is a door sensor. Dead easy to add to ZIgbee2mqtt and again, immediately visible in HA.
https://www.amazon.co.uk/dp/B0FPQLWRW1?ref=ppx_yo2ov_dt_b_fed_asin_title
The dongle is on the top floor of the house, and I wanted the sensor on the back door (just about as far apart as it's possible to get short of going into the garage) When I moved the sensor downstairs it dropped out pretty instantly (which wasn't a huge surprise) so quick bit of research found out that smart plugs will act as routers so...
https://www.amazon.co.uk/dp/B0FDQDPGBB?ref=ppx_yo2ov_dt_b_fed_asin_title
Took me about 30 seconds to connect. Updated the name. Instantly visible in Reactor with the new name pushed over from Zigbee2mqtt.
And lo, the door sensor now has a signal of 140 and works as far as I can tell perfectly and instantly (unlike my z-wave one).
A few more of those will be purchased and used to replace the Tuya wifi cloud devices and the (continually failing) Z-wave plugs (yeah, they were TKB so....)
Commended to the house. Thanks for everyone that got me on the right lines.
C
If you’re like me and still running HABridge to control your devices locally via Alexa, you might need to tweak your endpoints to call Reactor via HTTP. Here’s the best way to do it, IMO:
Insert the Reactor Canonical ID (e.g., zwavejs>71-1) into the MapID field, but make sure it’s URL-encoded like this: zwavejs%3E71-1.
Then, configure these endpoints as needed:
On: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.on
Off: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.off
Dim:
For lights: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/dimming.set?level=${intensity.decimal_percent}
For roller shutters: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/position.set?value=${intensity.decimal_percent}
Color: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/rgb_color.set_rgb?red=${color.r}&green=${color.g}&blue=${color.b}
Just replace [ReactorIP] with your actual IP address. By using these placeholders, you can standardize your endpoints across all devices, making maintenance easier.
This setup works with any device mapped under MSR, regardless of the controller (ZWaveJS, Vera, HASS, OpenSprinkler, virtual, MQTT, DynamicEntities, etc.). If you need different calls, just go to the entities, get the action and parameters, and adjust accordingly. Enjoy super fast access to your devices via Alexa!
If you're migrating from Vera, the endpoints are (URL-encoded) in a file called device.db, in JSON format, under your config. You'd write a script to align the new endpoints to the new one, if you prefer to do it automatically. YMMV.
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Good evening all,
For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time.
Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed.
Thanks.
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations.
Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction?
Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for.
I guess it's something of an edge case so no huge issue.
TIA!
C
I'm sure this has been asked, and answered, but damned if I can figure it out
Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage.
Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts.
After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!)
What I would like is for the 3 minute delay until the lights go off to start from the latest door open event.
That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity.
I've tried 'hacking' with a virtual switch, but can't seem to stop the delay.
Any pointers?
TIA
C
Hello oh great ones.
After a couple of hours messing with ports and permissions I have Zigbee2mqtt installed and running on my virtual pi
Can connect to the front end and everything
Odd one though, simply cannot get systemctl to work and the error is, well, unhelpful. The service file is this:
[Unit]
Description=zigbee2mqtt
After=network.target
[Service]
Environment=NODE_ENV=production
Type=notify
ExecStart=/usr/local/bin/node index.js
WorkingDirectory=/opt/zigbee2mqtt
StandardOutput=inherit
# Or use StandardOutput=null if you don't want Zigbee2MQTT messages filling syslog, for more options see systemd.exec(5)
StandardError=inherit
WatchdogSec=10s
Restart=always
RestartSec=10s
User=pi
[Install]
WantedBy=multi-user.target
Straight out of the docs with the change to point to my local node install (which we know works as it's the same as the very fine Reactor is using.
Running manually pnpm start
in /opt/zigbee2mqtt works fine
However:
catman@openluup:/etc/systemd/system$ sudo systemctl start zigbee2mqtt.service
Job for zigbee2mqtt.service failed because the control process exited with error code.
See "systemctl status zigbee2mqtt.service" and "journalctl -xe" for details.
Which I have
catman@openluup:/etc/systemd/system$ sudo systemctl status zigbee2mqtt.service
● zigbee2mqtt.service - zigbee2mqtt
Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2025-12-16 12:32:42 GMT; 4s ago
Process: 3093 ExecStart=/usr/local/bin/node index.js (code=exited, status=217/USER)
Main PID: 3093 (code=exited, status=217/USER)
and
-- A start job for unit zigbee2mqtt.service has begun execution.
--
-- The job identifier is 17477.
Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed to determine user credentials: No such process
Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed at step USER spawning /usr/local/bin/node: No such process
-- Subject: Process /usr/local/bin/node could not be executed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The process /usr/local/bin/node could not be executed and failed.
--
-- The error number returned by this process is ERRNO.
Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=217/USER
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit zigbee2mqtt.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 217.
Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit zigbee2mqtt.service has entered the 'failed' state with result 'exit-code'.
Dec 16 12:35:16 openluup systemd[1]: Failed to start zigbee2mqtt.
-- Subject: A start job for unit zigbee2mqtt.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit zigbee2mqtt.service has finished with a failure.
Which strikes me as very odd.
Any blindingly obvious things I'm missing?
TIA!
C
Posts
-
[Solved] function isRuleEnabled() issue -
[Solved] function isRuleEnabled() issueWow, those were in fact really bad! Sorry for that.
Rule idrule-mj4xiyr8is in this case Enabled
Rule expression:
Global expression:
-
[Solved] function isRuleEnabled() issueEdit: Rule id needs to be quoted, e.g. isRuleEnabled( 'rule_id' )
Bare metal 25325.
I'm getting
nullin both global and local expressions for the functionisRuleEnabled(). 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.
[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 -
Logic Assistance: Exterior Lights on when Illuminance Below Threshold@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.
-
Logic Assistance: Exterior Lights on when Illuminance Below ThresholdI have a local variable as trigger for cases like this. When
lightsOnistruethe 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 -
MQTT templates for ZIgbee scene controller, or a better way?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_singletosingle. -
[Solved] Local expression in Rule does not evaluate as they used to do -
[Solved] Local expression in Rule does not evaluate as they used to do -
[Solved] Local expression in Rule does not evaluate as they used to doEdit: 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.
Previously this worked, when Reactor uptime changed all local expressions were evaluated but now only timeNowis updated andtriggerNowdoes not change (even though it is dependent ontimeNow), so the Rule never sets.
I can work around the issue bygetEntity(...uptime)intriggerNow, then the expression is evaluated and changes totrueand 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 variableIs this the expected behavior?
Bare metal, latest-25321
-
Home Assistant 2025.11.2 and latest-25315Yes, solved. Thank you! Next time I will remember to do a manual backup of HASS before upgrading
-
Home Assistant 2025.11.2 and latest-25315Heads 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?
[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 -
Reactor w/HA 2025.11 error on set_datetime service call setting only time -
Reactor w/HA 2025.11 error on set_datetime service call setting only time -
There is an alternative to homebridge-mqttthingJust 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 tranformerseasier to to understand and use compared to MQTT-ThingApplyfunction.It took a while to migrate everything but I'm pleased and can recommend.
-
Reactor w/HA 2025.11 error on set_datetime service call setting only time@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. -
[Solved] alarm() in global expression throws error in log. -
[Solved] alarm() in global expression throws error in log.New variable, another entity but same error with
alarm()
There must be something off in my system then.[latest-25310]2025-11-07T17:14:14.037Z <Engine:NOTICE> Engine#1 creating global expression neverusedbeforevariable [latest-25310]2025-11-07T17:14:14.039Z <Engine:CRIT> Engine#1 alarm() scheduled neverusedbeforevariable tick for 1762535669039<2025-11-07 18:14:29> = now 1762535654039<2025-11-07 18:14:14> + delay 15000 [latest-25310]2025-11-07T17:14:22.195Z <Engine:ERR> Engine#1: error evaluating expression neverusedbeforevariable: [ReferenceError] alarm() can only be used in global expressions [-] [latest-25310]2025-11-07T17:14:22.195Z <Engine:ERR> Engine#1: expression: alarm(15), getEntity( "vera>device_56" ).attributes.x_vera_svc_micasaverde_com_EnergyMetering1.momentary_active_import [latest-25310]2025-11-07T17:14:22.195Z <Engine:CRIT> ReferenceError: alarm() can only be used in global expressions [-] ReferenceError: alarm() can only be used in global expressions at /home/homebridge/reactor/server/lib/Engine.js:1455:23 at _run (/home/homebridge/reactor/common/lexp.js:1704:34) at /home/homebridge/reactor/common/lexp.js:1426:29 at Array.forEach (<anonymous>) at _run (/home/homebridge/reactor/common/lexp.js:1425:28) at Object.run (/home/homebridge/reactor/common/lexp.js:1855:24) at Engine._eval_expr (/home/homebridge/reactor/server/lib/Engine.js:1170:141) at Engine._expr_dependency (/home/homebridge/reactor/server/lib/Engine.js:1555:82) at /home/homebridge/reactor/server/lib/MessageBus.js:114:195 at Array.forEach (<anonymous>) [latest-25310]2025-11-07T17:14:27.526Z <Rule:INFO> Notifiering - Auto off laddning poolrobot (rule-md7japbd in Notifieringar) starting rule state evaluation; because entity-changed Switch#mosquitto-mqtt>laddning_poolrobot [latest-25310]2025-11-07T17:14:29.039Z <Engine:CRIT> Engine#1 neverusedbeforevariable alarm() tick [latest-25310]2025-11-07T17:14:29.039Z <Engine:CRIT> Engine#1 alarm() scheduled neverusedbeforevariable tick for 1762535684039<2025-11-07 18:14:44> = now 1762535669039<2025-11-07 18:14:29> + delay 15000 [latest-25310]2025-11-07T17:14:30.681Z <Engine:ERR> Engine#1: error evaluating expression neverusedbeforevariable: [ReferenceError] alarm() can only be used in global expressions [-] [latest-25310]2025-11-07T17:14:30.681Z <Engine:ERR> Engine#1: expression: alarm(15), getEntity( "vera>device_56" ).attributes.x_vera_svc_micasaverde_com_EnergyMetering1.momentary_active_import [latest-25310]2025-11-07T17:14:30.681Z <Engine:CRIT> ReferenceError: alarm() can only be used in global expressions [-] ReferenceError: alarm() can only be used in global expressions at /home/homebridge/reactor/server/lib/Engine.js:1455:23 at _run (/home/homebridge/reactor/common/lexp.js:1704:34) at /home/homebridge/reactor/common/lexp.js:1426:29 at Array.forEach (<anonymous>) at _run (/home/homebridge/reactor/common/lexp.js:1425:28) at Object.run (/home/homebridge/reactor/common/lexp.js:1855:24) at Engine._eval_expr (/home/homebridge/reactor/server/lib/Engine.js:1170:141) at Engine._expr_dependency (/home/homebridge/reactor/server/lib/Engine.js:1555:82) at /home/homebridge/reactor/server/lib/MessageBus.js:114:195 at Array.forEach (<anonymous>) -
[Solved] alarm() in global expression throws error in log. -
[Solved] alarm() in global expression throws error in log.
