You are correct. Just recently I (my fault) had to re-pair my Hue Matter bridge. All the the lights were lost of course but it wasn’t a big problem. The routines are greyed out, but with a red sign to distinguish from disabled. In each routine select the placeholder and re-select the device. It restores the original values e.g. on/off, switch off after 10 minutes etc.
5 Likes
I will report back on the whole driver issue shortly, but after removing and adding the sensor, neither of the routines had been retained. Just for info.
I initially thought I would give it a try without uninstalling, and for a while it seemed to work fine. But then today it started failing to report illuminance. So, I uninstalled the Frient driver and left the Mc driver installed. I uninstalled the device and then installed it again. I waited for about an hour, but it didn’t update. I checked which driver it was using, and it was the default driver. So I changed to the Mc one. So far, it is detecting motion and has reported a temperature, but battery, illuminance and occupancy are showing nothing. Early days on that at the moment. As mentioned elsewhere, the routines were not retained in this process.
This device uses different endpoints for each cluster, temperature, illuminance, battery, occupancy.
My driver configures the device by explicitly sending each configuration to a specific endpoint to device reports correctly.
For this to happen, it must be paired directly with the Mc driver.
When I did the Drive, smartting did not correctly detect the device endpoints and not all the capabilities worked fine, I don’t know if that was fixed or not.
You should delete the stock driver as well and wait about 30 minutes, due to a smartthings problem, to pair directly with the Mc driver instead of the stock driver.
The above situation didn’t change, so I uninstalled again. This time, when I added the device, the Mc driver was added straightaway. It also started working immediately and I have had an illuminance reading every minute. I am still checking the interval for temperature, but that is much less important for me, and it does look like it is working as expected. I just need to find out what on earth “occupancy” actually means for this device!
2 Likes
This device reports movement, by the IASZone cluster and occupancy by the occupancy cluster.
Maybe the timeouts are different for movement and occupation, but I don’t know.
The reporting is definitely different, but I just literally don’t know what “away” and “inside” are meant to mean and how that differs from “movement” and “no movement”. “Inside” seems to trigger at the same time as “motion detected”, but “away” seems to trigger some time after the last “no motion” report. The only times it has reported so far, it was 3 and 4 minutes after “no motion”. There are no settings related to occupancy. I don’t think I really have any use for occupancy anyway. I got the pro version for the illuminance detection mainly, hence my concern about this aspect of it.
Edit: The latest “away” report is 8 minutes after a “motion detected” and without a “no motion” inbetween!
For some users, it can be used to execute more complex routines, if they have two different capabilities, without the need to use virtual devices.
This is the complete manual, if you want to see it.
By default, as @orangebucket says, it has different timeouts for movement, 30 sec and for occupancy, 240 sec.
They are configurable, but it is not implemented in the driver.
The impression I formed flicking through a technical manual for what I think may be a version of this device is that the occupancy cluster defaults to going active on the first movement detection and defaults to a four minute delay before going inactive.
The IASZone cluster is intended for use with alarms and so is less sensitive (though I couldn’t see this quantified) and the default delay to going inactive is twenty seconds. It seems to be necessary to acknowledge the initial alert before it can be cleared. I’ve no idea if that is typical when working with the IASZone.
I’ll leave it to those who have the devices and/or a far better understanding of the technicalities to decide if that seems plausible.
@Mariano_Colmenarejo Many thanks for the manual. It doesn’t really, as far as I can see, give any indication about the difference between movement detection and occupancy. In particular, I can’t see how “away” and “inside” are triggered without other movement detection events. I am looking at the history, which shows that “inside” is reported directly after “away” in the list and only one minute apart without any movement events. However, I don’t think I need that anyway.
So, I think I know what I need to know, and I think the sensor is now working as I need it to. So thank you to everyone who has contributed.
1 Like