This object is in archive!
How to configure a NEO Coolcam motion sensor?
Answered
Can someone help me to configure the sensor. The motion sensor is working but the lux sensor isn't. Maybe someone has an example to share.
The same question
No connection
Real-time notifications may not work
Hi Philippe,
I just recently bought two as well and am still experiencing with them. Movement works reasonably ok, but the lux-sensors are not really accurate.
Even when positioned right next to eachother, "PIR1" reads 7169 lux and "PIR2" reads 4444lux... They are litterly positioned in the same light,.. So I guess it's a matter of trial and error with each individual device to determine the values depending on the light.
I cannot show you my settings unfortunately, somehow my Zipatile settings is only showing 1 configuration option now, I didn't change anything though, besides option 9; I set that to 25 (standard=100), but to be honest, I still have to find out how accurate lux is changed. Perhaps '100' will do, but I have the feeling that in a darker room the sensor doesn't read much above 0 lux :-)
Let me if you find out any tips/tricks :-)!
Readings:
Physical setup while reading above:
Hi Philippe,
I just recently bought two as well and am still experiencing with them. Movement works reasonably ok, but the lux-sensors are not really accurate.
Even when positioned right next to eachother, "PIR1" reads 7169 lux and "PIR2" reads 4444lux... They are litterly positioned in the same light,.. So I guess it's a matter of trial and error with each individual device to determine the values depending on the light.
I cannot show you my settings unfortunately, somehow my Zipatile settings is only showing 1 configuration option now, I didn't change anything though, besides option 9; I set that to 25 (standard=100), but to be honest, I still have to find out how accurate lux is changed. Perhaps '100' will do, but I have the feeling that in a darker room the sensor doesn't read much above 0 lux :-)
Let me if you find out any tips/tricks :-)!
Readings:
Physical setup while reading above:
Hi all,
Weird thing happened... After downgrading the firmware (it resulted in weird values on my devices) I might stumble upon the same issue as Philippe about configuring the NEO Coolcam.
When I just received them, connected them to my Zipatile, everything was recognized fine:
- 1 module;
- a motion sensor in it;
- a light meter in it.
After 2 days though, Zipatile seems to think that the module can read temperatures as well, which it cannot.
I am not sure whether this is the way to go, but I tried "forcing" the module to be recognized as a light (lux) sensor, but that doesn't work.
When I go to the device browser (left side), you can see that the PIR2-LUM actually shows a value which might be correct (let's just state that the values differ depending on the light, I have no idea if these numbers are actually accurate).
On the module side though, I don't have the option to work with the lux-meter:
In the Module manager, the device is split up into several 'units' (?) I guess; group 2-4 won't be used by me, and being able to differentiate the other sensors I renamed them. 'Motion Sensor PIR2b' works fine, although:
'Motion Sensor PIR2b' is shown in my Device Browser, but I have to chose the 'Motion Sensor PIR2' as a device (in the Module > Sensor section on the right)
The weird thing is though, that the device thinks the second 'unit' is a temperature-unit, but it's ONLY a light-meter (lux meter). I forced this 'Neo Temp Sensor' to act as a 'Light sensor' (no other relevant options to chose), but that doesn't give the expected result,
The 'PIR2-LUM' is configured as a brightness meter, but that setting is immediate resetted by the Zipatile.
When trying to use the 'Neo Temp Sensor' as a light-meter (lux meter), it only gives me the option to chose for 'Temperature' - which it can not meassure...
Anybody who can help? Am I configuring it wrong as well? As stated; Out of the box it seemed plug and play, but all of a sudden the settings are changed and weird... Resetting the device or connecting it again, doesn't help either.
Hi all,
Weird thing happened... After downgrading the firmware (it resulted in weird values on my devices) I might stumble upon the same issue as Philippe about configuring the NEO Coolcam.
When I just received them, connected them to my Zipatile, everything was recognized fine:
- 1 module;
- a motion sensor in it;
- a light meter in it.
After 2 days though, Zipatile seems to think that the module can read temperatures as well, which it cannot.
I am not sure whether this is the way to go, but I tried "forcing" the module to be recognized as a light (lux) sensor, but that doesn't work.
When I go to the device browser (left side), you can see that the PIR2-LUM actually shows a value which might be correct (let's just state that the values differ depending on the light, I have no idea if these numbers are actually accurate).
On the module side though, I don't have the option to work with the lux-meter:
In the Module manager, the device is split up into several 'units' (?) I guess; group 2-4 won't be used by me, and being able to differentiate the other sensors I renamed them. 'Motion Sensor PIR2b' works fine, although:
'Motion Sensor PIR2b' is shown in my Device Browser, but I have to chose the 'Motion Sensor PIR2' as a device (in the Module > Sensor section on the right)
The weird thing is though, that the device thinks the second 'unit' is a temperature-unit, but it's ONLY a light-meter (lux meter). I forced this 'Neo Temp Sensor' to act as a 'Light sensor' (no other relevant options to chose), but that doesn't give the expected result,
The 'PIR2-LUM' is configured as a brightness meter, but that setting is immediate resetted by the Zipatile.
When trying to use the 'Neo Temp Sensor' as a light-meter (lux meter), it only gives me the option to chose for 'Temperature' - which it can not meassure...
Anybody who can help? Am I configuring it wrong as well? As stated; Out of the box it seemed plug and play, but all of a sudden the settings are changed and weird... Resetting the device or connecting it again, doesn't help either.
I'm experiencing the same thing, did you mange to find a fix?
I'm experiencing the same thing, did you mange to find a fix?
Its not a bug, its a bad device configuration.
Trough custom configuration options, just set parameter 99 to 5230 and it will work.
brgs
Its not a bug, its a bad device configuration.
Trough custom configuration options, just set parameter 99 to 5230 and it will work.
brgs
does the luminance sensor in general works? are there any constraints?
it seems that it cannot measure values below 50lux, or changes when light is below 50lux. can anybody look into event history if you have there values below 50?
does the luminance sensor in general works? are there any constraints?
it seems that it cannot measure values below 50lux, or changes when light is below 50lux. can anybody look into event history if you have there values below 50?
Replies have been locked on this page!