Comfigurator

[juwi_uk]

Hi

Please could you consider an enhancement request that when you scan for UCM\'s and it is an older version that does not support versioning then you DO NOT change the UCM type.

Every time I scan it changes my UCM/Smartfit to type General. Surely you know it didnt report back a type so cant you then just leave as currently set?

Julian

[juwi_uk]

Oh and maybe for these types of devices (any that donbt report version), perhaps you could unlock the version field so we can set manually in Comfugrator and save to the CCLX.

Julian

[Ingo]

In some instances you can edit the CCLX file directly. I did it for my Keypads, they now show 1.03.

Ingo

[juwi_uk]

Yep I\'ve done that in the past too but much better to be able to do in the UI surely.

[ident]

Does it report Unknown UCM or General UCM.? \"General\" would seem to mean the type was reported as UCM general

[juwi_uk]

It reports as \"General\" and I have to change it back to \"Smartfit\".

[ident]

What do you get when you type u?XX where xx is the hex ID of the smartfit UCM eg u?12 for  ID 2?

[juwi_uk]

Hi,

Any chance you can fix this in Comfigurator so that a rescan doesn\'t keep resetting my Smartfit settings.

Scan returns this and produces screenshot. If 000000 is returned and config is defined for that unit # already can you not leave that config in place instead?

> U?
< U?0A061811
> u?11
< u?110A0618
> u?12
< u?120E0617
> u?13
< u?13000000
> u?14
< u?14FFFFFF
> u?15
< u?15FFFFFF
> u?16
< u?16FFFFFF
> u?17
< u?17FFFFFF
> u?18
< u?18FFFFFF

Julian

[slychiu]

OK we will see if we can change that in the next version