Monoprice Zwave Motion Sensor and Openhab2

Group,

I’m reaching out because I’m only capable of getting the Monoprice PIR motion sensor (Monoprice PIR Sensor) to partially work with OH2. So far I have completed the following steps:

  1. Linked the Motion Sensor to my Aeon Zstick (Gen2 I believe)
  2. Searched for a new Thing via the Paper UI
  3. Added the new Thing (Node10) via the Paper UI
  4. Waited till the binding was able to identify the Thing (Motion Sensor)
  5. Four channels were automatically created and displayed in the Paper UI ( sensor_binary, sensor_temperature, battery-level, alarm_burlar)
  6. I created four items by cutting and pasting the channel info into the curly brackets for item binding (i.e. {channel=“zwave:device:cff9cd9b:node10:sensor_binary”} as I have with the GE dimmer switches. See items below

The Problem
When looking at the Openhab events.log file, after some time, I can see that the battery and temperature are being updated. The issue is the motion and tamper switch are not. Now… When I trigger the tamper switch or the motion sensor I see the following in the events log;

I also see the following in the openhab.log;

Thanks in advance for taking a look at this post. I can provide additional information upon request but may need a little guidance on where to get it. Especially if further logging information is needed. So far I’ve gotten by with the Openhab and events log only.

John

Monoprice PIR Sensor

I think your log is missing the bit we need to see, but is it possible the ‘type’ is wrong, and these missing items should be a Switch and not a Contact?

I will get a better capture of the log.

I should also add that I originally had the items defined as Switches and not Contacts but I changed them after taking a look at the items created in the binding examples (example) for a Monoprice motion sensor. No difference between the two.

The examples are for openHAB 1 installations. In OH2 some item types have changed. You can find the informations here:

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/openhab-2-channel-types

alarm_burglar and sensor binary are both SWITCH.

Please set the log level to DEBUG and post your log. Produce some motion during logging to see the events…

And do not “capture” the log (NO picture). Copy&Paste the log as preformatted text (see the icons above your posting window) or upload it as a file.

Following. I installed one via PaperUI and can confirm it wasn’t working. Went on the bottom of the list to troubleshoot.

Here is a copy of my log file after setting the zwave binding log level to DEBUG. I also changed the item type to Switch as well. The log is showing what comes up after I trigger the tamper switch by opening the case.

openhab> log:display

16:23:04.222 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 11 00 04 00 0A 0B 71 05 07 FF 00 FF 07 03 01 03 00 9E
16:23:04.225 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
16:23:04.226 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 11 00 04 00 0A 0B 71 05 07 FF 00 FF 07 03 01 03 00 9E
16:23:04.226 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 11 00 04 00 0A 0B 71 05 07 FF 00 FF 07 03 01 03 00 9E
16:23:04.226 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0A 0B 71 05 07 FF 00 FF 07 03 01 03 00
16:23:04.226 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 10: Application Command Request (ALIVE:DONE)
16:23:04.226 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Starting initialisation from DONE
16:23:04.226 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@22c2f5ac already registered
16:23:04.226 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 10: Incoming command class ALARM
16:23:04.226 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 10: Received ALARM command V4
16:23:04.226 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 10: Process NOTIFICATION_REPORT V4
16:23:04.226 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 10: NOTIFICATION report - 7 = 255, event=3, status=255
16:23:04.226 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 10: Alarm Type = BURGLAR (7)
16:23:04.227 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
16:23:04.227 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got an event from Z-Wave network: ZWaveAlarmValueEvent
16:23:04.228 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2. {}
java.lang.ClassCastException: org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveAlarmCommandClass$Alarm cannot be cast to java.lang.Integer
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveAlarmCommandClass$ZWaveAlarmValueEvent.getValue(ZWaveAlarmCommandClass.java:587)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveAlarmCommandClass$ZWaveAlarmValueEvent.getValue(ZWaveAlarmCommandClass.java:1)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.ZWaveIncomingEvent(ZWaveThingHandler.java:926)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.notifyEventListeners(ZWaveController.java:546)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveAlarmCommandClass.processNotificationReport(ZWaveAlarmCommandClass.java:196)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveAlarmCommandClass.handleApplicationCommandRequest(ZWaveAlarmCommandClass.java:123)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:119)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:247)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:213)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$7(ZWaveController.java:207)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1303)[188:org.openhab.binding.zwave:2.0.0.201609212035]
16:23:04.229 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_cff9cd9b_serial_sof changed from 4090 to 4091
16:23:04.342 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 11 00 04 00 0A 0B 71 05 07 FF 00 FF 07 03 01 03 00 9E
16:23:04.344 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_cff9cd9b_serial_sof changed from 4091 to 4092
16:23:04.345 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
16:23:04.346 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 11 00 04 00 0A 0B 71 05 07 FF 00 FF 07 03 01 03 00 9E
16:23:04.346 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 11 00 04 00 0A 0B 71 05 07 FF 00 FF 07 03 01 03 00 9E
16:23:04.346 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0A 0B 71 05 07 FF 00 FF 07 03 01 03 00
16:23:04.346 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 10: Application Command Request (ALIVE:DONE)
16:23:04.347 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Starting initialisation from DONE
16:23:04.347 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@22c2f5ac already registered
16:23:04.347 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 10: Incoming command class ALARM
16:23:04.347 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 10: Received ALARM command V4
16:23:04.348 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 10: Process NOTIFICATION_REPORT V4
16:23:04.348 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 10: NOTIFICATION report - 7 = 255, event=3, status=255
16:23:04.348 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 10: Alarm Type = BURGLAR (7)
16:23:04.348 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
16:23:04.348 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got an event from Z-Wave network: ZWaveAlarmValueEvent
16:23:04.348 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2. {}
java.lang.ClassCastException: org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveAlarmCommandClass$Alarm cannot be cast to java.lang.Integer
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveAlarmCommandClass$ZWaveAlarmValueEvent.getValue(ZWaveAlarmCommandClass.java:587)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveAlarmCommandClass$ZWaveAlarmValueEvent.getValue(ZWaveAlarmCommandClass.java:1)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.ZWaveIncomingEvent(ZWaveThingHandler.java:926)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.notifyEventListeners(ZWaveController.java:546)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveAlarmCommandClass.processNotificationReport(ZWaveAlarmCommandClass.java:196)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveAlarmCommandClass.handleApplicationCommandRequest(ZWaveAlarmCommandClass.java:123)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:119)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:247)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:213)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$7(ZWaveController.java:207)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1303)[188:org.openhab.binding.zwave:2.0.0.201609212035]
16:23:10.009 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 11 00 04 00 0A 0B 71 05 07 00 00 FF 07 00 01 03 00 62
16:23:10.011 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_cff9cd9b_serial_sof changed from 4092 to 4093
16:23:10.012 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
16:23:10.013 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 11 00 04 00 0A 0B 71 05 07 00 00 FF 07 00 01 03 00 62
16:23:10.013 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 11 00 04 00 0A 0B 71 05 07 00 00 FF 07 00 01 03 00 62
16:23:10.013 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0A 0B 71 05 07 00 00 FF 07 00 01 03 00
16:23:10.013 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 10: Application Command Request (ALIVE:DONE)
16:23:10.014 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Starting initialisation from DONE
16:23:10.014 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@22c2f5ac already registered
16:23:10.014 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 10: Incoming command class ALARM
16:23:10.014 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 10: Received ALARM command V4
16:23:10.014 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 10: Process NOTIFICATION_REPORT V4
16:23:10.014 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 10: NOTIFICATION report - 7 = 0, event=0, status=255
16:23:10.014 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 10: Alarm Type = BURGLAR (7)
16:23:10.014 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
16:23:10.014 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got an event from Z-Wave network: ZWaveAlarmValueEvent
16:23:10.015 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2. {}
java.lang.ClassCastException: org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveAlarmCommandClass$Alarm cannot be cast to java.lang.Integer
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveAlarmCommandClass$ZWaveAlarmValueEvent.getValue(ZWaveAlarmCommandClass.java:587)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveAlarmCommandClass$ZWaveAlarmValueEvent.getValue(ZWaveAlarmCommandClass.java:1)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.ZWaveIncomingEvent(ZWaveThingHandler.java:926)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.notifyEventListeners(ZWaveController.java:546)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveAlarmCommandClass.processNotificationReport(ZWaveAlarmCommandClass.java:196)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveAlarmCommandClass.handleApplicationCommandRequest(ZWaveAlarmCommandClass.java:123)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:119)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:247)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:213)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$7(ZWaveController.java:207)[188:org.openhab.binding.zwave:2.0.0.201609212035]
at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1303)[188:org.openhab.binding.zwave:2.0.0.201609212035]

