[SOLVED] Z-Wave unreliable in 2.5.0.M4

[Celaeno1 (Alex)]

Next testing:

“zwave binding 1731” with snapshot 1486:

Unfortunately binding is not installing due to dependency errors:

11:16:41.874 [WARN ] [org.apache.felix.fileinstall         ] - Error while starting bundle: file:/C:/Openhab2/addons/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [378]
  Unresolved requirement: Import-Package: com.thoughtworks.xstream; version="[1.4.0,2.0.0)"

        at org.eclipse.osgi.container.Module.start(Module.java:444) ~[?:?]
        at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) ~[?:?]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [10:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [10:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:520) [10:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [10:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [10:org.apache.felix.fileinstall:3.6.4]

OK.I stopped my testing.

Now I’m running Snapshot 1731 with “zwave binding 1486” again. I will observe if this is running stable and reliable.

[sihui]

@Celaeno1

Unfortunately binding is not installing due to dependency errors

Latest Zwave binding missing module?

In the Karaf console, what do you see when you run this? list -s | grep xstream In a recent 2.5 snapshot (build 1587), I see this. openhab> list -s | grep xstream 65 │ Active │ 80 │ 1.4.7.1 │ org.apache.servicemix.bundles.xstream In an older 2.5 snapshot (build 1502), I see nothing. If this bundle is not installed, try dropping this jar in addons. http://central.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.xstream/1.4.7_1/org.apache.servicem…

[Celaeno1 (Alex)]

@5iver
@mhilbush
@chris

Hello folks,

today I’ve tested the other way around: Snapshot 1486 with “Z-Wave Binding 1731” only.

Here are the results: automatic network heal does NOT work.

node8:

node9:

node10:

.
.
SUMMARY:

Network heal with Snapshot 1731 and z-wave binding (1731) is NOT RUNNING.
Network heal with Snapshot 1731 and downgraded z-wave binding (1486) is RUNNING.
Network heal with Snapshot 1486 and upgraded z-wave binding (1731) is NOT RUNNING.

Conclusion:

There seems to be a problem in the z-wave binding or database.

My 3 devices are all: Fibaro FGMS001, Firmware 2.7, Type: 0800:1001

Maybe that’s the problem?

[sihui]

@Celaeno1

There seems to be a problem in the z-wave binding or database.

I upgraded to Snapshot #1738 today (core and binding), deleted all things and re-added them (to pick up the full database export some time ago): all good, everything is working.

@Celaeno1

My 3 devices are all: Fibaro FGMS001 , Firmware 2.7, Type: 0800:1001

Same here, but just one with firmware version 2.6

[Celaeno1 (Alex)]

@sihui

deleted all things and re-added them (to pick up the full database export some time ago)

This is what I did also, see here (but with 1731):

[SOLVED] Z-Wave unreliable in 2.5.0.M4

. Originally I just updated. After finding the problems with the healing, I have deleted all zwave things (via PaperUI), also the controller, and have added these again using the previous ThingID. Will try the same using a new ThingID.

[SOLVED] Z-Wave unreliable in 2.5.0.M4

I now have deleted all zwave things (via PaperUI), also the controller thing, and have added these again using a new ThingID. Same result. Healing of nodes 8, 9, 10 ("non listening nodes) FAILED. The result is even worse. No manual healing is possible anymore. I could post the DEBUG.log here if anyone cares. If not, no matter.

[Celaeno1 (Alex)]

@sihui

all good, everything is working.

Also automatic nightly heal?

[sihui]

@Celaeno1

Also automatic nightly heal?

I can tell you tomorrow
I am reading those threads with interest because I never had problems with nightly heals (coming now from #1665).

[sihui]

@Celaeno1

all good, everything is working.

Also automatic nightly heal?

No issues after the nightly heal.

[Celaeno1 (Alex)]

@sihui

No issues after the nightly heal.

OK. Thanks for reporting.

[Celaeno1 (Alex)]

@sihui

No issues after the nightly heal.

I’ve compared 1738 to 1731, only a few database changes…

Why is it running on your PC and not on mine?

You have Linux, me Windows, which JAVA version do you use?

[sihui]

@Celaeno1

Why is it running on your PC and not on mine?

There are a bunch of people having problems with nightly heal. Maybe I have a lucky mix of devices. I started with Zwave 5 years ago, so my devices mostly are already old.

@Celaeno1

which JAVA version do you use?

I don’t think it has something to do with Java, but:

java -version
openjdk version "1.8.0_222"
OpenJDK Runtime Environment (Zulu 8.40.0.25-CA-linux64) (build 1.8.0_222-b10)
OpenJDK 64-Bit Server VM (Zulu 8.40.0.25-CA-linux64) (build 25.222-b10, mixed mode)

[Celaeno1 (Alex)]

@sihui

don’t think it has something to do with Java

I’ll try a new Java version.

Other question. Did you set any special settings with your FGMS001? e.g. Association or something else? Which controller are you using?
IIRC you have a zwave.me ZME_UZB1? In spring
of 2019 I’ve switched to “Aeon Z-Stick gen5”= ZW090-C (because it’s portable and has a backup tool for Windows).

[sihui]

@Celaeno1

Did you set any special settings with your FGMS001?

Not that I remember:

@Celaeno1

IIRC you have a zwave.me ZME_UZB1?

Correct, still working fine.

[Celaeno1 (Alex)]

@sihui

I could see a difference:

You have set:

.

And I have, by default: (I didn’t change anything!)
.

Was this recommended somewhere?

.

And what did you set here?

[sihui]

@Celaeno1

Was this recommended somewhere?

For every zwave device you need to set the Controller update association group to your controller stick to get updates for your values in openHAB.
For the Lifeline group this is done by the binding automatically. But not for older devices.
After you have changed the setting a pending mark appears in HABmin, you need to wake the device (fast triple click the button right next to the battery until the LED glows blue) until the pending mark disappears. You probably need to wake the device several times.

ZWave - Bindings

Associations are also used to send state updates to the controller when the state of a device changes. For example, if you turn a light on, the device will let the controller know so that the state of the light is shown correctly within the user interface.

@Celaeno1

And what did you set here?

Same as yours.

[Celaeno1 (Alex)]

@sihui

For every zwave device you need to set the Controller update association group to your controller stick to get updates for your values in openHAB.

.

I never had to set this, but I always got values in Openhab! That’s still the case.

Is this also needed for a network heal?

@sihui

For the Lifeline group this is done by the binding automatically.

I have a red X in all devices…

.

This I also never had to set.

[sihui]

@Celaeno1

I never had to set this, but I always got values in Openhab! That’s still the case.

You always have to set this, otherwise it won’t work reliable.

@Celaeno1

I have a red X in all devices…

This is just a display bug in HABmin, nothing to worry about. As you can see, the binding did set this group for you because it is Lifeline.

[Celaeno1 (Alex)]

@sihui

I never had to set this, but I always got values in Openhab! That’s still the case.

You always have to set this, otherwise it won’t work reliable.

When I look into XML file for node 8, 9, 10 in Snapshot 1486 and 1731:

<entry>
  <int>3</int>
  <associationGroup>
    <index>3</index>
    <maxNodes>0</maxNodes>
    <associations>
      <associationMember>
        <node>1</node>
      </associationMember>
    </associations>
  </associationGroup>
</entry>

.

It is set, but not shown in HABmin…

[sihui]

@Celaeno1

It is set, but not shown in HABmin…

I quickly checked all my nodes: all associations are set correctly in HABmin, maybe the display bug was fixed.

[Celaeno1 (Alex)]

@sihui

maybe the display bug was fixed.

That could be possible. I have to admit, the view is with the “old zwave binding 1486”.

EDIT: I’m going to check ALL XML files of snapshot 1731. If there is something other (e.g. lifeline) missing, I’ll let you know immediately.