Use case:
When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled.
To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work.
Then another situation: the water pump system and garden irrigation, another switch.
In short, I had to create several virtual switches in Hubitat to disable rules in MSR.
Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR.
If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR.
Would it be possible to do something like this? Any recommendations from the experts?
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of.
Thanks.
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI:
An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status
Last 11:20:37
My MQTT configuration (local_mqtt_devices.yaml) for the related entity is:
layzspa_message:
type: ValueSensor
capabilities: ["temperature_sensor", "value_sensor", "power_sensor"]
primary_attribute: power_sensor.value
events:
"layzspa/message":
"power_sensor.value":
json_payload: true
if_expr: '! isnull( payload?.PWR )'
expr: "float(payload.PWR)"
"value_sensor.air":
json_payload: true
if_expr: '! isnull( payload?.AIR )'
expr: "float(payload.AIR)"
"value_sensor.pump":
json_payload: true
if_expr: '! isnull( payload?.FLT )'
expr: "float(payload.FLT)"
"value_sensor.god":
json_payload: true
if_expr: '! isnull( payload?.GOD )'
expr: "float(payload.GOD)"
"value_sensor.lock":
json_payload: true
if_expr: '! isnull( payload?.LCK )'
expr: "float(payload.LCK)"
"value_sensor.unit":
json_payload: true
if_expr: '! isnull( payload?.UNT )'
expr: "float(payload.UNT)"
"value_sensor.error":
json_payload: true
if_expr: '! isnull( payload?.ERR )'
expr: "float(payload.ERR)"
"temperature_sensor.green":
json_payload: true
if_expr: '! isnull( payload?.GRN )'
expr: "float(payload.GRN)"
"temperature_sensor.red":
json_payload: true
if_expr: '! isnull( payload?.RED )'
expr: "float(payload.RED)"
"temperature_sensor.target":
json_payload: true
if_expr: '! isnull( payload?.TGT )'
expr: "float(payload.TGT)"
"temperature_sensor.value":
json_payload: true
if_expr: '! isnull( payload?.TMP )'
expr: "float(payload.TMP)"
"temperature_sensor.virtual":
json_payload: true
if_expr: '! isnull( payload?.VTM )'
expr: "round(float(payload.VTM), 1)"
"temperature_sensor.ambient":
json_payload: true
if_expr: '! isnull( payload?.AMB )'
expr: "float(payload.AMB)"
"layzspa/Status":
"value_sensor.status":
if_expr: '! isnull( payload )'
expr: "payload"
"layzspa/button":
"value_sensor.button":
if_expr: '! isnull( payload )'
expr: "payload"
and in reactor.yaml I have:
"layzspa_states":
name: "Lay-Z-Spa States"
friendly_name: 'Lay-Z-Spa States'
include: layzspa_message
I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded).
Get it at (install is similar to MQTTController and such):
https://github.com/dbochicchio/reactor-opensprinkler
Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty.
Since I've learnt a lot from this controller, I'll explore new controllers soon.
Good day all,
I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing.
I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container.
Has anyone done this? Any advice?
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.
Hi guys,
Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular.
Maybe there are better ways to organize my rule sets.
I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
I have the following yaml configuration in local_mqtt_devices file
x_mqtt_device:
set_speed:
arguments:
speed:
type: str
topic: "command/%friendly_name%"
payload:
type: json
expr: '{ "fan": parameters.speed }'
While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
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
