Hello,
I can’t seem to get the Hawking HomeRemote HRDS1 Door/Window ZWave Sensor to work with Vera. Does anyone else have any experience with these sensors?
Rich
Hawking’s sensors seem to be still in work
http://forum.micasaverde.com/index.php?topic=8.msg1014#msg1014
they don’t support sensor or alarm mode, only basic, but are pretty fine otherwise. I see no reason why they should not work with one of the next updates.
best regards,
Hari
OK. I still think we need some kind of window and/or door switch available that works with Vera. I looked on the shopping page and of all the products there isn’t anything that does this simple task.
I just got my Hawking sensors, and our programmer is working on them right now. Look for a new firmware in a couple days that supports them.
Hawking door/window sensor works like a charm with latest 404 firmware.
Nice to know, what’s left is to find a good deal on 'em 
So far no luck…
Unfortunately, MCV don’t have them in their shop.
The cheapest I could find was at ASIHome.
36 bucks is a real good price from ASIHome! ;D
Anyone know if there is something similar with European frequency?
yes, they are available as EU model, too.
br, Hari
Do you know where to get them?
I am impressed with how well the HRDS1 was to get working with Vera. Quick setup and fast reaction time. The latency from tripping the sensor to light on is 1-2 seconds.
As I wanted to use the sensor for a wardrobe, the light should go off when I close the door. Can Vera & HRDS1 be programmed to create a scene for that? In other words, is HRDS1 sending out a zwave signal when the door is closed, and how would Vera know?
UPDATE: I noticed that the HRDS1 sensor seems to be sending a zwave signal when it is closed, as well as when it opens. In Vera’s logs http://192.168.1.4:3451/data_request?id=zwave_status it states “<TRIPPED=YES>” or “<TRIPPED=NO>” depending of the position of the sensor. This update happens within a second or so.
Nancker you have to add an “A sensor () is tripped” event and choose the sensor goes idle after being tripped. And at commands choose Turn OFF light.
That is precisely what I tried. I re-tried it now again, and it still does not work. From the zwave logs I see that Vera indeed does recognize the instant the door is closed, but now after several minutes of waiting, the light in the wardrobe is still on.
Have other experimented with this?
How can I see if Vera recognized the events? If some of you have worked with HomeSeer, you will know what kind of logging I am looking for to help figure out what is wrong.
The best way to see what events are being fired is to log in and do this:
tail -f /var/log/cmh/DCERouter | grep ‘^07|^08|Event_Plugin::ProcessEvent’
Log entries 7 and 8 are commands and events. You will only see the entries for ‘Event_Plugin::ProcessEvent’ if you turn on verbose logging (advanced, logs), however, note that the logs will probably rotate every 15 minutes or so because Vera is just using a small ram drive. Log entries 7 and 8 will show what events are fired, and you will see the entry ProcessEvent for every event that has a corresponding event handler (ie add event in the scene), and it will say ‘Evaluated … to: [0|1]’. If it’s 1, that means the event was ‘tripped’ and it executed the scene (you’ll see the commands for the scene).
If you want to look at the logs for the Z-Wave module and see what internal events it has received, do:
tail -f /var/log/cmh/9-ZWave.log | grep ‘^07’
That follows the logs and shows new entries. To check previous data in the logs, change the syntax in both cases to be grep [expression] file, like:
grep ‘^07|^08|Event_Plugin::ProcessEvent’ /var/log/cmh/DCERouter
Sweet!
It would be even better to have this accessible in a HTML page, similar to the zwave log page. It will save a bit of time logging in and typing…
Having said that, I can get much further knowing what I know now - thanks!