LinuxMCE Forums

General => Users => Topic started by: purps on November 23, 2010, 12:14:18 pm

Title: Everspring door/window sensor not behaving - event problem?
Post by: purps on November 23, 2010, 12:14:18 pm
Having a bit of a problem getting this sensor working, any thoughts/pointers would be welcome.

I tried to add it with the wizard in the normal manner to begin with (as I did with my dimmer switch), but I got some very strange behaviour. It allowed to say what it was and where it was, but when it came to naming it, there was no "next" button! No matter, I cancelled the wizard, and had a look in web admin, which was where I got more confused...

It seemed to have added TWO "Generic Sensors" to CORE -> ZWave -> ZWave Embedded Security Interface, using the device template "Xine Plug-in #6". Now I'm no expert, but that doesn't seem right.

Is my controller to blame? I've got the Aeon Labs stick. I realise that the Seluxit is usually recommended over this device, but it's what I've got, and was all I could afford at the time. I could probably stretch to the Seluxit now if NOT having it is a complete show-stopper, but obviously I would like to try and get it all working with what I've got if it's possible.

Is there a procedure I can follow to add it manually? I tried to follow this http://wiki.linuxmce.org/index.php/ACT_Homepro_Motion_Detector and this http://forum.linuxmce.org/index.php?topic=9606.0, but to be honest I am struggling to understand some of the terms being used.

Cheers,
Matt.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: mythtified on November 23, 2010, 01:29:32 pm
I ran into a similar problem with a Hawking Door/window sensor that appears to be a version of the everspring.  The post for the fix is here.  http://forum.linuxmce.org/index.php?topic=10810.0 (http://forum.linuxmce.org/index.php?topic=10810.0)  You will smack yourself in the forehead when you see how easy it is to fix. ;D
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: purps on November 23, 2010, 02:46:05 pm
Thanks man, sorry, I didn't see that post during my searches. I'll give it a go when I get home tonight.

Am I right in saying that when one wants to add any new Z-wave device, all of the pre-existing Z-wave devices have to removed and added again along with the new one?

Cheers,
Matt.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: mythtified on November 23, 2010, 08:58:59 pm
While I don't know exactly how it works I do not believe that to be a true statement.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: totallymaxed on November 23, 2010, 11:11:55 pm
Thanks man, sorry, I didn't see that post during my searches. I'll give it a go when I get home tonight.

Am I right in saying that when one wants to add any new Z-wave device, all of the pre-existing Z-wave devices have to removed and added again along with the new one?

Cheers,
Matt.

Hi Matt,

Yes thats was true if you used the lighting Wizard to add ZWave lights for example. However if you have ZWave devices that are compatible with the new SIS Mode then you can add/remove devices with complete flexibility without this limitation.

See the wiki for more information on ZWave; http://wiki.linuxmce.org/index.php/ZWave (http://wiki.linuxmce.org/index.php/ZWave)

All the best


Andrew
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: purps on November 24, 2010, 12:13:31 am
OK thanks, that's good to know.

Every time I plug in the dongle it adds 2 lights and about 6 generic sensors (I have one dimmer and one door/window sensor at the moment). I have completely removed the Z-wave component from "My devices" (along with everything else that is Z-wave related of course) in order to start afresh, but when I plug the dongle back in, there are the 2 lights and 6-odd sensors waiting for me again!!

Does anybody know of a way to restore the Aeon Labs Z stick back to factory settings? The manual states that this must be done through the host software whilst the stick is in SerialAPI-mode. Can LMCE do it?