openhab>

Hi folks. Thus far, I have two of these devices. 10 months apart, the firmware has gone from 4.x to 8.x, and they are far different. Only a night or two ago, the entry was built for the 8.x firmware, and both of mine are working now. I am using OpenHAB2, and not using .items files at all. I am using Habmin2 for all configuration.

Here is my configuration for the v4.x firmware device:

and here is my configuration for the v8.x device:

Let me know any other specific questions, and I will help how I can. They are working pretty well for me now.

I have a few, possibly dumb, questions.

  1. I’m not sure what you mean by “entry” when you mention the build for the 8.x firmware. Are you referring to a newer version of the binding? If so, is this upgrade picked up when I do the apt-get upgrade process?
  2. Where can I identify the firmware rev on my device?
  3. Using only Habmin? I thought I had to have an item so I can use it in a rule.
  4. Did your devices (4.x and 8.x) not work till a night or two ago

John

Not dumb at all.

  1. Because the newer device has a newer firmware that is different than the older device, it needed an updated entry in the z-wave database. This is done now, and works. Yes, you will need a new binding, one built in the last day or two specifically. I am not sure when the binaries for apt-get are packaged, but I think they are built when the distribution is created, so a fresh update should get you what you need (and a restart to pick up the new binding).

2a If you have Habmin installed, go to things under configuration, select your device, then in the right panel, select attributes.
2b If you have PaperUI installed, go to configuration -> things, click your device and then click Show Properties

