How to upgrade from an old version of MSR?

[toggledbits]

Build 21060

Problem Reports:

PR 0000074: ContactSensor (Hubitat)
PR 0000068: Support HSM (Hubitat)
PR 0000068: Support system mode (Hubitat)
PR 0000050: Further enhancements to thermostat for Hass
PR 0000072: Support trip and untrip actions for Vera security sensors

Enhancements/non-PR fixes:

• Capability prefixing in Hubitat device mapping for increased specificity in certain types
• Improve the detail card display in the Entities list
• Temporary: enhanced logging of all actions performed on entities (e.g. by reactions, Entities list, etc.)
• Rule status card: Interval conditions now show date of last trip
• Rule status card: Date conditions now show time they are waiting for (may be temporary, maybe we like it and it stays)
• "tamper" system capability added

Today was a big day for details in device support. A lot of things got combed out, and many of the outstanding PRs addressed.

I will make a Synology docker container update tomorrow from this build.

[toggledbits]

Build 21061

0000050 - Additional tuning for Hass thermostats; please check

Other highlights:

• Support for color bulbs on Hubitat, with both RGB and HSL color modes (HSL is native to Hubitat);
• A bug in 21060 that caused newly-created rules to not be runnable until Reactor restart has been fixed;
• The build number will now be shown in the upper-right corner (previously unused area);
• Hubitat and Vera controllers were not passing control to superclass when an action didn't have a controller-specific implementation;
• Added new "hs_color" capability for hue+saturation color model (hsl is hs + dimming level);

IF YOU HAVE AN OPEN PR from a previously-opened device support issue, please check your PR and, if necessary, performance against this build 21061. I spent a lot of time today tweaking and tuning Hass thermostats, and Hubitat color lights. Yesterday's build included support for modes and HSM on Hubitat. But many of these bugs have no confirming feedback. Some of you are great at getting back to the PR and reporting your findings, good or bad; it would be great if everyone did this, as it's the easiest way for me to track. But the rule going forward is, no news is good news, and if I don't hear from you, I'll close the report.

ALSO please remember to check your email for reports from Mantis, and don't forget your Spam/Junk folders! Please mark "Not Spam" if your email system allows, or whitelist the domain, so you get the questions or feedback in a timely way.

[cw-kid]

@toggledbits What to do if the PR has already been closed? But we have feedback confirming what was implemented is working.

I've opened some PRs again just to leave that feedback.
But other times I've not bothered as they were already closed.

Wasn't sure what was best thing to do.

[toggledbits]

If it's not closed closed, you should be able to add a note without changing its status. That's why I've been leaving things "resolved" for at least a full day after the build the bug is fixed in. Mantis is new to me, too, so I'm still learning as well.

[cw-kid]

@toggledbits said in Multi-System Reactor Developer Preview AVAILABLE:

That's why I've been leaving things "resolved"

I can't leave a new note or comment on a PR that is currently resolved. For example this one here

To leave a note I have to press the Reopen button.

[toggledbits]

OK. Well, if it's good news, leave it closed; if it's needs work yet, go ahead and re-open.

[toggledbits]

Build 21062

Fixed:

• 0000078 - Fix dimming.set on Hass
• 0000077 - Support input_boolean on Hass
• 0000076 - Support GC100 plugin on Vera
• 0000050 - Thermostat support tweaks for Hass

Other work:

• Cleanup of RGB light model for Hass, added HS(L) model, support effects;
• Support ZWave device capability zwave_device, for Vera and Hass (Hubitat TBD)
• Documentation work

[kfxo]

Another good release. Confirming that 0000078 and 0000077 are tested and working on my system.

[toggledbits]

Build 21063

