Before i throw this Aeotec ZWave Tri Sensor against a wall, i thought i might ask the community if anyone has any suggestions to get it working properly OR if they had experienced anything similar
The device went off line about 3 to 4 weeks ago and i assumed it was battery, replaced battery and it has absolutely refused to work properly in ST ever since, for joining purposes it appears to work correctly, all normal joining methods work without issue, the app downloads a controler plugin and within the ST app all seems to display correctly, except there is no output recieved from the device, no motion, temp or Lux
If i press the button to get the device to wake the LEDs on the device flash correctly but nothing is recieved in ST, i have tried multiple removes and re adds, 3 different batteries just incase, a device factory reset, a zwave network repair and all of the above multiple times, its not a cheap device and i am not in the habit of giving up but …. i am out of ideas, is it actually Dead ?
On the odd occasion it does send a temp reading and sometimes a lux measurement is recieved in the app but it is a rare event, in 24 hrs it might send one measurement but never a motion event, that seems completely dead
Any ideas before i throw it ??
I will add, it does display battery info and that appears to update/change, the coloured LEDs in the device front window all appear to work correctly and i have checked the devices own network health check which returned a green double flash which i think indicated a good connection, i am not bouncing through other devices as i am joining right next to the hub
Also a very important note to readers of this post and Nayalez, my.smartthings.com is a Samsung controlled website
mysmartthings.comm without the (.) Between my and smartthings is a virus carrying parasite website, I forgot to add the . And ended up with a virus ! First time in 15 + years i been caught
Pc now offline and being scanned… for 35hrs (sigh)
There are some reports regarding Z-Wave devices not responding, since this is a sensor, I don’t know if it might be related.
Can you follow the steps below to collect some info about this issue, please?
Re-join the device
Try to trigger events on it to detect movement or illuminance changes. Please note the date and time of this attempt and share them with us, including your time zone. This is to check if the hub logs registered anything about the attempt.
Thanks Nayelyz, yeah it’s a real pain, I rarely access the advanced Web app, a robot tick box popped up on a black page and without thinking I clicked it, boom, I was hit😠
My account is already open for dev access, will re read your post and send what is needed
Hi,
If you install ‘Z-Wave Device Config Mc’ and temporarily set this as the Driver for your sensor, you may be able to change configurable settings to make the sensor more responsive.
You will need to study the specification of the sensor to see what the parameters are.
Things to look out for are ‘temperature delta’, ‘wakeup interval’, etc.
I do not have a Tri sensor but I have used this Driver to tweak the configuration of Z-Wave thermostats that I was writing Driver for.
Hope this helps.
I fully support 100 percent!
I have such a sensor, but the previous generation. The most stable operation on the driver: Z-Wave Sensor and Child Thermostat Mc, From Mariano (Always thank him!)
This driver version - 2025-06-15T22:03:58.784623393
(I’ve tested all the drivers and this one gives the most accurate readings)
P.S.
Sensor connected to the power supply unit, because this sensor is energy-intensive
Hi, @fido
I see the device is using a third-party driver, has this been in use since before the device started to fail? I think we need to also confirm the device is being configured correctly during joining mode.
To do so, you need to open the driver logs to see if there’s an error there:
You need to set up the ST CLI and run the command below:
smartthings edge:drivers:logcat
The CLI will prompt you to select from which hub and driver you want to listen to events
Then, rejoin the device so the events of the configuration are registered there.
Copy those logs into a file and share them with us. You can send it to build@smartthings.com
The device has been added countless times now, each time using the aeotec add device method, if it was noticed that a 3rd party driver was being used it was for a short time to test if there was a difference
Non the less i will fire up the the CLI and report back
The expected workflow correctly goes through the setup procedure, the device join button is pushed, The workflow requests a device secure number and the mobile Android app continues and shows the device has joined, a plugin downloads and all seems well in the world
However the CLI is running the whole time using the Aeotec Trisensor driver option 2 for me driver ID, the CLI reports no information, it does display connected so it is listening but is recieving no information from the joining procedure
Thank you for the logs you sent, the explanation you provided there also helped me with the confusion of you selecting the option “MultiSensor6” for the discovery and the device being connected to Mariano’s driver.
So, when you select an option in the catalog, it basically puts the Hub in pairing mode, the device gets paired to a driver following the “rules” for fingerprint match.
Finding the Manufacturer-specific fingerprint on a driver already installed is the first step.
Unfortunately, if several drivers match the device’s fingerprints and are already installed on your hub, we cannot define which one picks up the device, but you can change it afterwards.
About the logs, we can see a GET command to retrieve the current status of the device:
And later a report of it being IDLE is received which is translated to “inactive”:
After that, if you trigger movement on the physical device, do you see any message there?
We should still be able to see the received Z-Wave message of a Motion report, even if the driver didn’t handle it correctly, so, it would be useful to know that the device is reporting correctly.
Note: When we don’t know which driver will be used by the device, we can use the flag --all as shown below to show the logs of all the active drivers:
