Everspring door/window sensor not behaving - event problem?

[hari]

I was wondering how the dongle knows that a device is sending data?  In a polling situation the controller would talk to each device in turn and the devices would not talk to the controller unless they are queried. A process in a computer would use a hardware or software interrupt to gain the attention of the cpu. In the situation where the device is sleeping and wakes up after an event how does the device get the attention of the controller without being stepped on during the polling process? 

read this:

http://www.eilhk.com/en/product/Datasheet/Zensys/SDS10243-2%20-%20Z-Wave%20Protocol%20Overview.pdf

[hari]

and this: http://www.eilhk.com/en/product/Datasheet/Zensys/INS10244-3%20-%20Z-Wave%20Node%20Type%20Overview%20and%20Network%20Installation%20Guide.pdf

[mythtified]

So the Seluxit is your recommendation for a controller then or do you like something else?

I use a seluxit as static controller on the LinuxMCE core and really recommend it.

br Hari

I did not see a US version of that controller.  I did order a US version of the Tricklestar though.  Thx for the other info by the way.

[purps]

you need to put the dongle's node id into the association group 1 of the everspring sensor.  From the manual:
"The Door/Window Detector supports one association group with five nodes. This has the effect that when the Detector trigger, all devices associated with Detector will be operated."

so please RTFM: http://wiki.linuxmce.org/index.php/Everspring_SP103#Association
then send a "Set Association" command to the ZWave device, with the following parameters:
#239 - the node ID of your everspring sensor (can be seen in the port/channel field)
#249 - group number, this is 1 for this device
#250 - the node id of your dongle, probably 1 when you are using the crap dongle with the inclusion button

Hari

Still not having any luck. I've just had to reinstall (with snapshot 23388) as my hard disk went down, and now I cannot even make the tamper switch set off the alarm like I could before, and certainly not with the magnet. I've tried it both with and without your instructions.

Any known problems with this snapshot? I think I'm going to see about getting a replacement sensor, this behavior seems very strange to me.

I still don't understand how the tamper switch can trip the alarm, but the magnet does not. Surely this means that the Z-wave/LMCE side is set up correctly?! Oh I dunno.

[mythtified]

I know that I played with mine for quite a while before I put it into service as I had trouble getting it to work.  I cannot say now what I might have done to get it to work.  Turn on extended logging and watch the zwave log while you trigger it with the magnet.

[valent]

Hi Purps I also have everspring SM103 door sensor and today I'll play with it to see if I can get it to work. We will be in touch and hopefully will get it to work.

As soon as we get it to work I could write down (but help is also appreciated) all instructions on SM103 WIKI page.

Everspring security modules have some of the worst instruction manuals that I have ever seen. Others manufacturers have lots of examples how you use and setup their devices, but Everspring fails in that regard.

[purps]

Thanks, sounds good. I will happily help out with any documentation once we get it up and working.

To be honest I am thinking of splashing out on a Seluxit effort and an inclusion remote (which inclusion remote is best for LMCE?) in the new year, as I can see my Z-wave networking becoming somewhat large, and reliability/ease of setup is very important to me.

Regarding the manual (yes it is crap); what do you make of the part that talks about the wiring setup? Did I interpret it correctly, in that you can use this method to rig more than one window with only one sensor? Here (page 2, point 7) http://www.techstyleuk.co.uk/index_files/sm103_manual.pdf

Cheers,
Matt.

[mythtified]

Get the Seluxit.  I got the Tricklestar and was able to add the door sensor with no trouble.  It was surprising how well it worked.  I paired it with the controller.  The core restarted a couple of times and it was done.

[valent]

Regarding the manual (yes it is crap); what do you make of the part that talks about the wiring setup? Did I interpret it correctly, in that you can use this method to rig more than one window with only one sensor? Here (page 2, point 7) http://www.techstyleuk.co.uk/index_files/sm103_manual.pdf

Cheers,
Matt.

Let's first make it work with LinuxMCE after I'll experiment with other features but I think it can control multiple windows/doors with that external switch/sensor.

Cheers,
Valent.

[valent]

I'm going to buy Seluxit ZWave controller but until it gets here all I have to work with is Aeon labs ZWave usb controller.

I associated SP103 and SM103 security sensors with Aeon labs stick and after plugging it back in into Core they got recognized and I edited descriptions via webadmin UI.

