This page last changed on Jul 21, 2013 by moonf4.

Has anyone added/setup a Schlage RS200HC Motion Sensor (or similar) to their openremote installation? I am looking for the proper way to setup the sensor. I am not clear on the whole Command - Type - Custom sensor setup.

Found this comment in an Amazon review. Not sure if it is relevant or not.

The RS200HC works great with System xxx... After pairing, you'll see four new devices: Root, Power Management Alarm, Battery, and Binary Switch. The device is manufactured by Ecolink, runs ZDK version 4.54, and supports classes SENSOR BINARY, ALARM, MANUFACTURER SPECIFIC, VERSION, ASSOCIATION V2, WAKE UP, BATTERY, and CONFIGURATION V2.

Thanks,

M-

Are you using the native OR ZWave implementation or RazBerry or something else?
In general you can define PIR sensors with a status command and a switch sensor.

Posted by mredeker at Jul 22, 2013 08:58

Sorry, forgot to add the implementation details. I am running Openremote 2.1.0 on a Raspberry Pi with a Aeotec Z-Stick Series 2. From what I can tell all seems good with the install. (Very good instructions btw ) Openremote starts up cleanly and I see Node ID's 1 & 2 in the zwave-debug log.

Thanks for the reply. I'll double check the command and sensor I defined and do some more testing/troubleshooting.

Posted by moonf4 at Jul 22, 2013 16:23

Let us know how it goes. Always useful to have community report back on new and successfully integrated devices.

Posted by juha at Jul 23, 2013 11:24

No luck with getting any info from the motion sensor. All the sensors I have tried to setup show N/A on the Panel.

I have done some research which is clearing up bits and pieces, but I am still unclear on most of it. This motion sensor is battery operated, so I take it that it goes to sleep and wakes up every 60 seconds or something like that.

I removed all the sensors/commands from the Panel to get back to the beginning.

Can someone help me interpret the info I see in the debug-log? Obviously, there is Node ID 1 & 2, but doesn't "Sending: 06" mean there is a Node ID 6 ? Does one of the bytes in the received message indicate which Node ID it was sent from?

DEBUG 2013-07-27 14:18:49,295 (Z-Wave): Node id: 1 discovered
DEBUG 2013-07-27 14:18:49,297 (Z-Wave): Node id: 2 discovered
DEBUG 2013-07-27 14:18:49,303 (Z-Wave): sending: 01 04 00 41 01 bb
DEBUG 2013-07-27 14:18:49,312 (Z-Wave): Message lock exists. Frame waiting: 01 04 00 41 02 b8
DEBUG 2013-07-27 14:18:49,316 (Z-Wave): received: 06 01 09 01 41 92 16 00 02 02 01 33
DEBUG 2013-07-27 14:18:49,365 (Z-Wave): sending: 06
DEBUG 2013-07-27 14:18:49,369 (Z-Wave): sending: 01 04 00 41 02 b8
DEBUG 2013-07-27 14:18:49,377 (Z-Wave): received: 06 01 09 01 41 53 9c 00 04 20 01 5c
DEBUG 2013-07-27 14:18:49,383 (Z-Wave): sending: 06
DEBUG 2013-07-27 14:18:49,404 (Z-Wave): Node: 2 created, Type: BinarySensor, Listening: false
DEBUG 2013-07-27 14:41:01,900 (Z-Wave): received: 01 09 00 04 04 02 03 30 03 ff 3b
DEBUG 2013-07-27 14:41:01,903 (Z-Wave): sending: 06
DEBUG 2013-07-27 14:45:11,277 (Z-Wave): received: 01 09 00 04 04 02 03 30 03 00 c4
DEBUG 2013-07-27 14:45:11,280 (Z-Wave): sending: 06
DEBUG 2013-07-27 16:02:09,912 (Z-Wave): received: 01 09 00 04 04 02 03 30 03 ff 3b
DEBUG 2013-07-27 16:02:09,915 (Z-Wave): sending: 06
DEBUG 2013-07-27 16:05:20,658 (Z-Wave): received: 01 09 00 04 04 02 03 30 03 00 c4
DEBUG 2013-07-27 16:05:20,662 (Z-Wave): sending: 06
DEBUG 2013-07-27 17:13:55,205 (Z-Wave): received: 01 08 00 04 04 02 02 84 07 74
DEBUG 2013-07-27 17:13:55,208 (Z-Wave): sending: 06
DEBUG 2013-07-27 17:13:55,211 (Z-Wave): I am awake: 2
DEBUG 2013-07-27 17:13:55,213 (Z-Wave): Sending device back to sleep. Id: 2
DEBUG 2013-07-27 17:13:55,217 (Z-Wave): sending: 01 09 00 13 02 02 84 08 05 00 6c
DEBUG 2013-07-27 17:13:55,224 (Z-Wave): received: 06 01 04 01 13 01 e8
DEBUG 2013-07-27 17:13:55,227 (Z-Wave): sending: 06
DEBUG 2013-07-27 17:14:35,172 (Z-Wave): received: 01 09 00 04 04 02 03 30 03 ff 3b
DEBUG 2013-07-27 17:14:35,176 (Z-Wave): sending: 06
DEBUG 2013-07-27 17:17:46,479 (Z-Wave): received: 01 09 00 04 04 02 03 30 03 00 c4
DEBUG 2013-07-27 17:17:46,482 (Z-Wave): sending: 06
DEBUG 2013-07-27 17:18:37,326 (Z-Wave): received: 01 09 00 04 04 02 03 30 03 ff 3b
DEBUG 2013-07-27 17:18:37,330 (Z-Wave): sending: 06
DEBUG 2013-07-27 17:22:02,600 (Z-Wave): received: 01 09 00 04 04 02 03 30 03 00 c4
DEBUG 2013-07-27 17:22:02,604 (Z-Wave): sending: 06
DEBUG 2013-07-27 17:25:53,348 (Z-Wave): received: 01 09 00 04 04 02 03 30 03 ff 3b
DEBUG 2013-07-27 17:25:53,351 (Z-Wave): sending: 06
DEBUG 2013-07-27 17:29:04,853 (Z-Wave): received: 01 09 00 04 04 02 03 30 03 00 c4
DEBUG 2013-07-27 17:29:04,856 (Z-Wave): sending: 06
DEBUG 2013-07-27 19:23:41,198 (Z-Wave): received: 01 09 00 04 04 02 03 30 03 ff 3b
DEBUG 2013-07-27 19:23:41,202 (Z-Wave): sending: 06
DEBUG 2013-07-27 19:30:25,198 (Z-Wave): received: 01 09 00 04 04 02 03 30 03 00 c4
DEBUG 2013-07-27 19:30:25,201 (Z-Wave): sending: 06
DEBUG 2013-07-27 19:47:32,905 (Z-Wave): received: 01 09 00 04 04 02 03 30 03 ff 3b
DEBUG 2013-07-27 19:47:32,909 (Z-Wave): sending: 06
DEBUG 2013-07-27 19:50:45,796 (Z-Wave): received: 01 09 00 04 04 02 03 30 03 00 c4
DEBUG 2013-07-27 19:50:45,799 (Z-Wave): sending: 06

