New Aeotec Door/Window Sensor 7 not in Database yet?

ffr · July 2, 2019, 11:18am

@sihui : I just downloaded the zwave binding again (version from July 2nd). When I look at the list of supported devices, the ZWA008 is not included yet. Is there still something missing?

chris · July 2, 2019, 12:16pm

I have not updated the binding yet so it will not be included. I will try and do that tonight.

vossivossi · July 3, 2019, 9:29am

I just tested with Snapshot 1629 from tonight but the device is still not recognised.

In the device database on cd-jackson.com there is displayed a symbol which seems to indicate that there are still some information missing?

sihui · July 3, 2019, 11:25am

Please be patient, it has not made it into the snapshot yet:

https://github.com/openhab/org.openhab.binding.zwave/tree/master/src/main/resources/ESH-INF/thing/aeotec

ffr · July 7, 2019, 12:38pm

@sihui
I got the device added to my system now, but can’t get it secured.
I will send a private message with the log file to you and Chris.

calevans · July 28, 2019, 8:59pm

Any update on this? I notices that in the database this is still marked as “More information required” which I assume means it’s not in the current openhab Z-Wave module. @chris is there anything I can do to finish this out? I just bought 2 of these devices and want to see them in action.

Cheers!
=C=

mhilbush · July 28, 2019, 9:39pm

It looks like it was added to the binding 6 days ago, so it should be in the latest build.
https://github.com/openhab/org.openhab.binding.zwave/blob/master/src/main/resources/ESH-INF/thing/aeotec/zwa008_0_0.xml

calevans · July 28, 2019, 10:00pm

Oh sweet. thanks you.
=C=

calevans · July 29, 2019, 1:53pm

n00b question but is the zwave binding in the milestones?

I used to have it manually installed after I helped add something to it but went back to the “production” version after 2.4. If I get the milestone release will I get the new zwave binding or do I need to go back to manually installed?

Cheers!
=C=

ffr · July 29, 2019, 2:24pm

@calevans
do you plan to install the sensor with security on? If so, I will wait for your install before I try again. Secure include did not work for me about 3 weeks ago.

mhilbush · July 29, 2019, 2:37pm

The latest zwave binding will be in the snapshot release only (until there’s a 2.5 M2 release to pick it up).

You can install it manually, or you can try to update it as described in my post here.

calevans · July 31, 2019, 12:40am

This did NOT work for me.
Well, somethings changed. Here’s what I did and what happened.

I followed your instructions. The first time it failed but it seems to have been a permissions issue with the old 2.4.0 jar file. I made it world writable and then tried again and it worked…kinda.

Now I have ZWave installed via PaperUI I don’t know if that’s important.

The FIRST time I got the upgrade on the console to work, everything seems to have worked just fine. I used the command:

bundle:update org.openhab.binding.zwave https://openhab.jfrog.io/openhab/online-repo-snapshot/2.5/org/openhab/binding/org.openhab.binding.zwave/2.5.0-SNAPSHOT/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar

Then I checked the results with:

list -s | grep zwave

So far, so good, it listed the 2.5.0 jar with a long string of numbers that I assume is the snapshot or build number.

I rebooted my system.

Everything came back up.

I went back into the console and issued the ls command again and it was back to 2.4.0.

So I tried the update again.

Everything seemed to have worked, it was showing the 2.5.0 again. BUT. I got distracted for a few minutes and then just to make sure, I did the ls command again and it was back to 2.4.0.

Long story short, I could not get it to stay on 2.5.0. I eventually uninstalled it form the console, uninstalled it from PaperUI, rebooted and reinstalled 2.4.0 from Paper UI. (I cut out about an hour of banging my head on the monitor and trying different permutations.)

I now have 2.4.0 up and running just fine but obvs, I can’t use the sensors yet.

Have you ever seen it where the upgrade works but then it reverts to the older version? That jsut seemed odd.

Nothing else is running on this system, it’s a little RPi dedicated to openhab.

Thots?

Cheers!
=C=

mhilbush · July 31, 2019, 10:32am

I’ve not seen that behavior before. I suppose you could fall back to manually installing the jar in the addons directory.

Bruce_Osborne · July 31, 2019, 12:52pm

That is the proper procedure or use the script.

5iver · July 31, 2019, 6:14pm

@calevans, have you editted the binding line in your addons.cfg file? I vaguely remember this happening to me when trying out bundle:update.

mhilbush · July 31, 2019, 6:50pm

So is the Karaf command bundle:update

Bruce_Osborne · July 31, 2019, 7:12pm

OK, still learning…

calevans · July 31, 2019, 10:11pm

Excellent idea @5iver, thanks. I checked my addons.cfg and no, there is nothing there.

Cheers!
=C=

calevans · July 31, 2019, 11:11pm

That worked! Ran the script (still had it from the last time I did this during the 2.4 milestone days)

Cheers!
=C=

calevans · July 31, 2019, 11:51pm

It seems that “That Worked” only applied to getting the current Z-Wave binding installed.

I am currently running

274 x Active   x  80 x 2.5.0.201907292154     x org.openhab.binding.zwave

Which I believe is the current snapshot release. (Although I will admit that it may not be as I can’t figure out how releases are tagged on the github repo)

If, using PaperUI, I go to Configuration->Bindings->Z-Wave and in the search box I enter ZWA008, it does come up. So far, so good.

However, when I try to add the device, it keeps coming up as “Device Unknown”. I even used the ZWave diagnostics tool to forcibly remove the node from my controller, rebooted and re-added. Still it does not recognize the switch.

Anyone have any thoughts on what I am doing wrong?

Cheers!
=C=