When using Vera I made use of Deus Ex Machina II after Patrick took it over. Worked brilliantly for ghosting lights on and off when I was away.

Now that my devices are migrated to Hubitat I can't make use of DEMII.

Any thoughts on how to replicate this randomness with two or three lights in MSR?

Hi .... Is this reaction made right?
When I reload reaction the 2entity actions at the bottom is popping up. I erase them but when I reload the reaction they come back...

I want my shade to go close if window is closed and if open it should go to 70% (0.7).

/Mattias!Skärmavbild 2021-05-13 kl. 07.51.11.png

Feedback / solutions for openLuup's built-in Tasmota MQTT bridge.

For those using the Home Remote dashboard app, this maybe of interest, Bill has just shown me how to more easily either create buttons on your own custom pages or "Scene" devices / tiles on Group pages, that when pressed will send out HTTP commands to MSR, to then run either a Global Reaction or a Rule Set that is triggered via a Global Expression value change.

Apr 29 Feature Request - Make it easier to create button to send HTTP requests Feature Request - Make it easier to create button to send HTTP requests

I have managed to create two buttons that when pressed they send out a HTTP request. One button was an ON command and the other button was an OFF command. I followed the example here However for creating lots of buttons with this functionality I can see it being very difficult and a lot of hassle...

Been wanting to be able to do this for a while now.

This is a custom page with regular buttons, these two test buttons are initiating Global Reactions in MSR:

e5146a4e-75a4-48a5-a286-aec93e550e4d-image.png

This is a GROUP page with "Scene" tiles, these are initiating Rule Sets in MSR:

edde011d-0542-4b7a-aef5-d2986cc27f81-image.png

I have a Hubitat device errors of devices that I am pretty sure I have never published to MSR. I have looked through my rules and cant find any reference to the devices and have checked my Maker API instance and the devices are not included. I am using Version 21129. Here is an example:

2021-05-10T01:30:00.013Z Engine:5:1032:Engine.js _process_reaction_queue() running task 4 { "tid": 4, "id": "rule-kodpluwh:R", "rule": "rule-kodpluwh", "__reaction": [RuleReaction#rule-kodpluwh:R], "next_step": 0, "status": 0, "ts": 1620610200011, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] }
2021-05-10T01:30:00.013Z Engine:NOTICE Starting reaction Test-Stairs Light<RESET> (rule-kodpluwh:R)
2021-05-10T01:30:00.013Z Engine:NOTICE Test-Stairs Light<RESET> delaying until 1620610500013<5/9/2021, 8:35:00 PM>
2021-05-10T01:30:00.014Z Engine:5:1036:Engine.js _process_reaction_queue() task returned, new status 2; task 4
2021-05-10T01:30:00.015Z Engine:5:1071:Engine.js _process_reaction_queue() ending with 1 in queue; waiting for 1 (next delayed task)
2021-05-10T01:30:04.873Z HubitatController:ERR HubitatController#hubitat device 96 not found. You may need to publish the device in Maker API to make it accessible to Reactor.
2021-05-10T01:30:04.884Z HubitatController:ERR HubitatController#hubitat device 96 not found. You may need to publish the device in Maker API to make it accessible to Reactor.
2021-05-10T01:30:04.888Z HubitatController:ERR HubitatController#hubitat failed request for device 96 info: Error: unparseable response
2021-05-10T01:30:04.889Z HubitatController:CRIT Error: unparseable response
Error: unparseable response
at /opt/reactor/server/lib/Controller.js:486:35
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:93:5)

OK, people, here we go! At long last, Multi-System Reactor developer preview is available!

The package can be downloaded from the Reactor bug tracker, a MantisBT system (at https://reactor.toggledbits.com/mantisbt/). There is a download button in the left margin, as well as links to the documentation, which you will need for installation.

UPDATE 2021-02-24 -- To keep spammers off, I've locked down registration on the Bug Tracker. To get access to the Bug Tracker and preview downloads, please PM me (not reply here) your full name and email address and I will set up an account for you.

This version of MSR will run on Linux systems, including RPi's under Raspios Buster, running node.js version 12.10 or higher (v14.15.1). For RPi users, there is an installation script that will install a local copy of node.js (for the logged-in user).

Bugs reports will be handled through the bug tracker only. Discussion and questions in this forum are fine, though (if that leads to a bug report, we'll transition).

This version supports Vera (and openLuup to the degree it's compatible with Vera Luup), Hubitat, and Home Assistant. Some of the device support on the H platforms is still a bit basic, but it is largely controlled by configuration and progress can be made quickly.

The documentation beyond installation is a mess. Of course, I started with the existing documentation and have been massaging into MSR's particulars, but it still has a long way to go on the detail.

I know I don't have to say this, but I will anyway... let me know how it goes!

Hi came across this thought it may be worth discussing.

CORE by Oh-La LABS: Home Automation. Done Right. Just lauched their kick starter
https://www.indiegogo.com/projects/core-by-oh-la-labs-home-automation-done-right#/

I am a pretty active forum user over on the QNAP forum and there has been a number of viral threads there and on reddit about the spread of ransomware on these NAS.

I wanted to post here to say that this is a fresh reminder to be very cautious with the current state of the affair when it comes to smarthomes and the trend towards IOT we are observing from all these companies attempting to make our homes cloud dependent, opening so called "secure tunnels" to their servers which can turn into very real exposures to your LAN (home network).

In order to mitigate it, QNAP released a firmware which now has autoupdate enabled by default (reminds me one other company...) and IMHO is the climax of absurdity but in fact when I come to think about it is how the amazon echos and ecobees work for example without even offering the ability to disable.

I am in no way a security expert but have had enough exposure and interest about it to recommend using a real firewall for your home network to block these backdoors if you have a smarthome and avoid these cloud oriented platforms and devices as if they were COVID.

Hi

In my ongoing quest to try and retrieve as much information as I can about the amount of energy I’m using , I found out that I could use SNMP to see how much power (watts) my UPS is handling .

To do this, I installed snmpd/snmp on my Vera linked Raspberry Pi, and then ran the following command.

local command = io.popen("ssh -i /etc/dropbear/dropbear_rsa_host_key pi@192.168.102.37 'snmpwalk -Os -c public -v 1 10.10.10.103' 2>&1") local response = command:read("*a") print(response)

Which returned a huge amount of information, which prompted me to ask the community here if there anything on Vera/OpenLuup that people have that can process this sort of information into a new devices and associated variables to then monitor/track going forward ?

iso.3.6.1.2.1.1.1.0 = STRING: "Eaton 5P 1150" iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.705.1 iso.3.6.1.2.1.1.3.0 = Timeticks: (51435090) 5 days, 22:52:30.90 iso.3.6.1.2.1.1.4.0 = STRING: "Computer Room Manager" iso.3.6.1.2.1.1.5.0 = STRING: "ups239" iso.3.6.1.2.1.1.6.0 = STRING: "Computer Room" iso.3.6.1.2.1.1.7.0 = INTEGER: 72 iso.3.6.1.2.1.1.8.0 = Timeticks: (0) 0:00:00.00 iso.3.6.1.2.1.1.9.1.2.1 = OID: iso.3.6.1.6.3.1 iso.3.6.1.2.1.1.9.1.2.2 = OID: iso.3.6.1.6.3.10.3.1.1 iso.3.6.1.2.1.1.9.1.2.3 = OID: iso.3.6.1.6.3.11.3.1.1 iso.3.6.1.2.1.1.9.1.2.4 = OID: iso.3.6.1.6.3.15.2.1.1 iso.3.6.1.2.1.1.9.1.2.5 = OID: iso.3.6.1.6.3.16.2.1.1 iso.3.6.1.2.1.1.9.1.3.1 = STRING: "The MIB Module from SNMPv2 entities" iso.3.6.1.2.1.1.9.1.3.2 = STRING: "SNMP Management Architecture MIB" iso.3.6.1.2.1.1.9.1.3.3 = STRING: "Message Processing and Dispatching MIB" iso.3.6.1.2.1.1.9.1.3.4 = STRING: "USM User MIB" iso.3.6.1.2.1.1.9.1.3.5 = STRING: "VACM MIB" iso.3.6.1.2.1.1.9.1.4.1 = Timeticks: (0) 0:00:00.00 iso.3.6.1.2.1.1.9.1.4.2 = Timeticks: (0) 0:00:00.00 iso.3.6.1.2.1.1.9.1.4.3 = Timeticks: (0) 0:00:00.00 iso.3.6.1.2.1.1.9.1.4.4 = Timeticks: (0) 0:00:00.00 iso.3.6.1.2.1.1.9.1.4.5 = Timeticks: (0) 0:00:00.00 iso.3.6.1.2.1.2.1.0 = INTEGER: 2 iso.3.6.1.2.1.2.2.1.1.1 = INTEGER: 1 iso.3.6.1.2.1.2.2.1.1.2 = INTEGER: 2 iso.3.6.1.2.1.2.2.1.2.1 = STRING: "LOOPBACK" iso.3.6.1.2.1.2.2.1.2.2 = STRING: "eth0" iso.3.6.1.2.1.2.2.1.3.1 = INTEGER: 24 iso.3.6.1.2.1.2.2.1.3.2 = INTEGER: 6 iso.3.6.1.2.1.2.2.1.4.1 = INTEGER: 1500 iso.3.6.1.2.1.2.2.1.4.2 = INTEGER: 1500 etc....

I had an existing rule that turns on my Kitchen ceiling lights to 100% when motion is detected.

I want to make a change so that when Vera is in Night Mode the lights will instead turn on to 25% brightness.

I have added a Constraints Group in to the Set Reaction and set it to OR :

edbb6209-5075-42ed-86ce-fb1bd3bb7e16-image.png

Is this likely to work or not ?

Or do I need two Constraints Groups within the Set Reaction ?

I can test it later on when its time to put Vera in to Night mode.

Thanks

How are folks handling situations where they want to have Conditional Actions or Branching Logic in their Set Reactions for a rule? Are you creating Duplicating the same trigger and setting different conditions and Actions?

Is there an approach where you combine a main rule with your entity triggers with sub rules that trigger off Expressions? You then could write your conditions as Set Variable actions in the Main Rule for the Expressions that evaluate to true or false. Each sub rule would trigger based on the expression changing to true and then could also change it back to false after.

Not sure if that's worth the complexity for the reusability and control over duplicate triggers.

Posted this in Vera forum with no response:
Seeing this in reactor UI:
A newer version of the device information database is available. Please use the update function on the Tools tab to get it. This process is quick and does not require a Luup reload or browser refresh–you can immediately come back here and go right back to work! The new version is 865.877, and you are currently using 557.352…

Hit update in Tools and get an error: “The update could not be retrieved. If this problem persists, consult the documentation.”

Looked through logs and not seeing anything specific. You have a keyword I should search for?

I am not a programmer, so I am picking this up piece by piece.

I would like to use a rule-based expression to store the current value of a dimmer, change the dimmer value, then change it back to the stored value.

I have a working global expression that I have used.

getEntity( "VeraShop>device_24" ).attributes.dimming.level

I have a blank global expression ready to use in "set variable" that is available to set.

I am stuck with the formatting of the "set variable" field to set the variable. If I get pointed in the right direction, I am fairly confident I can get the rest going on my own. .

Thanks in advance

This was working and tested previously, but now doesn't seem to be.

caecaac3-2c49-4aa0-b911-ff1d16029883-image.png

I turned the heating on earlier, however I have since turned if off again. However the trigger in this rule still says the current set point value is 21. Its not its currently 10.

A window was just opened and a TTS heard, which drew my attention to this rule now as it should not of fired its actions.

dbf42371-5cef-49ff-9b26-87c15ad212ea-image.png

Vera variable now:

072f3f45-ef90-4ffe-a721-50eea18327ef-image.png

Thermostat device information from the Entities:

battery_power.level=0.49 battery_power.since=1620139135000 hvac_control.mode=null hvac_control.state=null hvac_heating_unit.setpoint=21 hvac_heating_unit.state=null hvac_heating_unit.units="c" power_switch.state=null value_sensor.units="c" value_sensor.value=18.1 x_vera_device.configured=true x_vera_device.device_number=189 x_vera_device.device_type="urn:schemas-upnp-org:device:Heater:1" x_vera_device.failed=false x_vera_device.mapped_by="*;device_type=urn:schemas-upnp-org:device:Heater:1" x_vera_device.mapped_class="heatonly_thermostat" x_vera_svc_micasaverde_com_HaDevice1.AutoConfigure="-1" x_vera_svc_micasaverde_com_HaDevice1.BatteryDate="1620139135" x_vera_svc_micasaverde_com_HaDevice1.BatteryLevel="49" x_vera_svc_micasaverde_com_HaDevice1.CommFailure="0" x_vera_svc_micasaverde_com_HaDevice1.CommFailureAlarm="1612455867,0" x_vera_svc_micasaverde_com_HaDevice1.CommFailureTime="0" x_vera_svc_micasaverde_com_HaDevice1.Commands="heater_setpoint" x_vera_svc_micasaverde_com_HaDevice1.Configured="1" x_vera_svc_micasaverde_com_HaDevice1.FirstConfigured="1485879775" x_vera_svc_micasaverde_com_HaDevice1.LastUpdate="1607103908" x_vera_svc_micasaverde_com_HaDevice1.ModeSetting="1:;2:H,10.0;3:H,10.0;4:H,10.0" x_vera_svc_micasaverde_com_HaDevice1.PollRatings="5.00" x_vera_svc_micasaverde_com_HaDevice1.WakeupRatings="5.00" x_vera_svc_micasaverde_com_HaDevice1.sl_BatteryAlarm="0" x_vera_svc_micasaverde_com_ZWaveDevice1.AssociationGet="2,190,;" x_vera_svc_micasaverde_com_ZWaveDevice1.AssociationNum="5" x_vera_svc_micasaverde_com_ZWaveDevice1.AssociationSet="2,190" x_vera_svc_micasaverde_com_ZWaveDevice1.Capabilities="18,150,0,1,8,0,B,|49:1,67,112,114,128,132:2,133,134," x_vera_svc_micasaverde_com_ZWaveDevice1.ConfiguredAssoc="2,190" x_vera_svc_micasaverde_com_ZWaveDevice1.ConfiguredName="" x_vera_svc_micasaverde_com_ZWaveDevice1.ConfiguredVariable="1-variable 1,1d,255,2-variable 2,1d,1,3-variable 3,1d,10" x_vera_svc_micasaverde_com_ZWaveDevice1.ConfiguredWakeupInterval="300" x_vera_svc_micasaverde_com_ZWaveDevice1.FirmwareInfo="" x_vera_svc_micasaverde_com_ZWaveDevice1.LastArr="1620138237,69" x_vera_svc_micasaverde_com_ZWaveDevice1.LastNnu="1620137632,69" x_vera_svc_micasaverde_com_ZWaveDevice1.LastReset="1485882104" x_vera_svc_micasaverde_com_ZWaveDevice1.LastRouteUpdate="1620109432" x_vera_svc_micasaverde_com_ZWaveDevice1.LastWakeup="1620152934" x_vera_svc_micasaverde_com_ZWaveDevice1.ManufacturerInfo="89,1,3" x_vera_svc_micasaverde_com_ZWaveDevice1.MeterScale="" x_vera_svc_micasaverde_com_ZWaveDevice1.MeterType="" x_vera_svc_micasaverde_com_ZWaveDevice1.MultiChCapabilities="" x_vera_svc_micasaverde_com_ZWaveDevice1.MultiChEndpoint="" x_vera_svc_micasaverde_com_ZWaveDevice1.NodeInfo="31,43,70,72,80,84,85,86," x_vera_svc_micasaverde_com_ZWaveDevice1.PollNoReply="378" x_vera_svc_micasaverde_com_ZWaveDevice1.PollOk="16295" x_vera_svc_micasaverde_com_ZWaveDevice1.PollSettings="10800" x_vera_svc_micasaverde_com_ZWaveDevice1.SensorBiType="" x_vera_svc_micasaverde_com_ZWaveDevice1.SensorMlScale="" x_vera_svc_micasaverde_com_ZWaveDevice1.SensorMlType="" x_vera_svc_micasaverde_com_ZWaveDevice1.SetPointInfo="H1," x_vera_svc_micasaverde_com_ZWaveDevice1.SubscribedAlarms="" x_vera_svc_micasaverde_com_ZWaveDevice1.TemperatureScale="1,0,2" x_vera_svc_micasaverde_com_ZWaveDevice1.VariablesGet="1,255,2,1,3,10," x_vera_svc_micasaverde_com_ZWaveDevice1.VariablesSet="1-variable 1,1d,255,2-variable 2,1d,1,3-variable 3,1d,10" x_vera_svc_micasaverde_com_ZWaveDevice1.VersionInfo="2,2,78,6,0" x_vera_svc_micasaverde_com_ZWaveDevice1.WakeupInterval="300" x_vera_svc_micasaverde_com_ZWaveNetwork1.ConsecutivePollFails="0" x_vera_svc_micasaverde_com_ZWaveNetwork1.LastPollSuccess="1620149034" x_vera_svc_upnp_org_Dimming1.LoadLevelTarget="58" x_vera_svc_upnp_org_HVAC_UserOperatingMode1.ModeStatus="HeatOn" x_vera_svc_upnp_org_SwitchPower1.Target="0" x_vera_svc_upnp_org_TemperatureSensor1.CurrentTemperature="18.10" x_vera_svc_upnp_org_TemperatureSetpoint1.AllSetpoints="10.00,0.00,5.00" x_vera_svc_upnp_org_TemperatureSetpoint1.CurrentSetpoint="10.00" x_vera_svc_upnp_org_TemperatureSetpoint1.NewCurrentSetpointC="23" x_vera_svc_upnp_org_TemperatureSetpoint1.NewCurrentSetpointF="73.4" x_vera_svc_upnp_org_TemperatureSetpoint1.Range="0,0/0,0;0,0/0,0;5,30/41,86" x_vera_svc_upnp_org_TemperatureSetpoint1.SetpointTarget="10.00" x_vera_svc_upnp_org_TemperatureSetpoint1_Heat.CurrentSetpoint="21.00" zwave_device.capabilities="18,150,0,1,8,0,B,|49:1,67,112,114,128,132:2,133,134," zwave_device.failed=false zwave_device.manufacturer_info="89,1,3" zwave_device.node_id=57 zwave_device.version_info="2,2,78,6,0" Capabilities: battery_power, hvac_control, hvac_heating_unit, power_switch, toggle, value_sensor, x_vera_device, x_vera_svc_micasaverde_com_HVAC_OperatingState1, 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_HVAC_UserOperatingMode1, x_vera_svc_upnp_org_SwitchPower1, x_vera_svc_upnp_org_TemperatureSensor1, x_vera_svc_upnp_org_TemperatureSetpoint1, x_vera_svc_upnp_org_TemperatureSetpoint1_Heat, zwave_device Actions: hvac_control.set_mode, hvac_heating_unit.set_setpoint, power_switch.off, power_switch.on, toggle.toggle, x_vera_device.set_variable, 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.ResetNetwork, 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_HVAC_UserOperatingMode1.SetEnergyModeTarget, x_vera_svc_upnp_org_HVAC_UserOperatingMode1.SetModeTarget, x_vera_svc_upnp_org_HVAC_UserOperatingMode1.SetName, x_vera_svc_upnp_org_SwitchPower1.SetTarget, x_vera_svc_upnp_org_TemperatureSensor1.SetApplication, x_vera_svc_upnp_org_TemperatureSensor1.SetName, x_vera_svc_upnp_org_TemperatureSetpoint1.SetApplication, x_vera_svc_upnp_org_TemperatureSetpoint1.SetCurrentSetpoint, x_vera_svc_upnp_org_TemperatureSetpoint1.SetName, x_vera_svc_upnp_org_TemperatureSetpoint1_Heat.SetApplication, x_vera_svc_upnp_org_TemperatureSetpoint1_Heat.SetCurrentSetpoint, x_vera_svc_upnp_org_TemperatureSetpoint1_Heat.SetName, zwave_device.poll

In the rule if I change the trigger to use this Entity Attribute instead, then now its correctly showing 10 as the current set point.

70833da9-d55d-4f89-8abf-724960e04a46-image.png

Besides having integrated the xiaomi vacuum cleaner robot to my system, I have actually also integrated a large number of air filters to my automation system (homeassistant -> bridged into openLuup) for quite sometime. I have been using them mostly to monitor the air quality in different rooms. All of these devices are wifi but are communicating through a local API. I was looking today at replacing also my foobot which is my very last cloud dependent devices (and a non critical one) and found/ordered this:

60.99US $ 38% OFF|Xiaomi Mijia Air Quality Tester 3.97 60.99US $ 38% OFF|Xiaomi Mijia Air Quality Tester 3.97

Smarter Shopping, Better Living! Aliexpress.com

It can very likely be integrated into home-assistant and then openLuup the same way I have with my filters but what I found particularly interesting is its low cost and the fact that it can also serve as a BT gateway! Why is this getting me excited? Because I have long regretted the loss of Plantlink which was a zigbee platform for soil/plant monitoring which unfortunately was cloud dependent and went belly up. I have since been automating my garden watering based on predictive algorithm only, without sensors. (yes still with openLuup). I am now looking forward to see how this will workout as my better half is very invested in gardening these days...

Hi Not seeing the download for this build in the MantisBT bug tracker.

In my Vera config I have two SiteSensors (one for Ambient Wx, one for OpenWxMap) that point to two unique Reactor devices for controlling HVAC in my home. This is done for redundancy - if the Ambient API drops it returns zero data which then triggers a standalone Master API Reactor device to flip on the OWM SiteSensor and corresponding HVAC Reactor device to continue controlling the house conditions.

Once the Ambient API returns to available the Master API Reactor device flips back to the Ambient SiteSensor and corresponding HVAC Reactor device, turning OFF the SiteSensor for OWM to save on API calls.

I've been able to duplicate one half of this, including the Master API role, in MSR. But... here's the tricky part... I can't turn "off" the MSR Rule Sets for the OWM version. As such, HVAC is sent conflicting data and doesn't know what to do.

Before I go alls deep into explaining how all of this currently works, am I missing something somewhere that would allow me to trigger the on/off of MSR Rule Sets?

General discussion on all things MQTT.

Knowing that MSR Preview may not yet fully implement LuaXP (CORRECTION: MSR uses a different language lexpjs), I could not resist whipping up some text expressions for fun. Whereupon two things popped out at me:

The new scaling (0.00 - 1.00) of Dimming Level will require a rewrite of certain Expressions that I use to balance my light levels. For example, it was my custom to monitor one lamp's brightness (0 - 100) with Reactor Luup, then set another lamp to 93% of that level, using this Expression: floor(getstate( 9, "urn:upnp-org:serviceId:Dimming1", "LoadLevelTarget" ) * 0.93)

Now, in MSR, it will become necessary to modify that to read:

floor ((getEntity( "vera>device_9" ).attributes.dimming.level * 0.93)*100)/100

which effectively scales the value up x 100 (so that floor() can act upon it correctly), then downscale it / 100. Just an FYI to ponder.

I'm noticing that every edit, however minor, of an Expression in MSR requires an immediate SAVE click before the 'Run' button will become active. That is to say, I cannot repeatedly evaluate the Expression during editing, without clicking SAVE first.

Only mentioning this latter behavior since it departs so dramatically from Reactor Luup's paradigm.