Posted by moonf4 at Jul 28, 2013 05:35

Hi Michael,

Thinks the 06 might be an ACK to the received frame, not a device id.

Posted by juha at Jul 28, 2013 08:56

The received messages are coming from node 2 (the sixth byte)

Posted by juha at Jul 28, 2013 09:25

It's receiving the payload from your binary sensor in node 2 which should translate to 'true' if the z-wave command is mapped to a 'switch' sensor in the Designer UI.

For some reason it doesn't seem to support 'custom' sensors in the designer.

Posted by juha at Jul 28, 2013 09:39

Thanks Juha, that was it. I was using a custom sensor. I setup a switch sensor and now the motion sensor is now reporting correctly to the panel.

Now to start reading up on how / if there is a way to send a text alert...

Thanks again!

Posted by moonf4 at Jul 28, 2013 18:45

Will look at extending the motion sensor to work with custom sensor as well, would appreciate if you could test the implementation.

Posted by juha at Jul 28, 2013 22:39

You got it. When you get to that point, just let me know.

Posted by moonf4 at Jul 28, 2013 23:08

Michael,

There's a new test version available at http://download.openremote.org/free/zwave/1.1/beta1

This version supports binding a 'custom' sensor to Z-wave binary sensors. It also adds an option to set distinct levels to DIM commands, e.g. 'DIM 25' to configure a command to dim lights to the specified level.

Would appreciate if you could test this release candidate.

Save the download to your controller's /webapps/controller/WEB-INF/lib directory by overwriting the existing zwave.jar file that is there.

Let us know if you find issues.

Best regards,

– Juha

Posted by juha at Aug 02, 2013 15:59

Juha,

The custom sensor appears to work fine. It reports as "on" or "off". Didn't appear to be a way to customize the Sensor State On or Off text in the UI, but I imagine that is step 2.

Mike

Posted by moonf4 at Aug 03, 2013 17:05

Hi Mike,

Thanks for verifying the fix. See the documentation on custom sensors here: Designer 2.0 - Create Custom Sensor. If the description at the bottom is correct, there's something odd with the implementation. Will check it once I get to applying the current set of overdue patches on the designer.

– Juha

Posted by juha at Aug 05, 2013 10:17

I am responsible for the last textual revision of that Custom Sensor description. I did test it with ORC 1.07. For a binary switch it is critical that the values in the Name column are on or off in lower case without any quotes in the string.
I perceive the Custom State item interface a bit counter intuitive. I would swap the colums, and change Name into Map to

Posted by pz1 at Aug 05, 2013 11:33

Yes, mapping is also the terminology used in the controller code for state sensors. Should update designer to reflect this.

Posted by juha at Aug 05, 2013 12:20

My mistake. Looking at my Switch Sensor, I created the Custom Sensor with only the status command. I added the Custom state items and now I see I can edit the sensor state text normally.

Posted by moonf4 at Aug 05, 2013 15:13

Hey Guys well i think that most motion sensors are battery power and don't require a immediate power However it is very important to make sure that battery power are always examined and changed often.Thanks!!

cross bridge load cells

Posted by markspend01 at Aug 21, 2013 19:57
Document generated by Confluence on Jun 05, 2016 09:41