Help to configure SP814 everspring motion detector

Other Devices & Integrations Door Locks & Sensors
41

today I wanted to change configuration for parameter #3, being the detector sensitivity level.
As it did not go straight forward i thought of sharing how I did it, as others may run into same problem

I wanted max sensitivity level, being decimal 10.

I used the approach as descrived by daiz 2 posts back.
I selected 1 byte HEX in the configuration and entered A in the field (Hex A is equal to Dec 10)

And finally it worked. Wauw, that thing can be quite sensitive! i wasnt aware :smiley:

42

[s]I still cannot get this device configured. I tried the method by Daiz and otterlo and repeated the attempts several times with different timings: first click configure now then 3x the button within 1.5 seconds and the other way around.

I’ve got 4 of these sensors none of them can be configured.

I’ve got an everspring sp103 as well and it configures without problems… so it isn’t me being clumsy.[/s]

Edit: it appears that I had some kind of problem with my z-wave network. After a reset of the z-wave network all devices configure as they should.

43

Hi,

Some question about this device. I did 2 scenes as suggested, 1 to turn on the light when tripped and 1 to turn off when no motion detected.

However, when I set the sensor to Bypass and like to keep the light manually, after a while, the scene that turns off the light when no motion detected still activates to turn off the light. By right when the sensor is set to bypass mode, it shouldn’t activate any scenes anymore?

Did anyone encounter this and how did you overcome this?

Mike
www.domotics.sg

44

Hi Mike

That should normally not happen. i use several scenes with the device in armed status but in bypass all is OK and not affected.
Probably you still have somewhere in your code (scenes) a trigger or condition that is associated to a sensor in bypass mode?
Please check

45

3 posts back in this thread I first reported that I cannot set the user configuration of the SP814. In order to solve other problems I did a factory reset of the vera and then I was again able to configure the SP814 without any problems. Just set the setting, click configure now and then wake up the sensor.

Now, about two weeks later I cannot set any of the devices anymore. I’m always getting ‘Failed at setting user configuration’. Why is it that I can set the configuration at one time, but not two weeks later?

I rebooted vera, didn’t matter. I excluded one of the sensors and re-included it; it didn’t matter. I don’t feel like trying wether a factory reset of vera would solve the problem again. I don’t know who is to blame here but either the support of vera of this device is not great, or the firmware of my sensors is flaky.

46

Same problem - cant configure it even after 60 attempts.

47

I have solved my configuration problem…

The SP814 tends to stay awake too short to be configured completely and therefore the configuration settings are not set. My solution is to click the ‘configure now’ button and then click the tamper button 3x within 1.5 seconds and then repeat this after 2-3 seconds until the configuration is done.

This way I am able to reliably configure the SP814.

There is a lot of complaining about the availability of IR sensor for Vera, but now I can configure these I am reasonably satisfied with these sensors. They could react a little quicker, sometimes it takes a few seconds to notice me, but they look quite nice and the ceiling and wall mounting option makes it versatile. The battery life is very good I think, more than a year.

48

Actually it is the worst sensor out of three I have. It is too slow and blind.

EZMotion seems the best choice so far.

p.s. After more attempts I was finally able to configure it.

49

For those it may interest I finally found a solution which is always working but require a little bit of LUUP code.
OK it not very user friendly but at least it is working :slight_smile:

First go to “Apps” > “Develop Apps” > “Test Luup code”
and past the following code:

 luup.call_action("urn:micasaverde-com:serviceId:ZWaveNetwork1","SendData",{Node="2", Data="0x70 0x04 0x05 0x01 0x0A"}, 1 )

change it according to your needs…

