Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Multidimensional Array
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@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.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
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.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
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.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
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?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
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.
Multi-System Reactor
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
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.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
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?
Multi-System Reactor
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor

Multidimensional Array

Scheduled Pinned Locked Moved Multi-System Reactor
28 Posts 3 Posters 2.9k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • wmarcolinW wmarcolin

    Hi @toggledbits it is possible to have an array in the following way

    ["Window 1"]["Status On"]
    ["Window 2"]["Status On"]
    ["Window 3"]["Status Off"]
    ["Window 4"]["Status On"]

    That is, bidirectional.

    How would this array be loaded? Normally we use Variable = ${{ ["Window 1", "Window 2", "Window 3", "Window 4"] }}, how would the array pair be loaded?.

    Then the use, how would be a looping where I want to ask who has "Status On" and it returns me a new array with the part 1, that is the list of "Window"?

    Or another search, I provide the information of the content of part 1, as "Window 2" and it would return me an array with the part 2 "Satus On".

    Is it possible to have something like this?

    Could you give the examples?

    Thanks.

    toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by toggledbits
    #5

    @wmarcolin I smell an X-Y problem, but I'll go on...

    I don't know what "bidirectionally" means in this context. Do you mean "two dimensional?" Bidirectional refers to movement, for example, forwards and backwards, or up and down, which is a different thing.

    A couple of minor comments to @Elcid 's response:

    ${{[["Window 1","Status On"],["Window 2","Status On"],["Window 3","Status Off"],["Window 4","Status On"]]}}

    Note that this is substitution syntax, not expression syntax when defining a variable. Adjust accordingly.

    each val in testarray : if val[1] === "Status On" then val[0] endif

    There is no === operator in the expression language, it's just ==

    (each val in testarray : if val[0] === "Window 1" then val[1] endif)[0]

    This is better written as first ... of ..., since you only want the one element (which by implication here the key "Window 1" must be unique in the array), and there's no need to keep searching through the array once you've found it (wastes CPU cycles).

    But about that uniqueness for "Window 1"... this is the real meat of my response:

    If the first element of each subarray (row) is unique, then using a two-dimensional array is inefficient (i.e. doable, but not the best choice). Where unique values are present, an object containing key/value pairs gives immediate random access to any "element", without iteration:

    devices = {
        "lamp1": "on",
        "lamp2": "off",
        "lamp3": "on"
    }
    

    In this example, we can quickly determine the status of any lamp without iteration: devices.lamp2 will give us off.

    This can be further broken down with additional data: each value in the key/value pairs of the object can be any data type, so they can be an array or object themselves:

    devices = {
        "lamp1": {
            "status": "on",
            "room": 0
        }
        "lamp2": { "status": "off", "room": 0 }
        "lamp3": { "status": "on", "room": 2 }
    }
    

    We can again quickly get to the state of lamp2 using devices.lamp2.status (result off again). Using devices.lamp3.room tells us that lamp3 is in room 2. Note that in the example code above, I have shown lamp1 with a typical (JSON-style) fully indented with line breaks for readability, but lamp2 and lamp3 are in a more compact form. Whitespace (including newlines) are not significant to the syntax. Use them for readability if you wish, or leave them out for compactness if that's acceptable.

    When you must search within the values, you can still use iteration. Find the devices in room 0:

        each dev,id in devices: dev.room==0 ? id : null
    

    By using each dev,id, the iterator will provide both the value and the key for each pair in the object. That is, on the first iteration, dev will contain our subobject (itself with keys status and room) for lamp1, and id will contain lamp1; on the second iteration, the subobject for lamp2 is given in dev, and id is lamp2, and so on. The result of the iteration in this case is an array of IDs of objects in room 0: ["lamp1","lamp2"]; you could also modify the iteration to return the data objects (using dev), if that was more efficient for your later use of this expression's result.

    Find the first device that is "off":

        first dev,id of devices: dev.status=="off" ? id : null
    

    Adding new devices after the initialization is also easy:

        devices.lamp4 = { "status": "on", "room": 2 }
    

    But this is all data storage theory, and details of an implementation for a problem that apparently hasn't been stated. We need to know what you are really trying to do, if you are asking for help getting it done. As I said, where we stand right now, this seems very X-Y-ish. The post title is also poor quality, and the head post itself breaks a couple of the posting guidelines.

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    wmarcolinW ElcidE 2 Replies Last reply
    0
    • toggledbitsT toggledbits

      @wmarcolin I smell an X-Y problem, but I'll go on...

      I don't know what "bidirectionally" means in this context. Do you mean "two dimensional?" Bidirectional refers to movement, for example, forwards and backwards, or up and down, which is a different thing.

      A couple of minor comments to @Elcid 's response:

      ${{[["Window 1","Status On"],["Window 2","Status On"],["Window 3","Status Off"],["Window 4","Status On"]]}}

      Note that this is substitution syntax, not expression syntax when defining a variable. Adjust accordingly.

      each val in testarray : if val[1] === "Status On" then val[0] endif

      There is no === operator in the expression language, it's just ==

      (each val in testarray : if val[0] === "Window 1" then val[1] endif)[0]

      This is better written as first ... of ..., since you only want the one element (which by implication here the key "Window 1" must be unique in the array), and there's no need to keep searching through the array once you've found it (wastes CPU cycles).

      But about that uniqueness for "Window 1"... this is the real meat of my response:

      If the first element of each subarray (row) is unique, then using a two-dimensional array is inefficient (i.e. doable, but not the best choice). Where unique values are present, an object containing key/value pairs gives immediate random access to any "element", without iteration:

      devices = {
          "lamp1": "on",
          "lamp2": "off",
          "lamp3": "on"
      }
      

      In this example, we can quickly determine the status of any lamp without iteration: devices.lamp2 will give us off.

      This can be further broken down with additional data: each value in the key/value pairs of the object can be any data type, so they can be an array or object themselves:

      devices = {
          "lamp1": {
              "status": "on",
              "room": 0
          }
          "lamp2": { "status": "off", "room": 0 }
          "lamp3": { "status": "on", "room": 2 }
      }
      

      We can again quickly get to the state of lamp2 using devices.lamp2.status (result off again). Using devices.lamp3.room tells us that lamp3 is in room 2. Note that in the example code above, I have shown lamp1 with a typical (JSON-style) fully indented with line breaks for readability, but lamp2 and lamp3 are in a more compact form. Whitespace (including newlines) are not significant to the syntax. Use them for readability if you wish, or leave them out for compactness if that's acceptable.

      When you must search within the values, you can still use iteration. Find the devices in room 0:

          each dev,id in devices: dev.room==0 ? id : null
      

      By using each dev,id, the iterator will provide both the value and the key for each pair in the object. That is, on the first iteration, dev will contain our subobject (itself with keys status and room) for lamp1, and id will contain lamp1; on the second iteration, the subobject for lamp2 is given in dev, and id is lamp2, and so on. The result of the iteration in this case is an array of IDs of objects in room 0: ["lamp1","lamp2"]; you could also modify the iteration to return the data objects (using dev), if that was more efficient for your later use of this expression's result.

      Find the first device that is "off":

          first dev,id of devices: dev.status=="off" ? id : null
      

      Adding new devices after the initialization is also easy:

          devices.lamp4 = { "status": "on", "room": 2 }
      

      But this is all data storage theory, and details of an implementation for a problem that apparently hasn't been stated. We need to know what you are really trying to do, if you are asking for help getting it done. As I said, where we stand right now, this seems very X-Y-ish. The post title is also poor quality, and the head post itself breaks a couple of the posting guidelines.

      wmarcolinW Offline
      wmarcolinW Offline
      wmarcolin
      wrote on last edited by wmarcolin
      #6

      @toggledbits

      Hi Patrick!

      %(#ff0000)[Again a Master Class on how to do the right things.]

      My use case is that I want to associate each device in my installation with an identification of which group it belongs to (door, window, security, light...).

      The group I will have to make the manual list (I think), so the first step of var1, I understand is the list I have to assemble, and whenever I have a new device, I update this list manually.

      386f4215-433c-4e29-81ea-159c7fca255a-image.png

      Just a note master, at the beginning of your example, I had to put the comma at each element of the array

      I reproduced your examples to test, and I just can't find the error in the example of the first (var4).

      b42bc82d-2277-419e-ac93-a5ad94058b84-image.png

      Now comes the use, to see device names and which group they are in, or even to search the groups. My next step, is to manage when a device has the true state of its sensor, to take actions such as triggering an action/alarm/siren/message according to the group the device is part of.

      7b1bf8f9-184e-4cbd-a7dc-34ffb1b61ab1-image.png

      If you can see, I am looking to work around not using (yet) a database, which we have had in other trackers to empower the information from the devices.

      Now exploring the Master, sorry 😁

      In your last example, you explain how to add one more row to the array, one more element, perfect. Now, is it possible to add another column to the existing array? For example, with the array I created, add a column that already stores the device name? A loop that looks at the devid and then looks at the device name attribute?

      I was forgetting, how do I change the contents of the array, is it possible with Set Variable? I want to change for example the group from DevWindow to DevDoor for one element.

      Thanks.

      toggledbitsT 1 Reply Last reply
      0
      • wmarcolinW wmarcolin

        @toggledbits

        Hi Patrick!

        %(#ff0000)[Again a Master Class on how to do the right things.]

        My use case is that I want to associate each device in my installation with an identification of which group it belongs to (door, window, security, light...).

        The group I will have to make the manual list (I think), so the first step of var1, I understand is the list I have to assemble, and whenever I have a new device, I update this list manually.

        386f4215-433c-4e29-81ea-159c7fca255a-image.png

        Just a note master, at the beginning of your example, I had to put the comma at each element of the array

        I reproduced your examples to test, and I just can't find the error in the example of the first (var4).

        b42bc82d-2277-419e-ac93-a5ad94058b84-image.png

        Now comes the use, to see device names and which group they are in, or even to search the groups. My next step, is to manage when a device has the true state of its sensor, to take actions such as triggering an action/alarm/siren/message according to the group the device is part of.

        7b1bf8f9-184e-4cbd-a7dc-34ffb1b61ab1-image.png

        If you can see, I am looking to work around not using (yet) a database, which we have had in other trackers to empower the information from the devices.

        Now exploring the Master, sorry 😁

        In your last example, you explain how to add one more row to the array, one more element, perfect. Now, is it possible to add another column to the existing array? For example, with the array I created, add a column that already stores the device name? A loop that looks at the devid and then looks at the device name attribute?

        I was forgetting, how do I change the contents of the array, is it possible with Set Variable? I want to change for example the group from DevWindow to DevDoor for one element.

        Thanks.

        toggledbitsT Offline
        toggledbitsT Offline
        toggledbits
        wrote on last edited by toggledbits
        #7

        @wmarcolin Well, I'm almost ready to release my first version of dynamic groups... still hashing out a few details. If you urgently need to do all this work, it's certainly a good opportunity to break your forehead on some sticky problems (I'm always in favor of experimentation and pushing limits).

        First, having var1 be an expression that does an assignment to devices isn't necessary. Just call your variable devices and put in the rest of the expression after the = in your screen shot and be done with it. You can also set up your devices structure more simply. I'm not sure what the extra dev001 and dev002 identifiers are doing for you, but you can (and probably should) just use the entity canonical IDs directly. It will make everything much simpler. Here's is the expression for the devices variable:

        {
            "hubitat>15": { group: "DevWindow" },
            "vera>device_1866": { group: "DevDoor" },
            ...etc...
        }
        

        Also, if group is the only data you are keeping, there is no value to creating a subobject to keep it, just make the group name be the value of the device's key/ID. But I'll continue with the structure you're trying to use...

        Anyway, by simplifying the structure of devices, here's what it looks like and how it changes your first three expressions:

        340a4917-f984-4a19-9112-39e53f13265e-image.png

        Looking at var2, we need to use quoted identifiers because a canonical ID contains a character (>) that cannot be used in an identifier, so this devices.hubitat>15.group is not valid. The quoted identifier syntax is context["complexKey"] as shown.

        The var3 expression is simpler, because we're not looking through the extra layer of indirection your structure had introduced, we're looking directly as our descriptive subobjects.

        The var4 expression is an error in the syntax on my part. The correct syntax is shown, but I've had to embellish a bit here (next release of Reactor for you, so it won't work until I publish and you update).

        But here's the important part...

        As for the rest of it, you're making it unnecessarily hard, I think, because entity.primary_value will give you the value of the primary attribute, so you don't really need to care what capability that comes from and go to the work of classifying devices in expressions to try to make that work. There's an easier way.

        Based on what I see here, now that we understand you are actually trying to accomplish, what you really need to do is set those primary attributes in local_hubitat_devices.yaml, and skip all of the devices complexity you are creating here, and just use the primary_value from the entity in your sort/search expressions.

        To do the overrides in local_hubitat_devices.yaml:

        entities:
          # Entry shows how an entity can have a service added and its name forced
          "hubitat>76":
            # Name override
            name: "Attic Environmental Sensor"
            #
            # List of capabilities to add to this device (array)
            capabilities:
              - SomeAdditionalCapability
              - AnotherAdditionalCapability
            #
            # Assign primary attribute for this device
            primary_attribute: "temperature_sensor.value"
          "hubitat>178":
            primary_attribute: "x_hubitat_extra_attributes.batteryLastReplaced"
        

        Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

        wmarcolinW 1 Reply Last reply
        0
        • toggledbitsT toggledbits

          @wmarcolin Well, I'm almost ready to release my first version of dynamic groups... still hashing out a few details. If you urgently need to do all this work, it's certainly a good opportunity to break your forehead on some sticky problems (I'm always in favor of experimentation and pushing limits).

          First, having var1 be an expression that does an assignment to devices isn't necessary. Just call your variable devices and put in the rest of the expression after the = in your screen shot and be done with it. You can also set up your devices structure more simply. I'm not sure what the extra dev001 and dev002 identifiers are doing for you, but you can (and probably should) just use the entity canonical IDs directly. It will make everything much simpler. Here's is the expression for the devices variable:

          {
              "hubitat>15": { group: "DevWindow" },
              "vera>device_1866": { group: "DevDoor" },
              ...etc...
          }
          

          Also, if group is the only data you are keeping, there is no value to creating a subobject to keep it, just make the group name be the value of the device's key/ID. But I'll continue with the structure you're trying to use...

          Anyway, by simplifying the structure of devices, here's what it looks like and how it changes your first three expressions:

          340a4917-f984-4a19-9112-39e53f13265e-image.png

          Looking at var2, we need to use quoted identifiers because a canonical ID contains a character (>) that cannot be used in an identifier, so this devices.hubitat>15.group is not valid. The quoted identifier syntax is context["complexKey"] as shown.

          The var3 expression is simpler, because we're not looking through the extra layer of indirection your structure had introduced, we're looking directly as our descriptive subobjects.

          The var4 expression is an error in the syntax on my part. The correct syntax is shown, but I've had to embellish a bit here (next release of Reactor for you, so it won't work until I publish and you update).

          But here's the important part...

          As for the rest of it, you're making it unnecessarily hard, I think, because entity.primary_value will give you the value of the primary attribute, so you don't really need to care what capability that comes from and go to the work of classifying devices in expressions to try to make that work. There's an easier way.

          Based on what I see here, now that we understand you are actually trying to accomplish, what you really need to do is set those primary attributes in local_hubitat_devices.yaml, and skip all of the devices complexity you are creating here, and just use the primary_value from the entity in your sort/search expressions.

          To do the overrides in local_hubitat_devices.yaml:

          entities:
            # Entry shows how an entity can have a service added and its name forced
            "hubitat>76":
              # Name override
              name: "Attic Environmental Sensor"
              #
              # List of capabilities to add to this device (array)
              capabilities:
                - SomeAdditionalCapability
                - AnotherAdditionalCapability
              #
              # Assign primary attribute for this device
              primary_attribute: "temperature_sensor.value"
            "hubitat>178":
              primary_attribute: "x_hubitat_extra_attributes.batteryLastReplaced"
          
          wmarcolinW Offline
          wmarcolinW Offline
          wmarcolin
          wrote on last edited by
          #8

          @toggledbits

          Hi Master!

          Wow, good news that we will have in the MSR capacity, I am your test guy if you need a tester. And I'm aligned with you, I like to explore, learn, go to the limit, even with knowledge limitations, I seek to explore.

          I will keep the array structure that can put more dimensions, surely I will explore.

          Aligned from var4, I repeated your instruction and it really follows the syntax error, no problem for now, as I said we are learning and testing.

          Master I am trying, to follow the correct path, instead of going all the way around creating the array. I edited the file local_hubitat_devices.yaml to test with these 4 devices, and I see that in the capabilities now appears the DeviceGroup, but I don't see in the attributes, or way to add the value.

          # This file has local definitions/overrides for Hubitat devices.
          ---
          entities:
            # Entry shows how an entity can have a capability added and its name forced
            "hubitat>NNN":
              # Name override
              #name: "Attic Environmental Sensor"
              #
              # List of capabilities to add to this device (array)
              #capabilities:
              #  - Tone
              #
              # Assign primary attribute for this device
              #primary_attribute: "temperature_sensor.value"
            "hubitat>15":
              capabilities:
                - DeviceGroup
              group: "Window"
            "hubitat>67":
              capabilities:
                - DeviceGroup
              group: "Window"
            "hubitat>98":
              capabilities:
                - DeviceGroup
              group: "Door"
            "hubitat>99":
              capabilities:
                - DeviceGroup
              group: "Door"
          
          

          5568b50f-ca49-4312-a31d-b5389676d1a3-image.png

          09834c78-b201-4a80-8033-50ebe0d0e371-image.png

          Now I have a question, can I use this same file for the Vera devices? Following the same path?

          Thanks.

          1 Reply Last reply
          0
          • toggledbitsT Offline
            toggledbitsT Offline
            toggledbits
            wrote on last edited by
            #9

            You can't make up data. Just because you assign the capability DeviceGroup to the device, that doesn't mean you get to assign the attributes (group) that may be associated with that capability. Hubitat would have to provide the group data from its side -- the values for that attribute still have to come from Hubitat. And that probably won't be happening, because DeviceGroup does not appear to be a valid Hubitat capability.

            Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

            wmarcolinW 1 Reply Last reply
            0
            • toggledbitsT toggledbits

              You can't make up data. Just because you assign the capability DeviceGroup to the device, that doesn't mean you get to assign the attributes (group) that may be associated with that capability. Hubitat would have to provide the group data from its side -- the values for that attribute still have to come from Hubitat. And that probably won't be happening, because DeviceGroup does not appear to be a valid Hubitat capability.

              wmarcolinW Offline
              wmarcolinW Offline
              wmarcolin
              wrote on last edited by
              #10

              @toggledbits I understand, so in this case for now is to use the array resource that we discussed before, until you publish the news.

              f0a66684-76aa-4340-992f-bfd1d3900bfc-image.png

              Anyway thanks for one more class of knowledge.

              902b8160-4309-49fa-ae87-847684ccae9f-image.png

              1 Reply Last reply
              0
              • toggledbitsT toggledbits

                @wmarcolin I smell an X-Y problem, but I'll go on...

                I don't know what "bidirectionally" means in this context. Do you mean "two dimensional?" Bidirectional refers to movement, for example, forwards and backwards, or up and down, which is a different thing.

                A couple of minor comments to @Elcid 's response:

                ${{[["Window 1","Status On"],["Window 2","Status On"],["Window 3","Status Off"],["Window 4","Status On"]]}}

                Note that this is substitution syntax, not expression syntax when defining a variable. Adjust accordingly.

                each val in testarray : if val[1] === "Status On" then val[0] endif

                There is no === operator in the expression language, it's just ==

                (each val in testarray : if val[0] === "Window 1" then val[1] endif)[0]

                This is better written as first ... of ..., since you only want the one element (which by implication here the key "Window 1" must be unique in the array), and there's no need to keep searching through the array once you've found it (wastes CPU cycles).

                But about that uniqueness for "Window 1"... this is the real meat of my response:

                If the first element of each subarray (row) is unique, then using a two-dimensional array is inefficient (i.e. doable, but not the best choice). Where unique values are present, an object containing key/value pairs gives immediate random access to any "element", without iteration:

                devices = {
                    "lamp1": "on",
                    "lamp2": "off",
                    "lamp3": "on"
                }
                

                In this example, we can quickly determine the status of any lamp without iteration: devices.lamp2 will give us off.

                This can be further broken down with additional data: each value in the key/value pairs of the object can be any data type, so they can be an array or object themselves:

                devices = {
                    "lamp1": {
                        "status": "on",
                        "room": 0
                    }
                    "lamp2": { "status": "off", "room": 0 }
                    "lamp3": { "status": "on", "room": 2 }
                }
                

                We can again quickly get to the state of lamp2 using devices.lamp2.status (result off again). Using devices.lamp3.room tells us that lamp3 is in room 2. Note that in the example code above, I have shown lamp1 with a typical (JSON-style) fully indented with line breaks for readability, but lamp2 and lamp3 are in a more compact form. Whitespace (including newlines) are not significant to the syntax. Use them for readability if you wish, or leave them out for compactness if that's acceptable.

                When you must search within the values, you can still use iteration. Find the devices in room 0:

                    each dev,id in devices: dev.room==0 ? id : null
                

                By using each dev,id, the iterator will provide both the value and the key for each pair in the object. That is, on the first iteration, dev will contain our subobject (itself with keys status and room) for lamp1, and id will contain lamp1; on the second iteration, the subobject for lamp2 is given in dev, and id is lamp2, and so on. The result of the iteration in this case is an array of IDs of objects in room 0: ["lamp1","lamp2"]; you could also modify the iteration to return the data objects (using dev), if that was more efficient for your later use of this expression's result.

                Find the first device that is "off":

                    first dev,id of devices: dev.status=="off" ? id : null
                

                Adding new devices after the initialization is also easy:

                    devices.lamp4 = { "status": "on", "room": 2 }
                

                But this is all data storage theory, and details of an implementation for a problem that apparently hasn't been stated. We need to know what you are really trying to do, if you are asking for help getting it done. As I said, where we stand right now, this seems very X-Y-ish. The post title is also poor quality, and the head post itself breaks a couple of the posting guidelines.

                ElcidE Offline
                ElcidE Offline
                Elcid
                wrote on last edited by Elcid
                #11

                @toggledbits said in Multidimensional Array:

                There is no === operator in the expression language, it's just ==

                Not according to your doc's.
                Screenshot_20211126-211238.png

                Also used in a test expression and working.

                Screenshot_20211126-211533.png

                Noted used "in" rather than "of" as I thought he wanted a 2D array not a object/dictionary.

                wmarcolinW toggledbitsT 2 Replies Last reply
                0
                • ElcidE Elcid

                  @toggledbits said in Multidimensional Array:

                  There is no === operator in the expression language, it's just ==

                  Not according to your doc's.
                  Screenshot_20211126-211238.png

                  Also used in a test expression and working.

                  Screenshot_20211126-211533.png

                  Noted used "in" rather than "of" as I thought he wanted a 2D array not a object/dictionary.

                  wmarcolinW Offline
                  wmarcolinW Offline
                  wmarcolin
                  wrote on last edited by
                  #12

                  @elcid actually, for the final search result, it was easier with object/dictionary, but it could have been done by array as well. Thanks, you also taught me how to make an array that will be useful for sure, it always is.

                  1 Reply Last reply
                  0
                  • ElcidE Elcid

                    @toggledbits said in Multidimensional Array:

                    There is no === operator in the expression language, it's just ==

                    Not according to your doc's.
                    Screenshot_20211126-211238.png

                    Also used in a test expression and working.

                    Screenshot_20211126-211533.png

                    Noted used "in" rather than "of" as I thought he wanted a 2D array not a object/dictionary.

                    toggledbitsT Offline
                    toggledbitsT Offline
                    toggledbits
                    wrote on last edited by toggledbits
                    #13

                    @elcid said in Multidimensional Array:

                    Not according to your doc's.

                    You are correct, I'm suffering from holiday brain-fade.

                    @wmarcolin Version 21331 just released has the first release of dynamic groups. It also includes a syntax enhancement to the expression first...in statement to allow a result expression, so it can return something other than what it finds (i.e. it can perform operations on what it finds and return that as a result). This is useful for your var4 of this post, which should be first dev,id of devices: dev.group=="DevDoor": id to give you the ID of the first matching device. But again, I think the combination of primary attribute assignment and dynamic groups is going to be the best way to solve this.

                    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                    wmarcolinW 2 Replies Last reply
                    0
                    • toggledbitsT toggledbits

                      @elcid said in Multidimensional Array:

                      Not according to your doc's.

                      You are correct, I'm suffering from holiday brain-fade.

                      @wmarcolin Version 21331 just released has the first release of dynamic groups. It also includes a syntax enhancement to the expression first...in statement to allow a result expression, so it can return something other than what it finds (i.e. it can perform operations on what it finds and return that as a result). This is useful for your var4 of this post, which should be first dev,id of devices: dev.group=="DevDoor": id to give you the ID of the first matching device. But again, I think the combination of primary attribute assignment and dynamic groups is going to be the best way to solve this.

                      wmarcolinW Offline
                      wmarcolinW Offline
                      wmarcolin
                      wrote on last edited by
                      #14

                      @toggledbits Hi!

                      Perfect, you have totally changed the command.

                      first dev,id in var1 with dev.group=="DevDoor": dev.devid

                      I'm going to study the dynamic group, because even though I can compare object or array contents, the usage is horrible. It's very difficult to validate an array inside another one, or to make combined selections.

                      Well, I don't really know the language, so I'm having a hard time. Let's see if the dynamic groups can make something that should be simple easier.

                      I'll return tomorrow with my experiences 🙂

                      1 Reply Last reply
                      0
                      • toggledbitsT toggledbits

                        @elcid said in Multidimensional Array:

                        Not according to your doc's.

                        You are correct, I'm suffering from holiday brain-fade.

                        @wmarcolin Version 21331 just released has the first release of dynamic groups. It also includes a syntax enhancement to the expression first...in statement to allow a result expression, so it can return something other than what it finds (i.e. it can perform operations on what it finds and return that as a result). This is useful for your var4 of this post, which should be first dev,id of devices: dev.group=="DevDoor": id to give you the ID of the first matching device. But again, I think the combination of primary attribute assignment and dynamic groups is going to be the best way to solve this.

                        wmarcolinW Offline
                        wmarcolinW Offline
                        wmarcolin
                        wrote on last edited by
                        #15

                        @toggledbits

                        Hi Patrick!
                        I don't know if I'm doing something wrong, but I followed the following steps to use DynamicGroupController.

                        1. Stopped the MSR
                        2. Compared the reactor configuration file
                        3. Added the new Groups instruction, the one in the file is almost the same as the manual, and below is the one I set up.
                          - 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.35
                                "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
                        
                        
                        1. I restarted MSR + Tools Restart + Crtl+F5 🙂
                        2. Search in Entities and I see that they are created, but without content

                        7e621920-da8d-439e-b2b0-7018f0720fd1-image.png

                        5e7fafc0-8c76-4868-95ce-4a4722cb6466-image.png

                        1. Check if they are available for action, yes but also without content.

                        332057ab-7718-4cc2-9253-dc5d33e2dd58-image.png

                        1. As the master instructed, let's go to the log file.
                        [latest-21331]2021-11-27T21:13:45.136Z <default:INFO> OWMWeatherController#weather done; 1 locations, 0 failed
                        [latest-21331]2021-11-27T21:13:45.137Z <default:NOTICE> Controller OWMWeatherController#weather is now online.
                        [latest-21331]2021-11-27T21:13:46.538Z <VeraController:NOTICE> Controller VeraController#vera is now online.
                        [latest-21331]2021-11-27T21:13:46.540Z <default:ERR> error updating dynamic group low_battery_entries: Error: Invalid selector key
                        [latest-21331]2021-11-27T21:13:46.541Z <default:CRIT> Error: Invalid selector key
                        Error: Invalid selector key
                            at DynamicGroupController._select (C:\MSR\reactor\server\lib\DynamicGroupController.js:260:23)
                            at DynamicGroupController._update_group (C:\MSR\reactor\server\lib\DynamicGroupController.js:193:45)
                            at C:\MSR\reactor\server\lib\DynamicGroupController.js:243:38
                            at Array.forEach (<anonymous>)
                            at DynamicGroupController._update (C:\MSR\reactor\server\lib\DynamicGroupController.js:240:95)
                            at C:\MSR\reactor\server\lib\DynamicGroupController.js:150:42
                            at processTicksAndRejections (node:internal/process/task_queues:96:5)
                        [latest-21331]2021-11-27T21:13:46.543Z <default:ERR> error updating dynamic group tripped_entries: Error: Invalid selector key
                        [latest-21331]2021-11-27T21:13:46.544Z <default:CRIT> Error: Invalid selector key
                        Error: Invalid selector key
                            at DynamicGroupController._select (C:\MSR\reactor\server\lib\DynamicGroupController.js:260:23)
                            at DynamicGroupController._update_group (C:\MSR\reactor\server\lib\DynamicGroupController.js:193:45)
                            at C:\MSR\reactor\server\lib\DynamicGroupController.js:243:38
                            at Array.forEach (<anonymous>)
                            at DynamicGroupController._update (C:\MSR\reactor\server\lib\DynamicGroupController.js:240:95)
                            at C:\MSR\reactor\server\lib\DynamicGroupController.js:150:42
                            at processTicksAndRejections (node:internal/process/task_queues:96:5)
                        [latest-21331]2021-11-27T21:13:46.544Z <app:NOTICE> Starting HTTP server and API...
                        [latest-21331]2021-11-27T21:13:46.552Z <app:NOTICE> Starting Reaction Engine...
                        
                        

                        Well, I found this error, and obviously, I don't know how to solve it. What I did? I reinstalled the MSR, using only the config and storage directory, and the result is the same.

                        1 Reply Last reply
                        0
                        • toggledbitsT Offline
                          toggledbitsT Offline
                          toggledbits
                          wrote on last edited by
                          #16

                          The groups would be empty if there were no tripped or low battery devices in their respective groups, so that's not all conclusive; it may be perfectly correct. The groups at least appear to be correct, for empty groups (no entities matched).

                          The time stamps in your log snippet are unrelated to the time stamp on the entities, so I can't really draw any conclusions from that either. If you post logs, make sure you are posting logs where the time stamps align to the problem you're reporting.

                          On your conditions, you can't compare an array to an empty string; that's not a valid test.

                          Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                          wmarcolinW 1 Reply Last reply
                          0
                          • toggledbitsT toggledbits

                            The groups would be empty if there were no tripped or low battery devices in their respective groups, so that's not all conclusive; it may be perfectly correct. The groups at least appear to be correct, for empty groups (no entities matched).

                            The time stamps in your log snippet are unrelated to the time stamp on the entities, so I can't really draw any conclusions from that either. If you post logs, make sure you are posting logs where the time stamps align to the problem you're reporting.

                            On your conditions, you can't compare an array to an empty string; that's not a valid test.

                            wmarcolinW Offline
                            wmarcolinW Offline
                            wmarcolin
                            wrote on last edited by wmarcolin
                            #17

                            @toggledbits

                            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.

                            6bf50285-7862-4ba5-acd6-2c9eff9a0aec-image.png

                            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

                            94523c4a-dd1f-4bc6-858a-351f010e4028-image.png

                            But the array is still empty

                            Any instructions where I can look for something?

                            1 Reply Last reply
                            0
                            • toggledbitsT Offline
                              toggledbitsT Offline
                              toggledbits
                              wrote on last edited by toggledbits
                              #18

                              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 of filter_expression (i.e. to make it Xfilter_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.

                              Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                              wmarcolinW 2 Replies Last reply
                              0
                              • toggledbitsT toggledbits

                                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 of filter_expression (i.e. to make it Xfilter_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.

                                wmarcolinW Offline
                                wmarcolinW Offline
                                wmarcolin
                                wrote on last edited by
                                #19

                                @toggledbits

                                I debugged removing filter_axpression entirely, and the variables are still empty. I'll wait for your version update and test again.

                                1 Reply Last reply
                                0
                                • toggledbitsT toggledbits

                                  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 of filter_expression (i.e. to make it Xfilter_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.

                                  wmarcolinW Offline
                                  wmarcolinW Offline
                                  wmarcolin
                                  wrote on last edited by
                                  #20

                                  @toggledbits well done

                                  Low Battery Devices charging perfect!

                                  a94effd2-b52f-4bf3-ac75-ddfd010df71d-image.png

                                  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?

                                  1 Reply Last reply
                                  0
                                  • toggledbitsT Offline
                                    toggledbitsT Offline
                                    toggledbits
                                    wrote on last edited by
                                    #21

                                    In your expression, you are not guarding for entities that have binary_sensor but do not have motion_sensor, and vice versa. Use the coalescing member access operator ?. in the two sub-expressions.

                                    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                                    wmarcolinW 1 Reply Last reply
                                    0
                                    • toggledbitsT toggledbits

                                      In your expression, you are not guarding for entities that have binary_sensor but do not have motion_sensor, and vice versa. Use the coalescing member access operator ?. in the two sub-expressions.

                                      wmarcolinW Offline
                                      wmarcolinW Offline
                                      wmarcolin
                                      wrote on last edited by
                                      #22

                                      @toggledbits

                                      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.

                                      toggledbitsT 1 Reply Last reply
                                      0
                                      • wmarcolinW wmarcolin

                                        @toggledbits

                                        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.

                                        toggledbitsT Offline
                                        toggledbitsT Offline
                                        toggledbits
                                        wrote on last edited by toggledbits
                                        #23

                                        @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?

                                        Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                                        wmarcolinW 1 Reply Last reply
                                        0
                                        • toggledbitsT toggledbits

                                          @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?

                                          wmarcolinW Offline
                                          wmarcolinW Offline
                                          wmarcolin
                                          wrote on last edited by
                                          #24

                                          @toggledbits

                                          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:

                                          1. 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"}
                                            }
                                          2. Now with Dynamic I have it easy that it is tripped;
                                          3. 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.

                                          toggledbitsT 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Recent Topics

                                          • Gradually turn on lights.
                                            Tom_DT
                                            Tom_D
                                            0
                                            1
                                            11

                                          • Error After Upgrade
                                            G
                                            gwp1
                                            0
                                            4
                                            31

                                          • Reset attribute value of entity in event handler
                                            R
                                            RHCPNG
                                            0
                                            5
                                            102

                                          • Need help figuring out how to delay a reset on reaction
                                            G
                                            gwp1
                                            0
                                            22
                                            315

                                          • Way to search for rules (rule state) in other rules
                                            T
                                            tamorgen
                                            0
                                            3
                                            49

                                          • Links to MSR from HA
                                            Tom_DT
                                            Tom_D
                                            0
                                            1
                                            53

                                          • Set Reaction > Script Action
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            11
                                            333

                                          • Wiring Samotech SM308-S into light fitting
                                            akbooerA
                                            akbooer
                                            0
                                            2
                                            105

                                          • Errors after updating to MQTTController build 25139
                                            toggledbitsT
                                            toggledbits
                                            0
                                            6
                                            199

                                          • 🎉 My very first MSR controller: OpenSprinkler
                                            therealdbT
                                            therealdb
                                            5
                                            13
                                            820

                                          • Advice reqeusted to migrate MSR from Bare Metal to Container
                                            T
                                            tamorgen
                                            0
                                            5
                                            207

                                          • Reactor (Multi-System/Multi-Hub) Announcements
                                            toggledbitsT
                                            toggledbits
                                            5
                                            122
                                            48.7k
                                          Powered by NodeBB | Contributors
                                          Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • Unsolved