Zwave plus

igorrobertifoc · September 3, 2016, 3:13pm

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

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]

Spaceman_Spiff · September 3, 2016, 3:29pm

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).

chris · September 3, 2016, 3:35pm

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…

igorrobertifoc · September 3, 2016, 3:45pm

I Set 20… but was not updated… I try, I have to umount from door 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

chris · September 3, 2016, 4:02pm

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.

igorrobertifoc · September 3, 2016, 4:17pm

I did

now there are something new 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

chris · September 3, 2016, 4:25pm

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?

igorrobertifoc · September 3, 2016, 9:14pm

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

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

Spaceman_Spiff · September 4, 2016, 6:19am

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

igorrobertifoc · September 4, 2016, 4:19pm

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