Move to Gen2 with Gen1 as slave

[Russ]

I have a Gen1 miniserver that I've used steadily for 10years (am only now replacing the SD card!).  Has been very reliable, but in thinking what I need for new pool+garden I'm wondering about getting a Gen2, moving the existing install onto that, and using the Gen1 as a slave for the new application.  I'm also using some KNX devices for rolling shutters so would need the KNX interface as well.  So not so cheap.  But after 10 years, I'd feel better about having the newer miniserver as the main one.

Has anyone done this migration?  If so, how painful was it and how does the setup with two miniservers work?

[Vahur Kivaste]

I have such a setup where I started with a Gen1 MS (about 4-5 years ago) in the sauna building (no SD issues so far) and about 2 years ago added a Gen2 MS in the main building. Working as a client-gateway setup and have had no major issues. 

Can't speak for the KNX part as I'm currently not using any KNX devices but should work fine (I know a local installer who I think used this combo as well for installations that required KNX). 

[Russ]

Thanks for the info.  I found the Loxone docs on setting up a gateway-client, which includes how to transfer the program from the old to the new.  Hopefully someone else can speak to the KNX part.  I only have three KNX modules for shutter control so worst case scenario I manually recreate that.  The KNX functions in the gen1 were not excellent and it is often hard to connect and transfer; hopefully with the new one this will perform better.

[Jan De Bock]

Just womdering, why don't you keep the KNX from

 the gen1 if you keep it anyhow as slave? 

This saves some money at least

[Russ]

Yes, could be a possibility.  The install for the pool+garden is about 50m from the house which is still within the 100m KNX limit.  The question would be cabling as everything is in the ground now.  OTOH I could try this and if it doesn't work then purchase the standalone Loxone KNX interface which is extremely overpriced. 

 I was also kind of thinking this was a preventive move so if the gen1 failed it would not be so critical and I would have the newer gen2 for critical functions for another 10 years of service at least.  So running the KNX (these interfaces handle all the rolling shutters) off the gen1  would partially mitigate that move.

But it is a possibility.

[Jan De Bock]

interesting, understand your points. 
I am also looking to upgrade to gen2, but indeed would keep the gen1 for KNX functionality.
So interested to hear your experience about this

Op do 20 jul 2023 om 08:29 schreef Russ <rspei...@gmail.com>:

--
You received this message because you are subscribed to a topic in the Google Groups "Loxone English" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/loxone-english/8jiuoiyEIos/unsubscribe.
To unsubscribe from this group and all its topics, send an email to loxone-englis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/loxone-english/dab0727d-2663-4619-94f6-be2c9efd0705n%40googlegroups.com.

--

Met vriendelijke groeten,

Jan.

[Russ]

Ok, just did this today.  Here are my thoughts on how it went and how to do it if anyone is interested:

- push terminals for inputs on the new MS are a pain as I used some small stranded wire for some.
- replacement/migration wizard worked well, doing a backup and then indicating when to physically swap out the old MS.  In my case it took about 3 hours before continuing as we had lunch after I finished the wiring.
- After clicking next the wizard also proceeded with a firmware update on the new MS so it would match the gen1.  At one point you have the option to assign a new IP address which should be done so there's no problem access the gen1 when you're finished with the replacement.  However, it did not save the new IP address in the project file, so you have to configure the new MS and change that within an hour.
- The wizard also kept the old name "MSXXXX" where XXXX = last four digits of serial number/MAC address from the gen1 MS.  This gets confusing immediately as you then have two MSs with the same name (but different MAC+IP addresses), so you need to change this as well using the Configure Miniserver function (I believe also within the first hour of restarting the new MS).
- after ensuring that the new MS is functioning correctly (and it did, except of course for the KNX devices), you need to open another project with the original gen1 MS (now connected over ethernet and with it's original static IP which is different from the new one if you exercised that option), and delete all the logic you don't want (basically everything since the new MS is taking over), leaving only the KNX commands (in my case for blinds and status).  Also delete the extensions that are now no longer connected to the gen1 MS.  Then close this project (I put gen1 in the name to keep it straight).
- open the project with the new MS and add the gen1 project as a client to the gateway.
- go through the new project which now has two MSs in it and replace the stubbed (phantom) knx devices (actuators etc) with the ones from the gen1 project and delete the non-existent knx extension from the now combined project.

The most time consuming part for me was labeling the wires before disconnecting everything.  ;-). It took a while to figure out how Loxone was doing the client-gateway functionality, but I got it after the third try (kept backups of course).

It's a bit weird in a way, because my KNX devices (MDT multi-fold shutter actuators) are in the same cabinet as the new MS, but they are being sent messages from the old MS which is now about 40 meters away...