Even if I choose in which room each device is in next time I plugged in Aeon Labs wizard popped up and said that both security devices are not assigned to any room so I choose rooms again via video wizard.

http://wiki.linuxmce.org/index.php/Everspring_SM103:
http://dl.dropbox.com/u/184632/door_01.png
http://dl.dropbox.com/u/184632/door_02.png

http://wiki.linuxmce.org/index.php/Everspring_SP103:
http://dl.dropbox.com/u/184632/motion_01.png
http://dl.dropbox.com/u/184632/motion_02.png

After editing "PK_FloorplanObjectType" and adding "door" as object type sensor moved outside zwave device tree

What is going on? What should I do? Delete all devices and start over? Report bugs? Any other suggestions?

Cheers,
Valent.

[valent]

Ok, deleted rogue device, removed and plugged aeon labs stick back in and now I got generic device back:
http://dl.dropbox.com/u/184632/generic_01.png
http://dl.dropbox.com/u/184632/generic_02.png

This looks ok, right?

[hari]

please do not use the wizard, it is broken at the moment.

br Hari

[valent]

you need to put the dongle's node id into the association group 1 of the everspring sensor.  From the manual:
"The Door/Window Detector supports one association group with five nodes. This has the effect that when the Detector trigger, all devices associated with Detector will be operated."

so please RTFM: http://wiki.linuxmce.org/index.php/Everspring_SP103#Association
then send a "Set Association" command to the ZWave device, with the following parameters:
#239 - the node ID of your everspring sensor (can be seen in the port/channel field)
#249 - group number, this is 1 for this device
#250 - the node id of your dongle, probably 1 when you are using the crap dongle with the inclusion button

Hari

I have done inclusion and association, but how to check and where that I did association correctly? Is there a way to list which device is associated with Aeon labs dongle?

#239 - channel for motion sensor is 7 and for door sensor 8
#249 - group is 1
#250 - aeon labs controller channel is 1

UPDATE: I got both SP103 (motion sensor) and SM103 (door sensor) to work and send trigger events!

Caveat #1: Motion sensor and led light
When I first turned on SP103 motion sensor whenever it's motion sensor was tripped red led light turned on, so it was an really easy to understand visual cue that device was working. After including motion sensor to my LinuxMCE via Aeon labs ZWave stick there was no led flashing when motion sensors was being tripped so I thought that motion sensor wasn't working and wasn't sending any alarm info to lmce, but it was. I just didn't know where to look and how to check if it was working ok or not. Now I know that all I need to do is look in webadmin Security > Status
After I done inclusion and association motion sensor showed tripping (motion detected) in webadmin Security > Status page.

Caveat #2: Door sensor needs convincing
Even after I got motion sensor to work my other sensor (door sensor SM103) didn't report any activity in Security > Status page. I tried triggering tamper switch, openning and closing doors, leaving door open, etc... but no activity showed in lmce webadmin page
Only after I deleted device from lmce, excluded it from my zwave network and repeated inclusion and association process I got it to work! First difference I saw was that now door sensor isn't using channel 8 anymore but that it is now on channel 10. And now everything works. When I open the door lmce gets signal immediately that door sensor is tripped.

I'm really, really happy that I got these sensors to work and now I can finally go do some more exciting stuff with programming lmce and making my flat smarter.

[purps]

you need to put the dongle's node id into the association group 1 of the everspring sensor.  From the manual:
"The Door/Window Detector supports one association group with five nodes. This has the effect that when the Detector trigger, all devices associated with Detector will be operated."

so please RTFM: http://wiki.linuxmce.org/index.php/Everspring_SP103#Association
then send a "Set Association" command to the ZWave device, with the following parameters:
#239 - the node ID of your everspring sensor (can be seen in the port/channel field)
#249 - group number, this is 1 for this device
#250 - the node id of your dongle, probably 1 when you are using the crap dongle with the inclusion button

Hari

Hari, if you wouldn't mind advising me please, is what you've said still necessary with the Seluxit viaSENS and Aeon Labs Minimote?

I'm all set up, I included the door/window sensor with the Minimote... and I see exactly the same behaviour as last time, which is:

"The sensor works perfectly when I pick it up off the table (i.e. the tamper switch), but I am getting no response from it when I move the magnet away."

Any help would be much appreciated.

Cheers,
Matt.

[valent]

I have only AeonLabs USB stick, currently no remote so I can't help you in that regard, but I would almost 100% bet that you bought a faulty device and need to replace it for a new one.