Z-Wave Philio PST02-1A not discovered

Hi All,
I’m working on OH 2.4 runnung on a Synology.
The installation is woking fine with KNX and other bindings.

The Z-Wave Binding is installed:

207 │ Active │ 80 │ 2.4.0 │ ZWave Binding

openhab-binding-zwave │ 2.4.0 │ x │ Started │ openhab-addons-2.4.0 │ Z-Wave Binding

I have a Nortek HUSBZB-1 as Z-Wawe controller

looking at device ‘/devices/pci0000:00/0000:00:15.0/usb1/1-3/1-3:1.0/ttyUSB0/tty/ttyUSB0’:
KERNEL==“ttyUSB0”
SUBSYSTEM==“tty”
DRIVER==""

looking at parent device ‘/devices/pci0000:00/0000:00:15.0/usb1/1-3/1-3:1.0/ttyUSB0’:
KERNELS==“ttyUSB0”
SUBSYSTEMS==“usb-serial”
DRIVERS==“cp210x”
ATTRS{port_number}==“0”

looking at parent device ‘/devices/pci0000:00/0000:00:15.0/usb1/1-3/1-3:1.0’:
KERNELS==“1-3:1.0”
SUBSYSTEMS==“usb”
DRIVERS==“cp210x”
ATTRS{bInterfaceClass}==“ff”
ATTRS{bInterfaceSubClass}==“00”
ATTRS{bInterfaceProtocol}==“00”
ATTRS{bNumEndpoints}==“02”
ATTRS{authorized}==“1”
ATTRS{supports_autosuspend}==“1”
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceNumber}==“00”
ATTRS{interface}==“HubZ Z-Wave Com Port”

The controller is online and after activating debug on z-wawe there are NO errors.
The controller ha the following parameters:

controller is master: YES
SIS Node:1
Inclusion mode timeout:30
default wakeup period:every hour
Inclusion Mode:High power (tried also the other two)
secure inclusion:do not use security (tried also the other two oprions)
network security key:xxxxxxxxx

I’m using Habmin to discover the PST02 (configuration->object->z-wave binding) that I previously reset (4 quick click, wait led off, click) tried in different order, discovery mode -> reset, reset -> discovery mode.
I tried also the discovery mode (3 quick cliks) but nothing happens.
Tried to remove and reinstall batteries, same result.

This is the OH log during dicovery process:

16:45:41.781 [INFO ] [smarthome.event.BindingEvent ] - org.openhab.binding.zwave.event.BindingEvent@25173ab1

16:46:11.775 [INFO ] [smarthome.event.ItemStateChangedEvent] - zwave_serial_zstick_fb9aa05e_serial_ack changed from 48 to 49
16:46:11.826 [INFO ] [smarthome.event.ItemStateChangedEvent] - zwave_serial_zstick_fb9aa05e_serial_sof changed from 37 to 38
16:46:11.832 [INFO ] [smarthome.event.ItemStateChangedEvent] - zwave_serial_zstick_fb9aa05e_serial_ack changed from 49 to 50

I see a BindingEvents and some frame received, but nothing is added.

Any Ideas?

First, and most importantly, you might want to edit your post to remove the network security key.

Try enabling debug logging on the zwave binding, then try to include it. That will give us better idea what might be happening.

Key removed… :slight_smile:

the log attached (log:tail during the operation) are the debug log (log:set debug org.openhab.binding.zwave )

If you need a different log please let me know how to get them.

Regards

That’s the right way to get debug logging, but I don’t see any attachments in your post. The log snippet you show above is showing the event log. You need the log info from openhab.log. In debug mode it will be very voluminous.

Sorry but as new user I cannot upload files…

Anyway, I checked the openhab.log but seem there are no zwawe errors, ther error are about homekit, if I understand well…
Here are the last hours:

