Create Expression to call out Entity ID of Tripped Binary Sensor
-
You can't do it in
x_hass_system.call_service(specifically and uniquely) because thedatais an object field in that action, and the substitution doesn't work in object types, only in strings. You need to use the actions available inx_hass_tts. If yourmedia_player.living_roomdoes not natively havex_hass_ttsactions listed, you'll need to add them by copy-pasting this to a file calledlocal_hass_devices.yamlin yourconfigdirectory (and restart Reactor):entities: # This media player supports TTS "hass>media_player_living_room": services: - ttsUnfortunately the Hass API doesn't expose enough info for Reactor to know that device supports the service, so it has to be done manually.
@toggledbits said in Create Expression to call out Entity ID of Tripped Binary Sensor:
You can't do it in
x_hass_system.call_service(specifically and uniquely) because thedatais an object field in that action, and the substitution doesn't work in object types, only in strings.Crap this throws a wrench in a lot of my automation plans. I tried to add the TTS functionality way back and never got it working will try again.
-
Having some issues with the expression that determines what zones are
true. It was working when I originally created the expression but I made a few tweaks to expression names and now it doesn't work. Here is a snippet of the logs. Also a screenshot of the expression
[latest-22248]2022-09-06T23:41:57.638Z <Rule:INFO> Zone Open ALERT (Rule#rule-grpot1ehov) evaluation complete [latest-22248]2022-09-06T23:41:57.639Z <Rule:INFO> Babay/Papa Windows (Rule#rule-l7jasakd) starting evaluation; because entity-changed Entity#hass>binary_sensor_babay_papa_windows [latest-22248]2022-09-06T23:41:57.639Z <Rule:INFO> Zone Open ALERT (Rule#rule-grpot1ehov) starting evaluation; because entity-changed Entity#hass>binary_sensor_babay_papa_windows [latest-22248]2022-09-06T23:41:57.640Z <Rule:INFO> Babay/Papa Windows (Rule#rule-l7jasakd) evaluated; trigger state unchanged (false); rule state remains RESET [latest-22248]2022-09-06T23:41:57.640Z <Rule:INFO> Zone Open ALERT (Rule#rule-grpot1ehov) evaluated; trigger state unchanged (false); rule state remains RESET [latest-22248]2022-09-06T23:41:57.640Z <Rule:INFO> Babay/Papa Windows (Rule#rule-l7jasakd) evaluation complete [latest-22248]2022-09-06T23:41:57.641Z <Rule:INFO> Zone Open ALERT (Rule#rule-grpot1ehov) evaluation complete [latest-22248]2022-09-06T23:41:57.641Z <Engine:ERR> [Engine]Engine#1: error evaluating expression tripped_zones: [ReferenceError]ReferenceError: Invalid scope in reference to member binary_sensor of (object)null [latest-22248]2022-09-06T23:41:57.642Z <Engine:ERR> [Engine]Engine#1: expression: each id in zones_list: getEntity(id).attribute.binary_sensor.state == "true" ? id : null [latest-22248]2022-09-06T23:41:57.642Z <Engine:CRIT> ReferenceError: Invalid scope in reference to member binary_sensor of (object)null ReferenceError: Invalid scope in reference to member binary_sensor of (object)null at _run (/home/armans2/reactor/common/lexp.js:1490:31) at _run (/home/armans2/reactor/common/lexp.js:1484:33) at _run (/home/armans2/reactor/common/lexp.js:1334:34) at _run (/home/armans2/reactor/common/lexp.js:1502:32) at _run (/home/armans2/reactor/common/lexp.js:1594:41) at /home/armans2/reactor/common/lexp.js:1324:29 at Array.forEach (<anonymous>) at _run (/home/armans2/reactor/common/lexp.js:1323:28) at run (/home/armans2/reactor/common/lexp.js:1704:22) at Object.evaluate (/home/armans2/reactor/common/lexp.js:1740:20) -
P Pabla marked this topic as a question on
-
P Pabla has marked this topic as solved on
-
You're right... it is almost the exact same expression... almost. (I'm teaching here... look closely at the one the works, and the one that doesn't).
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
Hi @Pabla
I'm sorry if I'm saying something wrong and out of the context of this discussion, but I'll put what I have that seems to be what you are looking for, using DynamicGroupController, which was an excellent feature that @toggledbits implemented.
config > reactor.yaml
- id: groups enable: true implementation: DynamicGroupController name: Dynamic Group Controller config: groups: "dgc_low_battery": name: DGC Low Battery select: - include_capability: - battery_power filter_expression: > entity.attributes.battery_power.level < 0.3 "dgc_tripped": name: DGC Tripped select: - include_capability: - door_sensor - motion_sensor - co_detector - smoke_detector - leak_detector filter_expression: > entity.attributes?.door_sensor?.state == true or entity.attributes?.motion_sensor?.state == true or entity.attributes?.co_detector?.state == true or entity.attributes?.smoke_detector?.state == true or entity.attributes?.leak_detector?.state == true "dgc_internal_motion": name: DGC Internal Motion select: - include_entity: - "hubitat>40" - "hubitat>41" - "hubitat>43" - "hubitat>73" filter_expression: > entity.attributes?.motion_sensor?.state == trueWhen I then have the information loaded, it is easy to handle in many situations.
In the example below, I put in the array HouseSECURITY which devices I want to monitor, according to the way the house is, and then I crosscheck with what comes from DynamicGroup, and display messages, take actions, etc..
At the moment, the house is in Day mode, so there is nothing, at night I load in this variable the list of doors and windows; when it is travel, I add movement.
I don't know if I helped or hindered.
Thanks.
-
It would be my preference that Pabla find his error, since the way he's doing it will work... worked before, and he said that, he just changed something that made it not work, and some troubleshooting is necessary. In this case, a "code review" is sufficient (a review of the failing expression, perhaps in conjunction with a careful comparison to the working similar expression).
-
You're right... it is almost the exact same expression... almost. (I'm teaching here... look closely at the one the works, and the one that doesn't).
@toggledbits said in Create Expression to call out Entity ID of Tripped Binary Sensor:
You're right... it is almost the exact same expression... almost. (I'm teaching here... look closely at the one the works, and the one that doesn't).
Had a feeling it was a typo mistake, gonna take a look with some fresh eyes later today.
-
Hi @Pabla
I'm sorry if I'm saying something wrong and out of the context of this discussion, but I'll put what I have that seems to be what you are looking for, using DynamicGroupController, which was an excellent feature that @toggledbits implemented.
config > reactor.yaml
- id: groups enable: true implementation: DynamicGroupController name: Dynamic Group Controller config: groups: "dgc_low_battery": name: DGC Low Battery select: - include_capability: - battery_power filter_expression: > entity.attributes.battery_power.level < 0.3 "dgc_tripped": name: DGC Tripped select: - include_capability: - door_sensor - motion_sensor - co_detector - smoke_detector - leak_detector filter_expression: > entity.attributes?.door_sensor?.state == true or entity.attributes?.motion_sensor?.state == true or entity.attributes?.co_detector?.state == true or entity.attributes?.smoke_detector?.state == true or entity.attributes?.leak_detector?.state == true "dgc_internal_motion": name: DGC Internal Motion select: - include_entity: - "hubitat>40" - "hubitat>41" - "hubitat>43" - "hubitat>73" filter_expression: > entity.attributes?.motion_sensor?.state == trueWhen I then have the information loaded, it is easy to handle in many situations.
In the example below, I put in the array HouseSECURITY which devices I want to monitor, according to the way the house is, and then I crosscheck with what comes from DynamicGroup, and display messages, take actions, etc..
At the moment, the house is in Day mode, so there is nothing, at night I load in this variable the list of doors and windows; when it is travel, I add movement.
I don't know if I helped or hindered.
Thanks.
-
@wmarcolin that’s my next plan! I want to get comfortable with some basic expressions first then dive into the dynamicgroupcontroller
@pabla said in Create Expression to call out Entity ID of Tripped Binary Sensor:
dynamicgroupcontroller
I highly recommend taking the time to use DynamicGroupController, before I had huge global variables, complexity to monitor and create array, when this feature was implemented it made these group management actions by characteristics much easier. Good luck!
-
You're right... it is almost the exact same expression... almost. (I'm teaching here... look closely at the one the works, and the one that doesn't).
@toggledbits said in Create Expression to call out Entity ID of Tripped Binary Sensor:
You're right... it is almost the exact same expression... almost. (I'm teaching here... look closely at the one the works, and the one that doesn't).
okay so I checked and noticed that I wrote
attributesingular and in the working one made itattributesplural. Still no success.. I even got someone else to check the syntax and they weren't able to find a difference between the working and non-working expression.I fear I am overlooking something super basic which I thought I fixed but I have yet to find the error
Edit: I had a typo in my array of entities all is well
-
Did the behavior change? If so, what does the new behavior look like? If not, what is in the logs?
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
Did the behavior change? If so, what does the new behavior look like? If not, what is in the logs?
@toggledbits it works as expected now, I had a typo in one of my entities in the array.
-
You can't do it in
x_hass_system.call_service(specifically and uniquely) because thedatais an object field in that action, and the substitution doesn't work in object types, only in strings. You need to use the actions available inx_hass_tts. If yourmedia_player.living_roomdoes not natively havex_hass_ttsactions listed, you'll need to add them by copy-pasting this to a file calledlocal_hass_devices.yamlin yourconfigdirectory (and restart Reactor):entities: # This media player supports TTS "hass>media_player_living_room": services: - ttsUnfortunately the Hass API doesn't expose enough info for Reactor to know that device supports the service, so it has to be done manually.
@toggledbits said in Create Expression to call out Entity ID of Tripped Binary Sensor:
You can't do it in x_hass_system.call_service (specifically and uniquely) because the data is an object field in that action, and the substitution doesn't work in object types, only in strings.
This restriction has been lifted in build 22251. The data will now be stored as a string rather than an object, so that substitution can occur. This requires that any use of
call_servicebe edited, so that the stored data is updated to the new form. You'll get alerts for actions that need to be edited. See the announcement for build 22251 for more info.
