Multi-System Reactor Developer Preview AVAILABLE
-
Pi4 (2GB RAM) arrived today. can't wait to join in the action.
Some advice please from the knowledgeable ones if I can.
I had intended to use a SATA HD instead of the SD Card, perhaps this isn't necessary and may be an overkill?
What does the collective think? -
No it’s not overkill. If you look at the HA forum, you will see legions of people migrating away from the rPI to intel NUC because of the SD card issue. These are very cheap, controller less (therefore cache less, garbage collection less, wear leveling less) NAND flash which have a relatively short lifetime (similar to what Ezio embedded in their updated/downgraded version of the vera). 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.
A big part of it of course will depend on how much storage writing you will be doing but regardless, mid-long term it’s a bit of a waste. The SSD cards are really designed for digital cameras where pictures are taken until the card is full, transferred and then erased again on a low frequency basis. They are not very good for computing storage use.
-
I'm on my second NUC. The first one was a Celeron, now on an i3 I found getting dust in our offices (it was used as front desk PC before the pandemic). This to say that probably eBay is your friend, and Amazon too. You could find a lot of deals (well under 100 USD/EUR) for used/reconditioned NUCs.
Mine with i3, 16GB ram (I added more) and 256 GB SSD is heavily used (openLuup, my own software, cams processing, mqtt server, a lot of mqtt clients, bluetooth for MiFlora and SwitchBot) and barely consuming more than 5% CPU.
-
They're good little boxes, although I wish they were a bit cheaper. My Hass runs on a NUC, and I also use a NUC as my on-LAN secondary DNS/NTP and a few other things (like Unifi management). I'm a big fan of the Jetson Nano, too. I think this board needs more attention.
-
Alternative here in the US: I just got an HP T640 for $90. It's a little big physically but all the memory is replaceable: 2 sodimm slots, one 16gb mmc which I replaced with an SSD and boom, that's my MSR box. CPU is a ryzen equivalent of the i3 8145U in the NUC. Runs circles around any rpi for a lot less when you add up all the storage and peripheral cost. Heck it adds up to be even cheaper than my mini pc celeron box I posted in this forum before and is 3x faster. (or 8-10x faster than any rpi)
More info here: https://forums.servethehome.com/index.php?threads/new-hp-t640-thin-client-ryzen-r1505g-4gb-16gf-no-kb-mouse-no-os-installed-109.31544/
Edit:
Added for reference comparison to rpi4... pretty hard to justify buying a raspberry honestly when they end up costing the same.or here
-
In the same tone of what I posted before but with an older slower 6W CPU if you want to dirt cheap, these are very good (as in more reliable, upgradable, cheaper) than rPIs
in the UK: https://www.ebay.com/itm/HP-Flexible-T520-Thin-Client/265062105722?
in the US: https://www.ebay.com/itm/HP-T520-Flexible-Thin-Client-4GB-DDR3-V2V45UA-ABA-No-Stand-SSD/313404749197?You just need to find an old HP laptop power supply for it. That won't break your scotch budget... and amazingly they come with a windows10 pro license in the BIOS.
-
In the same tone of what I posted before but with an older slower 6W CPU if you want to dirt cheap, these are very good (as in more reliable, upgradable, cheaper) than rPIs
in the UK: https://www.ebay.com/itm/HP-Flexible-T520-Thin-Client/265062105722?
in the US: https://www.ebay.com/itm/HP-T520-Flexible-Thin-Client-4GB-DDR3-V2V45UA-ABA-No-Stand-SSD/313404749197?You just need to find an old HP laptop power supply for it. That won't break your scotch budget... and amazingly they come with a windows10 pro license in the BIOS.
-
-
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.
-
No it’s not overkill. If you look at the HA forum, you will see legions of people migrating away from the rPI to intel NUC because of the SD card issue. These are very cheap, controller less (therefore cache less, garbage collection less, wear leveling less) NAND flash which have a relatively short lifetime (similar to what Ezio embedded in their updated/downgraded version of the vera). 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.
A big part of it of course will depend on how much storage writing you will be doing but regardless, mid-long term it’s a bit of a waste. The SSD cards are really designed for digital cameras where pictures are taken until the card is full, transferred and then erased again on a low frequency basis. They are not very good for computing storage use.
@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.
-
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.
-
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.
@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.
-
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.... -
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
-
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! -
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 sensorsEnhancements/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.
-
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.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
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.
@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.