2019-05-13 14:56:48.622 [ERROR] [lfe.hap.impl.http.impl.BinaryHandler] - Exception in binary handler
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[?:?]
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) ~[?:?]
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) ~[?:?]
at sun.nio.ch.IOUtil.read(IOUtil.java:192) ~[?:?]
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) ~[?:?]
at io.netty.buffer.UnpooledUnsafeDirectByteBuf.setBytes(UnpooledUnsafeDirectByteBuf.java:447) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:880) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:242) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:119) [219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511) [219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468) [219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382) [219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354) [219:org.openhab.io.homekit:2.4.0]
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112) [219:org.openhab.io.homekit:2.4.0]
at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137) [219:org.openhab.io.homekit:2.4.0]
at java.lang.Thread.run(Thread.java:748) [?:?]
2019-05-13 14:56:48.625 [ERROR] [.hap.impl.http.impl.AccessoryHandler] - Exception caught in web handler
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[?:?]
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) ~[?:?]
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) ~[?:?]
at sun.nio.ch.IOUtil.read(IOUtil.java:192) ~[?:?]
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) ~[?:?]
at io.netty.buffer.UnpooledUnsafeDirectByteBuf.setBytes(UnpooledUnsafeDirectByteBuf.java:447) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:880) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:242) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:119) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112) [219:org.openhab.io.homekit:2.4.0]
at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137) [219:org.openhab.io.homekit:2.4.0]
at java.lang.Thread.run(Thread.java:748) [?:?]
2019-05-13 15:00:13.092 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 15:05:14.260 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 15:10:16.172 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 15:15:17.436 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 15:20:18.652 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 15:25:19.811 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 15:30:21.621 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 15:35:22.178 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 15:40:23.820 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 15:45:24.674 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 15:48:21.030 [ERROR] [lfe.hap.impl.http.impl.BinaryHandler] - Exception in binary handler
java.io.IOException: Connection timed out
at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[?:?]
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) ~[?:?]
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) ~[?:?]
at sun.nio.ch.IOUtil.read(IOUtil.java:192) ~[?:?]
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) ~[?:?]
at io.netty.buffer.UnpooledUnsafeDirectByteBuf.setBytes(UnpooledUnsafeDirectByteBuf.java:447) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:880) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:242) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:119) [219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511) [219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468) [219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382) [219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354) [219:org.openhab.io.homekit:2.4.0]
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112) [219:org.openhab.io.homekit:2.4.0]
at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137) [219:org.openhab.io.homekit:2.4.0]
at java.lang.Thread.run(Thread.java:748) [?:?]
2019-05-13 15:48:21.032 [ERROR] [.hap.impl.http.impl.AccessoryHandler] - Exception caught in web handler
java.io.IOException: Connection timed out
at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[?:?]
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) ~[?:?]
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) ~[?:?]
at sun.nio.ch.IOUtil.read(IOUtil.java:192) ~[?:?]
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) ~[?:?]
at io.netty.buffer.UnpooledUnsafeDirectByteBuf.setBytes(UnpooledUnsafeDirectByteBuf.java:447) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:880) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:242) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:119) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354) ~[219:org.openhab.io.homekit:2.4.0]
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112) [219:org.openhab.io.homekit:2.4.0]
at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137) [219:org.openhab.io.homekit:2.4.0]
at java.lang.Thread.run(Thread.java:748) [?:?]
2019-05-13 15:50:25.945 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 15:55:27.203 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 16:00:28.432 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 16:05:29.648 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 16:10:30.917 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 16:15:31.870 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 16:20:33.458 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 16:25:34.231 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 16:30:34.990 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 16:35:36.219 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 16:40:37.951 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 16:45:39.593 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 16:50:41.278 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 16:55:42.182 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 17:00:43.364 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 17:05:44.232 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 17:10:45.382 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 17:15:46.076 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 17:20:47.524 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 17:25:49.248 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 17:30:50.459 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 17:35:51.491 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 17:40:53.093 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 17:45:53.798 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 17:50:55.442 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 17:55:56.702 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.
2019-05-13 18:00:57.456 [INFO ] [e.smarthome.model.script.iPhone Home] - iPhone is at home.

There are no zwave debug statements in what you posted above.

I would suggest you restart openHAB, then once the system is up and running, do a factory reset on the zwave device, then try to include it. After that, post your openhab.log file.

No worries. Just put the file on a file sharing service, such as Google Drive, One Drive, iCloud, etc., then post a link to the file here.

Ecco il link al file di Log

https://1drv.ms/u/s!Aj-MV_MOomJckyKh9r0PS7aP9hcF

e al file degli eventi

https://1drv.ms/u/s!Aj-MV_MOomJckyOEZLx-N82gyYN4