• 0000081: Implement RunLua action (on system entity for each VeraController instance)
• 0000080: Fix a problem running Vera scenes
• 0000075: Limit time delays to 24 hours (a multi-day delay on a schedule, specifically >24 days, could overflow JavaScript's 32-bit signed integer millisecond timers)

Other work:

• Fixed an issue with "changes" operator restoring configured values too literally (was inserting word "null" rather than blank/empty string)
• Progress on getting "set variable" action working. It's pretty much working for global expressions/variables. Still working on rule-based variables. PR 5 remains open.
• A lot of "linting". The old-school software-types will know what I mean.

[cw-kid]

Can confirm #80 and #81 and "issue with "changes" operator" are all working OK.

I've very nearly moved all my PLEG conditions / actions over to MSR.

I am waiting to be able to use an Expression value in a rule, for my "Master" dimmer virtual devices.

And for the Scene Activation stuff being exposed, for Fibaro Dimmer 2 modules for double / triple click events.

Also need to figure out how to setup a motion activated light rule.

[toggledbits]

I'm getting close on expressions. 21063 has working Set Variable for global expressions. Rule-based expressions is going to require some fairly large changes to the way evaluation of rules is done (not in the evaluation itself, but how they are scheduled). I could have pulled that off yesterday but it was getting late and the changes are not without risk, so I decided to defer. Once the configuration works, and Set Variable works, then I'll need to integrate the substitution capability into reaction arguments, etc. So still a couple of days, I think. That's PR#5 if you want to track it.

Scene activation is going to be tricky because Vera doesn't expose enough information over user_data or status requests. Doable, for sure, but it will need to be done slightly differently from the way you do it on Vera. It's the same thing openLuup runs into with scene controllers and sl_ prefixed state variables. I don't see a PR for that capability, though. Go ahead and open one.

[toggledbits]

Build 21064

• 0000082 - Support for ZWave scene controllers (system capability and Vera)

Other work:

Much time spent today getting Set Variable action update and running. Docs still need updates. The new substition syntax is ${{variable-name-or-expression}}

[toggledbits]

Just realized that one of the changes for variable substitution was causing an issue on some actions. I've respun the release and put it up. If you downloaded before 22:35 US Eastern, please re-download and install.

[toggledbits]

Build 21065

No PRs fixed today.

Work continued on expressions, and although I think I could mark PR #5 resolved, I'm going to leave it pending any reports related to them. I suspect there will be some discussion needed, at least, because they operate somewhat differently from Reactor for Vera/openLuup.

[toggledbits]

Build 21067

No PRs fixed today.

Ongoing work on expressions in the UI, and a number of other cleanups in the UI, for Rule editing in particular. Expression substitution using ${{...}} should be work in Reactions. Still working on conditions, so don't expect any success there yet.

[toggledbits]

Build 21068

• 0000089 - Entity action substitution values don't update after first run
• 0000090 - Expression not saving when modified
• 0000091 - Expression UI issues
• 0000092 - Expression UI issues

Expressions in conditions are still not available. I've chased UI issues most of the day today.

[toggledbits]

Build 21069

• 0000095: Fix annoying change of attribute when changing device selection
• 0000096: value_sensor.value now allows any data type
• 0000098: global expressions recreated with same name remember old values of prior expression

Lots of organizational and administrative work today as well.

[toggledbits]

Build 21072

• 0000108: Editing an extended attribute after having a system attribute selected applies validation rules of system attribute
• 0000107: Improve button consistency between rules and reactions
• 0000104: Error when attempting to recreate variable used in rule
• 0000095: Also fix in Reactions (reselect of action if device changes)
• 0000100: Make sl_CentralSceneAttr available for Vera

The x_vera_state capability is gone, and has been replaced with x_vera_svc_XXXX capabilities, wherein XXXX is the service ID on the Vera device. This slows startup, as additional queries must be made of every Vera device at initialization; the user_data query does not provide sufficient information. The Hubitat and Hass controllers also model this behavior. It's very tidy on Hubitat and Hass, I'm happy to say (and there is no performance penalty on these platforms).

The bad news (Vera users): If you are using x_vera_state attributes in your rules, you will need to edit them and choose the newer capability. Good news: this model will probably never change.

[toggledbits]

Build 21073:

• 0000110: Problem with formatting and reselection of Interval conditions in "relative to condition TRUE". Good time to mention that this mode is now DEPRECATED. This functionality was long ago replaced in Reactor for Vera by pulse output mode, but I didn't deprecate the feature in RFV at the time; should have. It is deprecated now in MSR.

Ongoing UI work, including exporting of group to new Rule, and importing of Rule to group.

[toggledbits]

Build 21074

• 0000110 - Interval condition not restoring related condition (option) correctly on edit
• 0000111 - Hass identified service not available (androidtv)
• 0000112 - Expression error
• 0000113 - Bridged Vera systems shows no devices (corrupt geofencing data)
• No PR - Fix precedence issue with lexpjs "each" and "first" statements

This version is also ready for testing under systemd on RPi (I've been running it that way all day). I will publish more on that later; I'm being called to the dinner table.