Dome Motion Detector

Posted on
Tue Nov 19, 2019 2:49 pm
matt (support) offline
Site Admin
User avatar
Posts: 19439
Joined: Jan 27, 2003
Location: Texas

Re: Dome Motion Detector

The module is battery powered, so sending a status request is going to result in a 'no ack' since the module will be asleep. In the next version of Indigo we will get the Status Request button disabled to avoid the confusion.

Based on WagnerOne's post above his module is sending the luminance updates, just not as often as it should.

Image

Posted on
Tue Nov 19, 2019 9:23 pm
t-star online
Posts: 57
Joined: Oct 26, 2007

Re: Dome Motion Detector

If it is sending Luminescence, Indigo isn’t storing it anywhere that I can tell. Still using 7.3.1. Am I missing it?

Posted on
Tue Nov 19, 2019 10:18 pm
matt (support) offline
Site Admin
User avatar
Posts: 19439
Joined: Jan 27, 2003
Location: Texas

Re: Dome Motion Detector

Wake your module then re-sync it and copy/paste the Event Log results into a reply for me.

Image

Posted on
Tue Nov 19, 2019 11:30 pm
Furball offline
Posts: 9
Joined: Jul 10, 2015

Re: Dome Motion Detector

Yes, that’s the issue I’m seeing. No luminescence value plus the no ack.

Posted on
Wed Nov 20, 2019 2:31 pm
Different Computers offline
User avatar
Posts: 1934
Joined: Jan 02, 2016
Location: East Coast

Re: Dome Motion Detector

I think it calls it "Luminance" and it did not appear for me until I re-synched it. Had been using it via raw commands.

Good news: It actually seems to be a pretty fine grained light sensor! all my other ones hit 100 and stay there almost all day long, regardless of cloud cover, rain, etc.

SmartThings refugee, so happy to be on Indigo. 10.13.6 on an i5 MBP w/Harmony Hub, Hue, DomoPad, Dynamic URL, Device Extensions, HomeKit Bridge, MatplotLib, Plex, uniFAP, Wunderground, Nanoleaf, LED Simple Effects, Airfoil Pro, Grafana.

Posted on
Wed Nov 20, 2019 10:44 pm
t-star online
Posts: 57
Joined: Oct 26, 2007

Re: Dome Motion Detector

Will try this on the weekend or early next week.

Posted on
Sun Nov 24, 2019 11:10 am
t-star online
Posts: 57
Joined: Oct 26, 2007

Re: Dome Motion Detector

So I have learned a lot in looking a little deeper into this. You will see a couple of updates before the synching. this is because I took the sensor down and unto the light. One of the parameters is: Syncing - retrieved parameter 9 "Luminance sensitivity" is 100 LUX So unless there is a change in Lux of more than 100 it won't send an update. Well, I have no idea how to judge a Lux but evidently in the corner of the room that my sensor is in. it does not really change more than 100 very often. I have not had it up and working long enough to k now if it will ever pass that threshold. It would be nice to change it if you have an idea how to do that. You will also notice (hopefully) that there is a note that it changed the units to Lux. This indicates to me that they is probably the first time that I got a value to store.

So in a nutshell it does work once it passes that threshold. I'll keep an eye on it.

Here is the the synching stuff plus some other things before and after. tried to separate by blank lines

Code: Select all
2019-11-23 22:44:09.081   Z-Wave   received "FIR-OFF-MTN" status update is on
2019-11-23 22:44:21.223   Z-Wave   received "FIR-OFF-MTN" status update is on
2019-11-23 22:44:30.636   Z-Wave   received "FIR-OFF-MTN" status update is on
2019-11-23 22:44:39.225   Z-Wave   received "FIR-OFF-MTN" status update is on
2019-11-23 22:44:48.663   Z-Wave   received "FIR-OFF-MTN" status update is on
2019-11-23 22:44:48.738   Z-Wave   received "FIR-OFF-LUM" sensor update to 191 lux
2019-11-23 22:44:48.741   Z-Wave   received "FIR-OFF-LUM" units changed to lux

2019-11-23 22:45:05.749   Z-Wave   received "FIR-OFF-MTN" status update is on
2019-11-23 22:45:14.576   Z-Wave   received "FIR-OFF-MTN" status update is on
2019-11-23 22:45:26.355   Z-Wave   received "FIR-OFF-MTN" status update is on
2019-11-23 22:45:34.842   Z-Wave   received "FIR-OFF-MTN" status update is on
2019-11-23 22:45:34.919   Z-Wave   received "FIR-OFF-LUM" sensor update to 20 lux
2019-11-23 22:45:43.874   Z-Wave   received "FIR-OFF-MTN" status update is on
2019-11-23 22:45:53.791   Z-Wave   received "FIR-OFF-MTN" status update is on
2019-11-23 22:46:02.720   Z-Wave   received "FIR-OFF-MTN" status update is on
2019-11-23 22:46:11.566   Z-Wave   received "FIR-OFF-MTN" status update is on
2019-11-23 22:46:22.079   Z-Wave   received "FIR-OFF-MTN" status update is on