I can’t access the links. Are you sure the files are set up to be sharable?

Yes… but I think to have messed up with the link command.
Try this
events.log
openhab.log

I can access the files now, but it doesn’t look like the zwave binding is in debug mode. There’s no debug-level logging in the openhab.log file.

Can you confirm that debugging is turned on? In the console, type

log:get org.openhab.binding.zwave

It should look like this.

openhab> log:get org.openhab.binding.zwave
DEBUG

you are right… I forgot that after reboot the log debug is lost.
Here you are the file in debug after a new inclusion test (failed of course)

openhab.log

Ok, there’s now some debug information.

From the log view below, it shows the controller is going into inclusion mode, but it doesn’t look like the device is sending anything to the controller.

You can see the controller ready to learn the node at 21:34:30.971.
Then you can see the 30-second inclusion timeout expiring at 21:35:00.949, at which point the binding takes the controller out of inclusion mode.

A couple things to look into:

  • Are you certain you’re pressing the correct button(s) on the device to start inclusion?
  • Have you done a factory reset on the device?
  • Are you sure the device is working properly?

You are right, I compared two logs, one in a “supposed” include mode of the device and the other one with the device without batteries and they are the same.

The device has 1 command activated by a button on the front and a trigger on the back, but the switch is the same.

Instruction reports:

There are two tamper keys in the device, one is in the back side,
another is in the front side. Both of them can add, remove, reset or
association from Z-WaveTM network.
In the first time, add the device into the Z-WaveTM network. First, make
sure the primary controller is in the add mode. And then power on the
device, just take out the insulation Mylar in the back side of the device.
The device will auto start the NWI (Network Wide Inclusion) mode. And
it should be included in 5 seconds. You will see the LED light ON one
second.

I tried and the log does not change

then you can reset the device:

Notice: Use this procedure only in the event
that the primary controller is lost or
otherwise inoperable.

  1. Pressing tamper key four times within 1.5 seconds
    and do not release the tamper key in the 4th
    pressed, and the LED will light ON.
  2. After 3 seconds the LED will turn OFF, after that
    within 2 seconds, release the tamper key. If
    successful, the LED will light ON one second.
    Otherwise, the LED will flash once.
  3. IDs are excluded and all settings will reset to
    factory default.

I tried and the correct led sequence appears (so I presume the device i working) but the result is the same

The third way is

Have Z-WaveTM Controller entered inclusion mode.
2. Pressing tamper key three times within 1.5 seconds
to enter the inclusion mode.
3. After add successful, the device will wake to
receive the setting command from Z-WaveTM
Controller about 20 seconds

With this procedure the device do nothing, so I really don’t know is the add mode is entered, but the results are the same.

To be sure I changed the discovery time to 60 seconds and put the device at 10 cm from the stick

I think there could be two kind of problems:
Stick not receiving or device broken.

I think I will buy another class of device and make some more tests…

Tks for the patience.

I’m running of of ideas, and I’m not familiar with this device.

This may be a stretch, but how quickly are you triple-pressing the button? Sometimes it requires that you press it pretty rapidly. Maybe try the triple-press at different rates to see if you can make it work.

first thing I tried…
I’ll try with a new device.
Can you suggest a 4-way dry contact sensor tested with OH2 ?

OT: I need to add the USB port link to the available ports, in my Synology installation do you know in which file I have to put the string?

export EXTRA_JAVA_OPTS="-Dgnu.io.rxts.SerialPorts=/dev/ttyUSB0:/dev/tty/USB1:/dev/ttyxHCI:/dev/ttyHubZ"

If you mean the four features of the PST02 device (PIR, door/window, light, and temp), I’m not familiar with another device that has those features.

I’m not familiar with the Synology install, but in my Ubuntu install it goes in start.sh.

No a simple z-wave dry contact, to monitor input from camera alarms I found 1-contact+1 realy for 50$ so I was wandering if exists a sensor with 4 dry contacts without relays I dont’ need…

Ah, I see. The Ecolink DWZWAVE25 has terminals that support an external dry contact relay (such as a Hall effect sensor). I have one of these attached to a PIR motion sensor on my patio. Wouldn’t this work for 4 sensors, since the sensors would be wired in parallel?