ZWave not generating XML for Aeotec TriSensor

Good day people,

For your benefit and the one of cinadr who is struggling as well with an Aeotec TriSensor, AEOTEC TRisensor fw 1.21 (20200731) cannot set association groups, I am adding this update on my own saga.

First, to ensure the continuity of my smart home, I bought a FIBARO Z-Wave Plus Multi Sensor for Motion, Temperature and Light (FGMS-001-ZW5). I found its light sensor less precise than the Aeotec TriSensor but it has been very reliable for the last 3 months.

Back in June, I contacted the Aeotec Support and explained how my Aeotec TriSensor was unreliable. They suggested that I upgrade my firm firmware from 2.09 to 2.21. Note that part of the firmware upgrade, you have to remove and re-add your device and that changes your device node number/id. The firmware did not resolve my reliability problem since the Aeotec TriSensor stopped sending information during 2 days.

The Aeotec Support staff asked me to check for following parameters: polling period, Group Association #1, Parameter 21 - Temperature threshold setting, Parameter 22 - Light Threshold setting, Parameter 23 - Temperature report interval and Parameter 24 - Light report interval. Since all those parameters were OK, they recommended warranty replacement of the unit.

By the third week of July I received the new TriSensor and I paired it successfully to my Z-Wave network. If the pairing went well, the new TriSensor appears to be less reliable than the previous one. In fact, for the first 4 days, the TriSensor had updated the temperature, luminance and alarm motion data only a few times. As recommended by the Aeotec Support staff, that I upgraded my firm firmware from version 2.15 to 2.21. Unfortunately, the TriSensor stopped sending temperature, luminance and alarm_motion data about 7 days after the firmware upgrade. Even the DEL showing motion detection stopped functioning as well.

At the end of the first week of August, the Aeotec Support staff suggested that I changed the Parameter 1 [2 byte] to 241 (1 second over the timeout time on Parameter 2). Like before, after 7 days of working well, the TriSensor stopped sending data. However, about 35 hours later, it resumed sending data without any intervention from my part. Even the battery level was updated. I do not understand why the TriSensor stopped and why it resumed sending data.

The Aeotec Support staffs have not given up on me yet. They are testing the TriSensor at their end and talking to their engineering team. To be continued…

2 Likes