HSP02 settings - anyone added some?

Other Devices & Integrations Door Locks & Sensors
1

Hi All

I have an HSP02 but it seems to take ages to retrigger after a trigger.

I see witht he SP814 you can set and amend settings to amend re trigger interval etc.

Do any one have any knowledge or advice with this unit? its a real pain as just does not trigger well but is an £80 unit! hopeing someone can help with setting.

Thanks in advance.

regards,
Neal

2

The default on-off interval is set to 15 seconds.
The default re-trigger interval is set to 180 seconds.

In a room with some motion, you will see one on event, an off event 15 seconds later, and nothing else for at least 180 seconds.

These settings try to conserve the battery … sending ZWave information uses more power than sensing motion.

If Vera does not currently recognize the device and provide a UI to set the parameters you can send Z-Wave commands (Advanced Users). See the manual for details: [url=http://adino.se/adino_doc/products/Manual_Everspring_HSP02.pdf]http://adino.se/adino_doc/products/Manual_Everspring_HSP02.pdf[/url]

3

Hi RichardTSchaefer,

Thank you for pointing me in the correct direction - huge help :slight_smile:

a few questions if i may:

Could you offer any more knowledeg on the “LUX Level” - I have done some reading but not sure i quite understand.

also I have used:

  1. 1 byte dec, 5 (time on before off , default 15)
  2. 1 byte dec, 30 (Time before detaecting anouther trigger - default is 180)
  3. 1 byte dec, 10 (sensitivity level - default is 6 but it seems everyone goes for maximum sensitivity, mine could certainly do with a boost so hopfuly this will help.)

However - I used “1 byte dec” as this was used in a similar thread (http://forum.micasaverde.com/index.php?topic=10462.0) is this correct or do you happen to know if i should use one of the other settings? I am not sure what the option in this drop doen refer to.

Many thanks again RichardTSchaefer, i think if i can get this done i will realy improve my meny detcetors around the house.

Kind regards,
LightsOn

4

Hi All,

Just anouther foot note - I notice when adding the above settings it notices and lists the default values so 50% of the way there - but will not set the new values desired and just gives error “failed at: Setting user configureation”

Any thoughts?

Many thanks in advance.

Kind regards,
LightsOn

5

Hi All,

Sorry for the many posts - I have no idea if the settings are corect but all seems to work - even thought I perhaps dont fully understand why I needed to choose the different “dec” settings.

Setttings that work great are:

  1. 2 byte dec, 5
  2. 4 byte dec, 30
  3. 1 byte dec, 10
6

Hi

I just got one of these sensors today, not sure its working fully yet.

I tried to change the default re-trigger interval from 180 to 60 seconds,

I used: 4. 4 byte dec, 60 as per LightsOn instruction, but in Vera the sensor just says Waiting for wake up to configure device, see screen shot.

I have tried tripping the sensor by moving in front of it but it still says waiting for wake up to configure any ideas how to wake it up for configuration ?

Thanks

EDIT: On the Settings tab for this sensor there is a button that says “Configure Node right now” if I press this the device then goes RED and says “Unable to get any information on node” or says “Failed at: Setting user configuration”

7

Typically, there’s a way (button) to manually wake up the device. Looking at the manual, it appears the tamper switch may provide that function.

Try it, and if Vera sees the wake-up, she should move on with configuring the device. You will see that status message change.

8

Hello,

Anyone added some settings to HSP02 finally ?

Impossible for me to modify settings even if the sensor is awake

9

I never bothered setting that config in the end I left the sensor as defaults.

10

Is it a problem known by MCV ? Will it be resolved in the next firmware ?

11

So, using the tamper switch to wake up the device for 30 seconds didn’t work?

12

Hello,

With the tamper switch the device is awake but VERA fails when trying to send the configuration to the device.

13

Thanks for the clarification.

If you remove the configuration parameters, does [tt]Configure node right now[/tt] work?

The configuration may get rejected if the wrong size is used. I don’t have this device, but from the manual it looks like the parameters are either of size 1 byte or 2 bytes. So, e.g., a size of 4 byte dec for parameter 4, may not be right.

To diagnose it, you could start with no parameters, then add them one by one and see which one fails.

14

I have always the same problem with and without parameters (with the right byte according to the manual) but I can retrieve the number of each. It seems that it works well with the zibase.

15

OK, in that case, could you state the problem that you are observing? (IIUC, the posts by others all seem related to changing the parameters and ending up with the device not accepting them ([tt]failed at: Setting user configuration[/tt]).)

16

Hi All,

Did anyone get anywhere with this? I’m having this problem and out of the box the parameters make it a little useless for what I am trying to use it for.

17

I don’t have this device. For clarity, could you restate the issue you are observing?

18

oTi@

When you try and configure parameters in Vera Lite UI5 I am getting “failed at: Setting user configuration”. Having a look at the logs there’s not much help, all I see are the calls to configure the parameters and then at the end it reads back the values from the device and it finds they have not changed so errors.

Weirdly enough I have finally got two of the three parameters set. How I don’t know, just a matter of trying and trying, I have another two (wish I had just bought one to test first) so perhaps when I have the energy I shall see if I can make sense of it. Even so it whilst I have managed to config some parameters, there does seem a problem here.

19

Tried configuring the second one and that’s gone equally well, and by well I mean badly. None of the variables were configuring and then one of them flipped to the value I set it to but the other two have failed to be set.

I have no idea what allows them to get set other than I constantly delete, change and add the variables. I wouldn’t mind but the variable I set on the second unit was variable 6 which is the variable that I can’t set on the first unit.

20

OK I think I have cracked it, just posting this for others out there. It’s not 100% and it a bit of messing but I think I have a way to get the config set.

Essentially you can only set one variable at once… I’m not sure if this is needed but it’s the way I have made it work. It’s possible you can set more but have yet to prove it. Once set click the tamper switch, this will almost always fail but then go and reconfigure and click the tamper switch and keep doing this until the variable is set. This will fail more than once but eventually it appears to take. You might have to wait for a minutes or two between configures too as I think it you might need to to go back to sleep before you try again.

To set a second variable delete the previous one, this is OK because the value is still stored in the unit so it’s not going to kill all your hard work. Then do the same as before to set the second variable.

Keep doing this until all your variables are set.

What I do then is go back and add all the variables so at least you know what’s set in the device, this won’t fail because you’re going to set them to what is already in the device.

Like I say it’s not definitive as there are still a few unknowns as is a little hit an miss but does seem to get it configed eventually.