-
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.
-
I have 3 outside temperatures and I would like to pick the middle value of the 3 to use as the outside air temperature for calculations and logic.
The obvious, to me, mid() function does not seem to exist. What function can I use to pick the middle of the three values?
Thanks,
Tom -
My trusty vera plus is starting to have some issues that are making me think that it is about to die. i now get constant luup reloads even though i've moved almost everything except for z-wave devices and the iphone locator off that machine. it is even booting off an ssd drive to minimize wear and tear on the internal memory. I've moved all my logic off box to MSR, so it is just a glorified zwave adapter. I would love to hear any ideas that would make moving 60ish devices off that box to something else as painless as possible. the thought of excluding and including the devices sends shivers down my spine, so anything that helps me migrate the network would be greatly welcomed. anyone have any suggestions?
-
I'm probably going to release my first pass at the MQTTController for Reactor (aka MSR) this week. It doesn't yet intrinsically know about a lot of devices, but you can train it for pretty much anything, I think, and it would be great if a couple of our heavy MQTT users could help check it out and maybe help contribute some device templates.
I'm hoping to package it up for mid-week, assuming the rest of life stays on track.
Success factors for the test: solid familiarity with MQTT, a big mix of devices, and comfortable editing YAML (for creating the templates/mappings).
-
Whenerver openLuup restarts or reloads Luup MQTTController can't reconnect and I have to restart Reactor to solve it.
[latest-21321]2021-11-24T07:39:17.842Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:39:17.844Z <MQTTController:ERR> Controller MQTTController#mqtt is off-line! [latest-21321]2021-11-24T07:39:32.849Z <MQTTController:NOTICE> attempting reconnect [latest-21321]2021-11-24T07:40:15.473Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:40:30.475Z <MQTTController:NOTICE> attempting reconnect [latest-21321]2021-11-24T07:40:52.696Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:41:07.702Z <MQTTController:NOTICE> attempting reconnect [latest-21321]2021-11-24T07:41:40.213Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:41:55.217Z <MQTTController:NOTICE> attempting reconnect [latest-21321]2021-11-24T07:57:39.113Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:57:54.114Z <MQTTController:NOTICE> attempting reconnect [latest-21321]2021-11-24T07:58:16.396Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:58:31.399Z <MQTTController:NOTICE> attempting reconnect [latest-21321]2021-11-24T07:58:37.271Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:58:52.278Z <MQTTController:NOTICE> attempting reconnect -
I have multiple sensors connected to via Bluetooth to a Tasmota device.
All sensors report their values in the SENSOR topic, how do I map those to individual entities? -
I can no longer access the Rule Sets menu after upgrading to build 21275. Nothing happens when I click on Rule Sets. Other menu options work fine. I have cleared history, hard refreshed the browser, Rebooted. Works fine in Firefox and google chrome. I have always used Safari.
Suggestions?Safari for Mac version 15.0
MSR Version 21275-df3d784
Synology Docker -
Hi, in Reactor there is "SendData" actions to change value for device's configurations without to use Lua. Is this possible also for MSR?
If not, which is the possible way to do it?Thanks in advance
-
Goal: xmas tree/mantel lights go on with outdoor lights (if mode = Evening) but shut off at 23:00 whilst outdoor remain until sunrise -20. Tree and mantel should only go one when someone is home, outdoor go on no matter what, hence the mode trigger.
Configurations
Ruleset "Arm For Xmas" triggers = date ranges (all vetted/proven in prior years, good to go here) and sunset/sunrise:Screen Shot 2021-11-21 at 12.05.18 PM.png
Ruleset "Xmas tree/mantel lights" triggers =
Screen Shot 2021-11-21 at 12.07.29 PM.png
Seeking confirmation that my use of start time from the "Arm For" and end time from the "Xmas tree/mantel" scene will play well together.
-
Noticed in the last few nights that my Global Reaction to turn on a mere six lights in the evenings the same two devices no longer turn on. One is a dimming smart bulb, the other is a wall outlet.
This has been running flawlessly for months - just in the last few nights I've noticed these two devices being left behind and yes, it's always these two devices only.
"What changed?"
No Hubitat firmware updates No new devices added to Hubitat list itemTwo MSR updates (the last two, I keep up with the latest) list itemHome Assistant releases (should have zero bearing, HA is nothing more than pretty dashboards) list itemAdded MQTT to MSRI did do a z-wave "repair" last night and am waiting to see if this helps.
Is there any maximum or cap on number of devices that should be included in a Global Reaction?
*Marked as solved as the question asked was answered. The issue persists but the question was answered.
-
I would like to consult, and maybe even suggest, the possibility that all devices have the common attribute binary_sensor.state.
I am in the process of switching from Vera to Hubitat, and I see huge benefits in Hubitat having very few attributes available to the devices, which makes the device lighter, and faster in my opinion.
But one point that bothers me is for example plug and switch has binary_sensor.state which basically replicates the state of the Tripped Vera.
In Hubitat motion devices don't have it (similar Tripped), the status is motion_sensor.state, in this case my suggestion is if it would be possible that MSR creates in these devices the attribute binary_sensor.state and equals automatically the motion_sensor.state.
Expandindo a solicitacao (asking is not prohibited 🙂 ) to thermostats for example, I imagine that the hvac_control.mode attribute, other than "off" which means the device is "on (heat, cool)", also has the binary_sensor.state set to "true" (heat, cool) for "on" and "false" for "off".
In summary, regardless of the hub, or type of device a standard attribute to indicate and command the "on" or "off" status, similar to Tripped that has Vera that creates a standard of the devices.
Thanks.
-
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.
Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed. -
I can't get power_switch.state to reflect current state in the UI for Tasmota sonoff basic/dual/4channel pro.
It triggers a green glow in the Entities for the device but the value is never changed to true.Config:
"larmlampa_takfläkt_hall": name: "Larmlampa Takfläkt Hall" topic: "TakfläktHall" unit: "1" uses_template: tasmota_generic_relayLog:
[latest-21314]2021-11-16T18:03:02.003Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=tele/TakfläktHall/STATE, payload={"Time":"2021-11-16T19:03:00","Uptime":"35T11:31:51","Vcc":3.170,"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"Orion","RSSI":52,"APMac":"60:F4:45:E7:68:E6"}} [latest-21314]2021-11-16T18:03:02.006Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=openLuup/update/30009/TakfläktHall/tele, payload={"Time":"2021-11-16T19:03:00","Uptime":"35T11:31:51","Vcc":3.170,"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"Orion","RSSI":52,"APMac":"60:F4:45:E7:68:E6"}} [latest-21314]2021-11-16T18:03:02.007Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=openLuup/update/30009/TakfläktHall/Uptime, payload=35T11:31:51 [latest-21314]2021-11-16T18:03:02.008Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=openLuup/update/30009/TakfläktHall/Time, payload=2021-11-16T19:03:00 [latest-21314]2021-11-17T10:30:48.246Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=cmnd/TakfläktHall/POWER2, payload= [latest-21314]2021-11-17T10:30:48.246Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=cmnd/TakfläktHall/POWER1, payload= [latest-21314]2021-11-17T10:30:48.247Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/RESULT, payload={"POWER2":"OFF"} [latest-21314]2021-11-17T10:30:48.247Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for takfläkt_hall: {"POWER2":"OFF"} [latest-21314]2021-11-17T10:30:48.249Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for larmlampa_takfläkt_hall: {"POWER2":"OFF"} [latest-21314]2021-11-17T10:30:48.297Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/POWER2, payload=OFF [latest-21314]2021-11-17T10:30:48.298Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/POWER2 for takfläkt_hall: OFF [latest-21314]2021-11-17T10:30:48.298Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/RESULT, payload={"POWER1":"OFF"} [latest-21314]2021-11-17T10:30:48.298Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for takfläkt_hall: {"POWER1":"OFF"} [latest-21314]2021-11-17T10:30:48.298Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for larmlampa_takfläkt_hall: {"POWER1":"OFF"} [latest-21314]2021-11-17T10:30:48.304Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/POWER1, payload=OFF [latest-21314]2021-11-17T10:30:48.304Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/POWER1 for larmlampa_takfläkt_hall: OFF [latest-21314]2021-11-17T10:30:50.592Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/RESULT, payload={"POWER1":"ON"} [latest-21314]2021-11-17T10:30:50.593Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for takfläkt_hall: {"POWER1":"ON"} [latest-21314]2021-11-17T10:30:50.593Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for larmlampa_takfläkt_hall: {"POWER1":"ON"} [latest-21314]2021-11-17T10:30:50.596Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/POWER1, payload=ON [latest-21314]2021-11-17T10:30:50.597Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/POWER1 for larmlampa_takfläkt_hall: ON [latest-21314]2021-11-17T10:30:52.585Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/RESULT, payload={"POWER1":"OFF"} [latest-21314]2021-11-17T10:30:52.586Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for takfläkt_hall: {"POWER1":"OFF"} [latest-21314]2021-11-17T10:30:52.587Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for larmlampa_takfläkt_hall: {"POWER1":"OFF"} [latest-21314]2021-11-17T10:30:52.588Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/POWER1, payload=OFF [latest-21314]2021-11-17T10:30:52.588Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/POWER1 for larmlampa_takfläkt_hall: OFFpower_switch.state.PNG power_switch.state2.PNG
I've also tried some best guessing with a custom template without success, probably because of lacking knowledge from my side.
OT: Is ìnit in an upcoming build? Because how to handle a system restart is my next puzzle.
-
I am curious what this means ?
"New system capability button to express state of a single button or contact closure."
Thanks
-
Did MSR running on Docker ever gain the ability to do the R4V import? I recall it being a platform limitation for those who installed it on Synology NAS in particular.
EDITOR'S (@toggledbits) NOTE: This post was made in this thread: How To: Send TCP packet in Reaction
To my good friend @LibraSun , SHAME! This is a textbook example of thread-jacking: question/post in a topic that has nothing to do with the OP's topic/title, starting a second thread of discussion within that topic. Bad dog! No treats for you! 🐶
And yes, to the best of my knowledge, I'm getting all your DMs. I don't see any on this subject. -
Hi!
I have a Nest hello, and as a integration in Home Assistent. I would want to be able to create a automation/reaction when someone press the doorbell button. The problem is that this event/service will only appear as triggers (in HA):
3a763870-d062-4de7-be32-619120e3f90a-image.png I can't access the doorbell as an entity. I can only access it if I open the 'doorbell' device in HA.
My question is therefor; is it possible to access the doorbell and it's triggers within MSR?
I have MSR build 21307-1746e27 and HA core-2021.11.2.
Have a great day!
/Fanan -
For MSR users with SiteSensor still installed back on Vera, you might want to consider letting MSR take over those duties. Here's a quick run-down of how I imported one of my SiteSensor recipes into a Rule on MSR, using OpenWeather API* as an example.
STEP 1: Copy the Basics from Vera
(a) Go to your Vera > Devices, locate SiteSensor (the main instance, not one of its children devices) and click ► for details then click SETTINGS.
(b) Copy and paste (into Notepad or other text editor) the Request URL along with each of the defined expressions.STEP 2: Create a Rule on MSR
(c) Jump into Rule Sets and click "Create Rule". Click its title to rename the rule 'OpenWeather (API)" and click 'Rename'.
(d) Decide on appropriate Triggers (in my case, it's an OR group that includes an [INTERVAL] set to "Every 3 hours" plus a few [ENTITY ATTRIBUTE] entries reacting to things like entering/leaving home, waking up, etc.).
(e) In Set Reacion, create an [HTTP REQUEST] > [GET] action.
(f) Paste your old "Request URL" into the "Request URL" box.FYI GET calls to OpenWeather API* take the form:
http://api.openweathermap.org/data/2.5/weather?zip=<your_ZIP_code>&id=<your_Wx_ID>&appid=<app-id>&units=imperial(g) Create four new blank Expressions (name them openWx, Tx, Hx and Rx).
(h) Click SAVE & EXITSTEP 3: Process the Response
(i) Re-open rule "OpenWeather (API)" by clicking the 'Edit' icon.
(j) Within the [HTTP REQUEST] action, assign "Capture response to:" ► openWx
(k) Down in Expressions, click "[+]Add Expresssion" then enter the following:
Tx := round(openWx.main.temp,1)
// yields current outdoor temperature
Hx := round(openWx.main.humidity)
// yields current humidity conditions
Rx := openWx.rain ? ( openWx.rain['3h'] ? openWx.rain['3h'] : 0) : 0
// yields predicted rainfall, if present; otherwise 0
(l) Click SAVE & EXIT. Enjoy!Naturally, your specific needs and workflow will differ from the one I've outlined here. For instance, you may wish to explore the contents of the JSON object in openWx for additional data of interest to you, and define variables to match.
My goal here has been to illustrate some key concepts needed for moving from SiteSensor over to MSR:
Some syntax is the same, such as dot notation for object.item.access; Other syntax has changed, such as the use of ternary A ? B : C in place of IF (A, B, C); Manually setting an [INTERVAL] in lieu of SiteSensor's timed schedule;Pro tip: If your workflow demands that other Rules react to the output of the "OpenWeather (API)" rule, then be sure to create all of the aforementioned Expressions under "Global Expressions" instead, so they become accessible across all Rule Sets.
Once the transition is complete, you can either DISARM SiteSensor on Vera or remove it entirely with "Remove Device" (which will automatically remove all of its child devices).
*Additional reading:
OpenWeather API : https://openweathermap.org/api
FREE SUBSCRIPTION REQUIRED TO USE THIS SERVICEPRO TIP: See below for optimal way to incorporate OpenWeatherMap into your MSR workflow(s), by enabling the service directly in the reactor.yaml config file.
-
Well finally after a long time, I bought my Hubitat and start the process of working with 2 hubs, with the final goal of staying only with Hubitat.
I want to share my first insight, and of course then a shortlist if you can help to speed up my change with some information.
First perception Hubitat is much more professional, lighter, more technical, and thus more difficult for beginners. Vera has the Dashboard and Devices part more visually elaborated, it is easier and faster to see things, something that Hubitat has to build but gives much more potential for creation. Hubitat's manuals and documents are infinitely better. In summary, the more technical features in my opinion, far outweigh the visual point of Vera.
Some small doubts:
Is there in Hubitat a way to update/force neighbor nodes? In Vera I use the variable x_vera_device.failed or zwave_device.failed to detect devices with problems (long discussions in other posts), in MSR I don't see this variable for Hubitat devices, how to know the device is in a failure state? In MSR Entities I see that Vera devices have many more variables than Hubitat devices. In this matchEntities({capability:['x_vera_device']}) expression that lists all the devices, for this x_vera_device parameter it only shows what is in the Vera, which would be common to any hub? Who is the equivalent of Vera's Switchboard Plugin from @toggledbits on Hubitat? Do you have something like SiteSensor?Sorry for asking these questions, I have already searched the manuals and forums and they are issues that after a week of searching I still can't solve.
Thanks.
-
Hi
Wanted to create a rule for monitoring the battery level of Z-Wave devices on my Vera hub.
I can select the battery level as the trigger OK.
But not sure how to handle the Reaction to send an alert / notification ?
If in the triggers I have multiple devices monitored for their battery level
39a2f0af-c2e4-450b-a1ce-f542df31d02d-image.png
How could I create say a TTS announcement or text alert that mentions the name of the device who's battery level has dropped below 10% ? The device that has triggered the rule.
I'd rather not have to create an individual rule for each device etc.
Any ideas?
Thanks
-
Q: Is it fair/accurate to say that MSR cannot directly set the "LoadLevelLast" attribute of a Z-Wave light switch (paired with Vera)?
Reason I'm asking is that I routinely use Luup-based Reactor to set that value (e.g. to "60") whenever the switch is turned OFF, which causes future ON commands to automatically dim the light to that value (in this case, "60"). Kind of a built-in brightness limiter.
Granted, insofar as "LoadLevelLast" is intended as a read-only, derived value -- not meant to be set directly by Reactor in the first place -- I know this sounds like a trick question. And admittedly, the manner in which Reactor has done this for me in the past was by executing a snippet of Luup code containing a [variable_set] command. But it has worked (in most cases I've applied it to).
Is there any way to replicate this functionality -- however ill-advised in the grand scheme of things -- with MSR?
Entity Action/Capabilities
-
In the actions for a device, can someone explain what the differences is for a Hubitat device such as power_switch.on and x_hubitat_Switch.on.
-
The
power_switchcapability is MSR's native capability. Thex_hubitat_Switchcapability is MSR echoing Hubitat's native capability. Unfortunately, Hubitat's APIs do not give complete information about devices, and the relationships between their native capabilities and the devices they manage (neither does HomeAssistant, for the record; Vera is the best of the three platforms at this, if you can imagine that).Both actions in their respective capabilities will do the same thing. But, if you move a device from Hubitat to another controller, it won't have the Hubitat native capability (
x_hubitat.Switch) and its action, but it would retain the MSR capability (power_switch) and action, which may simplify the process of amending your rules to reflect the change..