[Z-Wave Binding] Updating ZWave DB to get new devices

PleKy01 commented 1 year ago

Hello,

I've just received a new NEO Coolcam PIR sensor.

I'm not able to complete the discovery, OH states that the device is unknown. I've checked on the Z-Wave DB and saw it was added in october 22. thingType! 0258:0200:1036::3.3

Is it possible to get an update for the binding ? OR can I push something manually (I saw on the forums that normall process is to ask for an update).

Thanks, PleKy

Expected Behavior

Z-Wave device auto detected, configuration options appear, channels too

Current Behavior

The device is not in the database.

in the log: NODE xx: Device discovery could not resolve to a thingType! 0258:0200:1036::3.3

Possible Solution

updating the ZWave DB

Steps to Reproduce (for Bugs)

N/R

Context

Occurs after inclusion scan and multiple forced linked done

Your Environment

runtimeInfo: version: 3.3.0 buildString: Release Build locale: fr-FR systemInfo: javaVersion: 11.0.17 javaVendor: Red Hat, Inc. javaVendorVersion: (Red_Hat-11.0.17.0.8-2.el7_9) osName: Linux osVersion: 3.10.0-1160.76.1.el7.x86_64 osArchitecture: amd64

wborn commented 1 year ago

Can you transfer this issue to the zwave repo @kaikreuzer?

apella12 commented 1 year ago

The way OH works is each release is a snapshot in time and is not normally (only if severe security issue found) remodified/updates after the release. Your version is 3.3 (late June 2022) so any DB change after that time will not be retroactively added. It is not a bug. What you need to do is update to the latest snapshot binding that contains the device in question.

General outline

1)Remove UI Zwave binding - Don’t want two running 2) In karaf feature:install openhab-transport-serial - Needed in most systems, normally installed by UI 3) Download 1 and place jar in addons (same folder as the openhab-addons-3.3.0.kar) 4) wait 30 seconds Assuming you are on OH3.3 there should be no problem

openhab-bot commented 1 year ago

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/aeotec-zwave-switch/140314/10

PleKy01 commented 1 year ago

ok, thanks for the info. According to the thread on community, it looks like it would be good to wait for 3.4 :(

Again Thanks for your time & work

apella12 commented 1 year ago

I tend to view the milestones as a better bet for stability. Plus there is a dedicated topic in the forum for milestone issues. The developers tend to cram a lot into the Release and a lot of issues get uncovered because many folks just wait for the release. Yes, there is a code freeze, but the last milestones aren't around that long, so don't get any more testing than any ordinary milestone. Last release I thought 3.4M1 was "better" than 3.3. Of course just my opinion. I have 3.4M5 running on two systems without any issue. If you aren't anxious to get the device working, waiting is an option Edit: also note this thread

openhab / org.openhab.binding.zwave