Need help reducing false positive notifications

[rafale77]

If you are on a budget the T520 will run about as fast as a rPi4B for single core applications but slower for multi core. For home automation you probably won't see any difference. But it is definitely much faster than the rPi2 in every aspects. It is a perfect little machine to play around without having to worry about ever bricking it and you can repurpose it for other things later.

Edit:
This might be an even better choice:
https://www.ebay.com/itm/HP-T620-Dual-Core-AMD-Gx217Ga-1-65GHz-4GB-RAM-Radeon-HD-16GB-SATA-Flash-Drive/184659317870?

A little faster, only with W7ES license but has a 16GB eMMC.

[Matohl]

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

"The rPi4 is a bit tricky to boot from SATA but it can be done and if you want a reliable system, you should definitely go down that route."

Today with an upgraded system, since the RPi firmware has native support, it is fairly straight forward. There are tons of guides and videos online to help.

[LibraSun]

IN reading the MSR docs, I see we'll soon have the capability to import backup files saved from a Vera hub's master Reactor device, thereby auto-creating Rulesets on the receiving MSR.

I presume the necessary conversion applet (in the form of a .JS script) will be forthcoming as part of the /tools folder under MSR?

Has anyone tested this feature out yet? I wouldn't mind being a guinea pig, if more data points are required to iron out kinks.

[kfxo]

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

IN reading the MSR docs, I see we'll soon have the capability to import backup files saved from a Vera hub's master Reactor device, thereby auto-creating Rulesets on the receiving MSR.

I presume the necessary conversion applet (in the form of a .JS script) will be forthcoming as part of the /tools folder under MSR?

Has anyone tested this feature out yet? I wouldn't mind being a guinea pig, if more data points are required to iron out kinks.

Indeed that feature is already available. I imported close to 400 rules and it has been pretty smooth. We have ironed out a couple bugs already. But as pointed out in the guides, you really got to go through it all and fix some things as you go. My initial plan was to start fresh but I'm glad I didn't as it has saved me a lot of time. If you have a lot to transfer over I would definitely give it a shot.

[toggledbits]

Access to the /tools folder is also one of the challenges for the Synology docker container, and command line access is necessary to run the tool, there is no GUI. It's also a node.js application, and node is not available on the NAS when you SSH in; it exists only within the docker container.

For the moment, I'm happy to run the import for you, if you email me a recent (preferably new) Luup Reactor backup file via the email address in the "Support" section of the About page in MSR. Agh. Check that. I can't. It needs access to your device data. I'm going to have to work out some kind of GUI for this. Won't be soon....

[LibraSun]

Thanks for the clarification. Figured I might be a "special case" (who, me?).
Not a high priority on this end, just eager to play. In the meantime, I too shall research what are the options for one to conduct a Terminal session directly on one's Synology NAS. I feel as though this ought to be possible. Will report back any salient findings.

• Libra

N.B. I shall be starting my journey here... https://www.synology.com/en-global/knowledgebase/DSM/help/DSM/AdminCenter/system_terminal

[PerH]

I just tested importing all my reactors from openluup, and it worked beautifully! (once i changed the "-" to "_" in the "import-reactor-backup.js" - the manual has that wrong)

I'll try enabling some of the less important rules tomorrow. One thing i'll look into is how to have common logic for i.e. light control in multiple rooms.
Looks very nice, @toggledbits!

[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.