Unknown device: Telldus Plug-in Switch Mini, TZWP-102

Setup, Configuration and Use Beginners
,
21

Hi all,
Sorry for reopening this Telldus TZWP-102 Topic again, but in my now downgraded OH2.5.12 the Telldus Parameter 16 (report on change of power consumption) is no longer available for editing. Hence a pain for proper operation of my 20+ such devises.
I guess I was hoping that OH3 and the downgraded OH2.5.12 is using the same Binding.
So, is this something that can be updated?
Anyone observed this issue in OH3.x?
Thanks

22

That is not the way it works. However, using this XML
tzwp102_0_0.xml (9.3 KB) and this procedure you may be able to upgrade your jar.

23

Thanks Bob for quick response.
OH2.5.9 is working fine and OH2.5.12 is just a (minor?) upgrade, so a few questions:

  1. Your referenced Topic headline says: “… while waiting for a build”, but I guess there will never be one for OH 2.5.12, or could minor issues like this be updated in the next OH3 update? OH3 should at leased be checked for presence of same issue.
  2. OH2.5.9 and OH2.5.12 must have the very same Binding interface (file structure etc.), so can relevant working z-wave Binding file(s) from OH2.5.9 simply be copied to OH2.5.12, and if so, which file(s) are involved?
    Would make life easier for me!
    Thanks
24

It is possible I do not understand what you are doing.

What does this mean? Did you try OH3.x and then go back to OH2.5.12 or did you upgrade from OH2.5.9 to 2.5.12 and are just curious about 3.0?

I did go through some history on the device and parameter 16 has always been there. As near as I can tell 2.5.9 and 2.5.12 are the same for this device. I do see in Jan 26,2020 that parameters 17 thru 104 were added (probably about 2.5.1). The last 2.5 binding is dated Nov 25,2020. There will be no more. I do not see how you could have a problem unless you tried 3.x along the way.

Strict validation was introduced in 3.2 and parameter 16 would only report 0=disabled. However, that was fixed on April 7, 2022, so 3.3 and 3.4.x should all be fine. If you did try 3.x that might still be in memory somewhere. I’d suggest deleting the device (do no exclude) and rescan to see if it is editable again.

25

Thanks Bob. Enlightening.

I did a fresh install of OH3 using openhabian 1.7.4 (OH3,4 I guess) and downgraded to OH2.5.12 using openhabian-config. So no OH3.2 or less as far as I remember.

I had to do it this way to get a good version of Frontail.
Editing the openhabian.conf file to branch=stable before installing loads a crappy version of Frontail.

After that I Restored the system using my working OH2.5.9 system Backup (but without Z_Stick attached during restore). HABmin report parameters, but not the correct once. So i started parameter updates and discovered the parameter issue in mention.

I will start from scratch once more and use openhabian 1.7.5.
BTW Is the .xml file you attached the good OH2 or the bad OH3 version?

Ill keep you posted.
Stay tuned

26

So I suspected more was going on :wink:

Good. Because of the rigorous checking by the OH core, the parameter was changed from Limit to options = false from Limit to options = true That’s all. No other changes since Jan 26, 2020

My unsolicited advice is to get OH3.4 working and not worry about OH2.5.x. The UI is much better.

27

Bob,
Thanks for the unsolicited advice. Probably a good one, which I have heard before.
BUT, the thing is I have OH2.5.12 running OK (with files only) except for the Z-Wave parameter issue in mention. You know - Irritating - right??
So the question remains: Can it be fixed in a quick (and dirty) way?
I’ll take a closer look at the procedure pointed to above.
Thanks again and stay well.
Bjorn