Upgrade advice - upgrade from aarch64 to ARM64 image

[toggledbits]

Send me a PM with your email address and full name; I'll set up your account and the site will email you.

[gwp1]

@toggledbits Done. Thanks!

[therealdb]

Since we’re at it, I think the mqtt gateway should support announcements, lwt and so on.

This will make very easy to integrate things like Shelly, tasmota, and so on.

[PerH]

This post is deleted!

[toggledbits]

I had an issue with an account on the bug tracker (already?) so I locked it down. PM me your full name and email address and I'll set up your account. It will email you an access link.

[rafale77]

Got my instance going with Home Assistant. I am finding it brilliant as it is connecting to it through websocket. I am seeing the potential now to have reactor act as a bridge, detecting events happening on Home Assistant and forwarding them to openLuup and vice versa, eliminating the need for configuring additional scenes on openLuup and automation on home assistant!

[toggledbits]

I'm getting ready to assemble today's build (21051). I think I have everything urgent covered, with some PRs left open for confirmation. There's one more I want to try to address before I roll it up and out for the day.

This build also includes:

• Fix for condition trigger repeating when a sustained-for delay applies (#30);
• Fix an error on import (#29);
• Fix an error on Hass caused by an unhandled attribute (#27);
• New units configuration value "uk" (#31), as well as more granular control over units (if imperial, metric, or uk isn't enough, you can now set units by use class; per device/attribute is planned and part of the architecture as well);
• Fix elevation computation problem in sunrise/set data (mangles angles if elev configured <> 0) (#34);
• Now with working SMTP, Prowl, Pushover and Syslog notifications;
• Notification forwarding for Hubitat (see docs for configuration details);
• many documentation fixes and upgrades.

[toggledbits]

And 21051 is now available.

[rafale77]

Updated and now added openLuup. Doesn't seem to be a problem but why do openLuup scenes and room entities keep flashing green even without seemingly any updates?

[toggledbits]

I will look into that!

---

Edit: It looks like the jobs object is dropped on Vera Luup when it's empty, but is always present on openLuup. Since the comparison to see if a value changes doesn't "go deep" on objects and arrays, it sees two empty objects as different every time they are presented (using JS's comparison operator), and the scene is being presented on each update even though outwardly there don't appear to be any changes. So two small diffs between Vera Luup and openLuup contributing.

I'm just going to suppress anything that isn't a primitive and leave it at that. Deep inspection of objects and arrays isn't likely to be valuable or necessary.

[kfxo]

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

I'm getting ready to assemble today's build (21051). I think I have everything urgent covered, with some PRs left open for confirmation. There's one more I want to try to address before I roll it up and out for the day.

This build also includes:

• Fix for condition trigger repeating when a sustained-for delay applies (#30);
• Fix an error on import (#29);
• Fix an error on Hass caused by an unhandled attribute (#27);
• New units configuration value "uk" (#31), as well as more granular control over units (if imperial, metric, or uk isn't enough, you can now set units by use class; per device/attribute is planned and part of the architecture as well);
• Fix elevation computation problem in sunrise/set data (mangles angles if elev configured <> 0) (#34);
• Now with working SMTP, Prowl, Pushover and Syslog notifications;
• Notification forwarding for Hubitat (see docs for configuration details);
• many documentation fixes and upgrades.

Looking good, squashing those bugs. I will keep reporting anything I find. Just set up SMTP. Works great!

[Matohl]

For being a "Developer preview" it is quite solid. After some minor issues yesterday and have been solved with 21051, I have re-built most of my Reactor-sensors in Vera in the MSR and it is working fine. They are now disabled in the Vera and let's see how it goes in the coming days

[Andr]

Hi! I have really looking forward to this, MSR is the sole reason I have been trying to wrap my head around Home Assistant.

For now I am running Hassio on a VM at my Win10 "home server"
If I read the information right, I can't run MSR on Windows at the moment?

[toggledbits]

I'm close. I think by tomorrow or Wednesday I'll have the cross-platform issues nailed down.

[toggledbits]

Version 21054 now available.

• Fix 0000020: Play button doesn't run cover action (Fibaro-specific issue)
• Fix 0000034: Sunrise/sunset conditions over midnight don't trigger in the morning
• Fix 0000041: VeraController has no thermostat mapping (generic done; specific versions will almost surely be needed)
• Fix 0000044: Time conditions spanning midnight don't trigger in the morning
• Fix 0000045: Importer brings root group with options in, but root group options are not editable in MSR
• Fix 0000046: Hubitat configuration for URL needs to go deeper (IP and access token insufficient)
• Fix 0000047: VeraController rgb_color capability has attributes but no actions
• Fix 0000048: VeraController has no mapping for Harmony plugin

A couple of side notes:

1. The API functions mentioned here are integrated in this version;
2. This version runs on Windows, and there are draft instructions for how to get it installed.

[kfxo]

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

• Fix 0000041: VeraController has no thermostat mapping (generic done; specific versions will almost surely be needed)

Is it possible to get thermostat (climate) mappings for HassController?

[toggledbits]

Version 21055 now available

• 0000048 - No support for Harmony plugin or devices (basic support); related PR 0000053 still open (details).
• 0000049 - Version 21054 missing SMTP
• 0000051 - Show reaction ID on (Global) Reactions detail card
• 0000054 - ALTHUE Vera plugin mapping (basic support); please comment on this PR with issues
• 0000055 - Telegram plugin mapping; please comment on this PR with issues

Resolved, but left open for confirmation/feedback (comment on PR as needed; will be closed if not further comments):

• 0000053 - Harmony device details
• 0000052 - Thermostat attributes and actions for Horstmann thermostat
• 0000045 - Importer will bring in options on trigger (root) group, but you can't edit them
• 0000005 - Set Variable action not yet implemented; now has completely untested implementation.

[Black Cat]

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?

[rafale77]

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.

[Elcid]

In fact its a good idea, those sd cards can fail all to easily, with all the reading and writing.