Aeotec ZWAVE Trisensor - Setup Issues

[servoronine (Sergey)]

Hi All,

I have an Openhab installation (latest stable version) and use Aeotec ZWAVE stick to control my ZWAVE devices. So far I only had mains operated ZWAVE devices from Fibaro which operate flawlessly. I have however recently purchased an Aeotec Trisensor (ZWA005) which is battery operated and cannot get it to work.

The device was successfully discovered by Openhab and shows as online. When switching on debug level logging for Zwave addon, I can also see that some communication appears to be happening with it. It does not however appear in my mesh network. I assume that it due to the missing Lifeline association group and that is what I cannot get to work.

I tried to set it to the value “Controller” however it then goes into “Pending” state and never updates. I tried to search the forums for an answer but the typical answer appears to be: try to keep the device on so that it can communicate and/or remove and add the device again and hopefully it will work

I have tried to press the button on this device for 2 seconds which apparently should send a wakeup message to the controller. This is what I get in the log file when I do that:

2024-05-05 21:31:05.019 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Handler disposed. Unregistering listener.
2024-05-05 21:31:05.039 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 23: Serialise aborted as static stages not complete
2024-05-05 21:31:05.040 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:e3758d88d2:node23.
2024-05-05 21:31:05.042 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Controller status changed to ONLINE.
2024-05-05 21:31:05.043 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Controller is ONLINE. Starting device initialisation.
2024-05-05 21:31:05.044 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Updating node properties.
2024-05-05 21:31:05.045 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Updating node properties. MAN=881
2024-05-05 21:31:05.045 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Updating node properties. MAN=881. SET. Was 881
2024-05-05 21:31:05.046 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Properties synchronised
2024-05-05 21:31:05.047 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration synchronised
2024-05-05 21:31:05.056 [DEBUG] [ve.internal.protocol.ZWaveController] - Event listener added.
2024-05-05 21:31:05.057 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Initialising Thing Node...
2024-05-05 21:31:05.058 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Initialising cmd channel zwave:device:e3758d88d2:node23:sensor_temperature for QuantityType
2024-05-05 21:31:05.058 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Initialising state channel zwave:device:e3758d88d2:node23:sensor_temperature for QuantityType
2024-05-05 21:31:05.059 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Initialising cmd channel zwave:device:e3758d88d2:node23:sensor_luminance for DecimalType
2024-05-05 21:31:05.059 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Initialising state channel zwave:device:e3758d88d2:node23:sensor_luminance for DecimalType
2024-05-05 21:31:05.060 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Initialising cmd channel zwave:device:e3758d88d2:node23:alarm_motion for OnOffType
2024-05-05 21:31:05.060 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Initialising state channel zwave:device:e3758d88d2:node23:alarm_motion for OnOffType
2024-05-05 21:31:05.061 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Initialising cmd channel zwave:device:e3758d88d2:node23:battery-level for PercentType
2024-05-05 21:31:05.061 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Initialising state channel zwave:device:e3758d88d2:node23:battery-level for PercentType
2024-05-05 21:31:05.061 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Polling initialised at 86400 seconds - start in 39657600 milliseconds.
2024-05-05 21:31:05.062 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Device initialisation complete.

I also tried to then press the button for 5 seconds which apparently keeps the device on and communicating for 5 minutes and tried to change the value in the association group. Here is what I got in the log:

2024-05-05 21:34:49.992 [DEBUG] [ndclass.ZWaveAssociationCommandClass] - NODE 23: Creating new message for application command ASSOCIATIONCMD_SET, group=1, node=1
2024-05-05 21:34:49.992 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 23: SECURITY NOT required on COMMAND_CLASS_ASSOCIATION
2024-05-05 21:34:49.993 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 23: Command Class COMMAND_CLASS_ASSOCIATION is NOT required to be secured
2024-05-05 21:34:49.993 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 23: Bump transaction 1774 priority from Config to Immediate
2024-05-05 21:34:49.993 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 23: Adding to device queue
2024-05-05 21:34:49.993 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 23: Transaction already in queue - removed original
2024-05-05 21:34:49.994 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 23: Added 1774 to queue - size 11
2024-05-05 21:34:49.994 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2024-05-05 21:34:49.994 [DEBUG] [ndclass.ZWaveAssociationCommandClass] - NODE 23: Creating new message for application command ASSOCIATIONCMD_GET group 1
2024-05-05 21:34:49.994 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 23: SECURITY NOT required on COMMAND_CLASS_ASSOCIATION
2024-05-05 21:34:49.994 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 23: Command Class COMMAND_CLASS_ASSOCIATION is NOT required to be secured
2024-05-05 21:34:49.995 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 23: Bump transaction 1775 priority from Config to Immediate
2024-05-05 21:34:49.995 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 23: Adding to device queue
2024-05-05 21:34:49.995 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 23: Transaction already in queue - removed original
2024-05-05 21:34:49.995 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 23: Added 1775 to queue - size 11
2024-05-05 21:34:49.995 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2024-05-05 21:34:49.996 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration pending added for group_1
2024-05-05 21:34:49.996 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored group_3 to [] (ListN)
2024-05-05 21:34:49.996 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored group_2 to [] (ListN)
2024-05-05 21:34:49.996 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored wakeup_node to 0 (BigDecimal)
2024-05-05 21:34:49.996 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored config_12_1 to 0 (BigDecimal)
2024-05-05 21:34:49.997 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored config_13_1 to 0 (BigDecimal)
2024-05-05 21:34:49.997 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored config_15_1 to 0 (BigDecimal)
2024-05-05 21:34:49.997 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored config_20_1 to 0 (BigDecimal)
2024-05-05 21:34:49.997 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored config_21_2 to 25 (BigDecimal)
2024-05-05 21:34:49.997 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored wakeup_interval to 28800 (BigDecimal)
2024-05-05 21:34:49.998 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored config_1_2 to 30 (BigDecimal)
2024-05-05 21:34:49.998 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored config_100_2 to 1024 (BigDecimal)
2024-05-05 21:34:49.998 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored config_7_2 to 239 (BigDecimal)
2024-05-05 21:34:49.998 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored config_2_2 to 240 (BigDecimal)
2024-05-05 21:34:49.998 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored config_3_1 to 11 (BigDecimal)
2024-05-05 21:34:49.998 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored config_22_2 to 100 (BigDecimal)
2024-05-05 21:34:49.999 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored config_4_1 to 0 (BigDecimal)
2024-05-05 21:34:49.999 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored config_23_2 to 3600 (BigDecimal)
2024-05-05 21:34:49.999 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored config_5_1 to 3 (BigDecimal)
2024-05-05 21:34:49.999 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored config_24_2 to 3600 (BigDecimal)
2024-05-05 21:34:49.999 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored node_id to 23 (BigDecimal)
2024-05-05 21:34:49.999 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Configuration update ignored config_6_1 to 0 (BigDecimal)

and association group still did not get updated. I tried to switch it on before issuing a command and also after I change the value in Openhab UI - still no luck

I tried removing and re-adding the device via “Scan” function - this also did not help.

Having had a look in Openhab folders, I can see that an XML file has not been generated for Node 23 (my Trisensor) which according to other posts on the forum suggests that it has not been fully discovered. I do however see all of the attributes in the Thing in Main UI so not sure what is left to be discovered.

Any advice on what to do next will be greatly appreciated.

[apella12 (Bob Eckhoff)]

1. If there is no XML the device is not configured (correct). Also can check if there are 5 five lines on the UI page for the device. 2) There is no message that the node is awake in either log. Also it appears the binding is adding messages to the queue (another indication the binding has not been informed the device is awake.) Need to see something like this
   [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 4: Node Status event - Node is AWAKE

Two things to try (keep debug on to look for the message above)

1. on the zwave controller page set the max battery timeout to 20 from 10 (actually turn debug off for this step)
   

   

2. Try a short press rather than hold 2 seconds (wait 20 sec), then try three quick presses, wait 20 seconds, etc.? until a wake message.

Finally: Controller is forced in Association group 1, so once configured you won’t have to add it.

[servoronine (Sergey)]

Hi Bob,

Thank you very much for the suggestion. Just to clarify - what do you mean by “check if there are 5 lines on the UI page for the device”. Here is what I see on the Thing page in the UI:

And that is actually what confused me because when I had devices not properly configured in the past, I did not see details of these devices on the Thing page. This is not the case here.

I have changed the awake duration from 10 to 20 as you suggested and will try your suggestion (2) when I get home in the evening.

Thanks again for your help!

[Andrew_Rowe]

@servoronine

what do you mean by “check if there are 5 lines on the UI page for the device”.

like this - at the bottom

[servoronine (Sergey)]

Thanks Andrew! I do not have the 5th option:

So again suggests that it has not been fully initialized I will attempt the short press/three button presses suggested by Bob and will report back.

Thanks again for all of your support - much appreciated!

[apella12 (Bob Eckhoff)]

Could also try removing the battery for 30 seconds and reinstall. Sometimes that spurs a wake

[servoronine (Sergey)]

Hi,

I have now tried the suggestions above (i.e. variations on button presses and taking the battery out), however I now get absolutely no messages related to node 23 in the log.

Is there a way to completely restart the linking process? Perhaps it is a case of device thinking it is linked and controller not recognizing it?

Any other suggestions much appreciate as I completely stuck with this sensor

Thank you!

[chris4789 (Christian)]

I have since some years the aeotec with I think 5 or 6 sensors, so not the exactly same.
It took me hours to get the device included, although I am using the device without batteries.
Afai can remember it needed a direct connection to the controller.

Battery driven devices can be a pain, I remember on a Fibaro smoke sensor which took 5-6 days until inclusion was completed.

[Andrew_Rowe]

@servoronine

Any other suggestions much appreciate as I completely stuck

What Christian said above is sometimes true

@chris4789

It took me hours to get the device included

@chris4789

Battery driven devices can be a pain,

That has also been my experience. I’ve seen devices which the documentation gives a wake up or reset procedure that does not work as described. I myself have had battery devices I needed to wake up dozens of times.
Find the documentation for the device. Try the wake up procedure… repeatedly… only waiting maybe 30 seconds in between tries. If the device doesn’t seem to respond try 3 quick presses or three really long presses or just holding the button down for a long time. Keep trying
Removing the battery usually resets battery devices. Try that. Keep trying

[apella12 (Bob Eckhoff)]

Sorry for your troubles

@servoronine

however I now get absolutely no messages related to node 23

That is not good (assuming at Debug). How close is the device to the controller?

Before restarting inclusion (see below); Do an OH restart. Then try a new battery with button presses; Try an inbox scan (Don’t expect anything but maybe could be a new number?). Do a last check for the XML.

@servoronine

Is there a way to completely restart the linking process?

The recommended way is to put the Controller in Exclusion mode (on controller UI page) and do the button press sequence. However, that might not work since there are no messages, but try that first (say with a new battery).

If the Aeotec Zstick with the button: could stop the Zwave binding in the karaf console, remove the stick, go to the sensor location, put stick in exclusion, press the button sequence. If that works could put stick in inclusion and press button to include. If that works put stick back in OH and restart the binding and inbox scan for the device.

Lastly could factory reset the device and try inclusion again, but old node will need to be removed (eventually) using Simplicity Suite. As battery device it will not affect the network, but will be annoying.

[servoronine (Sergey)]

Hi All,

After a few hours of experimenting with button presses I finally managed to resolve the issue by starting from scratch. What I have done was:

• Deleted the thing from the list in Openhab
• Performed exclusion of the device (2 second button press on Aeotic stick + button press on the sensor)
• Factory reset the sensor (15 second button press)
• Performed inclusion of the device (button press on Aeotic stick + button press on the sensor)
• Plugged the stick back into my Raspberry Pi and switched the sensor on (5 second press of the button)

Interestingly, this time it took a while for the device to get fully detected as Node 24 (i.e. all details were blank for 3-4 minutes and then appeared). But now I can see all 5 options:

And it does also report the sensor readings when I link channels to items.

Not sure what has gone wrong the first time round but all is well now. Thanks a lot for your support on this - much appreciated!