I've managed to use MSR UI on iOS devices to some degree*, so that although UI elements (e.g. rule sets) are not visible in portrait mode, you've seen them in landscape. Now with recents builds (24302) this does not work anymore, elements (rule sets, entities) are not anymore visible in landscape mode.
Does anyone have similar experiences? Using iOS 18 and Safari/Chrome browser.
( *Drag & drop of rule conditions have never worked on a mobile)
Hi @toggledbits,
I have lots of logs with this:
<Engine:ERR> Assignment to alarm ignored -- expression-driven global cannot be set by assignmentAny hints to where look at to avoid this? Thanks.
Hi @toggledbits
I'd like to update my controllers with these new features, but I'm struggling to find any guidance in the docs - and in general to understand the context.
Could you please elaborate more? Thanks.
I have the following ACL defined:
groups: admin: users: - admin applications: true api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: trueAnd I have authenticated to MSR as "admin" user. However, I'm getting "access denied" when trying to access http://*******:8111/api/v1/log
So what I'm missing, is my ACL incorrectly defined?
Using build 24302 on Docker.
Thanks to @toggledbits for adding a custom CSS. I've started doing a darker Reactor style.
Here's the file: https://gist.github.com/dbochicchio/825098ac13b7f8cac22012eae37ff7ce
A couple of things are still too bright and I'll eventually catch-up. Just place it under your /config directory, naming the file as customstyles.css. Hard refresh your browser.
Hi!
In Home Assistant I sometimes uses the TTS, either to my Sonos or Google speakers. With reactor in Vera I also use TTS.
But in MSR I can't select the TTS-service. It's simply not there. Am I missing something, or is this the case, so far?
Thanks!
/Fanan
Hi
I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.
They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.
This is how that device looks in the Ezlo API.
Devices Info:
_id: "10696001" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "level_sensor" subcategory: "" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Digital" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696001" deviceId: "10696001" hasGetter: true hasSetter: false name: "smoke_density" show: true valueType: "substance_amount" scale: "parts_per_million" value: 2.7472610473632812 valueFormatted: "2.75" status: "idle"There is also an Analog Gas sensor that one did import in to MSR OK.
68d63dab-b871-4f44-912b-cf6e0b9eb4c6-image.png
Devices Info:
_id: "10696000" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "security_sensor" subcategory: "gas" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Analog" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696000" deviceId: "10696000" hasGetter: true hasSetter: false name: "gas_alarm" show: true valueType: "token" enum: 0: "no_gas" 1: "combustible_gas_detected" 2: "toxic_gas_detected" 3: "unknown" valueFormatted: "no_gas" value: "no_gas" status: "idle"And this is how this MQ2 Gas Sensor looks like on their dashboard:
Digital
cb77dfa3-4af5-4d06-9635-89207a716a89-image.png
Analog
4fb4da1b-e946-4b89-876c-bcd9f5699b6c-image.png
They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!
And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.
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.A couple of things for you @toggledbits, since you mentioned that this release has new features and some tweaks are expected.
Local expressions cannot be deleted. Pushing the X button has no effect for me.
When cloning an entity action, the result is strange (first is cloned one, second is the original action):
a92ea094-9e2c-4aaa-bf47-2d07a6ffdbd0-image.png
When changing the action on the cloned element, the params are added to the original one. See screenshot:
92ac3011-83c8-466b-bd23-47d483ad7a52-image.png
Dark theme has a couple of strange contrasts. One is visible in the previous screenshots (white text on yellow background). Another one is in groups (blue text on blue background):
9b3c4988-53ef-44e6-9672-30e744cacb75-image.png
Overall, I found blue, yellow, red and green (in buttons and forms) to be too bright.
On the bright side:
I love the new script action: thank you! The dark theme is a great start to avoid getting blinded at night I promise I'll try very soon the new features around actions. Thanks!@toggledbits
I just upgraded to version MSR 24293, bare metal running on Fedora. Upon restart, I am getting a error banner:
I followed the new directions about npm
npm i --no-save --no-package-lock --omit dev
Any idea what the issue is?
Seems like switching the UI to the newly added dark mode (thank you for this) does nothing. The UI stays in light mode and only a few buttons turn into dark mode (see screenshot)
Things I have tried:
Hard refresh
Different browser
Different computer
Restarting Reactor
Failed troubleshooting attempts:
No errors in Chrome console
No relevant errors in Reactor log (can still PM the full log file)
Reactor version: latest-24293-ea42a81d
Hardware: Odroid N2+
Linux version: Ubuntu 24.04.1 LTS
3df2806f-9146-485b-9ec1-d056e91cefe5-image.png Dark mode enabled
ff823023-c079-4684-b01f-d6ac6527d31a-image.png Light mode enabled
Good morning,
I have a service MQTT service that needs a restart occasionally. The add-on (Smartbed MQTT) is for the smart bed base for my bed. It has a "safety light" that I can control from HAAS & MSR as a light entity, and also moves the head of the bed to a preset at bedtime, and then lies it back flat in the morning The problem is, from time to time, the light becomes "unavailable" Restarting from the Add-ons tab in HAAS always fixes it, but I should be able to detect when it happens when "light.tempur_pedic_safety_lights" is not true or false, i.e., unavailable.
What I don't know how to do is how to restart that service. Does anybody have experience in restarting add-ons from MSR?
Running:
Reactor (Multi-hub) latest-24212-3ce15e25 ZWaveJSController [0.1.24232]HAAS:
RPi5-64 (8GB) Core 2024.7.3 Supervisor 2024.08.0 Operating System 13.0 Frontend 20240710.0Hi!
Is it possible to generate two additional log files, the first being the replica of what is displayed on screen by the Rule History widgets and the other with Recently Changed Entities?
And could I configure the generation of one file per day, and delete the older ones? For example, store the last 5 days?
And being more ambitious, does Windget have an icon to open these TXT files in the navigated?
Well, we're approaching Christmas, so here's my request to Santa Claus @toggledbits 🙂
Hi @toggledbits
I'm working on a controller to generate llm response from a prompt in reactor. I have http response coming thru an http request action at the moment, capturing the response inside a local variable. So, it's practically sync.
I want to create a controller, so I don't have to rely on a proxy (and have a simpler architecture), and duplicate absurd http actions, but AFAIK in the current implementation, actions are async only. But if I have multiple requests going on, I cannot be sure what it's really inside an attribute. I also thought that something like a correlation id when sending the request could be used to identity multiple responses, but I wanted to double check with you before starting with something too complicated. I also noticed that some actions in home assistant (ie forecast) are sync and I'm wondering if you have any plan or hint to address this situation. Thanks.
Thanks.
@togglebits I am curious as to why the tilt_sensor.state (primary) = NULL. I believe it should show true or false. I have to use binary_sensor.state instead in my rules.
Again, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the tilt sensor in hopes it can help.
Thanks in advance.
Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3
@toggledbits I have noticed after upgrading both Reactor and ZWaveJSController to version 24257 that two of my devices/entities, TILT-ZWAVE2.5-ECO and Zooz ZSE18, had their entity re-named in an unusual way and also appears to be duplicated.
Reactor version 24257
ZWaveJSController version 24257
Z-Wave JS UI version 9.18.1
zwave-js version 13.2.0
Vestibule Motion Sensor State attributes/partial screenshot of entities it created. All entities have the same attributes.
motion_sensor.state=true x_zwave_values.Notification_Home_Security_Motion_sensor_status=8 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=23 zwave_device.valueId=[113,"Notification","Home Security","Home Security","Motion sensor status","Motion sensor status"] zwave_device.version_info=nullTilt Sensor Door State and Tilt Sensor Door State Simple attributes/partial screenshot of entities it created. All entities have similar attributes with exception of x_zwave_values.Notification_Access_Control_Door_State = 22 or 23.
tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state_simple=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state_simple=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=nullI'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only).
Anyway, here's my reactor-mqtt-contrib package:
Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.
Simply download yaml files (everything or just the ones you need) and you're good to go.
I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them.
The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression.
Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests 🙂
Multidimensional Array
-
Ok let's go in parts, what I created in Group is the same thing I do in the traditional way and get the result, see the battery case.
I'm not seeing an error anymore, after a reboot of the MSR host.
[latest-21331]2021-11-28T02:45:18.584Z <default:null> Module httpapi v21308 [latest-21331]2021-11-28T02:45:18.661Z <VeraController:null> Module VeraController v21324 [latest-21331]2021-11-28T02:45:18.668Z <default:INFO> Structure#1 loading controller interface hubitat (HubitatController) [latest-21331]2021-11-28T02:45:18.676Z <HubitatController:null> Module HubitatController v21324 [latest-21331]2021-11-28T02:45:18.679Z <default:INFO> Structure#1 loading controller interface groups (DynamicGroupController) [latest-21331]2021-11-28T02:45:18.686Z <DynamicGroupController:null> Module DynamicGroupController v21331 [latest-21331]2021-11-28T02:45:18.688Z <default:INFO> Structure#1 loading controller interface weather (OWMWeatherController) [latest-21331]2021-11-28T02:45:18.693Z <OWMWeatherController:null> Module OWMWeatherController v21313
[latest-21331]2021-11-28T02:45:18.761Z <default:INFO> Starting controller HubitatController#hubitat [latest-21331]2021-11-28T02:45:18.782Z <default:INFO> Starting controller DynamicGroupController#groups [latest-21331]2021-11-28T02:45:18.784Z <default:NOTICE> Controller DynamicGroupController#groups is now online. [latest-21331]2021-11-28T02:45:18.785Z <default:INFO> Starting controller OWMWeatherController#weather
I see that the times are synchronized
But the array is still empty
Any instructions where I can look for something?
-
The recommended debugging for this would be to start unraveling your criteria and see what it produces. As a first step (don't do this, just read), I would remove the
filter_expression
and make sure that your selectors are producing the expected set of eligible devices. An easy way to do that is to simply put an "X" in front offilter_expression
(i.e. to make itXfilter_expression
), which changes the name of the key and hides it from the code that's looking for it. You could also comment it out, but that would require that you comment each subordinate line as well, which is more work and can be error-prone. Restart MSR after config changes, of course, and refreshes are also recommended (don't need to be hard refreshes).But, I found an error, and it's pretty subtle. For me, it logged one short line, so it would be easy to miss; I imagine you have it as well. But it's going to require a code change to fix, so I'll release another build later today. I'll also fix the doc issue you PM'd me about.
Also, don't forget that filtering by controller or capability is a good way to quickly remove "noise" from your Entities list.
-
I debugged removing filter_axpression entirely, and the variables are still empty. I'll wait for your version update and test again.
-
@toggledbits well done
Low Battery Devices charging perfect!
But there is a problem for "tripped", which repeated the same setting as "low_battery".
- id: groups enable: true implementation: DynamicGroupController name: Dynamic Group Controller config: groups: "low_battery": name: Low Battery Devices select: - include_capability: - battery_power filter_expression: > entity.attributes.battery_power.level < 0.3 "tripped": name: Tripped Devices select: - include_capability: - binary_sensor - motion_sensor filter_expression: > entity.attributes.binary_sensor.state == true or entity.attributes.motion_sensor.state == true
This is what is showing up in the log.
[latest-21332]2021-11-29T01:49:33.599Z <default:ERR> error updating dynamic group tripped: ReferenceError: Invalid reference to member state of null [latest-21332]2021-11-29T01:49:33.600Z <default:CRIT> ReferenceError: Invalid reference to member state of null ReferenceError: Invalid reference to member state of null at _run (C:\MSR\reactor\common\lexp.js:1369:31) at _run (C:\MSR\reactor\common\lexp.js:1233:34) at _run (C:\MSR\reactor\common\lexp.js:1290:44) at C:\MSR\reactor\common\lexp.js:1223:29 at Array.forEach (<anonymous>) at _run (C:\MSR\reactor\common\lexp.js:1222:28) at Object.run (C:\MSR\reactor\common\lexp.js:1564:22) at DynamicGroupController._update_group (C:\MSR\reactor\server\lib\DynamicGroupController.js:229:141) at C:\MSR\reactor\server\lib\DynamicGroupController.js:267:39 at Array.forEach (<anonymous>)
Would I have to include any additional information in the configuration to not have this problem with null?
-
In your expression, you are not guarding for entities that have
binary_sensor
but do not havemotion_sensor
, and vice versa. Use the coalescing member access operator?.
in the two sub-expressions. -
Perfect, solved, after putting the ?. in several places until I discovered how to use it correctly
"tripped": name: Tripped Devices select: - include_capability: - binary_sensor - motion_sensor filter_expression: > entity.attributes?.binary_sensor?.state == true or entity.attributes?.motion_sensor?.state == true
Boss, this thread started because I want to associate to each device an information of which group it would belong inside my system, external information that I will have to prepare manually, we started with the array, then we went to object, until you announce this new function.
What is the way now? At this moment my progress is to have in a more simplified way the ID of the devices that will understand a condition, now how in the case of Tripped I will be able to associate to the groups, the list assembled before? I already saw that I can have a global variable with the information, that this Dynamic instruction by the manual will be able to read.
Could you put together an example please?
Thanks.
-
@wmarcolin said in Multidimensional Array:
this thread started because I want to associate to each device an information of which group it would belong inside my system, external information that I will have to prepare manually
You still haven't stated why you want to do this, so in my view, we're on the Y of an X-Y problem. What you are asking seems an odd thing to do... error-prone, laborious, hard to maintain. If I understood why you think you need to do it, we might arrive at a better solution that works from existing functionality, or a clear requirement for a new feature. When I asked before for this clarification (and repair of the topic title), you replied with a restatement of your implementation question, not an explanation of the problem you are trying to solve (i.e. why you want to do the implementation you are asking about), just as you've again done now.
If I ask you how to ventilate an enclosed space that has small windows and a doorway that is usually left open, given no other information, what might you suggest?
Would you answer differently if I also told you in advance that the space will be a new module for the International Space Station?
-
Ok, I will try to explain what I want to do.
When using Vera, I in the Dashboard > My Modes panel determined which devices could trigger the house alarm in a given mode. With the change to Hubitat has no equal to Vera, and also not wanting to depend on the hub anymore, I want to have total control of the situation.
I thought about creating device groups (yes manually for now), i.e.: door group, window group, motion sensors, sensors like CO and water, and devices that should alarm and are not in the other groups.
So when I activate for example the night mode I want to trigger the alarm if the devices that are in the door group are tripped. If I enter Away mode, I want to join the devices' doors, windows, and motion. In Vacation mode, I put everything together and monitor if any device is tripped to trigger the alarm.
Another example, I can put all the liquid sensor devices in a water detector group, so when I evaluate the rule I refer to the group, and not to each device. You could say more there, just see who has leak_detector_state, but as we discussed before there is no standard, remember the discussion of the binary_sensor standard?
Another situation we could put together, the same way I put the door and window group together in Away mode, I could use it to if nothing is tripped, allow the central air in the house to work.
Trying to make a summary is, in a single table (beginning of this thread), I determine which group the device belongs to and do actions by group and not having to identify each device, we can say that it would be the equivalent in Vera as category_num and subcategory_num, and again this is from Vera, and they made mistakes by not respecting the table they created and both icon and device behavior not working, but it was interesting the grouping table (http://wiki.micasaverde.com/index.php/Luup_Device_Categories).
That is why even in this thread I thought if there was a way to add a group attribute to the devices in the MSR table, and by a set variable align this information, it did not work because you explained that if it does not come from the hub, there is no way to load the information.
Did I succeed in explaining the scenario?
Where I am at this moment:
- I created the object as you taught:
DeviceList = {
"vera>device_489": {group:"Door"},
"vera>device_432": {group:"Door"},
"hubitat>99": {group: "Window"},
"hubitat>15": {group: "Window"},
"vera>device_1672": {group:"Sensor"},
"vera>device_1867": {group:"Sensor"},
"vera>device_22": {group: "Security"},
"vera>device_1679": {group:"Security"},
"hubitat>1": {group: "Security"},
"vera>device_1822": {group:"Security"}
} - Now with Dynamic I have it easy that it is tripped;
- I have a global variable that is loaded in each mode, DeviceAlarm, which is an object that I put who will be monitored in the activated mode, for example, set variable DeviceAlarm = ${{["Door", "Window"]}}.
What I don't know how to do now, I don't dominate the programming/language, is how to ask and/or put together Dynamic's tripped + DeviceList object + DeviceAlarm + Device name.
What do I look for? Who is Tripped (Dynamic Tripped), with the parameter filter (DeviceAlarm), in the device list (Object DeviceList)? Give me the device name in one variable, and a second variable the list of Groups that are tripped. In this second answer, I pass the list of what I want to look at in DeviceAlarm, but it should only return what is tripped.
Sorry for the bother, and you are right that I am joining topics from several different threads. I'm just trying to have something that could make the operation easier, and optimize the code in my view.
Thanks.
- I created the object as you taught:
-
@wmarcolin Hubitat has modes, and it has the Hubitat Safety Monitor (HSM), both of which are supported by Reactor. HSM can set arming based on detection level, so it's worth looking into.
If you still want to keep it all off hub, I would simply make groups:
- door_sensors:
include_capability: door_sensor
- leak_sensors:
include_capability: leak_detector
- motion_sensors:
include_capability: motion_sensor
The create "tripped" versions of each:
- door_sensors_tripped:
include_group: door_sensors
,filter_expr: entity.attributes.door_sensor.state
- leak_sensors_tripped:
include_group: leak_sensors
,filter_expr: entity.attributes.leak_detector.state
- etc.
Creating these extra tripped groups does two things for you: (1) it isolates the expression to the capability, so you don't have to worry about
motion_sensor.state
vsleak_detector.state
within a single group, the group is homogenous; and (2) by segmenting the devices to type, you more easily make the conditions for what devices are active in what security mode.Then in your alarm rules for Night, Away, Vacation modes, you check if the tripped group for each group you are interested in for that mode is empty or not. So for Night, you would only be checking door_sensors_tripped, while for Away it will be the tripped door, window, and motion groups.
(ignore my group name -- I just picked a group I had to illustrate how the condition may be set up)
You don't need any variables at all (global or otherwise) to do what's described using dynamic groups.
- door_sensors:
-
@toggledbits first of all thank you for the quick response, and this may be one way.
However (sorry), I see a disadvantage, we use the case of sensors with the attribute door_sensor they are valid for access doors to the house, but are also for windows (first and second floor of the house, and the second floor is not turned on in night mode), and the same attribute has the internal door sensors, which in this case I use for air conditioning management (open door turns off the air).
Another example would be the motion_sensor, I have internal and external sensors, in night mode the external ones turn on the garage and entrance lights, if I group everything by the attribute a movement inside the house would also trigger.
This way your proposal is very valid, but there should be a way to dismember the groups, i.e. door_sensors_group1 (external door), door_sensors_group2 (window 1), door_sensor_group3 (internal door).... that's why I thought about the table that could specify each device and not use an attribute that generalizes the devices.
This way your proposal is very valid, but there should be a way to dismember the groups, i.e. door_sensors_group1 (external door), door_sensors_group2 (window 1), door_sensor_group3 (internal door).... that's why I thought about the table that could specify each device and not use an attribute that generalizes the devices.
I don't know if there could be something in these instructions referring to the global object we commented on DeviceList.
door_sensors: include_capability: door_sensor %(#ff0000)[contained in DeviceList = "Door External".]
or would it be something in this instruction
door_sensors_tripped: include_group: door_sensors, filter_expr: entity.attributes.door_sensor.state %(#ff0000)[contained in DeviceList = "Door External".]
(please don't laugh at my coding, I said I don't know it))
The excellent thing is that we are going to take more automatic paths as you are commenting.
Despite not wanting to depend on a hub, I looked at the HSM option, I see that it would be possible to create the groups I have commented, now I did not understand your comment that the MSR would talk to the HSM.
In HSM the actions I see are alert by text, audio, siren or light. The way, in this case, would be to create a virtual device connected with HSM, and this one the MSR would monitor to take action?
In the Apps that I set up the MSR, I don't see the option to select on device the action I created in the HSM. I have the option Allow control of HSM activated. Do I have to configure anything to show up on the MSR?
Fact that I will not make Hubitat take action, who performs action in my solution is the MSR.
-
@wmarcolin said in Multidimensional Array:
I don't know if there could be something in these instructions referring to the global object we commented on DeviceList.
door_sensors: include_capability: door_sensor contained in DeviceList = "Door External".No, you can't refer to global variables in a group filter expression.
Make as many groups as you need/want.
@wmarcolin said in Multidimensional Array:
In the Apps that I set up the MSR, I don't see the option to select on device the action I created in the HSM. I have the option Allow control of HSM activated. Do I have to configure anything to show up on the MSR?
Find the entity called "Safety Monitor" in the Entities list (hint: use the filters; it will come from your Hubitat controller, and it will have capability
x_hubitat_hsm
, as well as that very distinct name, so lots of ways to find it). -
Well, you put me to think a lot, I'm reviewing all the logic and I think progressing. You could have a video lesson on Creating Automations > Expressions I am looking to meet this with trial and error. I just tested this on Groups and it worked perfectly, it will help:
"internal_move": name: Internal Move Devices select: - include_entity: - "vera>device_1679" - "vera>device_1683" - "vera>device_1797" - "hubitat>1" - "hubitat>14" filter_expression: > entity.attributes?.motion_sensor?.state == true
Now from your last comment about the MSR visualizing the HSM, I really don't know what I have to do, the Safe Monitor you commented appears, but it is all Disarmed.
But in the HSM in the hub the rules are created, activated, and even with action alert activated.
Any recommendations on what I should do?
Thanks,
-