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. Rule for devices battery level ?
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
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S
I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved. The Runtime Error is different in the two browsers Safari v18.3 @http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Google Chrome 133.0.6943.142 TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Steps to reproduce: Click the pencil to edit a global reaction with a group. Click the Exit button. Runtime error appears. or Click Create Reaction Click Add Action Select Group Add Condition such as Entity Attribute. Add an Action. Click Save Click Exit Runtime error appears. I don’t know how long the error has been there as I haven’t edited the global reaction in a long time. Reactor (Multi-hub) latest-25060-f32eaa46 Docker Mac OS: 15.3.1 Thanks
Multi-System Reactor
Cannot delete Global Expressions
SnowmanS
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons. I have not created a global expression for some times and just noticed this while doing some clean-up. I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success. Here's what the log shows. [latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } Reactor latest-25067-62e21a2d Docker on Synology NAS
Multi-System Reactor
Local notification methods?
CatmanV2C
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method. This was prompted by yesterday's fun and games with my ISP. I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone) I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions? TIA C
Multi-System Reactor

Rule for devices battery level ?

Scheduled Pinned Locked Moved Multi-System Reactor
43 Posts 6 Posters 2.6k Views 7 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.
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #11

    Thanks I've changed the expressions to local rule ones instead and its all still working.

    1 Reply Last reply
    1
    • cw-kidC Offline
      cw-kidC Offline
      cw-kid
      wrote on last edited by
      #12

      How can I make this rule re-trigger ?

      Say I don't immediate go replace the battery on the device mentioned, can I have the rule run the alerts / notifications each day or week until I have done it and changed the batteries ?

      Also can the alerts also state what the battery level percentage actually is ?

      Thanks

      toggledbitsT IanI 2 Replies Last reply
      0
      • cw-kidC cw-kid

        How can I make this rule re-trigger ?

        Say I don't immediate go replace the battery on the device mentioned, can I have the rule run the alerts / notifications each day or week until I have done it and changed the batteries ?

        Also can the alerts also state what the battery level percentage actually is ?

        Thanks

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

        @cw-kid said in Rule for devices battery level ?:

        How can I make this rule re-trigger ?

        Wrap the condition in a group and put the group in "pulse" output mode with the timing you want.

        @cw-kid said in Rule for devices battery level ?:

        Also can the alerts also state what the battery level percentage actually is ?

        Yes, but I'm going to leave it as an exercise for the reader. Level of difficulty: moderate.

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

        cw-kidC 1 Reply Last reply
        0
        • cw-kidC cw-kid

          How can I make this rule re-trigger ?

          Say I don't immediate go replace the battery on the device mentioned, can I have the rule run the alerts / notifications each day or week until I have done it and changed the batteries ?

          Also can the alerts also state what the battery level percentage actually is ?

          Thanks

          IanI Offline
          IanI Offline
          Ian
          wrote on last edited by
          #14

          @cw-kid

          Try this.

          16c0d434-95ea-453d-b06e-e9a68663fbe5-image.png

          cw-kidC 1 Reply Last reply
          0
          • IanI Ian

            @cw-kid

            Try this.

            16c0d434-95ea-453d-b06e-e9a68663fbe5-image.png

            cw-kidC Offline
            cw-kidC Offline
            cw-kid
            wrote on last edited by cw-kid
            #15

            @ian

            Thanks Ian that works, my Telegram text message now has the number% at the end of the message now.

            However this messes up the Google Home TTS announcement sent via node-red, if I have a "%" in the expression. So I had to change it to the word "percent" instead and now the TTS sounds correct when spoken.

            join( each id in battery_low_list: getEntity(id).name + " " + "at" + " " + int(getEntity(id).attributes.battery_power.level * 100) + " percent", ', ')
            
            1 Reply Last reply
            0
            • toggledbitsT toggledbits

              @cw-kid said in Rule for devices battery level ?:

              How can I make this rule re-trigger ?

              Wrap the condition in a group and put the group in "pulse" output mode with the timing you want.

              @cw-kid said in Rule for devices battery level ?:

              Also can the alerts also state what the battery level percentage actually is ?

              Yes, but I'm going to leave it as an exercise for the reader. Level of difficulty: moderate.

              cw-kidC Offline
              cw-kidC Offline
              cw-kid
              wrote on last edited by
              #16

              @toggledbits said in Rule for devices battery level ?:

              Wrap the condition in a group and put the group in "pulse" output mode with the timing you want.

              Like this?

              146e1b92-875d-4a6e-8619-e555c355fbce-image.png

              5eed7d9c-43ab-4a1e-8505-c0679f0ce401-image.png

              Seems to be working and the alerts are repeating every 60 seconds now. I will just set this to 24hrs I think.

              1 Reply Last reply
              1
              • toggledbitsT toggledbits

                @cw-kid One of my to-do list tasks for expressions is to be able to create a list of devices that match a test. Until that comes, you can just build your own array of battery-operated devices like this (lets call this battery_device_list) :

                35882eb5-310f-41b1-a95e-eaf52dbc0bb8-image.png

                Then, you can reduce that list to all of the devices that have battery < 10%:

                c108f634-1ad1-4156-9e47-777c98c9d69b-image.png

                That leaves you with an array of the entities that have low battery. Use another expression to convert that into a comma-separated list of entity names:

                30ca5615-71c3-431e-b83f-d0aeff6144e4-image.png

                Your rule just checks to see if that battery_low_names (a string now) expression is not empty, and runs whatever notifications you want to run if it is not. You can include the battery_low_names variable in the text of your email or other notification, too.

                1bfd5d0f-1313-4613-ac2b-5731ddf5c594-image.png

                CrilleC Offline
                CrilleC Offline
                Crille
                wrote on last edited by
                #17

                @toggledbits said in Rule for devices battery level ?:

                One of my to-do list tasks for expressions is to be able to create a list of devices that match a test.

                This is very useful, is it released yet or still on the to-do list?

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

                  Still on the to-do list, but I think I'm close to figuring out what I want it to do. These things get harder with time: the more people use them, the more etched in stone they become, so making a "first guess" and completely changing things later isn't really something I want to do a lot of. If I can get something good on the first try, that's the way...

                  Here's what I'm thinking...

                  First, the matchEntities() function would quickly narrow down the set, in a manner similar to the filters on the Entities page and the Entity Picker:

                      living_room_sensors = matchEntities( { controller: 'vera', capability: [ 'binary_sensor', 'value_sensor'' ], group: 'Living Room' } )
                  

                  This would return an array of entities. From here, you could use an each statement to further filter any deep refinements. This expression would take the above array of sensors in the Living Room and pick out those that are battery powered and have battery level under 50%:

                      low_battery_living_room = each e in living_room_sensors: e.attributes.battery_power?.level <= 0.5 ? e : null
                  

                  I'm liking this approach because the function could do the bulk reduction of potential hundreds of entities down to a manageable list, and then the final filtering of the list can be done with expressions for maximum flexibility.

                  Any thoughts about that?

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

                  CrilleC 1 Reply Last reply
                  0
                  • toggledbitsT toggledbits

                    Still on the to-do list, but I think I'm close to figuring out what I want it to do. These things get harder with time: the more people use them, the more etched in stone they become, so making a "first guess" and completely changing things later isn't really something I want to do a lot of. If I can get something good on the first try, that's the way...

                    Here's what I'm thinking...

                    First, the matchEntities() function would quickly narrow down the set, in a manner similar to the filters on the Entities page and the Entity Picker:

                        living_room_sensors = matchEntities( { controller: 'vera', capability: [ 'binary_sensor', 'value_sensor'' ], group: 'Living Room' } )
                    

                    This would return an array of entities. From here, you could use an each statement to further filter any deep refinements. This expression would take the above array of sensors in the Living Room and pick out those that are battery powered and have battery level under 50%:

                        low_battery_living_room = each e in living_room_sensors: e.attributes.battery_power?.level <= 0.5 ? e : null
                    

                    I'm liking this approach because the function could do the bulk reduction of potential hundreds of entities down to a manageable list, and then the final filtering of the list can be done with expressions for maximum flexibility.

                    Any thoughts about that?

                    CrilleC Offline
                    CrilleC Offline
                    Crille
                    wrote on last edited by
                    #19

                    @toggledbits That would do it for me, is the matchEntities() function already available in Expressions? I get no error but no matter what I do the Expression always returns an empty array.
                    I'd expect this to contain at least something:

                    matchEntities( { controller: 'vera', capability: 'humidity_sensor' } )
                    
                    1 Reply Last reply
                    0
                    • toggledbitsT Offline
                      toggledbitsT Offline
                      toggledbits
                      wrote on last edited by
                      #20

                      No, it's not yet available.

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

                      CrilleC tunnusT 2 Replies Last reply
                      0
                      • CrilleC Offline
                        CrilleC Offline
                        Crille
                        wrote on last edited by
                        #21

                        Ah, that explains a lot 🙂 I like the idea, it seems very flexible.

                        1 Reply Last reply
                        0
                        • toggledbitsT toggledbits

                          No, it's not yet available.

                          CrilleC Offline
                          CrilleC Offline
                          Crille
                          wrote on last edited by
                          #22

                          @toggledbits Thanks, the new matchEntities() is brilliant. Now we can have dynamic arrays of devices.

                          toggledbitsT 1 Reply Last reply
                          0
                          • CrilleC Crille

                            @toggledbits Thanks, the new matchEntities() is brilliant. Now we can have dynamic arrays of devices.

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

                            @crille said in Rule for devices battery level ?:

                            Now we can have dynamic arrays of devices.

                            Tell me about that...

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

                            CrilleC 1 Reply Last reply
                            0
                            • toggledbitsT toggledbits

                              @crille said in Rule for devices battery level ?:

                              Now we can have dynamic arrays of devices.

                              Tell me about that...

                              CrilleC Offline
                              CrilleC Offline
                              Crille
                              wrote on last edited by
                              #24

                              @toggledbits Inspired by this topic I created a rule with similar expressions to monitor/notify x_ezlo_device.reachable for all my Ezlo devices. Instead of managing a static array, like the battery_device_list in this topic, the expression matchEntities( {capability: 'x_ezlo_device'} ) generates a list of devices that is dynamically updated if devices are added or removed from the controller.

                              1 Reply Last reply
                              1
                              • toggledbitsT toggledbits

                                No, it's not yet available.

                                tunnusT Offline
                                tunnusT Offline
                                tunnus
                                wrote on last edited by
                                #25

                                @toggledbits I'm testing this new function, but somehow it does not show all the devices I'm expecting it to show. See examples below

                                Screenshot 2021-09-30 at 17.34.23.png

                                Array is empty, although it should contain one device:

                                Screenshot 2021-09-30 at 17.41.02.png

                                Strange, as device 216 definitely has capability "x_vera_device"

                                Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

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

                                  One of the issues I see in matchEntities() as it currently works is that it returns an array of entity objects with attribute values, but it does not update that array when any of the returned entities' attributes or other values changes. So it's certain, then, that the attributes will go stale in the result array.

                                  For the next build, I will change the definition of this function to return canonical entity IDs only, rather than entity objects, so you will have to use getEntity() in your each over the results, as you did with your test_array example, and this will ensure that you are always looking at the latest attributes. You can test this theory now by modifying your each for d_failure_list to use getEntity( id.canonical_id ).

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

                                  tunnusT 1 Reply Last reply
                                  0
                                  • toggledbitsT toggledbits

                                    One of the issues I see in matchEntities() as it currently works is that it returns an array of entity objects with attribute values, but it does not update that array when any of the returned entities' attributes or other values changes. So it's certain, then, that the attributes will go stale in the result array.

                                    For the next build, I will change the definition of this function to return canonical entity IDs only, rather than entity objects, so you will have to use getEntity() in your each over the results, as you did with your test_array example, and this will ensure that you are always looking at the latest attributes. You can test this theory now by modifying your each for d_failure_list to use getEntity( id.canonical_id ).

                                    tunnusT Offline
                                    tunnusT Offline
                                    tunnus
                                    wrote on last edited by
                                    #27

                                    @toggledbits did what you suggested, but situation didn't really change, array is still empty:

                                    Screenshot 2021-09-30 at 19.25.05.png

                                    Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

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

                                      Can you show the entity detail for device 216 please?

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

                                      tunnusT 1 Reply Last reply
                                      0
                                      • tunnusT tunnus

                                        @toggledbits did what you suggested, but situation didn't really change, array is still empty:

                                        Screenshot 2021-09-30 at 19.25.05.png

                                        CrilleC Offline
                                        CrilleC Offline
                                        Crille
                                        wrote on last edited by Crille
                                        #29

                                        @tunnus I had some issues as well. I got an empty array and when tried getEntity() I got some "Type Error". Was sure I was doing something wrong but I restarted Reactor and copied the same expression to a new one and suddenly it worked.
                                        @toggledbits I also noticed the array isn't updated when entity changed so I pulse the trigger every minute to update it. Will change to getEntity() for next update.

                                        1 Reply Last reply
                                        0
                                        • toggledbitsT toggledbits

                                          Can you show the entity detail for device 216 please?

                                          tunnusT Offline
                                          tunnusT Offline
                                          tunnus
                                          wrote on last edited by
                                          #30

                                          @toggledbits here you go:

                                          dimming.level=0
                                          dimming.step=null
                                          power_switch.state=false
                                          x_vera_device.configured=false
                                          x_vera_device.device_number=216
                                          x_vera_device.device_type="urn:schemas-upnp-org:device:DimmableLight:1"
                                          x_vera_device.failed=true
                                          x_vera_device.mapped_by="*;device_type=/urn:schemas-upnp-org:device:DimmableLight:/"
                                          x_vera_device.mapped_class="generic_dimmer"
                                          x_vera_device.parent_device=1
                                          x_vera_device.room_id="1"
                                          x_vera_energy.amps=null
                                          x_vera_energy.day_kwh=null
                                          x_vera_energy.kwh="6.7000"
                                          x_vera_energy.life_kwh=null
                                          x_vera_energy.month_kwh=null
                                          x_vera_energy.power_factor=null
                                          x_vera_energy.volts=null
                                          x_vera_energy.watts=""
                                          x_vera_energy.week_kwh=null
                                          x_vera_energy.year_kwh=null
                                          x_vera_svc_cd_jackson_com_DataMine1.errorStatus="true"
                                          x_vera_svc_micasaverde_com_EnergyMetering1.ActualUsage="1"
                                          x_vera_svc_micasaverde_com_EnergyMetering1.KWH="6.7000"
                                          x_vera_svc_micasaverde_com_EnergyMetering1.KWHReading="1597268716"
                                          x_vera_svc_micasaverde_com_EnergyMetering1.Log="0,0,0,1633073400,1"
                                          x_vera_svc_micasaverde_com_EnergyMetering1.Watts=""
                                          x_vera_svc_micasaverde_com_HaDevice1.AutoConfigure="0"
                                          x_vera_svc_micasaverde_com_HaDevice1.CommFailure="1"
                                          x_vera_svc_micasaverde_com_HaDevice1.CommFailureAlarm="1628783888,1"
                                          x_vera_svc_micasaverde_com_HaDevice1.CommFailureTime="1628780288"
                                          x_vera_svc_micasaverde_com_HaDevice1.Configured="0"
                                          x_vera_svc_micasaverde_com_HaDevice1.FirstConfigured="1526668133"
                                          x_vera_svc_micasaverde_com_HaDevice1.LastTimeCheck="1605041801"
                                          x_vera_svc_micasaverde_com_HaDevice1.LastTimeOffset="2"
                                          x_vera_svc_micasaverde_com_HaDevice1.LastUpdate="0"
                                          x_vera_svc_micasaverde_com_HaDevice1.ModeSetting="1:;2:;3:;4:"
                                          x_vera_svc_micasaverde_com_HaDevice1.PollRatings="0.20"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.AgiInfo="X"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.AlarmType="0x4,0x8,"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.AlarmVersion="0,2"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.AssociationGroups="1"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.AssociationNum="4"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.Capabilities="211,156,1,4,17,1,L,R,B,RS,|37S,38S:3,39S,43S,44S,50S:3,89S,90B,94,112S,113S:4,114,115S,122S,129S,133S,134,152,"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.ConfiguredAssoc=""
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.ConfiguredVariable="80-Status notification type,1d,3,90- Enable or Disable energy reporting (0-1),1d,1,91-Minimum change in wattage for a REPORT (0-60000),2d,5,92-Minimum change in wattage percent for a REPORT,1d,5,120-Configure external switch mode for S1(0-3),1d,1,125,1d,1,128-Current working mode (0-2),1d,1,129-Dimming principle (0-2),1d,1,130-Dimmer load type connected(0-3),1d,1,131-Minimum brightness level,1d,20,132-Maximum brightness level,1d,90,249,1d,0"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.FirmwareInfo="134,111,41841"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.LastArr=""
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.LastNnu=""
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.LastReset="1526668110"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.LastRouteUpdate="1597229741"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.ManufacturerInfo="134,3,111"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.MeterScale="5"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.MeterType="1"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.NodeInfo="25S,26S,27S,2bS,2cS,32S,59S,5aB,5e,70S,71S,72,73S,7aS,81S,85S,86,98,"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.PlusInfo="1,5,0,6,0,6,0"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.PollNoReply="476"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.PollOk="37823"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.PollSettings="120"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.PollTxFail="1"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.SecurityFailed="0"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.SubscribedAlarms=",0x4,0x8,"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.SwitchMlSettings="2,0"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.VariablesGet="80,3,90,1,91,5,92,5,120,1,125,1,128,1,129,1,130,1,131,20,132,90,249,0,"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.VariablesSet="80-Status notification type,1d,3,90- Enable or Disable energy reporting (0-1),1d,1,91-Minimum change in wattage for a REPORT (0-60000),2d,5,92-Minimum change in wattage percent for a REPORT,1d,5,120-Configure external switch mode for S1(0-3),1d,1,125,1d,1,128-Current working mode (0-2),1d,1,129-Dimming principle (0-2),1d,1,130-Dimmer load type connected(0-3),1d,1,131-Minimum brightness level,1d,20,132-Maximum brightness level,1d,90,249,1d,0"
                                          x_vera_svc_micasaverde_com_ZWaveDevice1.VersionInfo="3,4,54,2,0"
                                          x_vera_svc_micasaverde_com_ZWaveNetwork1.ConsecutivePollFails="0"
                                          x_vera_svc_micasaverde_com_ZWaveNetwork1.LastPollSuccess="1597268720"
                                          x_vera_svc_upnp_org_Dimming1.LoadLevelLast="100"
                                          x_vera_svc_upnp_org_Dimming1.LoadLevelStatus="0"
                                          x_vera_svc_upnp_org_Dimming1.LoadLevelTarget="100"
                                          x_vera_svc_upnp_org_Dimming1.TurnOnBeforeDim="0"
                                          x_vera_svc_upnp_org_SwitchPower1.Status="0"
                                          zwave_device.capabilities="211,156,1,4,17,1,L,R,B,RS,|37S,38S:3,39S,43S,44S,50S:3,89S,90B,94,112S,113S:4,114,115S,122S,129S,133S,134,152,"
                                          zwave_device.failed=true
                                          zwave_device.manufacturer_info="134,3,111"
                                          zwave_device.node_id=53
                                          zwave_device.version_info="3,4,54,2,0"
                                          Capabilities: dimming, power_switch, toggle, x_vera_device, x_vera_energy, x_vera_svc_cd_jackson_com_DataMine1, x_vera_svc_micasaverde_com_Color1, x_vera_svc_micasaverde_com_EnergyMetering1, x_vera_svc_micasaverde_com_HaDevice1, x_vera_svc_micasaverde_com_ZWaveDevice1, x_vera_svc_micasaverde_com_ZWaveNetwork1, x_vera_svc_upnp_org_Dimming1, x_vera_svc_upnp_org_SwitchPower1, zwave_device
                                          Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, toggle.toggle, x_vera_device.set_variable, x_vera_energy.resetkwh, x_vera_svc_micasaverde_com_Color1.SetColor, x_vera_svc_micasaverde_com_Color1.SetColorRGB, x_vera_svc_micasaverde_com_Color1.SetColorTemp, x_vera_svc_micasaverde_com_EnergyMetering1.ResetKWH, x_vera_svc_micasaverde_com_HaDevice1.AllowPairing, x_vera_svc_micasaverde_com_HaDevice1.Poll, x_vera_svc_micasaverde_com_HaDevice1.Reconfigure, x_vera_svc_micasaverde_com_HaDevice1.Remove, x_vera_svc_micasaverde_com_HaDevice1.SetPollFrequency, x_vera_svc_micasaverde_com_HaDevice1.StressTest, x_vera_svc_micasaverde_com_HaDevice1.ToggleState, x_vera_svc_micasaverde_com_ZWaveNetwork1.AddNodes, x_vera_svc_micasaverde_com_ZWaveNetwork1.BackupDongle, x_vera_svc_micasaverde_com_ZWaveNetwork1.DownloadNetwork, x_vera_svc_micasaverde_com_ZWaveNetwork1.HealNetwork, x_vera_svc_micasaverde_com_ZWaveNetwork1.PollAllNodes, x_vera_svc_micasaverde_com_ZWaveNetwork1.PutByte, x_vera_svc_micasaverde_com_ZWaveNetwork1.ReconfigureAllNodes, x_vera_svc_micasaverde_com_ZWaveNetwork1.RemoveNodes, x_vera_svc_micasaverde_com_ZWaveNetwork1.SendData, x_vera_svc_micasaverde_com_ZWaveNetwork1.SetPolling, x_vera_svc_micasaverde_com_ZWaveNetwork1.SimulateIncomingData, x_vera_svc_micasaverde_com_ZWaveNetwork1.UpdateNeighbors, x_vera_svc_micasaverde_com_ZWaveNetwork1.UpdateNetwork, x_vera_svc_upnp_org_Dimming1.PauseRamp, x_vera_svc_upnp_org_Dimming1.ResumeRamp, x_vera_svc_upnp_org_Dimming1.SetLoadLevelTarget, x_vera_svc_upnp_org_Dimming1.SetOnEffect, x_vera_svc_upnp_org_Dimming1.SetOnEffectLevel, x_vera_svc_upnp_org_Dimming1.SetRampRate, x_vera_svc_upnp_org_Dimming1.SetStepDelta, x_vera_svc_upnp_org_Dimming1.StartRampDown, x_vera_svc_upnp_org_Dimming1.StartRampToLevel, x_vera_svc_upnp_org_Dimming1.StartRampUp, x_vera_svc_upnp_org_Dimming1.StepDown, x_vera_svc_upnp_org_Dimming1.StepUp, x_vera_svc_upnp_org_Dimming1.StopRamp, x_vera_svc_upnp_org_SwitchPower1.SetTarget, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config
                                          

                                          Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

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


                                          Recent Topics

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

                                          • Reactor (Multi-System/Multi-Hub) Announcements
                                            toggledbitsT
                                            toggledbits
                                            5
                                            122
                                            35.4k

                                          • Z-Wave Future....
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            5
                                            130

                                          • Can´t restart or upgrade/deploy MSR
                                            toggledbitsT
                                            toggledbits
                                            0
                                            4
                                            85

                                          • [Solved] Limit HA Entity in MSR
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            7
                                            191

                                          • Disaster recovery and virtualisation
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            5
                                            659

                                          • Remote access of Zwave stick from Z-wave server
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            3
                                            383

                                          • Organizing/ structuring rule sets and rules
                                            G
                                            gwp1
                                            0
                                            5
                                            374

                                          • Moving MSR from a QNAP container to RP 5 - some issues
                                            G
                                            gwp1
                                            0
                                            5
                                            345

                                          • Widget deletion does not work and landing page (status) is empy
                                            G
                                            gwp1
                                            0
                                            4
                                            338

                                          • Need help reducing false positive notifications
                                            T
                                            tamorgen
                                            0
                                            7
                                            520
                                          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