Node=“2” must be replaced with your Zwave node ID (not the Vera device #ID). You can find it in the device advanced tab ‘altid’ attribute.

0x70 = COMMAND_CLASS_CONFIGURATION (you should keep it as it is)
0x04 = CONFIGURATION_SET (you should keep it as it is)
0x05 = SP814 config parameter 5 (change with your settings)
0x01 = means 1 byte value long (add after this values as many values as you have additional bytes) (change with your settings)
0x0A = value (10 dec) (change with your settings)

Wake up the SP814 device (press 3 times the back button) and then press the GO button just after the red light turn off. It should turn on again for a very short time after you press the GO button.

Go in the device options and check the result by using the read only method (don’t know why but it may take few minutes before the change is correctly reported here)

Note that if you need to set values being more than 1 byte long then you need to take care on the order you put those bytes !!!
For instance if you need to set a value “1” of 2 bytes long then here is the data sequence:

 Data="0x70 0x04 0x05 0x02 0x00 0x01"

One interesting thing with this method is that this LUUP code may also be used in Scenes to change the config parameters of any of your devices.

Hope this can help some of you who are blocked with the default params of the SP814…

50

Is is possible to change the values without pressing the button 3 times?

51

How can i set parameter 6 to 600 (seconds)?

52

like in the attached picture, but for parameter 6.

53

Vera doesnt let me change parameters in SP814 via advanced tab, only with luup code.

54

then try via luup as in the following topic: http://forum.micasaverde.com/index.php?topic=6669.45
the sensor will take the command on the next wake-up or you press the button from the sensor 3 times.

55

How do i put 600 (decimals) to hex(?) for luup code?

56

For value 600, you need 2 bytes:

First convert 600 (dec) to (bin):1001011000
Then split it in 2x8 bits and convert them to HEXA:

00000010 => 0x02
01011000 => 0x58

Don’t forget to specify 2 bytes long (0x02) before the value (0x02 0x58).

57

Thanks! :slight_smile:

58

This is the worse device I ever had. I finished setup after few hours, now I need to change one value but it’s not possible. Tried also with lua. Where is the bug in the device itself or in vera?

59

[quote=“luv4rice, post:23, topic:168419”]I did it… still cannot believe but it’s working now! :slight_smile: :slight_smile: :wink: :wink: :smiley: :smiley: ;D ;D 8) 8) :stuck_out_tongue: :stuck_out_tongue:

So… how to get the parameters set… still not 100% sure but roughly follow these steps:

  • go to the sensor configuration Device Options, add 6 parameters numbers 1 … 6 and set all on ‘default’ as a start (when the choice ‘default’ is selected the value behind is ignored and the device will reset the parameter value back to it’s default value).
  • close the dialog and press the big red ‘save’ on the top right and wait will you see a little green line under the sensor device box ‘waiting for the device to become active’. Then you press 3 times quickly on the tamper switch on the back of the SP814 (3 quick beeps, you have to complete the 3 presses within 1.5 seconds so press fast! triple click)
  • this should succeed, you can now wait till you see the parameters ‘current value’ shown in the sensor’s device option tab.
  • I think there’s some bug or communication with this as well, the parameters do not showup , you either have to wait a very long time or you have to be lucky to do a ‘poll’ just at the same instance that the device has a wakeup moment. To increase my chances I’ve set the poll interval to 10 seconds and the device wakeup interval to the minimum value of 60 seconds - but even then it took an awful long time before I finally managed to get the ‘current parameters’ (shown the default values of 0,1,6,15,10,15 or similar - whatever you device has as defaults, mine seems to be giving slightly different values from what’s printed in the manual as 0,1,6,5,10,5).
  • now you set all parameters to the values that you wish them to be , and choose the selection ‘1 byte decimal’ (unless you have values > 127 or 255 … not sure, but in that case select ‘2 byte decimal’; anyway this setting does not really seem to matter, probably 4 byte decimal works just as well for all parameters, just make sure that you do not leave the setting on ‘monitor’ or ‘default’ if you want the parameter to change to your preferred setting!).
  • in the advanced tab clear the VariablesGet field to clear the ‘current parameters’ (so that you know when a fresh set is retrieved from the SP814)
  • close the dialog and click on the red save button
  • wait till you see the ‘waiting for device to be come active’ message and triple click the tamper switch on the SP814.
  • most likey you now get a red error message ‘configuration failed’, don’t panic, just keep trying till you drop ;-0
  • I went to the ‘settings tab’ and clicked ‘configure node right now’, then when the green text under the sensor box showed some activity I quickly pressed 3x on the tamper switch
  • I clicked on poll now , then quickly 3x tamper switch, then on the big ‘Reload’ button on the top, waiting to get a fresh set of ‘current values’
  • in most cases after several ‘poll’, ‘reload’, ‘configure now’, triple clicks of the tamper switch I eventually got a new set of ‘current parameter’ values and what suprised me that some of the parameters were actually set correctly. In my last attempt 3 out of 4 parameters that I changed did actually change.
  • I continued for another 45 minutes trying to get the 4th parameter corrected: change the value in the Device Options tab a little bit (e.g. +1), then save the settings and when ‘waiting for device to become active’ 3x click tamper switch
  • if you get an error again, change the value again +1 or now -1 and repeat the process
  • keep repeating those steps till at some point no error is shown

