Zwave plus

Add-ons Bindings
11

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) :slight_smile:

12

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

13

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 :wink:

Cheers
Chris

14

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 :slight_smile:

15

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?

16

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.

17

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.

18

Good,
time is always most important thing :slight_smile:

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.

19

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]
20

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.

21

I don’t undestand, sorry to technical, The contact status and motion alarm are sent but they are not parsed until the new release?

Channel update are, as expected, only temperature (28° inside!!!) and illuminance.
Is a bit strange, because if found a thread from a person who has the same hardware and to him it’s work:

Not really clear for me :frowning:

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.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.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.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.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.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.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.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: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.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.934 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:161955dc:node12:sensor_temperature to 28.3 [DecimalType]

22

Did you change the custom configuration parameter as suggested?
I have six devices on two locations running just fine (One with Gen5 = secure and one with Gen4 = no secure).

23

Yes, they are sent, and they are processed. But the processing is assuming this is using the ALARM command class where it’s using the NOTIFICATION class. This needs to process the data in a different way. Currently, the values are being updated, but it always says OFF (you can see this in the log) -:

Updating channel state zwave:device:161955dc:node12:alarm_burglar to OFF [OnOffType]

I have not looked at the configuration, but this might be a backward compatibility mode to use the older ALARM class…

24

I Set 20… but was not updated… I try, I have to umount from door :disappointed_relieved: for press three time the button …

For Chris,This is the parameter suggested by Spaceman

7: Customer Function
4
Parameter to set the Customer Function.
Bit 0: Reserved.
Bit 1: Enable sending motion OFF report. 0: Disable, 1: Enable. Note: Depends on the Bit4, 0: Report Notification CC, Type: 0x07, Event: 0xFE 1: Sensor Binary Report,

20 --> set the bit 4

25

You shouldn’t need to. If the wakeup timer is set, then you just need to wait for this to time out - normally it is set to 1 hour I think.

26

I did :slight_smile:

now there are something new :slight_smile: but is still not working . This sensor is a pain in a$$

2016-09-03 16:07:11.145 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:161955dc:node12:battery-level to 100 [DecimalType]
2016-09-03 16:07:11.154 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_BINARY, value = 255
2016-09-03 16:07:11.155 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter set for channel zwave:device:161955dc:node12:sensor_door
2016-09-03 16:07:11.157 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 6
2016-09-03 16:07:11.158 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter set for channel zwave:device:161955dc:node12:sensor_luminance
2016-09-03 16:07:11.160 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 84
2016-09-03 16:07:11.161 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter set for channel zwave:device:161955dc:node12:sensor_luminance
2016-09-03 16:07:12.101 [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 16:07:12.102 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:161955dc:node12:battery-level to 100 [DecimalType]
2016-09-03 16:07:12.107 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_BINARY, value = 255
2016-09-03 16:07:12.108 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter set for channel zwave:device:161955dc:node12:sensor_door
2016-09-03 16:07:12.110 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter set for channel zwave:device:161955dc:node12:sensor_luminance
2016-09-03 16:07:12.113 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter set for channel zwave:device:161955dc:node12:sensor_luminance
2016-09-03 16:07:18.158 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:161955dc:node12:battery-level to 100 [DecimalType]
2016-09-03 16:07:18.170 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_BINARY, value = 0
2016-09-03 16:07:18.175 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 7
2016-09-03 16:07:18.178 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 84
2016-09-03 16:07:18.179 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter set for channel zwave:device:161955dc:node12:sensor_luminance
27

Can you provide a log and I’ll take a look. When the wakeup occurs, any pending configuration transactions should be sent - it works here at least…

What version of the binding you are using?

28

Ok, many thx. Now temperature+illumination+door contact work :open_mouth:

The motion is still not working for both (philio + and fibaro). The message arrive to set 255 but not arrive the message to set to 0.

But I do a step forward, Thank you

29

This is intentional as I have described in the other thread.
Just use ReveicedUpdate.

30

Ok, if I want to monitor with a chart presence I can’t. So it’s ok, just to understand how to replicate this with a timer rule and a dummy variable :slight_smile: