Aotec multisensor 6 doesn't pick up parameter changes

Add-ons Bindings
,
1

Hi all,

I have an aotec multisensor 6 which I am using with openhab and habmin/habmin2.

I am trying to set the a few parameters, parameter 101 for group 1 periodic report to 227 (default 225) to report ultraviolet readings, and parameter 111 for group 1 periodic report interval to 900 (default 3600).

Seems that p101 always reverts back to 225. p111 gets updated to 900 in habmin, but the sensor still reports readings in 3600 intervals.

I have given it sufficient time to pick things up (been trying for a month or so), also update the bindings to the latest snapshot.

any help would be appreciated.

1 Like
2

Hi
Can you provide a debug log and I’ll take a look. I suggest the following -:

  • delete the zwave.log file
  • start the binding
  • set the parameter to 227 in HABmin
  • wake up the device at least a couple of times. The yellow background in HABmin should dissappear
  • stop the binding and send me the log file (or attach it here if you can)

Also, can you post a link to the technical manual for the device - I can’t seem to find it from a quick scan on the web.

Chris

3

Hi Chris,

thanks for the reply.

I have tried a few times to start from scratch. it seems that it sends the values ok (the yellow background in habmin disappears), put the logs here.

also, here is the link for the manual.

many thanks

4

Thanks - it looks like the unit is acking the message, but as you say, it’s staying at 225…

I’m actually looking for the tech manual… I’ll have a dig around as I think I have it somewhere (just can’t find it!).

5

Ok - found the manual.

This shows that a value of 227 (hex E3) is not a valid value so the sensor is rejecting it. What exactly are you trying to do?

Chris

6

thanks for checking it.

just realised that there was a typo in my manual (which they corrected in the version online), that I should send 241 not 225 (as the ultraviolet flag is 16 not 2), seems that is picked up now.

wondering if you have any suggestion for the other issue (update interval is picked up but does not work on the sensor)

thanks

7

Can you get a log for setting param 111 as well? Also, can you post the XML file from /etc/zwave/node3.xml.

8

sure, thanks.

here they are: logs, node3.xml

(I was trying to set param 111 to 1000)

9

It looks like it worked ok -:

21:41:11.390 [DEBUG] [eController$ZWaveReceiveThread:1365 ] - Receive queue ADD: Length=1
21:41:11.390 [DEBUG] [b.z.i.protocol.ZWaveController:1123 ] - Receive queue TAKE: Length=0
21:41:11.392 [DEBUG] [o.b.z.i.protocol.SerialMessage:233  ] - Assembled message buffer = 01 0E 00 04 00 03 08 70 06 6F 04 00 00 03 E8 08 
21:41:11.394 [DEBUG] [b.z.i.protocol.ZWaveController:1124 ] - Process Message = 01 0E 00 04 00 03 08 70 06 6F 04 00 00 03 E8 08 
21:41:11.396 [DEBUG] [b.z.i.protocol.ZWaveController:190  ] - Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 03 08 70 06 6F 04 00 00 03 E8 
21:41:11.397 [DEBUG] [ApplicationCommandMessageClass:38   ] - NODE 3: Application Command Request (ALIVE:DONE)
21:41:11.398 [DEBUG] [ApplicationCommandMessageClass:56   ] - NODE 3: Incoming command class CONFIGURATION
21:41:11.399 [DEBUG] [ZWaveConfigurationCommandClass:76   ] - NODE 3: Received Configuration Request
21:41:11.399 [DEBUG] [ZWaveConfigurationCommandClass:121  ] - NODE 3: Node configuration report, parameter = 111, value = 1000

The above log shows the returned value reported from the device which is 00 00 03 E8, which is 1000 in decimal… The XML file also shows this…

<entry>
<int>111</int>
<configurationParameter>
<index>111</index>
<size>4</size>
<value>1000</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>

So, as best as I can tell, this is working ok - why do you think it’s not working?

Chris

10

I have some MultiSensor 6’s as well. This is all useful to know! Makes sense as to why things weren’t working properly.

