Navigation

    Discussion Forum to share and further the development of home control and automation, independent of platforms.

    SmartHome Community

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Unsolved
    (Last Updated: January 7, 2022)
    • Adding remotes, scene controllers as entities to MSR

      A

      EDIT: 2022.07.01

      So I will try to remake this thread to some kind of guide for future use, or in worst case a documentation of my failure. At least that could also be useful for letting someone know what didn't work...
      I have zero knowledge of programming, so every time I need to edit a config file in HomeAssistant or similar it requires a good portion of googletime and read, re-reading instructions.
      Also is english not my native language, so bear with me.

      Two goals!
      1: Get MSR to take notice (and then actions of course) of pressed buttons on remotes.
      2: Document what I do in hope I can help someone else in the future.

      I will use a Fibaro Keyfob as described below, but what I understand from Togglebits answers most type of remotes should work in similar ways.

      Original thread:
      Fibaro Keyfob support in MSR? (thru Hassio & Z-wave JS)
      Hi

      I just bought a Fibaro Keyfob FGKF-601 and plan to give this to my son so he can control some stuff in his own room. Primary some lightning and Sonos, maybe blinds in the future.

      As the noob I am it will, of course, not work as I expected.👶🏻

      The remote handle 1x, 2x, 3x clicks per button (six of them) and "release button"
      I thought that it would appear like some "scene controller" in HA and that I could make Rules in MSR depending on what scene-entety that was triggered.
      So is not the case, and if that is because of HA, Z-wave JS or MSR I have no idea.
      I found a HA Blueprint that works in HA, but of course I would prefer to keep all automation in MSR.
      I guess a workaround could be using HA virtual switches "Helpers" that I suppose will come up as an on/off trigger in MSR, but before going this way I would like to check with the wisdom of your guys if there is a better way of doing this.

      I am using:
      MSR 22168 on windows.
      Home Assistant Core 2022.6.7
      Home Assistant Supervisor 2022.05.3
      Home Assistant OS 7.6
      Z-Wave JS version: 0.1.64

      Multi-System Reactor
    • Constraints under triggers or under constraints, what is the difference?

      A

      Need to ask, have thougth about this since the move from Rector to MSR I think.

      What is the difference between putting constraints under trigger groups, like this
      23b4a249-3292-41cd-9927-7f49c9bf1d07-image.png

      Compared to this similar rule, but the time limits is under contraints instead?
      ee596c9f-f52b-4a39-9605-f5932f3d9ed5-image.png

      I think the Constraints parts in manual is still to be done because I can only find in the chapter menu, but it is not mentioned anywhere else.

      Multi-System Reactor
    • The Home Remote with MSR

      MikeReadington

      Did anyone do/start any work on a full integration with The Home Remote application yet?

      Multi-System Reactor
    • Condition must occur after -restriction not working

      tunnus

      Running MSR 22123 in Docker container and trying to use "condition must occur after" option. Will update to the latest build and log a PR if needed, but wanted to poll first if anyone is using this option successfully?

      I have the following rules:

      Screenshot 2022-06-28 at 15.18.50.png

      Notification activity connected to "Alarm disabled" rule did not trigger. I also did another test with quite simple rules and that didn't work either (FWIIW - when observing that test in "real-time", I didn't see any timer running on the second rule while the first rule was true).

      As said, before going further with debug/logs, nice to know if someone is using this option/restriction (successfully).

      Multi-System Reactor
    • Reactor (Multi-System/Multi-Hub) Announcements

      toggledbits

      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
    • [Solved] Changes in 22178 for HASS sensor no longer provide a value in topic "value", MQTTController echo capability

      Crille

      Before updating to 22178 there was a primary value echoed in MQTTControllers echo capability, can I tell the controller which value to put as primary from HASS sensors after this change as it now is null? or is it a bug?

      I have not changed the

      primary_attributes: true

      mqtt_value.PNG

      Reactor latest-22178 bare metal
      Hass 2022.6.7

      Edit: Solved in build 22179

      Multi-System Reactor
    • Using InfluxDB with MSR

      wmarcolin

      Hi!

      I have a system that I consider pretty stable, running in a VM Ubuntu 20.04, it has some communication failures, but I think more by HE than by the OS/MSR.

      I'm thinking of taking the next step to get more advantages from the system, and I'm thinking of using InfluxDB maybe for queries or to extend rules.

      The question is, I would like practical examples of what really helps to install InfluxDB? What would you be doing that really makes a difference with this installation? Can you post examples of features or information?

      Thanks

      Multi-System Reactor
    • git hub docker container not available?

      Black Cat

      @toggledbits - what now?

      Re: Cheapest platform on which to run MSR

      21aaf68e-c031-414d-847d-d8bec01d57e7-Clipboard01.jpg

      Multi-System Reactor
    • Synology NAS docker image replacement

      MikeReadington

      Hi Everyone,

      MSR had a docker image file naming convention change, and I am not exactly sure how to swap the image out. I'm sure it's not rocket science, I've just never done this before.

      I am using a Synology NAS, and under the environment tab there is a "REACTOR_IMAGE" variable. Can I just change the image name to the new image naming convention and clear the container, or should I launch a new container and populate the volume location from the previous reactor?

      Thanks in advance

      Multi-System Reactor
    • Cheapest platform on which to run MSR

      T

      Please can anyone give me advice on a cheap way to run MSR (both initial cost and ongoing electricity cost). I currently run it on my QNAP network drive (which works very well incidentally). However, this draws a constant 35Watts (£90/yr @ 30p/kWh) and given the recent rise in fuel costs I am evaluating the best way forwards. Note, I only really need to turn my QNAP on for an hour a week to back-up my computer data. I understand that MSR can run on a Raspberry PI, but I am not competent with Linux! Thanks.

      Multi-System Reactor
    • Copying configuraiton and rules from QNAP install to Raspberry PI 4 install

      T

      I have made good progress setting up a new Raspberry PI 4 with the latest OS (64bit) and latest Reactor images in Docker. However I am not able to copy my configuraiton files (.yml) and reactor reactions over. I am not yet that confident with linux commands, so I have tired to drag and drop the files from a USB drive to the working folders in my new Raspberry PI. I am getting a popup in the GUI stating 'The file operation was completed with errors.' and Errors occured: "rule-xxxxxx.json: Error opening file "/home/pi/reactor/....................................json":Permission denied.

      I suspect it's something to do with permissions?

      Is there an easier way to copy my configuration over??

      Multi-System Reactor
    • Alexa TTS via Home Assistant?

      T

      Hello All -

      I'm gradually moving away from Vera to Home Assistant. I've recently gotten the Alexa and Mini Media Player setup in Home Assistant and everything is working well.

      Is there a way to call this service from Reactor? My goal is to send TTS requests to HAAS upon certain events within Reactor (e.g. "Front Door Opened")

      Multi-System Reactor
    • Integrate UPS with MSR

      wmarcolin

      I have a Tripp-Lite UPS (https://www.tripplite.com/smartpro-lcd-120v-1500va-900w-line-interactive-ups-avr-tower-lcd-usb-10-outlets~smart1500lcdt) that connected by a USB cable to my computer, reports various power supply and failure information, as shown in the panel below.

      b9f0ea34-d654-4b26-b968-4f8cf0a4e0c1-image.png

      afa73913-5318-42c6-af9a-02d36e2e6ea1-image.png

      The application I installed runs Java and opens the console to send the information.

      Has anyone tried to bring the information into the MSR? Or even a VeraPlus?

      Thanks.

      Multi-System Reactor
    • Reactor as tab in Hass sidebar

      Matohl

      panel_iframe in configuration.yaml. If you access MSR with HTTP it works in HA with HTTP to Reactor and HTTPS to HTTPS obviously.

      configuration.yaml

      # ============ SIDEBAR ============ panel_iframe: reactor: title: "Reactor" url: "http://192.168.0.23:8111/reactor/sv-SE/"
      Multi-System Reactor
    • Documentation>Network Status

      S

      It appears that in the Manual, under Management>Network Status is for Reactor on Vera. Is the Internet check functionality available with MSR and if so is there updated instructions? I do see a variable reactor_system.internet.ok but the value is null.
      I am looking for a way to check for internet status with MSR before installing an extra app on a hub to get the information.

      Synology Docker latest-22149

      Multi-System Reactor
    • MSR Upgrade from 22119 to 22136 fails, service wont start

      W

      Windows Server 2022 Build 20348
      Nodejs v16.14.0
      Currently running Reactor (Multi-hub) stable-22119-ae7212f
      Linked to Hass 2022.0.5.4 (on a different box)
      Windows server is dedicated to MSR and doesn't do anything else.

      I'd like to upgrade to 22136 to take advantage of the SSL feature added recently, and also to bring my current version of Hass into the 'supported' column with MSR.

      Following the instructions here: link text, section "Upgrade Windows Bare Metal"

      Stop Reactor Service Extract the zip, overwriting the reactor folder in c:\reactor\reactor There is no package-lock.json file so I skip that. Run "npm install --no-save --omit dev"

      Next step is to start the service. I start the service and it immediately stops. "Windows could not start the Reactor service on Local Computer. Error 1067: The process terminated unexpectedly".

      Tried rebooting, service won't stay running.

      I suspect I'm missing something, it's probably obvious but I've not been able to figure it out.

      I rolled back the reactor folder version (Windows Shadow copies) and then the service starts fine.

      Anyone else running Windows and know what I'm missing?

      Tail of log file from running OK version, before upgrade attempt [stable-22119]2022-06-01T22:20:19.081Z <Rule:INFO> Lounge Billy Ambient Lighting - Turn On (Rule#rule-l0ki453b) evaluation complete [stable-22119]2022-06-01T22:20:19.082Z <httpapi:NOTICE> HTTP API v1 22021 base URL http://172.16.128.6:8111; listening [stable-22119]2022-06-01T22:20:19.228Z <app:NOTICE> HTTP server running; registering proxy endpoints. [stable-22119]2022-06-01T22:20:19.228Z <app:NOTICE> Starting WSAPI... [stable-22119]2022-06-01T22:20:19.229Z <wsapi:NOTICE> wsapi: starting version 21334 [stable-22119]2022-06-01T22:20:19.656Z <Engine:INFO> [Engine]Engine#1 master timer tick, local time "6/2/2022, 8:20:19 AM" (TZ offset 600 mins from UTC) [stable-22119]2022-06-01T22:27:54.788Z <wsapi:INFO> wsapi: connection from ::ffff:172.16.128.5 Tail of log file from failed to start after upgrade (is identical, ii.e. nothing has been appended to it) [stable-22119]2022-06-01T22:20:19.081Z <Rule:INFO> Lounge Billy Ambient Lighting - Turn On (Rule#rule-l0ki453b) evaluation complete [stable-22119]2022-06-01T22:20:19.082Z <httpapi:NOTICE> HTTP API v1 22021 base URL http://172.16.128.6:8111; listening [stable-22119]2022-06-01T22:20:19.228Z <app:NOTICE> HTTP server running; registering proxy endpoints. [stable-22119]2022-06-01T22:20:19.228Z <app:NOTICE> Starting WSAPI... [stable-22119]2022-06-01T22:20:19.229Z <wsapi:NOTICE> wsapi: starting version 21334 [stable-22119]2022-06-01T22:20:19.656Z <Engine:INFO> [Engine]Engine#1 master timer tick, local time "6/2/2022, 8:20:19 AM" (TZ offset 600 mins from UTC) [stable-22119]2022-06-01T22:27:54.788Z <wsapi:INFO> wsapi: connection from ::ffff:172.16.128.5 reactor.wrapper.log (log file the failed to start event points to) 2022-06-02 08:19:23 - Stopping reactor.exe 2022-06-02 08:19:23 - ProcessKill 3628 2022-06-02 08:19:25 - Shutdown exception Message:A system shutdown is in progress. Stacktrace: at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.Management.ManagementScope.InitializeGuts(Object o) at System.Management.ManagementScope.Initialize() at System.Management.ManagementObjectSearcher.Initialize() at System.Management.ManagementObjectSearcher.Get() at winsw.WrapperService.GetChildPids(Int32 pid) at winsw.WrapperService.StopProcessAndChildren(Int32 pid) at winsw.WrapperService.StopIt() at winsw.WrapperService.OnShutdown() 2022-06-02 08:20:11 - Starting C:\Program Files\nodejs\node.exe C:\reactor\reactor\node_modules\node-windows\lib\wrapper.js --file C:\reactor\reactor\app.js --scriptoptions= --log "Reactor wrapper" --grow 0.25 --wait 1 --maxrestarts 3 --abortonerror n --stopparentfirst undefined 2022-06-02 08:20:11 - Started 3272 2022-06-02 08:30:54 - Stopping reactor.exe 2022-06-02 08:30:54 - ProcessKill 3272 2022-06-02 08:30:54 - Found child process: 3280 Name: conhost.exe 2022-06-02 08:30:54 - Found child process: 3504 Name: node.exe 2022-06-02 08:30:54 - Stopping process 3280 2022-06-02 08:30:54 - Send SIGINT 3280 2022-06-02 08:30:54 - SIGINT to 3280 failed - Killing as fallback 2022-06-02 08:30:54 - Stopping process 3504 2022-06-02 08:30:54 - Send SIGINT 3504 2022-06-02 08:30:54 - SIGINT to 3504 failed - Killing as fallback 2022-06-02 08:30:54 - Stopping process 3272 2022-06-02 08:30:54 - Send SIGINT 3272 2022-06-02 08:30:54 - SIGINT to 3272 failed - Killing as fallback 2022-06-02 08:30:54 - Finished reactor.exe 2022-06-02 08:33:41 - Starting C:\Program Files\nodejs\node.exe C:\reactor\reactor\node_modules\node-windows\lib\wrapper.js --file C:\reactor\reactor\app.js --scriptoptions= --log "Reactor wrapper" --grow 0.25 --wait 1 --maxrestarts 3 --abortonerror n --stopparentfirst undefined 2022-06-02 08:33:41 - Started 4184 2022-06-02 08:36:57 - Starting C:\Program Files\nodejs\node.exe C:\reactor\reactor\node_modules\node-windows\lib\wrapper.js --file C:\reactor\reactor\app.js --scriptoptions= --log "Reactor wrapper" --grow 0.25 --wait 1 --maxrestarts 3 --abortonerror n --stopparentfirst undefined 2022-06-02 08:36:57 - Started 3100 Windows event log event: Child process [4184 - C:\Program Files\nodejs\node.exe C:\reactor\reactor\node_modules\node-windows\lib\wrapper.js --file C:\reactor\reactor\app.js --scriptoptions= --log "Reactor wrapper" --grow 0.25 --wait 1 --maxrestarts 3 --abortonerror n --stopparentfirst undefined] finished with 1
      Multi-System Reactor
    • [Solved] suninfo.period "night" and rule trigger for sunset are at different times

      Crille

      I'm just curious, what's the difference between suninfo.period changing from "day" to "night" vs "after sunset" with no offset?
      suninfo.period changes to "night" 7 minutes and 33 seconds before "after sunset" is triggered in my latest-22149 bare metal setup.

      Multi-System Reactor
    • Status page rule history length.

      MikeReadington

      Hello Patrick,

      On the status page rule history is there any adjustably on length of the history shown? I had an occasion where it would have been helpful to go a few notches farther back than it does as currently configured.

      I don't know if this is a log parser or if it is a separate smaller data set. If it is a log parser, any chance for maybe something like a "more" button?

      Thanks,
      Mike

      Multi-System Reactor
    • [Solved] New device on Ezlo is not added in Reactor

      Crille

      I can't find any posts or reference in docs for this log message

      <EzloController:NOTICE> EzloController#ezlo received notice of new device, but auto-rediscover is OFF; ignoring

      I've restarted MSR and hard refreshed browser but the new entity is not added. Can I set auto-rediscover to ON or how do I get the new device added into Reactor?

      Edit:
      Bare metal latest-22142
      The device is a Xiaomi Mini Switch, it's publishing correct values in ezmqtt.

      Edit 2: The Xiaomi Aqara Mini Switch is now mapped in build 22149.

      Multi-System Reactor
    • Disk Warning on Multisystem Reactor

      S

      334ccd7a-9499-4dea-8a4a-2347609dce62-image.png

      For the life of me I cannot figure this out.
      when I run the du -hs command (from the host) for the mapped volume I get 25M
      (/home/seth/ReactorConfig maps to /var/reactor)

      Inside the container I ran du -hs for each of the folders that the ui is complaining about
      /opt/reactor = 71.2M
      /var/reactor/storage = 2.9M
      /var/reactor/logs = 17.6M

      If I run df on the docker container I get this. Disk space is not critical
      1f5d230c-0792-468b-b3b7-9f45e31581c5-image.png

      What gives?

      Multi-System Reactor
    For those who registered but didn't received the confirmation email, please send an email to support@smarthome.community with the email you used

    Last Modifed Information

    Multi-System Reactor
    3
    17
    174
    Loading More Posts
    • 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.
    • wmarcolin
      wmarcolin last edited by

      Hi

      Is it possible to access the information that the MSR has about the last date and time that a device suffered a change? The information that appears in the Entities area?

      dfd353df-15f9-44ef-bda3-8351363ea486-image.png

      Use Case: I want to monitor all devices, and those that are not communicating/acting for more than 48 hours, take notice and action

      Of course there are some that will not communicate by their nature, such as a water valve, so a list of exceptions would be created.

      The principle is almost the same as Hubitat's WatchDog APP, but I want to have my own, and not be dependent on Hubitat's communication or action.

      Thanks.

      1 Reply Last reply Reply Quote 0
      • wmarcolin
        wmarcolin last edited by

        @toggledbits hi!

        Is it possible to get the information?

        Thanks.

        1 Reply Last reply Reply Quote 0
        • toggledbits
          toggledbits last edited by toggledbits

          Everyone is used to looking at the attributes of entities, but the structure of an entity itself has properties. Actually, attributes is a property of entities (it's a map containing key/value pairs). The entity's name, id, and canonical_id are also properties of the entity. You could refer to these in an expression the same way you refer to attributes (as a property), and many of you are already doing this to get the name of an entity for some purpose (alert messages, commonly): getEntity( 'someid' ).name.

          There is a lastupdate property on an entity, but it may not work like you think/want it to. The lastupdate property is modified any time an entity is modified, and this would include modifications to other properties, like its name. It also tends to be modified when controllers start up or reconnect, because they re-inventory the hub and reconcile all of the entities and their capabilities at that time. In any case, the "Last Modified" time shown on the Entities list is that time, but again, it is not necessarily the time that an attribute was modified, and more particularly, it is not the time that an attribute you care about was last modified (there are lots of attributes on most entities that people never look at). It is not usable for the purpose you describe, and there is no alternative other than looking for changes in attribute values.

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

          wmarcolin 1 Reply Last reply Reply Quote 0
          • wmarcolin
            wmarcolin @toggledbits last edited by

            @toggledbits thanks for your comment.

            Based on it, I will try to progress with the idea of actually knowing that the timestamp is from an action of the device and not from updates or restarts as you comment.

            An additional help, you correctly comment that there are a number of attributes as you mention canonical_id. How is it possible to know these attributes? Where would they be exposed?

            Thanks.

            1 Reply Last reply Reply Quote 0
            • toggledbits
              toggledbits last edited by

              OK, let me make sure you understand:

              1. lastupdate is not a reliable indicator of device updates; there are many other things that will cause it to change, thereby invalidating its usefulness for the purpose you propose.
              2. canonical_id is not an attribute, it is a property. The attributes structure is itself a property, but the values contained in it are not properties, they are attributes. Properly terminology is important here, because if you start talking about canonical_id (incorrectly) as an attribute, you and/or others will start thinking you can get to it via entity.attributes.canonical_id, which is incorrect. Properties are directly accessible on the entity (entity.canonical_id is correct). @therealdb has already opened a PR for more description of entities and capabilities, and I will add to that some discussion of attributes and properties at a later date.

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

              wmarcolin 1 Reply Last reply Reply Quote 0
              • wmarcolin
                wmarcolin @toggledbits last edited by wmarcolin

                @toggledbits ok, thanks!

                Well after a few hours of thinking about your comments, lastupdate really doesn't serve the purpose of monitoring. There should be something that informs when the entity.attributes.door_sensor.state (motion_sensor...) changes state, and then it will be monitored.

                Now I understand why APP monitors that have Hubitat used battery_power.since as a reference, because it is the closest to a communication of the device effectively passing its state. But in this situation it excludes everything that does not work with battery power.

                Well back to another old discussion, that in Vera we had the zwave_device.failed that helped in this problem identification.

                Well anyway it was good to understand a little of the theme attribute and property, and I'm waiting for the information you commented that @therealdb requested.

                Thanks!

                1 Reply Last reply Reply Quote 0
                • G
                  gwp1 last edited by

                  I could be missing the boat here completely but it sounds like Vera was passing different/additional attributes than Hubitat is/does, yes? If Hubs won't pass it then MSR wouldn't know of it and, therefore, be unable to action on it.

                  Or am I missing the aforementioned watercraft?

                  Hubitat C-7 2.3.0.124, Home Assistant 2022.2.9, MSR on RPi4 bare metal Model B 2GBs latest-22168-5ab4d6c2

                  toggledbits 1 Reply Last reply Reply Quote 0
                  • toggledbits
                    toggledbits @gwp1 last edited by

                    @gwp1 said in Last Modifed Information:

                    I could be missing the boat here completely but it sounds like Vera was passing different/additional attributes than Hubitat is/does, yes?

                    That's right. Vera has its urn:micasaverde-com:serviceId:HaDevice1/CommFailure state variable, which at least applies to Z-Wave parent devices. There does not seem to be an analogue for this in Hubitat or Hass, but, of the two, I think Hubitat is most likely to fix it itself, and it may also be possible for a third-party app to address it (I have not ruled out abandoning Maker API as the interface for MSR and writing my own, but I have other things I want to spend my time on in this project right now).

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

                    wmarcolin 1 Reply Last reply Reply Quote 0
                    • wmarcolin
                      wmarcolin @toggledbits last edited by

                      @toggledbits

                      Sorry for the insistence with the subject 🙂

                      I exchanged a few messages with the developer of the Hubitat Z-Wave Mesh Details APP, Tony Fleisher also asked if there would be information about the last activity of the device with the z-wave radio.

                      He just answered me, that in the last version was incorporated the information extension, see his comment:

                      As to your question, the closest we have on Hubitat is the "Last Activity At" date, which you can see in the "Last Activity" column on the Devices page or at the end of the device details pages in the data section.

                      The latest version of the Z-Wave Mesh Tool has this available if you follow these steps:

                      1. Authorize Extended device data for your z-wave devices.
                      2. Select "Last Active Time" in the Additional Columns drop-down.

                      Looking at the information presented, I see that the date and time presented, effectively is not of a reboot or update of the device name, for example, it would actually be closer to what would be the last communication of the device with the hub.

                      350ff846-06ef-4ab4-974b-03cd68cef20d-image.png

                      I searched for this information in the MSR and don't see it, surely as he comments it is an extension of the device information.

                      Would it be possible for you @toggledbits, your kindness to perhaps look at this information, if we would be able to access it, or would it depend on the Make API?

                      Thanks, and again sorry for the insistence.

                      toggledbits 1 Reply Last reply Reply Quote 0
                      • toggledbits
                        toggledbits @wmarcolin last edited by

                        @wmarcolin said in Last Modifed Information:

                        surely as he comments it is an extension of the device information.

                        Then we should be able to see it in Reactor.

                        At this point, Reactor can only work with information that is passed through Maker API and Hubitat's events websocket, and it needs to be directly presented as attributes on the devices as those interfaces report them. If they do add attributes to the existing native Z-Wave devices, then those would be automatically immediately visible in the listed attributes of the Entities list.

                        Anything presented in the Hubitat UI is of no use if it does not make its way out of either Maker API, the events websocket, or another API that I might be able to access (the last option being the least desirable/most work).

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

                        wmarcolin 1 Reply Last reply Reply Quote 0
                        • wmarcolin
                          wmarcolin @toggledbits last edited by

                          @toggledbits

                          Ok, I get it, and that is what I thought, the Make API has to publish this additional information, otherwise of course the MSR won't be able to see it.

                          So this goes along with your comments that you would be working on a way to not use the Make API for MSR and open up a wider universe of integration, is that correct?

                          Anyway, I did the search below, and I see that all devices have capabilities.x_hubitat_extra_attributes which is an object. How do I read this object, I lack the knowledge here to work out this additional step to the query. Could you help me?

                          1386f32a-afe0-4f85-b168-9563a72e7a01-image.png

                          Thanks.

                          1 Reply Last reply Reply Quote 0
                          • toggledbits
                            toggledbits last edited by toggledbits

                            Why don't you just look at the Entities list?

                            f3528f46-e03c-423a-906c-8ef9ceaf9272-image.png

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

                            wmarcolin 1 Reply Last reply Reply Quote 0
                            • wmarcolin
                              wmarcolin @toggledbits last edited by

                              @toggledbits

                              Yes, I look everything up in Entities and then try to elaborate queries to use in the actions. My question was more in the sense of knowledge/learning, how to read what appears as [object Object], if it is possible.

                              1 Reply Last reply Reply Quote 0
                              • toggledbits
                                toggledbits last edited by toggledbits

                                OK. Well you can't get to attributes by going through the capabilities property. You've never done it that way before, when you reference other attributes on an entity. The attributes under ...extra... work the same as any other... power_switch, dimming, binary_sensor...

                                I think you're over-thinking it.

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

                                wmarcolin 1 Reply Last reply Reply Quote 0
                                • wmarcolin
                                  wmarcolin @toggledbits last edited by

                                  @toggledbits

                                  3001e71e-3dfc-4873-90f4-a0763b718875-image.png

                                  1 Reply Last reply Reply Quote 0
                                  • toggledbits
                                    toggledbits last edited by

                                    LOL!

                                    OK. Let's work from something you probably already do... checking the battery level. You are probably using an expression, either in a global variable or a group filter, that does this: entity.attributes.battery_power.level < 0.5.

                                    This is an access through several objects to get to the final member, level. The top object is the entity itself, supplied either by the context (in the case of a group filter as shown), or some variant of getEntity(). Either way, the result is an object that contains the definition of the entity.

                                    Adding .attributes to that, to make entity.attributes gets to the attributes property of the entity, which is itself an object that contains objects, the inner objects being identified by a capability name. So...

                                    Adding .battery_power then, to make entity.attributes.battery_power gets us to the object that contains the attributes for the battery_power capability. That capability publishes one attribute...

                                    Adding .level, to make entity.attributes.battery_power.level, which is the member that contains the (numeric) level, 0 to 1, representing the charge state of the battery.

                                    So accessing any other capabilities attributes is done the same way... entity.attributes.x_hubitat_extra.somename

                                    You can also enumerate the contents of an object using the each...in statement. For objects, in particular, the two-identifier syntax is useful because objects contain key/value pairs, and you want access to both the key and the value. So each v,k in obj: something will make the key and value available in the variables k and v to the something expression, for every key/value pair on obj.

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

                                    wmarcolin 1 Reply Last reply Reply Quote 0
                                    • wmarcolin
                                      wmarcolin @toggledbits last edited by wmarcolin

                                      @toggledbits again a class of knowledge, thank you!

                                      The part of checking the battery level I'm already using since you launched the Dynamic Group Controller, and of course already expanded to several other features, such as tracking the tripped devices.

                                      Anyway, I also opened a ticket so that the Make API can contemplate this extension of information, which is not really published as the date of the last device x hub communication.

                                      1 Reply Last reply Reply Quote 0
                                      • First post
                                        Last post

                                      Welcome. If you’d like to participate in the discussion, rather than just read, then you can join the forum. As a member, you can interact with others here to share your experience and ask the questions you need answered.

                                      Powered by NodeBB | Contributors
                                      Hosted freely by PointPub Media Communications Inc. | Contact us