3 You do need to create an item, but the item can exist in the MapDB used by OpenHAB2, and does not need to exist in a .items file. Your rules can reference it by name either way. Give this a read: http://www.cd-jackson.com/index.php/openhab/habmin

4 My 4.x device did work. Only the battery and the alarm on the 8.x device worked until the database update, and now everything works.

Hope this helps

Jim

Sorry if this is a little off topic, but what is the difference between the binary sensor and burglar alarm? Is the alarm the equivalent of a tamper alarm?

So… Partial success. I can now get the temp, battery, and Motion (Burglar). I cannot however get the tamper (binary sensor) to come in. I have went as far as rolling back the server (on VM) to before I added the device. I updated the driver then added the device with no “custom” items. No joy on the binary sensor. But to be honest with you I’m not that worried about the tamper switch.

On to the next issue. After rolling the server back and upgrading both Openhab and the zwave binding something broke with the Ecobee binding. So I went back to the current, working, snapshot. The only issue remaining is I see in the logs that the binding is attempting to update node 9 as well as node 10 every time I trigger the motion sensor. I suspect this is due to the fact that when I was trying to get the motion sensor to work I linked (inclusion) it to the zwave controller and the first time it came in as node 9. I then unlinked (exclusion) it then proceeded to relink (inclusion). So I suspect somewhere Openhab or the binding is retaining that device as node 9. Question, does anyone know where I can clean this up at. See the log below of what I’m describing.

13:06:31.488 [INFO ] [marthome.event.ItemStateChangedEvent] - DiningMotion changed from NULL to ON
13:06:31.489 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'ON' for item 'DiningMotion' to handler for channel 'zwave:device:cff9cd9b:node9:sensor_binary', because no thing with the UID 'zwave:device:cff9cd9b:node9' could be found.

Alright… A little more investigation reveals that openhab has node 9 linked still (see below). How can I delete this link?

openhab> links