Cheers,
Matt.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: purps on November 24, 2010, 12:44:33 am
OK, so I found the itsby bitsy teeny weeny reset button on the Z-stick... held it down for a pretty long time... and still the various lights/sensors pop up when I plug it back into the core  :(
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: mythtified on November 24, 2010, 02:05:10 am
I did reset my micasverde dongle once by accident removed everything from the dongle.  I believe I went to the advanced page of the interface and selected send a command to device.  Clicked the drop down and selected reset.  Then clicked the send button.  I believe that removed all the devices from the dongle.  I could be remembering wrong because it has been a while since I did it
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: hari on November 24, 2010, 11:51:48 pm
purps: send a "reset" from the web admin (not a dce reset but a reset command to the z-wave dongle itself)

It will erase all network information stored in the dongle and you can re-create your z-wave network.

br Hari

btw, I never use the wizard, it is broken.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: purps on November 25, 2010, 12:33:55 am
Thanks chaps, with your advices I've managed to factory reset the Z-stick, and have added the generic sensor, assigned a room, icon, etc.

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. Have any of you guys seen this before?

In case it's relevant...

(http://i687.photobucket.com/albums/vv234/purpss/sensor1.png)
(http://i687.photobucket.com/albums/vv234/purpss/sensor2.png)
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: hari on November 25, 2010, 11:53:35 am
 what do you mean with no response? When you are referring to the led, that is normal behavior to save power.

I have the same unit installed here, works fine, you just need to make sure that the dongle is associated to group 1.

br Hari
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: purps on November 25, 2010, 02:36:01 pm
What I mean is that when I set the alarm from an orbiter, if I pick up the sensor from the table, the alarm sounds (due to the tamper switch), so that's fine and working as it should.

However, if I set the alarm, but separate the two parts of the sensor (simulating the opening of a door), the alarm does NOT sound.

For the dongle, the "Port/Channel number" is set to "1", is this what you are referring to? Or is the group thing different?

Cheers,
Matt.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: mythtified on November 25, 2010, 03:08:03 pm
if you leave the tamper switch enabled you can treat the led as a walk/test indicator.  With the sensor in your hand bringing the magnet close and away should cause the led to light.  I also found that the magnet supplied with the sensor is almost worthless.  I am using a larger bar magnet in order to make it work.  You could also adjust the pluto.conf file to increase the loglevel and see if it is operating in the zwave interface log.  One other thing I noticed when initially playing with it is there seemed to be some delay between activations.  This is probably due to device polling but I am not sure.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: hari on November 25, 2010, 03:33:23 pm
no polling involved, it sends a report to the associated node in group 1 (that should be your dongle)..

br Hari
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: purps on November 25, 2010, 04:17:42 pm
if you leave the tamper switch enabled you can treat the led as a walk/test indicator.  With the sensor in your hand bringing the magnet close and away should cause the led to light.  I also found that the magnet supplied with the sensor is almost worthless.  I am using a larger bar magnet in order to make it work.  You could also adjust the pluto.conf file to increase the loglevel and see if it is operating in the zwave interface log.  One other thing I noticed when initially playing with it is there seemed to be some delay between activations.  This is probably due to device polling but I am not sure.

Talking about the tamper switch, by "enabled", do you mean "popped out"?

Logically, I would have thought that if the tamper switch activates the alarm, then all of the Z-wave/LinuxMCE setup is complete, and does not require any further tinkering. Is that a fair comment?

Maybe it is the strength of the magnet as you say, I will have a play tonight. I can definitely hear a faint *click* when I move the magnet close and then move it away again, so something is happening. The sensor could just be shagged for all I know.

Thanks for the info guys.

Cheers,
Matt.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: mythtified on November 25, 2010, 08:07:12 pm
no polling involved, it sends a report to the associated node in group 1 (that should be your dongle)..

br Hari

I thought that zwave devices were polled.  So they can send data without being asked for it first?  I have to do some reading.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: purps on November 25, 2010, 11:13:50 pm
No joy.

mythtified, I've tested the sensor as you've described, and the LED indicates that it is working.

I have tried the sensor with a VERY powerful magnet, and it still does not sound the alarm.

I've reset and re-added everything several times, but still the same problem on every occasion; only the tamper switch sets off the alarm.

Does anybody have any other suggestions please? I simply cannot think of anything else to try.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: hari on November 26, 2010, 12:01:01 pm
no polling involved, it sends a report to the associated node in group 1 (that should be your dongle)..

br Hari

I thought that zwave devices were polled.  So they can send data without being asked for it first?  I have to do some reading.

yes. This is  why you usually set proper associations. You cannot poll a sleeping device (battery powered). Polling is only used to update the status of light switches.

br Hari
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: mythtified on November 26, 2010, 05:52:23 pm
I did some reading yesterday and found out about the battery operated sleeping device cannot be used as a repeater.  So when an event occurs the sleeping device wakes up and sends information to the associated device(dongle)?  With polling going on is it some kind of pseudo interrupt driven mechanism to catch the attention of the dongle?  I saw something about collision avoidance but have not had a chance to read it thoroughly yet.  I found an article on Dr Dobbs site and found a pdf that was marked as confidential.  It is too bad zwave is closed source.  So lmce is using the open source version of the zwave protocol?  Sorry about all the questions.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: hari on November 26, 2010, 08:11:47 pm
I did some reading yesterday and found out about the battery operated sleeping device cannot be used as a repeater.  So when an event occurs the sleeping device wakes up and sends information to the associated device(dongle)? 
correct

Quote
With polling going on is it some kind of pseudo interrupt driven mechanism to catch the attention of the dongle?  I saw something about collision avoidance but have not had a chance to read it thoroughly yet.  I found an article on Dr Dobbs site and found a pdf that was marked as confidential.  It is too bad zwave is closed source.  So LinuxMCE is using the open source version of the zwave protocol?
i don't understand your question.

Br Hari
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: mythtified on November 27, 2010, 02:19:24 am
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? 
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: purps on November 27, 2010, 11:12:50 am
Sorry gents, without wanting to sound like a complete arse, would you two mind having this conversation on another thread please? I'm concerned that people are going to miss my posts regarding the problem I'm having with my door/window sensor (only the tamper switch activates the alarm; moving the magnet away does not).

I appreciate the advice I've been given so far. If you or anybody else has any other thoughts I would be glad to hear them.

Cheers,
Matt.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: hari on November 29, 2010, 07:35:05 am
@Matt: if you did setup the associations properly after inclusion I'd suspect that your unit might be broken.

br Hari
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: purps on November 29, 2010, 10:47:15 am
Define "properly" :)

This is what I did...

Removed the dongle. Placed next to sensor. Pressed the button on the dongle to make the light flash. Pressed tamper switch on sensor three times (dongle blinks more rapidly, then goes back to blinking like normal). Put dongle back in core. Wizard starts, click on cancel. Asked to reload router - yes. Go into webadmin, find generic sensor (child of "z-wave security interface", child of "Zwave"). Change name to "DoorTest", specified a room, and chose the door icon. Have then gone into "Active Sensors" and selected "Security" in dropdown menu for DoorTest under "armed - away".

Then, if I arm the alarm, moving the magnet away from the main part of the sensor does not give a security breach, but as I said before, the tamper switch DOES give a security breach (pretty much instantly), when the sensor is picked up from the table.

Is any more than this required from the point of view of setting up the associations? I would have thought that if the tamper switch is setting off the alarm, then it must be setup correctly?

Cheers,
Matt.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: hari on November 29, 2010, 01:36:50 pm
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
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: mythtified on November 29, 2010, 02:04:34 pm

#250 - the node id of your dongle, probably 1 when you are using the crap dongle with the inclusion button

Hari

Hari, I get the distinct impression that you do not like this dongle.  Could you give me the reason why and your preferences in a private message so as to not to give the appearance of hijacking this thread?

Thx
Larry
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: purps on November 29, 2010, 03:04:17 pm

#250 - the node id of your dongle, probably 1 when you are using the crap dongle with the inclusion button

Hari

Hari, I get the distinct impression that you do not like this dongle.  Could you give me the reason why and your preferences in a private message so as to not to give the appearance of hijacking this thread?

Thx
Larry

I believe it is because it lacks SIS mode (whatever that is!) which means these associations have to be done manually. Apparently the antenna design is inferior to the Seluxit also.

Thank you for the advice Hari, I have been having trouble grasping the node/group business, but your post does make it a bit clearer. Should've bought the Seluxit ;) Trouble is one can RTFM, but still have no idea what is relevant! Will report back, thanks again.

Cheers,
Purps.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: hari on November 29, 2010, 04:26:01 pm
I believe it is because it lacks SIS mode (whatever that is!) which means these associations have to be done manually. Apparently the antenna design is inferior to the Seluxit also.
correct.

SIS mode is very nice, as you are doing the inclusion of a new node with an inclusion controller. The dongle stays connected to the core that way. The inclusion controller will ask the node id server (read; our core with the connected dongle and LinuxMCE running) for a new node id and will do the inclusion on behalf of the node id server (SIS). The really cool thing with that is that we'll receive a network change information frame on the LinuxMCE side as soon as the device is included. Even battery powered devices are powered up while the inclusion takes place. So this is just the right point in time to do basic configuration (like the wake up configuration for the wake up command class used by nearly all battery powered devices). Some devices like the Danfoss RA-PLUS-w thermostat even requires SIS mode.
That dongle with the inclusion button is nice when you only want to add a few simple devices like lamps. But things get hard when you want to use more advanced z-wave stuff.

br Hari
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: mythtified on November 29, 2010, 07:24:20 pm
So the Seluxit is your recommendation for a controller then or do you like something else?
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: hari on November 29, 2010, 07:27:18 pm
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 lmce core and really recommend it.

br Hari
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: hari on December 01, 2010, 01:10:58 pm
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
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: hari on December 01, 2010, 01:12:25 pm
and this: http://www.eilhk.com/en/product/Datasheet/Zensys/INS10244-3%20-%20Z-Wave%20Node%20Type%20Overview%20and%20Network%20Installation%20Guide.pdf
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: mythtified on December 01, 2010, 02:00:00 pm
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.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: purps on December 02, 2010, 01:09:00 am
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.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: mythtified on December 02, 2010, 01:59:41 am
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.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: valent on December 21, 2010, 12:20:01 pm
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.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: purps on December 21, 2010, 12:32:14 pm
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.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: mythtified on December 22, 2010, 11:48:48 pm
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.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: valent on December 24, 2010, 11:16:18 pm
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.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: valent on January 04, 2011, 08:31:30 pm
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.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: valent on January 04, 2011, 08:54:07 pm
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?
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: hari on January 04, 2011, 10:58:41 pm
please do not use the wizard, it is broken at the moment.

br Hari
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: valent on January 06, 2011, 10:03:47 am
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.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: purps on January 14, 2011, 08:47:24 pm
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.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: valent on January 14, 2011, 09:24:59 pm
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.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: purps on January 14, 2011, 10:00:43 pm
I am of the same opinion, but the sensor works in diagnosis mode (i.e. the LED lights up when I move the magnet away), plus I can hear a very faint *click*. Of course it could still be faulty.

Just wondered if I have missed some crucial step. I followed this guide to the letter http://wiki.linuxmce.org/index.php/Z-Wave#SUC.2FSIS_Mode_.28recommended.29
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: valent on January 14, 2011, 11:25:22 pm
Have you checked out my previous post and caveats that I have stumbled across? I have only limited experience but I can suggest you do the same as I did.

1. Unplug ZWave stick
2. Delete ZWave device tree in lmce webui
3. plug in ZWave stick
4. test if now your device shows tripped state when magnet is moved

it that doesn't help then un associate all devices from ZWave usb stick including door sensor.
Then include ONLY the door sensor and send associate command via lmce webui

Check which channel us your door sensor using, I got mine working only after it changed and used a new channel.

Hope this helps.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: purps on January 15, 2011, 02:31:43 pm
I am using the Seluxit controller and Aeon Labs Minimote now, not the Z-stick. I didn't think it would be as much of a frig once I had bought this new hardware.

Do I still need to do the associate stuff with this hardware? I thought this was all done automagically with SIS mode. All I have done is the inclusion, I have not used the "Associate" button on my minimote at all.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: hari on January 15, 2011, 07:00:38 pm
Are you sure that you use SIS mode? The Aeon Labs Minimote needs to be added as inclusion controller. Usually the dongle (Seluxit) should have node id 1 in this case (port/channel in the web admin).

When you include the Door/Window sensor in SIS mode, the Seluxit dongle will receive a network change information together with the node information frame form the new node. This includes the supported command classes, like COMMAND_CLASS_ASSOCIATION. If the association command class is supported, the ZWave DCE device automatically sends the proper commands to the new device to add the dongle node id (usually 1) to association group 1 of the new device.

In your case, when using SIS mode, the everspring sensor should work right after inclusion (and a quick reload of the DCErouter), like it does in my setup (same dongle, same remote and same sensor).

br Hari
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: purps on January 16, 2011, 07:20:40 pm
I can't be sure, but I certainly thought I was in SIS mode. Plugged in the dongle, canceled wizard and sent reset command through web admin (in My devices -> CORE -> Zwave...... "Zwave Controller" has a blank pulldown list under in "send command", so I assume I'm meant to do it through "Zwave").

Checked dongle was on Port/Channel Number "1". Did quick reload. Did a "Send Node", again in My devices -> CORE -> Zwave. Pressed "learn" button on Minimote, second "Zwave controller" appears in My Devices with Port/Channel Number "2". Did quick reload.

I then try to include other devices using the "include" button on the remote. I can include my door/window sensor, but it has the same problem it has always had http://forum.linuxmce.org/index.php?topic=10971.45.

I can't include the Duwi light switch at all. Minimote doesn't pick it up, and it certainly doesn't appear in web admin. I know wizard is broken, but I tried using the wizard for the light as alsol (that always worked when I had the Z-stick with built-in inclusion remote) and it did not work either.

Cheers,
Matt.
Title: Re: Z-wave woes - Everspring door/window sensor not behaving
Post by: purps on January 19, 2011, 11:08:25 am
Quick update on this situation...

Hari very kindly helped me out with getting my Zwave controller and remote sorted, and we managed to add the non-responsive light switch, so I am happy that everything is set up the way it should be on the Zwave side.

However, seeing same problem with the door/window sensor. According to the Zwave logs, moving the magnet away DOES provoke a response, but alas the alarm does not sound. If I pick up the sensor (i.e. activate the tamper switch), the alarm sounds.

Hari has speculated that it could be an events problem, but I have no idea where to go from there. Seeing as the tamper switch sets off the alarm, and the Zwave logs shows the magnet as working, I am really stuck.

Cheers,
Matt.
Title: Re: Everspring door/window sensor not behaving - event problem?
Post by: purps on January 29, 2011, 02:23:47 pm
Sorry guys going to have to bump this, I can't work out what's happening.
Title: Re: Everspring door/window sensor not behaving - event problem?
Post by: hari on January 29, 2011, 11:14:20 pm
fixed