MCV - please please investigate what is going on here and if you can improve something in Vera/Vera Lite/UI5 to make this process easier or if you can fully blame Everspring for the problems (but now I’m not so sure about that anymore, the device seems to work perfectly well on all its functions once the parameters are set).

Ok let me tell you what I discovered on the ‘functionaly’ of this device (which I finally could test properly after having the parameters set to some decent values :-):

  • the device has 2 association groups: group 1 is intended to communicate with the controller, max 1 node; it’ll send reports of ‘presence’ and ‘battery’ to the vera controller at any time and completely ignores the ‘lux sensitivity’ setting (i.e. it’ll report movements no matter if it’s light or dark in the room - this is the ‘alarm’ scenario where you want to get notified of a break in day time and night time; it makes sense).

For this group the parameters 2 (enable/disable), 3 (sensitivity), 4 (retrigger interval) all work just fine. However parameter 5 (lux level) and 6 (on-off duration) are completely ignored for reports in this group.

Group 2 can be used to associate up to 3 other zwave devices directly, i.e. control a light switch and a sirene fully autonomously (without the need for 'scene’s and the vera controller). The SP814 will directly send a value of ‘BASIC Set Level’ (parameter 1) to each device in group 2. You can perform those associations from the Device options tab by entering Group Id ‘2’ and then press the add group button and choose the ‘Set’ button.

Now the special magic: the devices associated in Group 2 will only be triggered when the ‘Lux Level’ is met, i.e. when it is dark enough in your room (dark below the level set, i.e. I set Lux Level=3 , which means 3% of fully bright dayligth and with that setting the associated light switch only switched on the light when all my lights in the living room were switched off, with some lights switched on the lamp switch was not activated).

I haven’t fully tested yet (as I’m not too interested in those group 2 associations yet), but I assume that the On-Off duration also only applies to the devices associated in Group 2; i.e. if you set it to 300 your associated lamp switch will remain on for 5 minutes after being triggered, then switch off. The green led will blink after 15 seconds of the interval to indicate that the associated devices group is still active… as I understand it. Not sure it’ll keep blinking every 15 seconds thereafter or just once.

LR[/quote]

Great help. After struggling several days I was able to configure all I wanted:
Parameters 5 and 6 (it takes some time until the real value is visible in Vera, but it is in effect immediately after configuration)
Assosication with my switch (indeed light level is important to change if you do it during the day).

THANKS !

60

1yr later, I am hit with this issue. Just got this motion sensor.

Manage to get all parameters in wan in but…see attachment, I like to change device association. Instead of devices 16,39. It keeps going back to the 14, 39 devices that was set previously by me…Agrhhh…For the parameters, the solution provided earlier works for me so I used the same method, remove from advance tab, “Getassociation” but method didn’t seem to work for association…Whyyyy…Errr…Anyone?