Platform information: Hardware: KVM VM OS: Ubuntu 16.04 Java Runtime Environment: openjdk version “1.8.0_202” openHAB version: 2.4.0 Release Build Zwave binding: 2.5.0.201911230756 Hi I have a couple ghost devices that I can’t seem to get rid of: [image] The motion sensor was one of my first…

[image] Bruce_Osborne: Paper UI does not report the Z-Wave status accurately Why not? What is the problem? Ive not heard any issue reported and I don’t really see why it would be wrong. Also, the image is not Paper UI - it’s HABmin - does that also have the same problem? It would be good to…

It does not report the z-wave status like REQUEST_INF when a device is not fully discovered, for example. I need to use HABmin to see the status if I miss it in the logs.

[image] Bruce_Osborne: It does not report the z-wave status like REQUEST_INF when a device is not fully discovered, for example. Does it need to? The main states are ONLINE/OFFLINE. States such as you mention here are internal progress during the interrogation and not related to the state of …

It is the state of communication between the device & binding. I likely use that more than most people. I believe I have seen the Paper UI say a device was online when HABmin reports correctly. I assumed that was due to the deprecated Paper UI development.

[image] Bruce_Osborne: It is the state of communication between the device & binding. No - it’s absolutely not this at all. It is solely an internal state that the binding uses to sequence the interrogation. It will NOT stop ongoing communications between the device and the binding.

It is an indication of the discovery progress and that it is incomplete though. I guess I really phrased things poorly in this thread.

[image] Bruce_Osborne: z-wave status like REQUEST_INF I guess you meant REQUEST_NIF. :wink:

[image] Bruce_Osborne: It is an indication of the discovery progress and that it is incomplete though. Yes, that’s finally something that is correct :wink: . Does that matter though? It’s not the device status, and it does not prevent the device working at all. It’s simply an internal state t…

[image] Celaeno1: @plysdyret Two questions. You have a snapshot 2.5.0.201911230756 binding over 2.4.0 release build? If so, what resulting the following commands? bundle:list |grep ZWave bundle:list |grep erial bundle:list |grep xstream . Looks close enough? openhab> bundle:list |grep …

@plysdyret Just want to be sure, that all dependencies are installed.

Zwave ghost devices

Add-ons Bindings

sihui (SiHui) November 26, 2019, 7:59am 31

I guess this is related to: