Aeotec TriSensor does not clear the motion

🛎️ Get Help
1

Hello,

I've added Aeotec TriSensor to Hubitat but it doesn't seem to work correctly with because it keeps the motion: active infinitely.

I tried (multiple times and in different combinations):

  • Forcing to wake up the device
  • Reinstalling the battery
  • Restarting the hub

I'm not sure what I need to do to make the motion sensor actually work (and clear the motion).
Note:

  • he sensor also doesn't seem to pick up the Temperature Offset (-6.5ºC - see logs). But that's less important than making the motion actually clear;
  • there are 7 pending changes that will be sent to the device the next time it wakes up and even after waking up the device - this number doesn't go down (failing to apply settings? but no log/trace of it)

Any suggestions?

The debug logs (starting with the battery insertion, then forced wake up):

dev:2262019-12-10 01:25:01.378 am warnThere are 7 pending changes that will be sent to the device the next time it wakes up.  You can force the device to wake up immediately by opening the device and holding the connection button for 3 seconds.
dev:2262019-12-10 01:24:57.341 am debugLight Calibrated Coefficient (Param #100) = -4352
dev:2262019-12-10 01:24:55.839 am debugTemperature Offset (Param #30) = 0
dev:2262019-12-10 01:24:54.277 am debugLight Reporting Interval (Param #24) = 21020
dev:2262019-12-10 01:24:52.793 am debugTemperature Reporting Interval (Param #23) = 8897
dev:2262019-12-10 01:24:51.254 am debugLight Reporting Threshold (Param #22) = 4592
dev:2262019-12-10 01:24:49.757 am debugMotion Clear Time (Param #2) = 8065
dev:2262019-12-10 01:24:48.177 am debugMotion Retrigger Time (Param #1) = 26624
dev:2262019-12-10 01:24:47.183 am debugChanging Light Calibrated Coefficient (Param #100) to "1024" (null)
dev:2262019-12-10 01:24:47.178 am debugChanging Temperature Offset (Param #30) to "-65" (-6.5°)
dev:2262019-12-10 01:24:47.174 am debugChanging Light Reporting Interval (Param #24) to "1800" (30 Minutes)
dev:2262019-12-10 01:24:47.169 am debugChanging Temperature Reporting Interval (Param #23) to "3600" (1 Hour)
dev:2262019-12-10 01:24:47.165 am debugChanging Light Reporting Threshold (Param #22) to "100" (100 lux)
dev:2262019-12-10 01:24:47.159 am debugChanging Motion Clear Time (Param #2) to "5" (5 Seconds)
dev:2262019-12-10 01:24:47.151 am debugChanging Motion Retrigger Time (Param #1) to "1" (1 Second)
dev:2262019-12-10 01:24:47.076 am debugsyncDevice()...
dev:2262019-12-10 01:24:46.991 am debugDevice Woke Up
dev:2262019-12-10 01:23:37.637 am infoLiving Room: illuminance is 32767lux
dev:2262019-12-10 01:23:37.634 am debugSensorMultilevelReport(precision:0, scale:1, sensorType:3, sensorValue:[127, 255], size:2, scaledSensorValue:32767)
dev:2262019-12-10 01:22:49.965 am infoLiving Room: temperature is 24.5°C
dev:2262019-12-10 01:22:49.962 am infoLiving Room: motion is active
dev:2262019-12-10 01:22:49.953 am debugSensorMultilevelReport(precision:1, scale:0, sensorType:1, sensorValue:[0, 245], size:2, scaledSensorValue:24.5)
dev:2262019-12-10 01:22:49.949 am debugNotificationReport(v1AlarmType:0, v1AlarmLevel:0, reserved:0, notificationStatus:255, notificationType:7, event:8, sequence:false, eventParametersLength:0, eventParameter:[])
dev:2262019-12-10 01:20:39.315 am warnThere are 7 pending changes that will be sent to the device the next time it wakes up.  You can force the device to wake up immediately by opening the device and holding the connection button for 3 seconds.
dev:2262019-12-10 01:20:35.323 am debugLight Reporting Interval (Param #24) = 21020
dev:2262019-12-10 01:20:34.006 am debugVersionReport(zWaveLibraryType:3, zWaveProtocolVersion:4, zWaveProtocolSubVersion:61, applicationVersion:2, applicationSubVersion:15)
dev:2262019-12-10 01:20:33.777 am debugTemperature Reporting Interval (Param #23) = 8897
dev:2262019-12-10 01:20:33.268 am infoLiving Room: battery is 90%
dev:2262019-12-10 01:20:33.265 am debugBatteryReport(batteryLevel:90)
dev:2262019-12-10 01:20:32.845 am debugLight Calibrated Coefficient (Param #100) = -4608
dev:2262019-12-10 01:20:32.553 am debugTemperature Reporting Interval (Param #23) = 8897
dev:2262019-12-10 01:20:32.467 am debugTemperature Reporting Interval (Param #23) = 8897
dev:2262019-12-10 01:20:32.319 am debugLight Reporting Threshold (Param #22) = 4592
dev:2262019-12-10 01:20:28.399 am debugMotion Clear Time (Param #2) = 8065
dev:2262019-12-10 01:20:28.220 am debugChanging Light Calibrated Coefficient (Param #100) to "1024" (null)
dev:2262019-12-10 01:20:28.216 am debugChanging Temperature Offset (Param #30) to "-65" (-6.5°)
dev:2262019-12-10 01:20:28.212 am debugChanging Light Reporting Interval (Param #24) to "1800" (30 Minutes)
dev:2262019-12-10 01:20:28.209 am debugChanging Temperature Reporting Interval (Param #23) to "3600" (1 Hour)
dev:2262019-12-10 01:20:28.205 am debugChanging Light Reporting Threshold (Param #22) to "100" (100 lux)
dev:2262019-12-10 01:20:28.194 am debugChanging Motion Clear Time (Param #2) to "5" (5 Seconds)
dev:2262019-12-10 01:20:28.186 am debugChanging Motion Retrigger Time (Param #1) to "1" (1 Second)
dev:2262019-12-10 01:20:28.120 am debugsyncDevice()...
dev:2262019-12-10 01:20:28.044 am debugDevice Woke Up
dev:2262019-12-10 01:20:27.638 am infoLiving Room: battery is 90%
dev:2262019-12-10 01:20:27.635 am debugBatteryReport(batteryLevel:90)
dev:2262019-12-10 01:20:27.606 am infoLiving Room: temperature is 24.5°C
dev:2262019-12-10 01:20:27.603 am debugSensorMultilevelReport(precision:1, scale:0, sensorType:1, sensorValue:[0, 245], size:2, scaledSensorValue:24.5)
dev:2262019-12-10 01:20:27.595 am infoLiving Room: illuminance is 647lux
dev:2262019-12-10 01:20:27.592 am debugSensorMultilevelReport(precision:0, scale:1, sensorType:3, sensorValue:[2, 135], size:2, scaledSensorValue:647)
dev:2262019-12-10 01:20:27.564 am infoLiving Room: motion is inactive
dev:2262019-12-10 01:20:27.556 am debugNotificationReport(v1AlarmType:0, v1AlarmLevel:0, reserved:0, notificationStatus:255, notificationType:7, event:0, sequence:false, eventParametersLength:1, eventParameter:[8])
dev:2262019-12-10 01:20:27.237 am infoLiving Room: temperature is 24.5°C
dev:2262019-12-10 01:20:27.233 am debugSensorMultilevelReport(precision:1, scale:0, sensorType:1, sensorValue:[0, 245], size:2, scaledSensorValue:24.5)

My config screenshot:

image
image.png1826×1634 209 KB

2

So you see that warning at the top of your logs? That means that there are configuration parameters that have not been sent to the device because it is asleep. You have to wake it up, usually by pushing the pairing button once, and then it will finish configuring the device.

1 Like
3

I did that many times as I explained in my post. As per suggestion, held the button for 3 seconds and the settings were sent (at least according to logs) but the message persists.

4

Then that is not what is waking up the sensor. Try just hitting the button once and do it after you set the setting in the driver.

Also, screenshots of your errors, rather than copy/paste is preferable and easier to read.

But motion is going inactive:

dev:2262019-12-10 01:20:27.564 am infoLiving Room: motion is inactive

dev:2262019-12-10 01:22:49.962 am infoLiving Room: motion is active

It was inactive for over 2 minutes. So, I'm not sure why you say it isn't.

1 Like
5

It does wake up the sensor as I can see the settings being sent out immediately.

The log in the OP confirms that:

...
dev:2262019-12-10 01:24:47.151 am debugChanging Motion Retrigger Time (Param #1) to "1" (1 Second)
dev:2262019-12-10 01:24:47.076 am debugsyncDevice()...
dev:2262019-12-10 01:24:46.991 am debugDevice Woke Up

It wasn't reliable and I had to "force it" into "inactive" (can't remember how - perphaps by reinstalling the battery)

But even if you ignore that - it should be changed to "inactive" after 5 seconds as per the settings and not after 2.5 minutes.

I also added a 2nd (Tri)Sensor and it has the same behaviour. It stays active for at least half an hour now and I'm not sure how much longer it will be active for despite no any movement or anything like that (I even pointed it in the dead corner to eliminate false movements).

It activated 6:23 and it is now 7:10 and it still appears as "active". See screenshot:

image
image1770×1602 806 KB

So I have no idea what I'm doing wrong and any suggestions would be appreciated :disappointed:

6

So the second sensor finally turned into inactive after more than 1.5 hrs and I'm having the opposite problem - it doesn't become active anymore even if I jump with and around it :cry:

image
image.png1640×1540 730 KB

7

I would do a factory rest on them and re-pair them to the hub.

8

Do you know by any chance how to do it?
They are all brand new so :man_shrugging:

9

I just bought 3 ZSE18 sensors and they were all unresponsive after pairing and pulling the battery. I had to factory reset all of them and re-pair them to get them to work.

10

The device is waking up, but it's rejecting the 5 second clear time setting and reporting that it's 8035 which explains why it's taking so long.

It's possible Aeotec released new firmware with a higher minimum clear time so try setting it to 30 seconds.

UPDATE:

I checked the my SmartThings handler and I have the minimum value of "Motion Retrigger" at 15 seconds and "Motion Clear" at 30 seconds so using those values or above should solve the syncing issue for those 2.

If it does, try higher values for the others and let me know if that works.

UPDATE 2:

I'm not sure if I'm correct about the minimum values for the motion re-trigger and motion clear settings being 15 and 30 seconds is correct.

I know that the original version of my SmartThings handler had the same options as Hubitat's and that's what all the manuals show, but I increased them in mine. I can't remember if that was requested by Aeotec or users were having syncing issues...

11

The reset instructions are in the manual. Tri Sensor User Guide : Aeotec Group

12

Don't bother, I just joined mine and it's doing the same thing as yours so it looks like there's a bug in either the driver or the platform.

Instead of waiting for that to get fixed you can use the driver below to manually change those settings. Once you've changed them you can set it back to the built-in driver and everything should work as expected.

Those are all size 2 parameters and the logging results you posted show the parameter numbers (Param #) and the values they need to be set to (number in quotes).

  • Light Calibrated Coefficient (Param #100) to "1024" (null)
  • Temperature Offset (Param #30) to "-65" (-6.5°)
  • Light Reporting Interval (Param #24) to "1800" (30 Minutes)
  • Temperature Reporting Interval (Param #23) to "3600" (1 Hour)
  • Light Reporting Threshold (Param #22) to "100" (100 lux)
  • Motion Clear Time (Param #2) to "5" (5 Seconds)
  • Motion Retrigger Time (Param #1) to "1" (1 Second)
13

Thanks guys for the info.
I've sent the devices back and the seller will diagnose those and see what is going on.

Nudge me in a bit if you want me to report back on it.

14

FYI, this was a confirmed issue with Hubitat that was fixed in the latest hotfix...

15

Thanks. Do you have any link/details of what the actual issue was?

16

It's the size 2 configuration parameter fix that's mentioned in the 2.1.7 release notes.

17

The 2.1.7 was released 19 days ago from what I can see and I still had the problem 5 days ago.
Fairly sure I installed the updates by then.

So I'm not sure if I should take my chances and get the sensors back as the vendor said they couldn't find anything wrong with them.

Can anyone please confirm that it was indeed fixed and the TriSensor works as expected?

18

It was fixed in one of the recent hot fixes.

I have the device, I confirmed that mine was doing the same thing as yours, and after that hotfix it works as expected again...

1 Like
19

Having a very similar issue to @dnagir -- TriSensor will pair and operate fine for an indeterminate time and then will lock into "active." I have reset / repaired / factory reset and the best result I had was when I forced active and pushed 30s retrigger & 30s clear settings -- lasted ~1.5d

This is a brand new unit & I'd hate to have to return... @ccheng any advice?

20

Assuming you've upgraded your hub to the latest version then your issue is unrelated to what @dnagir was seeing.

I had a defective one of these that was doing the same thing as yours.