With mine, other than UV being in-absentia I found that (after asking Aeon labs directly) the tamper switch has a command class of CC COMMAND_CLASS_NOTIFICATION_V3 or NOTIFICATION_REPORT_V3. I don’t see these options available in the z-wave binding though. Is this something that needs the z-wave binding to be modified to allow it?

What I assumed (incorrectly) was that Aeotec would have already figured out what the correct configuration parameter values were before they sold their product. I can’t understand how or why they would release it (and not release its manual on their website too btw) with clearly incorrect data.

Perhaps this latest version of the manual and technical data sheet will absolve some of these issues.

Chris, the manual on Vesternet has the data sheet appended to the end of the PDF. The one you linked to is actually for an older sensor so perhaps might be causing some confusion?

11

D’oh, you’re right. When I opened it I was looking for the Engineering Specification and didn’t scroll down to the end…

These aren’t currently supported and I have no information on the classes. All I can suggest is that if you can capture a debug log of these messages being sent, then I’m happy to take a look at the log to see if I can work out what’s happening with a view to supporting it…

Chris

12

I think it is not working because it is still sending the readings once an hour (instead of ~16 mins) or sometimes even less. Or maybe I misunderstood how these sensors should behave?

13

Well, one thing I can think of to try - delete the XML file for this node, and restart the binding and see what the value shows. If it’s still showing 1000, then I’d be pretty sure it’s set ok… If not, then I don’t know as the response packet from the device is showing 1000 seconds…

14

Hi,