a5004 -> zwave:device:cff9cd9b:node5:switch_dimmer
a5003 -> zwave:device:cff9cd9b:node7:switch_dimmer
a5002 -> zwave:device:cff9cd9b:node8:switch_dimmer
a5001 -> zwave:device:cff9cd9b:node6:switch_dimmer
a5000 -> zwave:device:cff9cd9b:node3:switch_dimmer
DiningMotion -> zwave:device:cff9cd9b:node10:sensor_binary
HallDimmer -> zwave:device:cff9cd9b:node6:switch_dimmer
KitchenDimmer -> zwave:device:cff9cd9b:node3:switch_dimmer
AddyDimmer -> zwave:device:cff9cd9b:node7:switch_dimmer
DiningMotion -> zwave:device:cff9cd9b:node10:alarm_burglar
DiningTemp -> zwave:device:cff9cd9b:node10:sensor_temperature
DiningMotionBatt -> zwave:device:cff9cd9b:node10:battery-level
DiningMotion -> zwave:device:cff9cd9b:node10:sensor_binary
DiningMotion -> zwave:device:cff9cd9b:node9:sensor_binary
DiningMotionBatt -> zwave:device:cff9cd9b:node9:battery-level
DiningMotionTamper -> zwave:device:cff9cd9b:node9:alarm_burglar
DiningTemp -> zwave:device:cff9cd9b:node9:sensor_temperature
harmonyhub_device_LivingRoom_25088811_buttonPress -> harmonyhub:device:LivingRoom:25088811:buttonPress
harmonyhub_device_LivingRoom_25088843_buttonPress -> harmonyhub:device:LivingRoom:25088843:buttonPress
harmonyhub_device_LivingRoom_25088947_buttonPress -> harmonyhub:device:LivingRoom:25088947:buttonPress
harmonyhub_device_LivingRoom_25379995_buttonPress -> harmonyhub:device:LivingRoom:25379995:buttonPress
harmonyhub_device_LivingRoom_38436350_buttonPress -> harmonyhub:device:LivingRoom:38436350:buttonPress
harmonyhub_hub_LivingRoom_currentActivity -> harmonyhub:hub:LivingRoom:currentActivity
zwave_device_cff9cd9b_node3_switch_dimmer -> zwave:device:cff9cd9b:node3:switch_dimmer
zwave_device_cff9cd9b_node5_switch_dimmer -> zwave:device:cff9cd9b:node5:switch_dimmer
zwave_device_cff9cd9b_node6_switch_dimmer -> zwave:device:cff9cd9b:node6:switch_dimmer
zwave_device_cff9cd9b_node7_switch_dimmer -> zwave:device:cff9cd9b:node7:switch_dimmer
zwave_device_cff9cd9b_node8_switch_dimmer -> zwave:device:cff9cd9b:node8:switch_dimmer
zwave_serial_zstick_cff9cd9b_serial_ack -> zwave:serial_zstick:cff9cd9b:serial_ack
zwave_serial_zstick_cff9cd9b_serial_can -> zwave:serial_zstick:cff9cd9b:serial_can
zwave_serial_zstick_cff9cd9b_serial_nak -> zwave:serial_zstick:cff9cd9b:serial_nak
zwave_serial_zstick_cff9cd9b_serial_oof -> zwave:serial_zstick:cff9cd9b:serial_oof
zwave_serial_zstick_cff9cd9b_serial_sof -> zwave:serial_zstick:cff9cd9b:serial_sof

You should be able to find the items under either Habmin or PaperUI under Items and delete them.

hi, i have been thinking about getting thispir(slightly different that one you linked on top here) sensor instead of the phillips hue due to that it has temperature, humidity and light for the same price as the hue. I have hue 1 hub, can i use that as zvawe controller or do i need something else?

Hi guys, sorry to revive an older thread.

@xsnrg or @john_n_tunell - Would either of you guys have a working example of your items and sitemap for this device? I cannot seem to get any values off of my device. I am fairly certain it paired - I had received an Inbox notification, ignored it (I create my Z-Wave items manually) and then created it manually with the 4 channels according to CJackson’s website. I don’t seem to get any values, though.

I don’t have an items file for zwave as I use the json db with Habmin for most of the configuration. I end up putting all of the items in a room into a group, and then my sitemap displays the group, so that is not a lot of help to you either.

Thanks, @xsnrg. So I wound up doing like you and using HABmin to set these up. Which seems to be working now, for the most part. What is weird is that one of the sensors does not report battery status, and the other cannot seem to change from Celsius to Fahrenheit. Did you ever have this problem?