All,
I have the Aeotec Multisensor and a z-wave-enabled lighgt. I've set up a pretty straightforward scene to switch on the light when motion is detected by the Multsensor, under the condition that current luminosity (again, as measured by the Multisensor) is below a certain threshold. This scene simply does not work, although the Multisensor switches to 255. i.e. motion detected.
Now, if I associate the light with the Multisensor, the scene works, but completely disregards the luminosity condition, i.e. the light switches on every time motion is detected, even in broad daylight.
Any idea what could be wrong here? Thanks!
Cheers
Alfons
Switching on a Light when Motion detected
- 163 Views
- Last Post 01 November 2014
awlieser
posted this
30 October 2014
tnamey
posted this
30 October 2014
Can you post a screen shot of the trigger and condition screens for this scene?
awlieser
posted this
30 October 2014
[quote=tnamey]Can you post a screen shot of the trigger and condition screens for this scene?[/quote]
Here we go:
1 - Device (it's a z-wave enabled bulb)
http://s12.postimg.org/erwik7fod/Device.png
2 - Trigger (the Aeotec sensor, 255 means motion detected)
http://s30.postimg.org/o4680sjfl/Trigger.png
3 - Condition (Helligkeit = luminosity - virtual device based on teh Aeotec Multisensor - , standard daylight value is 1000)
http://s30.postimg.org/pog5cxh7l/Condition.png
Cheers
Alfons
weidnerj
posted this
30 October 2014
All,
I have the Aeotec Multisensor and a z-wave-enabled lighgt. I've set up a pretty straightforward scene to switch on the light when motion is detected by the Multsensor, under the condition that current luminosity (again, as measured by the Multisensor) is below a certain threshold. This scene simply does not work, although the Multisensor switches to 255. i.e. motion detected.
Now, if I associate the light with the Multisensor, the scene works, but completely disregards the luminosity condition, i.e. the light switches on every time motion is detected, even in broad daylight.
Any idea what could be wrong here? Thanks!
Cheers
Alfons
1. Did you create a device for each sensor?
My main Aeon Labs sensor is a configured as a motion sensor.
The light sensor is setup as a LevelDisplayer
2. Trigger should be "device" detects motion
3. Conditions should be "light sensor" <=>
If you use 900 as the trigger, that is almost daylight level so that might be why it comes on during daylight. I use closer to 200 which still is a bit light, enough to see but what worked for me.
Also if you click on the Devices tab, and to the immediate right is a pull down of tile / list. Use list mode, that will show you the current settings and levels of your device(s).
awlieser
posted this
31 October 2014
All,
I have the Aeotec Multisensor and a z-wave-enabled lighgt. I've set up a pretty straightforward scene to switch on the light when motion is detected by the Multsensor, under the condition that current luminosity (again, as measured by the Multisensor) is below a certain threshold. This scene simply does not work, although the Multisensor switches to 255. i.e. motion detected.
Now, if I associate the light with the Multisensor, the scene works, but completely disregards the luminosity condition, i.e. the light switches on every time motion is detected, even in broad daylight.
Any idea what could be wrong here? Thanks!
Cheers
Alfons
1. Did you create a device for each sensor?
My main Aeon Labs sensor is a configured as a motion sensor.
The light sensor is setup as a LevelDisplayer
2. Trigger should be "device" detects motion
3. Conditions should be "light sensor" <=>
If you use 900 as the trigger, that is almost daylight level so that might be why it comes on during daylight. I use closer to 200 which still is a bit light, enough to see but what worked for me.
Also if you click on the Devices tab, and to the immediate right is a pull down of tile / list. Use list mode, that will show you the current settings and levels of your device(s).
Hi,
thanks, pls see comments below:
1 - yes
2 - motion detection is not the problem - it works
3 - I tried various values here (I know that 900 is nearly daylight), but none did work (e.g. < 100,="">
Cheers
Alfons
Ryan-Scott
posted this
31 October 2014
All,
I have the Aeotec Multisensor and a z-wave-enabled lighgt. I've set up a pretty straightforward scene to switch on the light when motion is detected by the Multsensor, under the condition that current luminosity (again, as measured by the Multisensor) is below a certain threshold. This scene simply does not work, although the Multisensor switches to 255. i.e. motion detected.
Now, if I associate the light with the Multisensor, the scene works, but completely disregards the luminosity condition, i.e. the light switches on every time motion is detected, even in broad daylight.
Any idea what could be wrong here? Thanks!
Cheers
Alfons
Does your scene work if the condition is removed? You can also enable some extra logs for scene stuff in tools/options. These show up in your logfile.txt. It'll print out the reason the scene did (or didn't) execute. I'm curious what your log shows after you enable that option... can you show it here?
awlieser
posted this
31 October 2014
All,
I have the Aeotec Multisensor and a z-wave-enabled lighgt. I've set up a pretty straightforward scene to switch on the light when motion is detected by the Multsensor, under the condition that current luminosity (again, as measured by the Multisensor) is below a certain threshold. This scene simply does not work, although the Multisensor switches to 255. i.e. motion detected.
Now, if I associate the light with the Multisensor, the scene works, but completely disregards the luminosity condition, i.e. the light switches on every time motion is detected, even in broad daylight.
Any idea what could be wrong here? Thanks!
Cheers
Alfons
Does your scene work if the condition is removed? You can also enable some extra logs for scene stuff in tools/options. These show up in your logfile.txt. It'll print out the reason the scene did (or didn't) execute. I'm curious what your log shows after you enable that option... can you show it here?
Hi Ryan,
the problem is that the scene triggers despite the condition, i.e. the condition is completely disregarded. Will enable extra scene logging and post here.
Cheers
Alfons
Ryan-Scott
posted this
31 October 2014
Now, if I associate the light with the Multisensor, the scene works, but completely disregards the luminosity condition, i.e. the light switches on every time motion is detected, even in broad daylight.
the problem is that the scene triggers despite the condition, i.e. the condition is completely disregarded. Will enable extra scene logging and post here.
Cheers
Alfons
Do you still have the light associated with the multisensor? If so, it's likely that your motion is actually turning the light on directly (i.e, if you turned off InControl, the light would still turn on).
awlieser
posted this
31 October 2014
Hi Ryan,
yes, the lamp is still associated with the motion sensor - otherwise nothing works :-(
Cheers
Alfons
awlieser
posted this
31 October 2014
Now, if I associate the light with the Multisensor, the scene works, but completely disregards the luminosity condition, i.e. the light switches on every time motion is detected, even in broad daylight.
the problem is that the scene triggers despite the condition, i.e. the condition is completely disregarded. Will enable extra scene logging and post here.
Cheers
Alfons
Do you still have the light associated with the multisensor? If so, it's likely that your motion is actually turning the light on directly (i.e, if you turned off InControl, the light would still turn on).
Hi Ryan,
I did enable extra scene logging and triggered the scene - nothing in the logfile. Seems the association overrides whatever scene has been defined.
Cheers
Alfons
awlieser
posted this
31 October 2014
Hi Ryan,
additionally, I was thinking about replacing the Aeotec Multisensor with a simple motion detector, but then I wouldn't have the luminance value and I can't use a time condition between sunset and sunrise, because there's this 3 hour offset which I can't define in a condition (i.e. if I use sunset I have a 180 min offset, so that a device switches on at current local - German - sunset time).
Cheers
Alfons
Ryan-Scott
posted this
31 October 2014
Hi Ryan,
I did enable extra scene logging and triggered the scene - nothing in the logfile. Seems the association overrides whatever scene has been defined.
Cheers
Alfons
I'd get back to the basics and see where we are... if you wouldn't mind, can you do this:
1- Make sure the only thing associated with the Motion sensor is the USB stick (i.e, remove the association to the light)
2- Remove the condition
Once the basic scene is working, we'll move on to adding the condition in.
Also, just thought I'd check - are you on the latest 3.148?
awlieser
posted this
31 October 2014
Hi Ryan,
will do. And yes, I'm on the latest version
Cheers
Alfons
awlieser
posted this
31 October 2014
Hi Ryan,
thanks - did as requested and now the scene works (though there's quite some delay between motion detection and switchting on of the lamp). Will now add the luminance condition back and see what happens.
Cheers
Alfons
awlieser
posted this
31 October 2014
Ok, now the scene does not trigger any more (with condition "Luminance < 200").="" now="" have="" to="" wait="" for="" it="" to="" get="" dark="">
Cheers
Alfons
Ryan-Scott
posted this
31 October 2014
Hi Ryan,
thanks - did as requested and now the scene works (though there's quite some delay between motion detection and switchting on of the lamp). Will now add the luminance condition back and see what happens.
Cheers
Alfons
How much of a delay are you seeing? Could you double-check that you are NOT polling your motion sensors -- or any other battery powered sensor for that matter? That can cause delays by itself.
awlieser
posted this
31 October 2014
Hi Ryan,
about 20 sec. And no, I don't poll battery-operated devices. Shouldn't be a latency problem either - both devices (lamp and sensor) are about 3 meters horizontally and 3 meters vertically from the sensor.
Cheers
Alfons
Ryan-Scott
posted this
31 October 2014
Hi Ryan,
about 20 sec. And no, I don't poll battery-operated devices. Shouldn't be a latency problem either - both devices (lamp and sensor) are about 3 meters horizontally and 3 meters vertically from the sensor.
Cheers
Alfons
20 seconds is too long in a network that is optimized - does the light on your USB stick ever go dark for a long period of time? Does your logfile.txt show any "failed" messages to any devices?
awlieser
posted this
31 October 2014
Hi Ryan,
about 20 sec. And no, I don't poll battery-operated devices. Shouldn't be a latency problem either - both devices (lamp and sensor) are about 3 meters horizontally and 3 meters vertically from the sensor.
Cheers
Alfons
20 seconds is too long in a network that is optimized - does the light on your USB stick ever go dark for a long period of time? Does your logfile.txt show any "failed" messages to any devices?
Strange you mention that - it goes indeed off at odd intervals (it's zwave.me stick) - no idea why. No "failed" messages in the logfile. What could be the problem here? Thanks!
Cheers
Alfons
Ryan-Scott
posted this
31 October 2014
Strange you mention that - it goes indeed off at odd intervals (it's zwave.me stick) - no idea why. No "failed" messages in the logfile. What could be the problem here? Thanks!
Cheers
Alfons
That usually happens when the USB stick is waiting for are response from a device. So for example, let's say you try to send a "power on" command to a motion sensor, or a switch that's too far away, the USB stick will either wait for an acknowledgement or wait for a timeout (usually 30 seconds) before allowing new commands to go out.
You could try to enable audits for all your devices and see if you have something that periodically takes longer than normal. Be sure to restart after enabling the audit.
awlieser
posted this
31 October 2014
Strange you mention that - it goes indeed off at odd intervals (it's zwave.me stick) - no idea why. No "failed" messages in the logfile. What could be the problem here? Thanks!
Cheers
Alfons
That usually happens when the USB stick is waiting for are response from a device. So for example, let's say you try to send a "power on" command to a motion sensor, or a switch that's too far away, the USB stick will either wait for an acknowledgement or wait for a timeout (usually 30 seconds) before allowing new commands to go out.
You could try to enable audits for all your devices and see if you have something that periodically takes longer than normal. Be sure to restart after enabling the audit.
Hi Ryan,
scene works now (after dark). The only problem I've got left presently is that the Multlevel sensor drains the batteries like mad (from 100% to 39% within 24h) - already contacted Aeotec about this.
Will try the audit and report back!
Thanks!
Alfons
