Build: latest-26221-b25bb3e3, Docker on Synology.
Hi, I have a Rule whose Trigger/Constraints reference other Rules via Rule State ... is TRUE. At some point it stops firing.
Expanding the rule's condition tree in the UI shows every Trigger and Constraint condition green/TRUE — confirmed live by walking into the room and watching Motion go true in real time. Rule History shows no new SET, just old reset entries.
Tried, on the same rule, same evening: recreating the trigger conditions with fresh IDs, recreating the constraint conditions with fresh IDs (flat and wrapped in a new Group — wrapping in a Group produced one SET, but it didn't reproduce on repeat attempts with the same structure), and finally a full container restart with a verified-correct saved rule. Still no SET, even with a fresh live motion event right after the restart.
Separately, I found that this rule (and its 10 per-room clones) share identical internal condition/group IDs with each other — leftover from a batch clone done months ago, never regenerated. Not sure if that's related, since fixing the IDs didn't reliably fix the symptom either.
Has anyone seen a Rule State condition show TRUE in the UI without the Rule ever producing a SET, surviving a clean restart?
Thanks in advance
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group.
First of all, I think I found a typo in the doc:
primary_attribute: "binary_sensor.state"
primary_attribute_value: |
d = false;
each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d,
d
I think the correct code snippet is d = false,
All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
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.
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well.
As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API.
Updates: (the latest versions first in the list)
OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Edit: Solved in latest-26221.
Bare-metal latest-26193
I have this group:
"OKforLarm":
name: OK för Larm
select:
- include_controller: vera
- include_capability: door_sensor
filter_expression: entity.attributes.door_sensor.state
It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
Hey @toggledbits
One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets.
#1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth.
Both will be appreciated, but I understand the technical challenges. Thanks!
I'm currently on version 26011. I understand that the aarch64 image is no longer supported. So, I therefore need to update to the ARM64 image. Can anyone possibly suggest how I update my docker compose.yaml file (see below). Ideally I'd like to keep my existing reactions etc. rather than start from scratch.
# Multi-System Reactor template docker-compose.yml (version 22160)
#
# Change the lines indicated by "DO"...
#
services:
reactor:
container_name: reactor
environment:
# DO change the TZ: line to set your local time zone.
# See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
TZ: GB
#
# DO NOT change this path. Your directory location is in "source" below.
REACTOR_DATA_PREFIX: /var/reactor
# DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4)
image: toggledbits/reactor:latest-aarch64
restart: "always"
expose:
- 8111
ports:
- 8111:8111
volumes:
# DO change the /home/username/reactor below to the directory you created for
# your local data; DO NOT change the /var/reactor part
- /home/pi/docker/reactor:/var/reactor
- /etc/localtime:/etc/localtime:ro
tmpfs: /tmp
Owntracks Entity does not update as expected
-
Me again
Bare metal install of latest-22274-24dfd72c on Debian Bullseye on an Intel NUC.I definitely traversed the region boundary this afternoon. In the Mostquito log I can see:
1665508761: Client catmancatmaniphone disconnected. 1665508821: Socket error on client catmancatmaniphone, disconnecting. 1665508821: New client connected from 192.168.70.1 as catmancatmaniphone (c0, k60, u'catman'). 1665508821: owntracks/catman/catmaniphone 1665508821: Sending CONNACK to catmancatmaniphone (1, 0) 1665508821: Received PUBLISH from catmancatmaniphone (d0, q1, r1, m32, 'owntracks/catman/catmaniphone', ... (241 bytes)) 1665508821: Sending PUBACK to catmancatmaniphone (Mid: 32) 1665508821: Sending PUBLISH to reactor_openluup_mqqt (d0, q0, r0, m0, 'owntracks/catman/catmaniphone', ... (241 bytes)) 1665508821: Sending PUBLISH to catmancatmaniphone (d0, q1, r0, m264, 'owntracks/catman/catmaniphone', ... (241 bytes)) 1665508821: Received PUBACK from catmancatmaniphone (Mid: 264) 1665508825: Received DISCONNECT from catmancatmaniphone 1665508825: Client catmancatmaniphone disconnected. 1665508974: Sending PUBLISH to rachel49610FDD9BED4C648D4F36DC952B61BC (d0, q1, r0, m392, 'owntracks/catman/catmaniphone', ... (195 bytes)) 1665508974: Sending PUBLISH to rachel49610FDD9BED4C648D4F36DC952B61BC (d0, q1, r0, m393, 'owntracks/catman/catmaniphone', ... (200 bytes)) 1665508974: Sending PUBLISH to rachel49610FDD9BED4C648D4F36DC952B61BC (d0, q1, r0, m394, 'owntracks/catman/catmaniphone', ... (241 bytes)) 1665511338: Socket error on client catmancatmaniphone, disconnecting. 1665511338: New client connected from 192.168.70.1 as catmancatmaniphone (c0, k60, u'catman'). 1665511338: owntracks/catman/catmaniphone 1665511338: Sending CONNACK to catmancatmaniphone (1, 0The entries at 1665508401 correlate with my phone entering the region and immediately publishing the fact to my wite's pone (which makes sense and seem to indicate that Owntracks and Mosquitto are correctly configured.
1665508401 is 1805 local time (Zulu +1)
MSR logs:
[latest-22274]2022-10-11T16:50:41.344Z <VeraController:CRIT> *Entity#vera>device_20631 [latest-22274]2022-10-11T17:00:00.002Z <Rule:INFO> Morning Lights (Rule#rule-l6gxvycu) starting evaluation; because timer-trigger Timer#rule-l6gxvycu [latest-22274]2022-10-11T17:00:00.005Z <Rule:INFO> Morning Lights (Rule#rule-l6gxvycu) evaluated; trigger state unchanged (false); rule state remains RESET [latest-22274]2022-10-11T17:00:00.007Z <Rule:INFO> Morning Lights (Rule#rule-l6gxvycu) evaluation complete [latest-22274]2022-10-11T17:00:00.007Z <Rule:INFO> Morning Heating (Rule#rule-l60fkpo3) starting evaluation; because timer-trigger Timer#rule-l60fkpo3 [latest-22274]2022-10-11T17:00:00.013Z <Rule:INFO> Morning Heating (Rule#rule-l60fkpo3) evaluated; trigger state unchanged (false); rule state remains RESET [latest-22274]2022-10-11T17:00:00.014Z <Rule:INFO> Morning Heating (Rule#rule-l60fkpo3) evaluation complete [latest-22274]2022-10-11T17:00:00.015Z <Rule:INFO> Morning Lights (Rule#rule-l6gxvycu) starting evaluation; because timer-trigger Timer#rule-l6gxvycu [latest-22274]2022-10-11T17:00:00.016Z <Rule:INFO> Morning Lights (Rule#rule-l6gxvycu) evaluated; trigger state unchanged (false); rule state remains RESET [latest-22274]2022-10-11T17:00:00.017Z <Rule:INFO> Morning Lights (Rule#rule-l6gxvycu) evaluation complete [latest-22274]2022-10-11T17:00:00.023Z <Rule:INFO> Morning Heating (Rule#rule-l60fkpo3) starting evaluation; because timer-trigger Timer#rule-l60fkpo3 [latest-22274]2022-10-11T17:00:00.025Z <Rule:INFO> Morning Heating (Rule#rule-l60fkpo3) evaluated; trigger state unchanged (false); rule state remains RESET [latest-22274]2022-10-11T17:00:00.025Z <Rule:INFO> Morning Heating (Rule#rule-l60fkpo3) evaluation complete [latest-22274]2022-10-11T17:00:05.003Z <Engine:INFO> [Engine]Engine#1 master timer tick, local time "10/11/2022, 6:00:05 PM" (TZ offset 60 mins from UTC) [latest-22274]2022-10-11T17:15:00.008Z <Rule:INFO> Morning Lights (Rule#rule-l6gxvycu) starting evaluation; because timer-trigger Timer#rule-l6gxvycu [latest-22274]2022-10-11T17:15:00.011Z <Rule:INFO> Morning Lights (Rule#rule-l6gxvycu) evaluated; trigger state unchanged (false); rule state remains RESET [latest-22274]2022-10-11T17:15:00.013Z <Rule:INFO> Morning Lights (Rule#rule-l6gxvycu) evaluation completereactor.yaml for the entity:
- 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: Home2Owntracks config screen:
Owntracks region
I'm going away tomorrow. Please save me from myself!
TIAC
-
I'm not sure your topic is correct in config. Try owntracks/catman/catmaniphone
I'm away from my PC so I couldn't double check the template, but I'll definitely try it.
--
On a mission to automate everything. -
I'm not sure your topic is correct in config. Try owntracks/catman/catmaniphone
I'm away from my PC so I couldn't double check the template, but I'll definitely try it.
Thanks, pretty sure (as mentioned in another thread) it's right. Here's the template:
# owntracks_in_region # Receive OwnTracks location updates and drive a binary sensor that tells if a designated device # is in a given region or not (e.g. is Dad home?). The topic is the "Device ID" configured in the # OwnTracks app (under Identification). The regionName is the name of a region defined in the app. # Requires: topic, regionName owntracks_in_region: capabilities: [ binary_sensor ] primary_attribute: binary_sensor.state type: BinarySensor events: "owntracks/user/%topic%": "binary_sensor.state": json_payload: true if_expr: "payload._type == 'location'" expr: > ( first region in ( payload.inregions ?? [] ) with region == regionName: true ) ?? falseStill think I I should change. Looks to me like it should just be catmaniphone?
C
-
I see the issue... for some reason, your phone is publishing the topic
owntracks/catman/catmaniphone, where it seems most others getowntracks/user/catmaniphone... it must be possible to set theuserpart somewhere in the app, although I'm not sure where.No worries. Update the template (in
mqtt_device.yaml-- just this once, I normally don't encourage modifying system files) -- make the lines look like this:events: "owntracks/%user%/%topic%":And then add
user: catmanto your entity config indented the same as thetopicandnamelines.Edit: also the
regionline in your entity config should sayregionName: Home2Edit2: Mystery solved. The
userportion of the topic is the username defined in the Identification section of Owntracks preferences, and it is set whether login with password is used or not. I've already updated the template for the next version of MQTTController to incorporate the change above. -
C CatmanV2 has marked this topic as solved on
-
T toggledbits locked this topic on