Zwave plus

igorrobertifoc · September 2, 2016, 2:50pm

Hello,
i installed some zwave plus devices and my key is Zwave plus in my OH2.

2 x Philio PST02A and 1 x fibaro multisensor gen5.

I have others normal zwave installed and they work well

In these 3 i get only temperature and illuminance but the motion alarm i can’t get.

Is ZPlus working in OH2? I see some post about security, maybe I have to configure something?

Security Network
The device support the security function. When the device included
with a security controller, the device will auto switch to the security
mode. In the security mode, the follow commands need using Security
CC wrapped to communicate, otherwise it will not response.
COMMAND_CLASS_BATTERY
COMMAND_CLASS_NOTIFICATION_V4
COMMAND_CLASS_ASSOCIATION_V2
COMMAND_CLASS_CONFIGURATION
COMMAND_CLASS_SENSOR_BINARY_V2
COMMAND_CLASS_SENSOR_MULTILEVEL_V5
COMMAND_CLASS_WAKE_UP_V2

Thank you very much for any answer

igorrobertifoc · September 2, 2016, 4:06pm

I though was an association problem… but temperature and motion use the same group (1)

Monitoring Motion.
The MultiSensor can send Basic Set Command to association group 1, which is setup via the Association Command Class, when the MultiSensor detects motion to control the associated devices to “OPEN” state. After 4 minutes by default, if the Motion Sensor is not triggered again, the MultiSensor will send Basic Set Command to these devices to control them to “CLOSE” state, but if the Motion Sensor is triggered again in 4 minutes, the MultiSensor will reset the timing, and start to timing again.

The 4 minutes delay time can be changed through the usage of Z-Wave command built into Z-Wave certified controllers/gateways. The specific Z-Wave command supporting this function is Configuration Command Class. Please consult the operation manual for these controllers / gateways for specific instructions on setting the Multisensor.

Monitoring Temperature, Humidity and Luminance.
The Multisensor can report temperature, humidity, and luminance to a Z-Wave gateway or controller when requested. If this function is supported by the gateway/controller, the data will be displayed in the user interface of the gateway/controller. The specific Z-Wave command supporting the monitoring is the Multilevel Sensor Command Class. Automatic reports are sent to association group 1, which is setup via the Association Command Class. Please consult the operation manual for these gateways/controllers for specific instructions on setting the Multisensor.

chris · September 2, 2016, 7:25pm

Yes. ZWave Plus is backward compatible with the older system. It adds some additional classes, which are mostly implemented.

Security is not implemented. I’d recommend to disable it.

I don’t understand the point you are making with your second post - it looks like something from a manual or something? Can you advise what point you are making with this?

I believe the devices you have installed should work ok, but if not, you should check the logs to see what is wrong.

Spaceman_Spiff · September 3, 2016, 6:55am

Search for a recent post of mine. I was helping a guy with the PST02.
You have to change some stuff in the configuration.
It is pretty well documented in the small paper though.

igorrobertifoc · September 3, 2016, 8:27am

Hello Chris and Spaceman,
both of this zwave sensors have a lot of problems. I changed software many times to getting work this 2.
I like openhab2 and I would like use this one for my home

fibaro multisensor gen5 has some bug with motion alarm. I see in various post, there is not a solution clean to get this working . You are lucky if the sensor start a internal procedure that activate the motion alarm! It worked for 1 year (after 1 month of try), but when I link to OH2, after a exclusion and inclusion, the nightmre begin another time ( not work on domoticz too ).

for Philio PST02A I think problem is different, maybe the security. Chris how I can disable the security? In this case on domoticz the sensor work as expected the I think the problem can be the security.

In my opinion, I thing there is something that not work with writing parameters on device. I tryed 5-6 times to write a value with OH2 but without success, then I tryed on domoticz and work at first time. Maybe can be the security too?

Thank you very much.

chris · September 3, 2016, 8:34am

If you select the controller, enable “Advanced Mode” in HABmin (in the tools menu in the top right of the window) then you should see “Secure Inclusion Mode”

