Zwave Difficulties

I am stuck again.

I am running openhabian 2.5.0.M2. Got it up and running with about 50 zwave devices. All was good.

Was getting CT101 Thermostats running. All good. Then wanted to add 3 more devices, LED Strip, the Aon Motions Sensor and the Jasco Outdoor motion. I removed the Zstick and included the devices. They were found but never identified. I then reset the Zstock and now I cant communicate with anything.

I removed all of the devices (Had to force removal of all of them)

I cannot get any devices to show up in the inbox even though I am communicating with the Zstick.

I have done a few other things and have had these strange results (At least it seems strange)

  1. I did a soft reset of the Zwave controller in PaperUI. Everytime I do this, All Openhab resets. Why would a soft reset of the zwave controller, restart Openhab.

  2. I cleared cache. This did another strange thing. The demo.things and demo.rules re-appeared. This seems strange to me as well.

Here is zwave debug stuff:
2019-09-07 08:49:06.085 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06

2019-09-07 08:49:06.088 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=

2019-09-07 08:49:06.089 [vent.ItemStateChangedEvent] - zwave_serial_zstick_c88ccc3d_serial_ack changed from 10 to 11

2019-09-07 08:49:06.107 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=

2019-09-07 08:49:06.128 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 38: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 0

2019-09-07 08:49:06.129 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK

2019-09-07 08:49:06.131 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2019-09-07 08:49:06.132 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.

2019-09-07 08:49:11.107 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 255: TID 38: Timeout at state WAIT_REQUEST. 3 retries remaining.

2019-09-07 08:49:11.110 [DEBUG] [sactionManager$ZWaveTransactionTimer] - TID 38: Transaction is current transaction, so clearing!!!

2019-09-07 08:49:11.113 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 38: Transaction CANCELLED

2019-09-07 08:49:11.115 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: notifyTransactionResponse TID:38 CANCELLED

2019-09-07 08:49:11.117 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-09-07 08:50:44.718 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Stop zwave:serial_zstick:c88ccc3d

2019-09-07 08:50:44.723 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave inclusion process not running - nothing to do

2019-09-07 08:50:44.727 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Start zwave:serial_zstick:c88ccc3d

2019-09-07 08:50:44.731 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller start inclusion - mode 2

2019-09-07 08:50:44.735 [DEBUG] [ve.internal.protocol.ZWaveController] - Event listener added.

2019-09-07 08:50:44.738 [DEBUG] [al.protocol.ZWaveInclusionController] - ZWave controller start inclusion

2019-09-07 08:50:44.745 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Added 39 to queue - size 1

2019-09-07 08:50:44.749 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-09-07 08:50:44.759 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A C1 04 75

2019-09-07 08:50:44.766 [WARN ] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.

2019-09-07 08:50:44.770 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 39: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 4

2019-09-07 08:50:49.773 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 255: TID 39: Timeout at state WAIT_REQUEST. 3 retries remaining.

2019-09-07 08:50:49.778 [DEBUG] [sactionManager$ZWaveTransactionTimer] - TID 39: Transaction is current transaction, so clearing!!!

2019-09-07 08:50:49.780 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 39: Transaction CANCELLED

2019-09-07 08:50:49.782 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: notifyTransactionResponse TID:39 CANCELLED

2019-09-07 08:50:49.785 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-09-07 08:51:44.727 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Stop zwave:serial_zstick:c88ccc3d

2019-09-07 08:51:44.729 [DEBUG] [al.protocol.ZWaveInclusionController] - ZWave controller stopping inclusion at IncludeSent

2019-09-07 08:51:44.732 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Added 40 to queue - size 1

2019-09-07 08:51:44.734 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-09-07 08:51:44.738 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 05 05 B0

2019-09-07 08:51:44.740 [WARN ] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.

2019-09-07 08:51:44.742 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 40: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 5

2019-09-07 08:51:49.744 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 255: TID 40: Timeout at state WAIT_REQUEST. 3 retries remaining.

2019-09-07 08:51:49.746 [DEBUG] [sactionManager$ZWaveTransactionTimer] - TID 40: Transaction is current transaction, so clearing!!!

2019-09-07 08:51:49.748 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 40: Transaction CANCELLED

2019-09-07 08:51:49.750 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: notifyTransactionResponse TID:40 CANCELLED

2019-09-07 08:51:49.752 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-09-07 08:51:59.752 [DEBUG] [al.protocol.ZWaveInclusionController] - Inclusion timer at IncludeDone

2019-09-07 08:56:30.338 [DEBUG] [al.protocol.ZWaveInclusionController] - ZWave inclusion controller finalised.

I am stuck.

Thanks.

Nothing much in that log snippet.

Question: I’m going to guess the LED strip is mains powered. Are either of the two motion sensors battery powered?

Just so I understand, you unplugged the zwave dongle from the server and carried it to the location of the 3 devices in order to include them correct?

If they are battery powered devices, it may require waking the devices up several times to complete the discovery process

Why? What problem were you encountering that resetting the stick sounded like a good idea? You had already successfully included 50 zwave devices and then reset the stick?
Are the LED strip and the two motion sensors all zwave devices?

First suggestion is use HABmin for zwave configuration. I think Paper UI has some display bugs when using it to configure zwave and HABmin works better

From looking at he lack if code fences, I think the OP is not one to follow documentation or search for answers. That leaves the volunteers here to try & guess the solution to the puzzle. As is stated in another thread, this is not a HelpDesk.

Ill look at HABmin. Thanks.

Did you verify what /dev/ the zstick registered itself as in the OS? Everytime I have taken out my Aeon stick to add devices the /dev/ value changes and OH is not notified of the change.

Using habmin to set the inclusion so the stick can stay in the system or you can set udev rules and have a static entry created that maps to whatever /dev/ is registered to the OS. I suggest both so you don’t have to worry about the issue down the road.

1 Like