Problem with Loxone Config

[L P]

I am running the latest version of Loxone Config and my Miniserver Gen1 is up to date. My standard routine when making a change to the configuration is to open my latest config file with Loxone Config, connect to the Miniserver and perform "Load from Miniserver" to ensure that the stored version is in sync with any Automatic Designer changes made from the app. Recently, when doing this, Loxone Config continues to show "Program not identical". Even if I start with a blank configuration and import the running config from the Miniserver it still shows "Program not identical". This worries me as I don't want there to be any configuration drift between the Miniserver and the stored configuration. Has anyone else seen this? I opened a ticked with Loxone almost two weeks ago and they have not yet responded.

[g...@camleyphotographic.com]

I would try with a different computer with a fresh installation of Loxone Config.

It sounds like a local PC issue.

George

--
You received this message because you are subscribed to the Google Groups "Loxone English" group.
To unsubscribe from this group and stop receiving emails from it, send an email to loxone-englis...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/loxone-english/C4B471D4-CC3F-4690-AD2D-06CACC25AB21%40gmail.com.

[L P]

I just did, same result. “Program not identical”. :-(

[Rob_in]

Yes. I have this all the time. Have had an open ticket with Loxone for literally years.

[Jonathan Dixon]

If you save Config into mini server then load it back what happens?

To view this discussion visit https://groups.google.com/d/msgid/loxone-english/D8136052-D47A-4222-A03A-0325AB8432DA%40gmail.com.

[L P]

I don’t dare do that since I don’t know what I’d be pushing back to the Miniserver. I had a look on the Loxone site and this seems to be an issue that has been “fixed” on a few previous releases so I’m guessing that it has happened again.

13.1.10.18

BG-I18069 Automatic Scene: program not identical when input "Off" is Triggered

13.03.01.15

BG-I22351 Config shows program not identical

[Rob_in]

No. Always a problem for me so hasn't been fixed and returned.

[Jonathan Dixon]

Take a backup of the sd card first, and put that on a spare before trying.

This is odd, in 5 years I've never seen a "not identical" that wasn't revolve by load/save/load. (In fact the first load is always enough unless there's a version skew between server and app)

To view this discussion visit https://groups.google.com/d/msgid/loxone-english/FB56B507-4256-4028-BADD-43B86997DCB7%40gmail.com.

[L P]

I just checked and the ticket I opened with Loxone has been deleted. I guess that's one way to "fix" it...

[Rob]

I updated to the latest v15.3.12.13 a couple of days ago and am finding a similar issue (Gen2). If I load from the MS it says "identical" but if i then save into the miniserver without making any changes it says "not identical".

I think it's a bug in config.

This has happened with previous versions too (can't remember which) but was usually resolved in a subsequent release.

I'm going to raise a ticket with Loxone too.

[Rob]

Saw this in list of fixes in config 15.5 Beta 1..........

• Project shown as not identical when saving it on the PC

Haven't tested it yet but hopefully fixed (again!)

[Rob_in]

I was talked to installing the Beta by Loxone support today. This is what I just reported back to them:

...I went ahead and installed 15.5.1.21 then:

- Opened my project, the little star appeared next to the filename to indicate changes, even though I did nothing. I assume that's because this version of Loxone Config has updated something automatically and needs to now save the updated file. Why I mention this you will see below.

- Upon connecting to my Miniserver I was shown a message about firmware update. So I went ahead and performed that update. I did not load config from the server and elected to upload the copy from my PC as part of the update.

- When the update completed I actually saw the 'Program identical' message. This is the first time in literally years I have seen this.

- Although at this point, I hadn't saved the update program on the PC yet. I went ahead and hit CTRL-S to save it. The little star next to the filename disappeared, and the message next to it changed to 'Program not identical'. So that looks like a failure to me.

- I uploaded the config to the Miniserver once more to see what would happen and got the 'Program identical' message back.

- I picked a page at random and deleted a memory flag output. Star appeared next to the filename and 'Program not identical' message is shown - as expected as something has changed.

- I hit CTRL-Z to undo the change. Star was still next to the filename and 'Program not identical' message was still shown, even though the undo put the config back in the exact same state as when it was first loaded and as it is in the Miniserver. So another failure.

- I closed the project without saving and re-opened it. Connecting to the Miniserver correctly shows 'Program identical'.

This is somewhat of an improvement, but there is still work to do IMHO.

[Clegger]

"- I hit CTRL-Z to undo the change. Star was still next to the filename and 'Program not identical' message was still shown, even though the undo put the config back in the exact same state as when it was first loaded and as it is in the Miniserver. So another failure."

Are you sure that isn't the intended behaviour? Couldn't the flag just change when you first make any change, and then stay changed until the file is uploaded to the miniserver? Keeping a continuous track of the value of every parameter in the file to maintain a live status about whether the files are identical feels like overkill for what I suspect the flag is intended to show.

[Rob_in]

Well... I would create a hash of the config being edited and after every change compare it with the hash of the config running on the Miniserver. Thus if you change something then undo it the hash would revert and behaviour would be correct.

[Clegger]

That's not quite what I'm saying.

A hash is one way of making the comparison, but recalculating the hash for every single keystroke or click that results in a change sounds like potentially a lot of processing.

However, if all they're interested in is telegraphing to the user that the current open config file was successfully imported (or exported) and now represents what's on the miniserver, then the easiest way would be to set the flag upon successfully importing/exporting the config file. The flag would be changed to "Program not identical" as soon as any change is made, and then not changed again until the config is saved to the miniserver or overwritten by re-importing the config from the miniserver. In that case, reverting to the original version would not reset the flag.  

I've just checked how my Config works. A single change results in the status changing to "Program Not Identical". Undoing that change doesn't change the status. So if yours isn't working properly, neither is mine!

[Rob_in]

On Friday, 31 January 2025 at 17:00:40 UTC+1 Rob_in wrote:

- I closed the project without saving and re-opened it. Connecting to the Miniserver correctly shows 'Program identical'.

That didn't last long. After a couple of saves I'm seeing 'Program not identical' directly after saving again and haven't seen the correct message again.

Sigh.