Eminent EM6580 motion detector settings

[edek]

Just tested an Eminent EM6580 motion detector. Feels like a very solid device, build quality is good.
Took me a while to get it working, it's necessary to associate it with Homeseer, and you have to wait for a timeout before you can retrigger. So at first it looks like it works only one time, and fails after that. Is it possible to configure this timeout? I believe with a HSM100 you are able to set it to 0 or 1 minute (or more) through the configuration option, " off delay". This will make the sensor available sooner for detection as far as I know.
I didn't time the EM6580 yet, but it looks like it takes 15 or 20 minutes. Can this be changed by sending a parameter with a value? Where can I obtain a list of parameters?

regards,
Edek

[edek]

Just found out it should be an Everspring SP103, I did find some parameter information here:
http://www.pepper1.net/zwavedb/device/59

Great Z-wave device database by the way!

No luck there though, the mentioned parameters won't help me with my problem. I like this motion detector, but I want it to react again within 1 or 2 minutes, not only after 20 minutes or so....

Anyone?

[mhn]

If it's a Everspring SP 103 (like my Flex-Control), you can change the timeout with a screwdriver at the button of the "head".

But be careful, it can eat a lot of battery.

Regards
Morten

[edek]

Morten,
I'm not sure if this is the same function, this is how long the switch will stay ON, it has no influence on how long it will take before it starts detecting and switching again.
The HSM100 is available for switching within a minute, the Everspring/Eminent only after more then 10 minutes (still have to time this, this is difficult since there should be no movement during this time, so it's trying after 5 min, 10 min, 11 min, 12 min etc and you have to wait in between each test for at least the time before it comes available, which I don't know yet).

regards.

[mhn]

If I turn mine to the lowest point. My PIR reacts quick, and eats a lot of battery.

If you PIR acts different, there must be a differnce in the firmware.

In Homeseer mine says: Everspring 101 H 1 H False 2.9 (ZDK Version 4,22) App: 1.0 Unknown (0) 40.0Kbps Basic: ROUTING SLAVE Generic: SENSOR BINARY SENSOR BINARY, CONFIGURATION V2, WAKE UP, MANUFACTURER SPECIFIC, VERSION, ASSOCIATION V2, BATTERY

Regards
Morten

[edek]

Looks the same here:
Everspring 101 H 1 H False 2.9 (ZDK Version 4,22) App: 1.0 Acceptable (5) 40.0Kbps Basic: ROUTING SLAVE
Generic: SENSOR BINARY
SENSOR BINARY, CONFIGURATION V2, WAKE UP, MANUFACTURER SPECIFIC, VERSION, ASSOCIATION V2, BATTERY


I'll have to test later today...