I did it… still cannot believe but it’s working now! 
;D ;D 8) 8) 
For the past 3 hours I’ve been repeating the same steps over and over again and I cannot tell what /how/which timing exactly did it but the bottom line is: persevere and it is possible to set all 6 parameters of the SP814…
This must be either a bug in Vera Lite/UI5 or a sever communication problem between the everspring SP814 and vera/controller (maybe there is some issue with setting configuration parameters that the battery operated device only comes online very very briefly and the time window is too short to set all parameters correctly…? it does in the end seem to be random and after many tries I managed to get all parameters just the way I want them - and my battery is now showing 90% after all communication & resetting activity).
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
