Advice reqeusted to migrate MSR from Bare Metal to Container

[Matohl]

@cadwizzard I have notised that myself. Probably by design, and the reason I left MSR.

[Cadwizzard]

@matohl
My biggest concern is that this happens without me knowing in future and all sorts of things break if i'm away and I have guests looking after the house (including my heating system which is entirely smart home controlled with logic in MSR!)

And how to build MSR logic to alert if the triggers don't run?

[tunnus]

@matohl said in [Solved] Big change in my system - How to update MSR as best as possible?:

@cadwizzard I have notised that myself. Probably by design, and the reason I left MSR.

Which exactly is by design?

[PerH]

@Matohl - If you're thinking about when the only way to make actions happen is the "play" button next to each individual action, I really doubt that its by design, nor being an automated way to say that an update is available. My system had a cascade of dead entities, and I suspect that had something to do with it.

The proper thing to do in that case is to save logs/setup files and open a mantis ticket, just like I didn't here. That how bugs disappear.

[Cadwizzard]

@PerH
I think MSR is great (came from many years of reactor in Vera), but we never saw this behaviour there. I actually miss the easy way to check for and install updates from the UI in Vera a lot, it has an easy way to pull new databases, and hopefully this will come to MSR. I've seen someone ask for it already. Even a check & warning that there is an update needed would be a great step. MSR checks for HA version compatibility ready, so should be possible)
When this happened to me, it was from an install that i'd done a while ago setting up HASS, but had never added any Zwave devices (or any other integrations). I added a first device onto the zwave network (simple double boiler switch) and began testing the automations and that MSR worked before getting into a huge amount of logic work. It was then I first saw the issue, before there was hardly anything system wise that could have gone wrong or dead etc.

[gwp1]

@cadwizzard Set this thread to send you notifications. That's where @toggledbits posts all release announcements.

[toggledbits]

Next build will have update notices. It's already done.

[Matohl]

@tunnus

Which exactly is by design?

For me ”by design” is a behavior that is intended by the creator witch means it’s in the design.

Well, suddenly one day all automations didin’t work anymore. I was way behind updating the MSR updates (I guess +150 days or something) because everything was working as it should and I didn’t se the need for updating. I realised that I was not alone but the thread is lost for me now.

So, I had the impression that after a certain time the automations in MSR, if not updated, it will stop to function ”by design” . My guess was that (I could be wrong, that happens) that is probably ”by design” in the code by the creator to force the user to upgrade and not have to deal with questions about old versions. I’m fine with that, it is the creators code, but I can not have something at in my home that suddenly stops working for this reason.
This got me thinking about my options and I went in an another direction. Don’t get me wrong I really like MSR but I’m not there anymore.

[gwp1]

@matohl This is my opinion only, let me say that.

I believe it is unrealistic to expect a piece of software to NOT change and grow and improve as new technologies and approaches for coding are discovered and implemented - and as that happens legacy functionality would be deprecated and replaced by something else.

The only way "one day all automations didn't work" happens is if something is changed. If I'm reading the OP correctly, other elements were changed that weren't in place when the older version of MSR was installed thus creating an incompatibility. That's not the fault of MSR. To believe that "after a certain time the automations in MSR, if not updated, will stop to function" if nothing else in the chain has changed (ie dependencies) is woefully inaccurate.

[CatmanV2]

@matohl said in [Solved] Big change in my system - How to update MSR as best as possible?:

So, I had the impression that after a certain time the automations in MSR, if not updated, it will stop to function ”by design” . My guess was that (I could be wrong, that happens) that is probably ”by design” in the code by the creator to force the user to upgrade and not have to deal with questions about old versions. I’m fine with that, it is the creators code, but I can not have something at in my home that suddenly stops working for this reason.

I am absolutely, 100% sure that is NOT the case. But as you say, you've moved on.

C

[tunnus]

@matohl Deliberate aging? Quite outrageous accusation

[gwp1]

@perh

@perh said in [Solved] Big change in my system - How to update MSR as best as possible?:

this entity is now gone from the system, choose a replacemen

If an entity or ruleset is gone that was used in other rulesets, the remaining ruleset will have a yellow triangle next to it and the field for the missing element has missing? (or something similar to that wording) in it. I don't have any examples atm or I'd shared a screenshot.

[PerH]

@gwp1 : Yes, I've seen (100s!) of those, no problem there!

I just had this notion that there was some other function in place, where if a device was gone, it would prompt you "This entity is gone, select replacement here", and that this would do replacement of all uses of that entity/device.

To the other discussion:
My problems started when I moved ALL devices to a new system, as in all entity addresses changed.
I have previously been on the same MSR version for long periods of time without any issues, so I very much doubt any "planned obsolesence".