If the device isn’t included correctly (eg due to security), then it’s likely that configuration will not work. I don’t think there’s a problem with configuration in general, however if you can provide a logfile I will take a look (please ensure debug is enabled). I really can’t comment much without log files as otherwise it’s just a complete guess - sorry.

igorrobertifoc · September 3, 2016, 8:42am

Perfect, I changed to no Security I hope this is the way I have to do something now? exclude /reinclude devices?

Thank you.

My configuration was like this:

chris · September 3, 2016, 8:44am

If you have further problems, then please grab a debug log and I’ll take a look.

Cheers
Chris

igorrobertifoc · September 3, 2016, 8:52am

Thank you,
I see lots of post that you ask to give a log file, do you think about the possibility in future to create a button on OH2 like “monitoring mode” and the possibility to send the result on your website? You can link directly to the item with configuration of the user You will have ( maybe ) less questions about "not working items " and people can see if others user has the same problem

Thank you Chris

chris · September 3, 2016, 9:09am

I understand your point, and agree with the idea behind your suggestion, but I’m not sure how to implement it. It’s not something that should go in the binding, and configuring the logging isn’t something that the binding can do even (AFAIK anyway). I think at the moment there’s no way for me to do this sort of thing, but I’ll have a think.

I have added links in the log viewer to the database, so when I get a logfile, it automatically reads the database to check the configuration. Also, in HABmin, there are links to the database from the binding list of supported things and when I get a chance I will also link the user manuals to this so that people can directly read the manuals at the click of a button. So, where I can I’m trying to add this sort of thing, but I’m limited in what the framework will allow.

I like the idea though, and if anyone has ideas on how this sort of thing can be implemented, I think it would be a useful feature.

Thanks
Chris

igorrobertifoc · September 3, 2016, 9:58am

I’m really new on OH2. but I guess that a stucture can be:

create a new package “community debug help” (maybe can be generalised)
give the possibility to set extended or normal log
select devices you will monitor
Show the result @ screen (maybe people see the error by itself )
upload to community (extension / all the configuration of device / log file / versions of software + …).

This DB can be accessed from a web site, and people can speak about problems or success of configuration.

For this I think we need just the access to log file and with the rest api we will get informations about configuration.

it’s important that people, with the package UI, can give a feedback of the status of the community request help. Because is necessary to have a “clean” database without old thing

I don’t see somenthing that you see with your experience you see? I just wrote this as dummy users ( I don’t really like manage files txt)

igorrobertifoc · September 3, 2016, 10:09am

Maybe a start/stop debugging can help to take low the weight of the DB.

Example, Motion on sensor dowesn’t work.
I start the monitoring
I try to fire the motion with the hand
Stop monitoring
look what happen
Send to community

chris · September 3, 2016, 10:11am

I agree that this sort of use case is nice, but it’s not so simple - although maybe not impossible. I looked at trying to get access to the logs via rest interface in HABmin in the past - it is possible, but I couldn’t get it to work at the time. Maybe there are better methods now, but at the moment it means people have to grab their own logs.

If someone wanted to implement this though, I think it would be very useful.

This is the sort of thing that is available in the log viewer (although the filtering of nodes is not implemented in the latest version). The viewer tries to make it easier to see what is happening than reading the log - it’s what I use, and it’s what I try and encourage others to use it themselves as much as possible.

By DB, do you mean a database containing peoples logs? I’ve currently avoided this - you’ll see a statement in the log viewer saying that I don’t download any data. This is because sometimes important information can be logged into logs and people should be careful to just upload them to a globally accessible place.

That said, I have considered adding a button to the log viewer that allows uploading of logs - this would have two benefits - it would make sure people at least look at the logs themselves before sending to me (;)) and it would potentially make it easier for me to get the logs.

Me neither - that’s exactly why I wrote HABmin (over 3 years ago now – how time flies…), and also made the ZWave log viewer - it’s meant to make it easier for people to use the system ;).