2019-11-23 22:50:42.814   Z-Wave   Syncing - started for "FIR-OFF-MTN"
2019-11-23 22:50:42.830   Z-Wave   Syncing - retrieved module neighbors list: 29, 36, 38
2019-11-23 22:50:42.830   Z-Wave   Syncing - assigning return route to "041 - FIR-OFF-MTN"
2019-11-23 22:50:45.603   Z-Wave   Syncing - assigned return route
2019-11-23 22:50:46.253   Z-Wave   Syncing - retrieved manufacture and model names: Dome - 021F, Motion Sensor (DMMS1) - 00030083
2019-11-23 22:50:46.633   Z-Wave   Syncing - retrieved protocol version 4.05, app version 3.92
2019-11-23 22:50:47.304   Z-Wave   Syncing - retrieved class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01, base 00)
2019-11-23 22:50:47.304   Z-Wave   Syncing - retrieved command classes: 20v1 80v1 84v2 85v1 86v1 30v1 70v1 71v1 72v1 73v1 59v1 31v7 5Av1 5Ev1
2019-11-23 22:50:47.304   Z-Wave   Syncing - retrieved encrypt commands: - none -
2019-11-23 22:50:47.305   Z-Wave   Syncing - retrieved capabilities: routing, battery, beaming, waking
2019-11-23 22:50:47.633   Z-Wave   Syncing - retrieved wake interval of 60 minutes
2019-11-23 22:50:47.715   Z-Wave   Syncing - device "041 - FIR-OFF-MTN" wake interval changed to 60 minutes
2019-11-23 22:50:48.375   Z-Wave   Syncing - retrieved group 1 associations: [1]
2019-11-23 22:50:48.705   Z-Wave   Syncing - retrieved group 2 associations: []
2019-11-23 22:50:49.035   Z-Wave   Syncing - retrieved group 3 associations: []
2019-11-23 22:50:49.368   Z-Wave   Syncing - retrieved group 4 associations: []
2019-11-23 22:50:49.368   Z-Wave   Syncing - group 1 association to interface already exists (skipping)
2019-11-23 22:50:49.753   Z-Wave   Syncing - retrieved parameter 4 "Enable motion sensor" is true
2019-11-23 22:50:50.087   Z-Wave   Syncing - retrieved parameter 1 "Motion sensor sensitivity" is 12
2019-11-23 22:50:50.420   Z-Wave   Syncing - retrieved parameter 2 "Off delay" is 240 seconds
2019-11-23 22:50:50.753   Z-Wave   Syncing - retrieved parameter 6 "Re-trigger interval" is 8 seconds
2019-11-23 22:50:57.753   Z-Wave   Syncing - retrieved parameter 9 "Luminance sensitivity" is 100 LUX
2019-11-23 22:50:58.083   Z-Wave   Syncing - retrieved parameter 7 "Luminance reporting interval" is 180 seconds
2019-11-23 22:50:58.423   Z-Wave   Syncing - retrieved parameter 10 "LED blink during motion" is true
2019-11-23 22:50:58.755   Z-Wave   Syncing - retrieved battery level of 100%
2019-11-23 22:50:58.961   Z-Wave   Syncing - complete

2019-11-23 22:53:35.945   Z-Wave   Optimizing - started network optimization for nodes: 41
2019-11-23 22:53:39.024   Z-Wave   Optimizing - starting "041 - FIR-OFF-MTN"
2019-11-23 22:53:47.178   Z-Wave   Optimizing - ping completed in 8051 ms
2019-11-23 22:53:47.178   Z-Wave   Optimizing - finding neighbors
2019-11-23 22:53:47.206   Z-Wave   Optimizing - requesting neighbor list update
2019-11-23 22:54:07.113   Z-Wave   Optimizing - neighbor list updated from 29, 36, 38 to 29
2019-11-23 22:54:07.120   Z-Wave   Optimizing - finished "041 - FIR-OFF-MTN"
2019-11-23 22:54:07.120   Z-Wave   Optimizing - complete
2019-11-23 22:54:07.121   Z-Wave   Optimizing - update succeeded: "041 - FIR-OFF-MTN"

Who is online

Users browsing this forum: No registered users and 0 guests