I deleted the xml, and left it for a day to recover. Seems it all reverted to default (or more like most of the fields are empty). Attached the screenshot from habmin (https://dl.dropboxusercontent.com/u/15765058/Screen%20Shot%202015-09-01%20at%2021.45.47.png).

thanks,

15

The empty fields just means that the binding didn’t receive the information from the device (yet). It doesn’t necessarily mean that the configuration has reverted to default. The device might need to be woken up to speed up the process.

If it doesn’t download the data then there’s a button in HABmin that allows you to request a refresh of the parameters- press that an wake the device.

16

Hi,

I’ve got the same problem. Trying to set parameter 201, it keeps getting reset in habmin.

If I don’t misinterpret the following log, then after having received the set command, the sensor seems to be sending an unsolicited (?) configuration report, saying the value is now -1 (again, as it used to be before the ‘set’).
No idea why.

Chris, attention: it’s all about new multisensor 6. Your link to the manual on Vesternet is on the old sensor (called ‘4-in-1’ or ‘Gen5’), although it seems to be largely the same. See Tamas’ link for the new one.

I also contacted Aeon Labs on the issue, but no response yet.

regards
Markus

PS: the forum does not allow to attach files? That’s pretty annoying. Sorry for posting inline, no dropbox at hand…

2015-09-03 10:33:52.255 [TRACE] [veController$WatchDogTimerTask] - Watchdog: Checking Serial threads
2015-09-03 10:33:52.393 [DEBUG] [.z.i.config.ZWaveConfiguration] - doSet domain 'nodes/node71/parameters/configuration201' to '-40'
2015-09-03 10:33:52.672 [DEBUG] [.z.i.config.ZWaveConfiguration] - Set parameter index '201' to '-40'
2015-09-03 10:33:52.676 [DEBUG] [ZWaveConfigurationCommandClass] - NODE 71: Creating new message for application command CONFIGURATIONCMD_SET
2015-09-03 10:33:52.677 [DEBUG] [o.b.z.i.protocol.SerialMessage] - NODE 71: Creating empty message of class = SendData (0x13), type = Request (0x00)
2015-09-03 10:33:52.679 [DEBUG] [b.z.i.protocol.ZWaveController] - Callback ID = 78
2015-09-03 10:33:52.680 [DEBUG] [b.z.i.protocol.ZWaveController] - Enqueueing message. Queue length = 1
2015-09-03 10:33:52.680 [DEBUG] [WaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2015-09-03 10:33:52.681 [TRACE] [o.b.z.i.protocol.SerialMessage] - Calculated checksum = 0x53
2015-09-03 10:33:52.681 [DEBUG] [ZWaveConfigurationCommandClass] - NODE 71: Creating new message for application command CONFIGURATIONCMD_GET
2015-09-03 10:33:52.682 [DEBUG] [o.b.z.i.protocol.SerialMessage] - Assembled message buffer = 01 0D 00 13 47 06 70 04 C9 02 FF D8 25 4E 53 
2015-09-03 10:33:52.682 [DEBUG] [o.b.z.i.protocol.SerialMessage] - NODE 71: Creating empty message of class = SendData (0x13), type = Request (0x00)
2015-09-03 10:33:52.683 [DEBUG] [b.z.i.protocol.ZWaveController] - Callback ID = 79
2015-09-03 10:33:52.684 [DEBUG] [WaveController$ZWaveSendThread] - NODE 71: Sending REQUEST Message = 01 0D 00 13 47 06 70 04 C9 02 FF D8 25 4E 53 
2015-09-03 10:33:52.685 [DEBUG] [b.z.i.protocol.ZWaveController] - Enqueueing message. Queue length = 1
2015-09-03 10:33:52.687 [TRACE] [eController$ZWaveReceiveThread] - Received ACK
2015-09-03 10:33:52.692 [DEBUG] [eController$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
2015-09-03 10:33:52.693 [TRACE] [o.b.z.i.protocol.SerialMessage] - NODE 255: Creating new SerialMessage from buffer = 01 04 01 13 01 E8 
2015-09-03 10:33:52.694 [TRACE] [o.b.z.i.protocol.SerialMessage] - Calculated checksum = 0xE8
2015-09-03 10:33:52.695 [TRACE] [o.b.z.i.protocol.SerialMessage] - NODE 255: Checksum matched
2015-09-03 10:33:52.696 [TRACE] [o.b.z.i.protocol.SerialMessage] - NODE 255: Message payload = 01 
2015-09-03 10:33:52.696 [TRACE] [WaveController$ZWaveSendThread] - Message SENT
2015-09-03 10:33:52.698 [TRACE] [eController$ZWaveReceiveThread] - Message is valid, sending ACK
2015-09-03 10:33:52.716 [TRACE] [eController$ZWaveReceiveThread] - Response SENT
2015-09-03 10:33:52.717 [DEBUG] [eController$ZWaveReceiveThread] - Receive queue ADD: Length=1
2015-09-03 10:33:52.717 [DEBUG] [b.z.i.protocol.ZWaveController] - Receive queue TAKE: Length=0
2015-09-03 10:33:52.719 [TRACE] [o.b.z.i.protocol.SerialMessage] - Calculated checksum = 0xE8
2015-09-03 10:33:52.720 [DEBUG] [o.b.z.i.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
2015-09-03 10:33:52.721 [DEBUG] [b.z.i.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
2015-09-03 10:33:52.722 [DEBUG] [b.z.i.protocol.ZWaveController] - Message: class = SendData (0x13), type = Response (0x01), payload = 01 
2015-09-03 10:33:52.723 [TRACE] [b.z.i.protocol.ZWaveController] - Incoming Message type = RESPONSE
2015-09-03 10:33:52.724 [TRACE] [b.z.i.p.s.SendDataMessageClass] - Handle Message Send Data Response
2015-09-03 10:33:52.725 [DEBUG] [b.z.i.p.s.SendDataMessageClass] - NODE 71: Sent Data successfully placed on stack.
2015-09-03 10:33:53.034 [DEBUG] [eController$ZWaveReceiveThread] - Receive Message = 01 07 00 13 4E 00 00 23 86 
2015-09-03 10:33:53.036 [TRACE] [o.b.z.i.protocol.SerialMessage] - NODE 255: Creating new SerialMessage from buffer = 01 07 00 13 4E 00 00 23 86 
2015-09-03 10:33:53.036 [TRACE] [o.b.z.i.protocol.SerialMessage] - Calculated checksum = 0x86
2015-09-03 10:33:53.037 [TRACE] [o.b.z.i.protocol.SerialMessage] - NODE 255: Checksum matched
2015-09-03 10:33:53.038 [TRACE] [o.b.z.i.protocol.SerialMessage] - NODE 255: Message payload = 4E 00 00 23 
2015-09-03 10:33:53.038 [TRACE] [eController$ZWaveReceiveThread] - Message is valid, sending ACK
2015-09-03 10:33:53.056 [TRACE] [eController$ZWaveReceiveThread] - Response SENT
2015-09-03 10:33:53.057 [DEBUG] [eController$ZWaveReceiveThread] - Receive queue ADD: Length=1
2015-09-03 10:33:53.057 [DEBUG] [b.z.i.protocol.ZWaveController] - Receive queue TAKE: Length=0
2015-09-03 10:33:53.058 [TRACE] [o.b.z.i.protocol.SerialMessage] - Calculated checksum = 0x88
2015-09-03 10:33:53.059 [DEBUG] [o.b.z.i.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 4E 00 00 23 00 00 88 
2015-09-03 10:33:53.060 [DEBUG] [b.z.i.protocol.ZWaveController] - Process Message = 01 09 00 13 4E 00 00 23 00 00 88 
2015-09-03 10:33:53.061 [DEBUG] [b.z.i.protocol.ZWaveController] - Message: class = SendData (0x13), type = Request (0x00), payload = 4E 00 00 23 
2015-09-03 10:33:53.062 [TRACE] [b.z.i.protocol.ZWaveController] - Incoming Message type = REQUEST
2015-09-03 10:33:53.062 [TRACE] [b.z.i.p.s.SendDataMessageClass] - Handle Message Send Data Request
2015-09-03 10:33:53.063 [DEBUG] [b.z.i.p.s.SendDataMessageClass] - NODE 71: SendData Request. CallBack ID = 78, Status = Transmission complete and ACK received(0)
2015-09-03 10:33:53.063 [TRACE] [o.b.z.i.protocol.SerialMessage] - Ack Pending cleared
2015-09-03 10:33:53.065 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor] - Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 47 06 70 04 C9 02 FF D8 
2015-09-03 10:33:53.066 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor] - Recv message Message: class = SendData (0x13), type = Request (0x00), payload = 4E 00 00 23 
2015-09-03 10:33:53.067 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, expected=SendData, cancelled=false
2015-09-03 10:33:53.067 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor] -          transaction complete!
2015-09-03 10:33:53.068 [DEBUG] [b.z.i.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2015-09-03 10:33:53.069 [DEBUG] [.z.internal.ZWaveActiveBinding] - ZwaveIncomingEvent
2015-09-03 10:33:53.070 [TRACE] [b.z.i.protocol.ZWaveController] - Released. Transaction completed permit count -> 1
2015-09-03 10:33:53.070 [DEBUG] [WaveController$ZWaveSendThread] - NODE 71: Response processed after 385ms/3310ms.
2015-09-03 10:33:53.071 [TRACE] [WaveController$ZWaveSendThread] - Acquired. Transaction completed permit count -> 0
2015-09-03 10:33:53.072 [DEBUG] [WaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2015-09-03 10:33:53.073 [TRACE] [o.b.z.i.protocol.SerialMessage] - Calculated checksum = 0x74
2015-09-03 10:33:53.074 [DEBUG] [o.b.z.i.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 13 47 03 70 05 C9 25 4F 74 
2015-09-03 10:33:53.075 [DEBUG] [WaveController$ZWaveSendThread] - NODE 71: Sending REQUEST Message = 01 0A 00 13 47 03 70 05 C9 25 4F 74 
2015-09-03 10:33:53.078 [TRACE] [eController$ZWaveReceiveThread] - Received ACK
2015-09-03 10:33:53.083 [DEBUG] [eController$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
2015-09-03 10:33:53.084 [TRACE] [o.b.z.i.protocol.SerialMessage] - NODE 255: Creating new SerialMessage from buffer = 01 04 01 13 01 E8 
2015-09-03 10:33:53.085 [TRACE] [o.b.z.i.protocol.SerialMessage] - Calculated checksum = 0xE8
2015-09-03 10:33:53.086 [TRACE] [o.b.z.i.protocol.SerialMessage] - NODE 255: Checksum matched
2015-09-03 10:33:53.087 [TRACE] [WaveController$ZWaveSendThread] - Message SENT
2015-09-03 10:33:53.087 [TRACE] [o.b.z.i.protocol.SerialMessage] - NODE 255: Message payload = 01 
2015-09-03 10:33:53.088 [TRACE] [eController$ZWaveReceiveThread] - Message is valid, sending ACK
2015-09-03 10:33:53.106 [TRACE] [eController$ZWaveReceiveThread] - Response SENT
2015-09-03 10:33:53.107 [DEBUG] [eController$ZWaveReceiveThread] - Receive queue ADD: Length=1
2015-09-03 10:33:53.107 [DEBUG] [b.z.i.protocol.ZWaveController] - Receive queue TAKE: Length=0
2015-09-03 10:33:53.108 [TRACE] [o.b.z.i.protocol.SerialMessage] - Calculated checksum = 0xE8
2015-09-03 10:33:53.109 [DEBUG] [o.b.z.i.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
2015-09-03 10:33:53.109 [DEBUG] [b.z.i.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
2015-09-03 10:33:53.110 [DEBUG] [b.z.i.protocol.ZWaveController] - Message: class = SendData (0x13), type = Response (0x01), payload = 01 
2015-09-03 10:33:53.110 [TRACE] [b.z.i.protocol.ZWaveController] - Incoming Message type = RESPONSE
2015-09-03 10:33:53.110 [TRACE] [b.z.i.p.s.SendDataMessageClass] - Handle Message Send Data Response
2015-09-03 10:33:53.110 [DEBUG] [b.z.i.p.s.SendDataMessageClass] - NODE 71: Sent Data successfully placed on stack.
2015-09-03 10:33:53.259 [DEBUG] [eController$ZWaveReceiveThread] - Receive Message = 01 07 00 13 4F 00 00 12 B6 
2015-09-03 10:33:53.260 [TRACE] [o.b.z.i.protocol.SerialMessage] - NODE 255: Creating new SerialMessage from buffer = 01 07 00 13 4F 00 00 12 B6 
2015-09-03 10:33:53.261 [TRACE] [o.b.z.i.protocol.SerialMessage] - Calculated checksum = 0xB6
2015-09-03 10:33:53.262 [TRACE] [o.b.z.i.protocol.SerialMessage] - NODE 255: Checksum matched
2015-09-03 10:33:53.263 [TRACE] [o.b.z.i.protocol.SerialMessage] - NODE 255: Message payload = 4F 00 00 12 
2015-09-03 10:33:53.263 [TRACE] [eController$ZWaveReceiveThread] - Message is valid, sending ACK
2015-09-03 10:33:53.264 [TRACE] [eController$ZWaveReceiveThread] - Response SENT
2015-09-03 10:33:53.265 [DEBUG] [b.z.i.protocol.ZWaveController] - Receive queue TAKE: Length=0
2015-09-03 10:33:53.265 [DEBUG] [eController$ZWaveReceiveThread] - Receive queue ADD: Length=1
2015-09-03 10:33:53.266 [TRACE] [o.b.z.i.protocol.SerialMessage] - Calculated checksum = 0xB8
2015-09-03 10:33:53.267 [DEBUG] [o.b.z.i.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 4F 00 00 12 00 00 B8 
2015-09-03 10:33:53.268 [DEBUG] [b.z.i.protocol.ZWaveController] - Process Message = 01 09 00 13 4F 00 00 12 00 00 B8 
2015-09-03 10:33:53.269 [DEBUG] [b.z.i.protocol.ZWaveController] - Message: class = SendData (0x13), type = Request (0x00), payload = 4F 00 00 12 
2015-09-03 10:33:53.270 [TRACE] [b.z.i.protocol.ZWaveController] - Incoming Message type = REQUEST
2015-09-03 10:33:53.270 [TRACE] [b.z.i.p.s.SendDataMessageClass] - Handle Message Send Data Request
2015-09-03 10:33:53.271 [DEBUG] [b.z.i.p.s.SendDataMessageClass] - NODE 71: SendData Request. CallBack ID = 79, Status = Transmission complete and ACK received(0)
2015-09-03 10:33:53.272 [TRACE] [o.b.z.i.protocol.SerialMessage] - Ack Pending cleared
2015-09-03 10:33:53.273 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor] - Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 47 03 70 05 C9 
2015-09-03 10:33:53.274 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor] - Recv message Message: class = SendData (0x13), type = Request (0x00), payload = 4F 00 00 12 
2015-09-03 10:33:53.275 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, expected=ApplicationCommandHandler, cancelled=false
2015-09-03 10:33:53.387 [DEBUG] [eController$ZWaveReceiveThread] - Receive Message = 01 0B 00 04 00 47 05 70 06 C9 01 FF F3 
2015-09-03 10:33:53.388 [TRACE] [o.b.z.i.protocol.SerialMessage] - NODE 255: Creating new SerialMessage from buffer = 01 0B 00 04 00 47 05 70 06 C9 01 FF F3 
2015-09-03 10:33:53.389 [TRACE] [o.b.z.i.protocol.SerialMessage] - Calculated checksum = 0xF3
2015-09-03 10:33:53.389 [TRACE] [o.b.z.i.protocol.SerialMessage] - NODE 255: Checksum matched
2015-09-03 10:33:53.390 [TRACE] [o.b.z.i.protocol.SerialMessage] - NODE 255: Message payload = 00 47 05 70 06 C9 01 FF 
2015-09-03 10:33:53.391 [TRACE] [eController$ZWaveReceiveThread] - Message is valid, sending ACK
2015-09-03 10:33:53.391 [TRACE] [eController$ZWaveReceiveThread] - Response SENT
2015-09-03 10:33:53.392 [DEBUG] [eController$ZWaveReceiveThread] - Receive queue ADD: Length=1
2015-09-03 10:33:53.392 [DEBUG] [b.z.i.protocol.ZWaveController] - Receive queue TAKE: Length=0
2015-09-03 10:33:53.393 [TRACE] [o.b.z.i.protocol.SerialMessage] - Calculated checksum = 0xF3
2015-09-03 10:33:53.394 [DEBUG] [o.b.z.i.protocol.SerialMessage] - Assembled message buffer = 01 0B 00 04 00 47 05 70 06 C9 01 FF F3 
2015-09-03 10:33:53.395 [DEBUG] [b.z.i.protocol.ZWaveController] - Process Message = 01 0B 00 04 00 47 05 70 06 C9 01 FF F3 
2015-09-03 10:33:53.396 [DEBUG] [b.z.i.protocol.ZWaveController] - Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 47 05 70 06 C9 01 FF 
2015-09-03 10:33:53.397 [TRACE] [b.z.i.protocol.ZWaveController] - Incoming Message type = REQUEST
2015-09-03 10:33:53.398 [TRACE] [ApplicationCommandMessageClass] - Handle Message Application Command Request
2015-09-03 10:33:53.398 [DEBUG] [ApplicationCommandMessageClass] - NODE 71: Application Command Request (ALIVE:DONE)
2015-09-03 10:33:53.399 [DEBUG] [ApplicationCommandMessageClass] - NODE 71: Incoming command class CONFIGURATION
2015-09-03 10:33:53.400 [TRACE] [ApplicationCommandMessageClass] - NODE 71: Found Command Class CONFIGURATION, passing to handleApplicationCommandRequest
2015-09-03 10:33:53.400 [DEBUG] [ZWaveConfigurationCommandClass] - NODE 71: Received Configuration Request
2015-09-03 10:33:53.401 [TRACE] [ZWaveConfigurationCommandClass] - NODE 71: Process Configuration Report
2015-09-03 10:33:53.402 [DEBUG] [ZWaveConfigurationCommandClass] - NODE 71: Node configuration report, parameter = 201, value = -1
2015-09-03 10:33:53.403 [DEBUG] [b.z.i.protocol.ZWaveController] - Notifying event listeners: ZWaveConfigurationParameterEvent
2015-09-03 10:33:53.404 [DEBUG] [.z.internal.ZWaveActiveBinding] - ZwaveIncomingEvent
2015-09-03 10:33:53.405 [DEBUG] [.z.internal.ZWaveActiveBinding] - NODE 71: Got a value event from Z-Wave network, endpoint = 0, command class = CONFIGURATION, value = org.openhab.binding.zwave.internal.protocol.ConfigurationParameter@1c9ee0c
2015-09-03 10:33:53.406 [TRACE] [.b.z.i.c.ZWaveConverterHandler] - Getting converter for item = Aeon_Feuchtigkeit, command class = CONFIGURATION, item command class = sensor_multilevel
2015-09-03 10:33:53.407 [TRACE] [.b.z.i.c.ZWaveConverterHandler] - Getting converter for item = Aeon_tamper, command class = CONFIGURATION, item command class = sensor_alarm
2015-09-03 10:33:53.408 [TRACE] [.b.z.i.c.ZWaveConverterHandler] - Getting converter for item = Aeon_battery, command class = CONFIGURATION, item command class = battery
2015-09-03 10:33:53.409 [TRACE] [.b.z.i.c.ZWaveConverterHandler] - Getting converter for item = Aeon_Auge_Lux, command class = CONFIGURATION, item command class = sensor_multilevel
2015-09-03 10:33:53.410 [TRACE] [.b.z.i.c.ZWaveConverterHandler] - Getting converter for item = Aeon_Auge_UV, command class = CONFIGURATION, item command class = sensor_multilevel
2015-09-03 10:33:53.411 [TRACE] [.b.z.i.c.ZWaveConverterHandler] - Getting converter for item = Aeon_Temp, command class = CONFIGURATION, item command class = sensor_multilevel
2015-09-03 10:33:53.412 [TRACE] [.b.z.i.c.ZWaveConverterHandler] - Getting converter for item = Aeon_Auge, command class = CONFIGURATION, item command class = sensor_binary
2015-09-03 10:33:53.418 [TRACE] [.b.z.i.p.i.ZWaveNodeSerializer] - Initializing ZWaveNodeSerializer.
2015-09-03 10:33:53.463 [TRACE] [.b.z.i.p.i.ZWaveNodeSerializer] - Initialized ZWaveNodeSerializer.
2015-09-03 10:33:53.464 [DEBUG] [.b.z.i.p.i.ZWaveNodeSerializer] - NODE 71: Serializing to file etc/zwave/node71.xml
2015-09-03 10:33:53.533 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor] - Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 47 03 70 05 C9 
2015-09-03 10:33:53.534 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor] - Recv message Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 47 05 70 06 C9 01 FF 
2015-09-03 10:33:53.535 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, expected=ApplicationCommandHandler, cancelled=false
2015-09-03 10:33:53.536 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor] -          transaction complete!
2015-09-03 10:33:53.537 [DEBUG] [b.z.i.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2015-09-03 10:33:53.537 [DEBUG] [.z.internal.ZWaveActiveBinding] - ZwaveIncomingEvent
2015-09-03 10:33:53.538 [TRACE] [b.z.i.protocol.ZWaveController] - Released. Transaction completed permit count -> 1
2015-09-03 10:33:53.538 [DEBUG] [WaveController$ZWaveSendThread] - NODE 71: Response processed after 462ms/3310ms.
2015-09-03 10:33:53.539 [TRACE] [WaveController$ZWaveSendThread] - Acquired. Transaction completed permit count -> 0
17

Hi,

I just got a response from Aeotec engineering:

When you are seeing a return of 0, then this issue is mostly done by sending the wrong sized byte into the setting.
Parameter 201 is actually only 1 byte in size. In a previous sheet i sent out, it use to be 2 byte size which could be the cause.

They’ve also sent me the latest manual: Engineering_Spec_Aeon_Multisensor_6

Chris, can you change byte size for #201 to 1, please? Then I can check.
Tamas’ problem was with parameter #111, which should be 4 bytes in size.

rgds
Markus

18

@mstormi that link for the doc is painful. I tried 3 times, getting redirected to play games and download adware. Can you not just attach it to this thread with the upload (I have not tried yet )

19

Agreed - it would be useful to be able to attach files. However, if you correctly format the text (as I’ve just done in your message) then it’s reasonably usable by posting inline. To do this, just select the log, and press the </> button.

I’ll take a look at this when I get a chance…

20

Parameter 111 is already 4 bytes long. From the log I looked at, the sensor was acking this so I’ve no reason to suspect that this isn’t working (other than Tamas doesn’t think it is :smile:). This still needs confirming from the XML from Tamas.

Will do.