Everspring door/window sensor not behaving - event problem?

[purps]

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

[valent]

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.

[purps]

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.

[hari]

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

[purps]

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.

[purps]

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.

[purps]

Sorry guys going to have to bump this, I can't work out what's happening.

[hari]

fixed