Mostly this sort of thing is about time and priorities - there’s just not enough time I find

Cheers
Chris

igorrobertifoc · September 3, 2016, 10:34am

Give me direction. Logs file are saved just in the file or in a database? How do you think is possible access? Just few words

chris · September 3, 2016, 10:37am

Logs are stored in a file (in the userdata/logs folder). However to enable debug logging, you need to log on to the Karaf console and type -:

log:set debug org.openhab.binding.zwave

There are programatic interfaces to do some of this as well, which might be usable in a more user oriented system, but I’m not familiar with what’s available.

Hopefully that’s what you’re after?

igorrobertifoc · September 3, 2016, 11:24am

I’m looking for give an help on development of openhab and I think events and log file are used only by developpers ( or high-level users). Like me, when I try at first time openhab, I just see if “work or not work”. When I see that there are something that not work I just changed software and see if it work on that.

This moment is critical for success of the software. If people have an access to log or events in a method very fast, they can try to understand what’s happen and try to find a solution… Dev people on OH are many, competent and OH2 has a good structure now,
It’s necessary to structure a link beetwen user/community with an efficent way. How many times there is post. I need this, which version you have? can you send the log, how I can enable? which parameter do you have? ahh How I can set?..

We need to have shortest path to get a solution about a problem.

For this, my proposal is to create a REST API that give the access to the log and events. After that, try to understand how log and events are linked to items or service. Then I think, the way is done, Just need to understand to how integrate in the Paper UI. Export to community will be the last thing, because like you wrote is “dangerous” with sensible data.

chris · September 3, 2016, 11:47am

I agree with everything you say. The question is always time - if you are a developer (?) maybe you could look at implementing on the server side (ie providing a REST interface)? If so, the client side is easy (at least I can add it to HABmin easily). This might also be worth discussing on the ESH forum as it’s something that might be of interest in the core.

igorrobertifoc · September 3, 2016, 12:06pm

Good,
time is always most important thing

Yes, i’m a dev ( I don’t use anymore at work, but I i’m an IT Engineer ).
I posted on ESH Forum, now a moderator have to approve the post.

igorrobertifoc · September 3, 2016, 2:30pm

Continuing on my zwave error,

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/168

I show you the result when I open and close the door. Motion and door contact are not updated.

Thank you Chris

 01 18 06 31 05 01 0A 00 53 6F 
2016-09-03 14:19:37.051 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-09-03 14:19:37.053 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 24 00 04 00 0C 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 07 08 00 05 31 05 03 01 18 06 31 05 01 0A 00 53 6F 
2016-09-03 14:19:37.055 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 24 00 04 00 0C 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 07 08 00 05 31 05 03 01 18 06 31 05 01 0A 00 53 6F 
2016-09-03 14:19:37.058 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0C 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 07 08 00 05 31 05 03 01 18 06 31 05 01 0A 00 53 
2016-09-03 14:19:37.059 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 12: Application Command Request (INITIALIZING:PING)
2016-09-03 14:19:37.060 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 12: Node is ALIVE. Init stage is PING.
2016-09-03 14:19:37.062 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveNodeStatusEvent
2016-09-03 14:19:37.063 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2016-09-03 14:19:37.064 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Setting ONLINE
2016-09-03 14:19:37.068 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 12: Node Status event during initialisation - Node is ALIVE
2016-09-03 14:19:37.070 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 12: Node advancer - PING: queue length(0), free to send(true)
2016-09-03 14:19:37.071 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 12: Node advancer: loop - PING try 1: stageAdvanced(false)
2016-09-03 14:19:37.072 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 12: Node advancer: PING - send NoOperation
2016-09-03 14:19:37.073 [DEBUG] [ndclass.ZWaveNoOperationCommandClass] - NODE 12: Creating new message for command No Operation
2016-09-03 14:19:37.074 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 12: Node advancer - queued packet. Queue length is 1
2016-09-03 14:19:37.076 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 12: Putting message SendData in wakeup queue.
2016-09-03 14:19:37.077 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 12: Node Status event - Node is ALIVE
2016-09-03 14:19:37.078 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 12: Incoming command class MULTI_CMD
2016-09-03 14:19:37.079 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Received Multi-Command Request
2016-09-03 14:19:37.080 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Incoming command class BATTERY
2016-09-03 14:19:37.080 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Calling handleApplicationCommandRequest.
2016-09-03 14:19:37.081 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 12: Received Battery Request
2016-09-03 14:19:37.082 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 12: Battery report value = 100
2016-09-03 14:19:37.082 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2016-09-03 14:19:37.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2016-09-03 14:19:37.084 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 100
2016-09-03 14:19:37.084 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:161955dc:node12:battery-level to 100 [DecimalType]
2016-09-03 14:19:37.087 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 12: CC event during initialisation stage IDLE
2016-09-03 14:19:37.088 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Incoming command class ALARM
2016-09-03 14:19:37.088 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Calling handleApplicationCommandRequest.
2016-09-03 14:19:37.090 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 12: Received Alarm Request V3
2016-09-03 14:19:37.091 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 12: Process Alarm Report, V3, length 33
2016-09-03 14:19:37.092 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 12: Alarm report - 7 = 0, sensor=0, event=8, status=255
2016-09-03 14:19:37.093 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 12: Alarm Type = Burglar (7)
2016-09-03 14:19:37.093 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2016-09-03 14:19:37.094 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2016-09-03 14:19:37.095 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
2016-09-03 14:19:37.097 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:161955dc:node12:alarm_burglar to OFF [OnOffType]
2016-09-03 14:19:37.098 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Incoming command class SENSOR_MULTILEVEL
2016-09-03 14:19:37.099 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Calling handleApplicationCommandRequest.
2016-09-03 14:19:37.099 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Received SENSOR_MULTILEVEL command V5
2016-09-03 14:19:37.100 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Sensor Multi Level REPORT received
2016-09-03 14:19:37.100 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Sensor Type = Luminance(3), Scale = 0
2016-09-03 14:19:37.101 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Sensor Value = 24
2016-09-03 14:19:37.102 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
2016-09-03 14:19:37.103 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2016-09-03 14:19:37.104 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 24
2016-09-03 14:19:37.105 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:161955dc:node12:sensor_luminance to 24 [DecimalType]
2016-09-03 14:19:37.106 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Incoming command class SENSOR_MULTILEVEL
2016-09-03 14:19:37.107 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Calling handleApplicationCommandRequest.
2016-09-03 14:19:37.109 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Received SENSOR_MULTILEVEL command V5
2016-09-03 14:19:37.109 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Sensor Multi Level REPORT received
2016-09-03 14:19:37.110 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Sensor Type = Temperature(1), Scale = 1
2016-09-03 14:19:37.111 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Sensor Value = 83
2016-09-03 14:19:37.112 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
2016-09-03 14:19:37.114 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2016-09-03 14:19:37.115 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 83
2016-09-03 14:19:37.116 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 12: Sensor is reporting scale 1, requiring conversion to 0. Value is now 83.
2016-09-03 14:19:37.116 [DEBUG] [converter.ZWaveCommandClassConverter] - Converted temperature from 83F to 28.3C
2016-09-03 14:19:37.117 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:161955dc:node12:sensor_temperature to 28.3 [DecimalType]
2016-09-03 14:19:37.118 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 19: Transaction not completed: node address inconsistent.  lastSent=19, incoming=255
2016-09-03 14:19:37.916 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 24 00 04 00 0C 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 06 16 00 05 31 05 03 01 1C 06 31 05 01 0A 00 53 74 
2016-09-03 14:19:37.930 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-09-03 14:19:37.932 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 24 00 04 00 0C 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 06 16 00 05 31 05 03 01 1C 06 31 05 01 0A 00 53 74 
2016-09-03 14:19:37.933 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 24 00 04 00 0C 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 06 16 00 05 31 05 03 01 1C 06 31 05 01 0A 00 53 74 
2016-09-03 14:19:37.935 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0C 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 06 16 00 05 31 05 03 01 1C 06 31 05 01 0A 00 53 
2016-09-03 14:19:37.936 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 12: Application Command Request (ALIVE:DETAILS)
2016-09-03 14:19:37.936 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 12: Incoming command class MULTI_CMD
2016-09-03 14:19:37.937 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Received Multi-Command Request
2016-09-03 14:19:37.937 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Incoming command class BATTERY
2016-09-03 14:19:37.939 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Calling handleApplicationCommandRequest.
2016-09-03 14:19:37.939 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 12: Received Battery Request
2016-09-03 14:19:37.940 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 12: Battery report value = 100
2016-09-03 14:19:37.940 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2016-09-03 14:19:37.941 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2016-09-03 14:19:37.941 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 100
2016-09-03 14:19:37.942 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:161955dc:node12:battery-level to 100 [DecimalType]
2016-09-03 14:19:37.943 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Incoming command class ALARM
2016-09-03 14:19:37.943 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Calling handleApplicationCommandRequest.
2016-09-03 14:19:37.944 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 12: Received Alarm Request V3
2016-09-03 14:19:37.944 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 12: Process Alarm Report, V3, length 33
2016-09-03 14:19:37.945 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 12: Alarm report - 6 = 0, sensor=0, event=22, status=255
2016-09-03 14:19:37.946 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 12: Alarm Type = Access Control (6)
2016-09-03 14:19:37.946 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2016-09-03 14:19:37.947 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2016-09-03 14:19:37.948 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
2016-09-03 14:19:37.949 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:161955dc:node12:alarm_access to OFF [OnOffType]
2016-09-03 14:19:37.952 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Incoming command class SENSOR_MULTILEVEL
2016-09-03 14:19:37.953 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Calling handleApplicationCommandRequest.
2016-09-03 14:19:37.954 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Received SENSOR_MULTILEVEL command V5
2016-09-03 14:19:37.954 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Sensor Multi Level REPORT received
2016-09-03 14:19:37.955 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Sensor Type = Luminance(3), Scale = 0
2016-09-03 14:19:37.955 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Sensor Value = 28
2016-09-03 14:19:37.956 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
2016-09-03 14:19:37.956 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2016-09-03 14:19:37.957 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 28
2016-09-03 14:19:37.958 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:161955dc:node12:sensor_luminance to 28 [DecimalType]
2016-09-03 14:19:37.959 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Incoming command class SENSOR_MULTILEVEL
2016-09-03 14:19:37.959 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Calling handleApplicationCommandRequest.
2016-09-03 14:19:37.965 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Received SENSOR_MULTILEVEL command V5
2016-09-03 14:19:37.965 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Sensor Multi Level REPORT received
2016-09-03 14:19:37.966 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Sensor Type = Temperature(1), Scale = 1
2016-09-03 14:19:37.967 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Sensor Value = 83
2016-09-03 14:19:37.974 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
2016-09-03 14:19:37.974 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2016-09-03 14:19:37.975 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 83
2016-09-03 14:19:37.976 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 12: Sensor is reporting scale 1, requiring conversion to 0. Value is now 83.
2016-09-03 14:19:37.976 [DEBUG] [converter.ZWaveCommandClassConverter] - Converted temperature from 83F to 28.3C
2016-09-03 14:19:37.977 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:161955dc:node12:sensor_temperature to 28.3 [DecimalType]
2016-09-03 14:19:37.978 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 19: Transaction not completed: node address inconsistent.  lastSent=19, incoming=255
2016-09-03 14:19:38.879 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 24 00 04 00 0C 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 06 17 00 05 31 05 03 01 16 06 31 05 01 0A 00 53 7F 
2016-09-03 14:19:38.885 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-09-03 14:19:38.887 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 24 00 04 00 0C 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 06 17 00 05 31 05 03 01 16 06 31 05 01 0A 00 53 7F 
2016-09-03 14:19:38.889 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 24 00 04 00 0C 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 06 17 00 05 31 05 03 01 16 06 31 05 01 0A 00 53 7F 
2016-09-03 14:19:38.891 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0C 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 06 17 00 05 31 05 03 01 16 06 31 05 01 0A 00 53 
2016-09-03 14:19:38.891 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 12: Application Command Request (ALIVE:DETAILS)
2016-09-03 14:19:38.892 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 12: Incoming command class MULTI_CMD
2016-09-03 14:19:38.892 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Received Multi-Command Request
2016-09-03 14:19:38.893 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Incoming command class BATTERY
2016-09-03 14:19:38.894 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Calling handleApplicationCommandRequest.
2016-09-03 14:19:38.894 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 12: Received Battery Request
2016-09-03 14:19:38.895 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 12: Battery report value = 100
2016-09-03 14:19:38.895 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2016-09-03 14:19:38.896 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2016-09-03 14:19:38.896 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 100
2016-09-03 14:19:38.897 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:161955dc:node12:battery-level to 100 [DecimalType]
2016-09-03 14:19:38.898 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Incoming command class ALARM
2016-09-03 14:19:38.899 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Calling handleApplicationCommandRequest.
2016-09-03 14:19:38.901 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 12: Received Alarm Request V3
2016-09-03 14:19:38.901 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 12: Process Alarm Report, V3, length 33
2016-09-03 14:19:38.902 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 12: Alarm report - 6 = 0, sensor=0, event=23, status=255
2016-09-03 14:19:38.903 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 12: Alarm Type = Access Control (6)
2016-09-03 14:19:38.903 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2016-09-03 14:19:38.904 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2016-09-03 14:19:38.904 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
2016-09-03 14:19:38.905 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:161955dc:node12:alarm_access to OFF [OnOffType]
2016-09-03 14:19:38.906 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Incoming command class SENSOR_MULTILEVEL
2016-09-03 14:19:38.907 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Calling handleApplicationCommandRequest.
2016-09-03 14:19:38.911 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Received SENSOR_MULTILEVEL command V5
2016-09-03 14:19:38.913 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Sensor Multi Level REPORT received
2016-09-03 14:19:38.914 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Sensor Type = Luminance(3), Scale = 0
2016-09-03 14:19:38.915 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Sensor Value = 22
2016-09-03 14:19:38.917 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
2016-09-03 14:19:38.918 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2016-09-03 14:19:38.919 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 22
2016-09-03 14:19:38.920 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:161955dc:node12:sensor_luminance to 22 [DecimalType]
2016-09-03 14:19:38.921 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Incoming command class SENSOR_MULTILEVEL
2016-09-03 14:19:38.921 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 12: Calling handleApplicationCommandRequest.
2016-09-03 14:19:38.927 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Received SENSOR_MULTILEVEL command V5
2016-09-03 14:19:38.927 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Sensor Multi Level REPORT received
2016-09-03 14:19:38.928 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Sensor Type = Temperature(1), Scale = 1
2016-09-03 14:19:38.929 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 12: Sensor Value = 83
2016-09-03 14:19:38.930 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
2016-09-03 14:19:38.931 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2016-09-03 14:19:38.931 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 83
2016-09-03 14:19:38.932 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 12: Sensor is reporting scale 1, requiring conversion to 0. Value is now 83.
2016-09-03 14:19:38.933 [DEBUG] [converter.ZWaveCommandClassConverter] - Converted temperature from 83F to 28.3C
2016-09-03 14:19:38.934 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:161955dc:node12:sensor_temperature to 28.3 [DecimalType]

chris · September 3, 2016, 2:41pm

It looks like the device is working ok.

The device is sending the notification class - in the current implementation (which was designed for the alarm class), this just results in an update of the channel which I can see in the log.

There is an update due in the binding to provide better support for the notification class - I’ll try and get this merged in the next week.