Zwave and Danfoss Thermostat valve: struggling with inclusion

ariela · July 15, 2016, 2:49pm

Hi folks,

I’m not able to include my Danfoss LC-13.

My configuration:
OH2 on Debian 8
org.openhab.ui.habmin_0.1.7-SNAPSHOT.jar

Procedure:
click on search in HABmin to go to inclusion mode
click on button in the middle on Danfoss to start the inclusion

Danfoss flash quickly, then a bit less (and antenna and alarm symbols are fixed), then … nothing

My log:

2016-07-15 16:48:49.937 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller start inclusion - mode 2
2016-07-15 16:48:49.937 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Setting controller into INCLUSION mode, highPower:true networkWide:false.
2016-07-15 16:48:49.937 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 255: Creating empty message of class = AddNodeToNetwork (0x4A), type = Request (0x00)
2016-07-15 16:48:49.938 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2016-07-15 16:48:49.938 [TRACE] [wave.internal.protocol.SerialMessage] - Calculated checksum = 0x30
2016-07-15 16:48:49.938 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 81 01 30 
2016-07-15 16:48:49.938 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 81 01 30 
2016-07-15 16:48:49.938 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2016-07-15 16:48:49.938 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 0. Queue={}
2016-07-15 16:48:54.938 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2016-07-15 16:48:54.939 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2016-07-15 16:48:54.939 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2016-07-15 16:48:54.939 [TRACE] [wave.internal.protocol.SerialMessage] - Calculated checksum = 0x30
2016-07-15 16:48:54.939 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 81 01 30 
2016-07-15 16:48:54.939 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 81 01 30 
2016-07-15 16:48:54.939 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2016-07-15 16:48:59.940 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2016-07-15 16:48:59.940 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2016-07-15 16:48:59.940 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2016-07-15 16:48:59.940 [TRACE] [wave.internal.protocol.SerialMessage] - Calculated checksum = 0x30
2016-07-15 16:48:59.940 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 81 01 30 
2016-07-15 16:48:59.940 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 81 01 30 
2016-07-15 16:48:59.940 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2016-07-15 16:49:04.941 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2016-07-15 16:49:04.941 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2016-07-15 16:49:04.941 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2016-07-15 16:49:04.941 [TRACE] [wave.internal.protocol.SerialMessage] - Calculated checksum = 0x30
2016-07-15 16:49:04.941 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 81 01 30 
2016-07-15 16:49:04.941 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 81 01 30 
2016-07-15 16:49:04.941 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2016-07-15 16:49:09.942 [WARN ] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Too many retries. Discarding message: Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=81 01

can you please help here?

Thanks
Andrea

ariela · July 15, 2016, 3:27pm

It seems I’m not able to include all devices.

Only node1 in my xml devices list (the controller)

chris · July 15, 2016, 3:48pm

There seems to be an error writing to the serial port. I don’t know what would cause the input/output error, but somehow you need to solve this before the binding will work. Sorry - I know that’s not helpful, but at it’s probably nothing to do with the Danfoss and maybe something to do with the serial driver or something in that area.

ariela · July 15, 2016, 3:55pm

I’m also trying with a Wall Plug from Fibaro. Nothing.

I’ve just see 5 devices, that are most likely devices configured in my previous configuration with OH1 (in another VM).

In my previous installation (OH1) the USB port was:

crw-rw—T 1 root dialout 188, 0 Jul 15 13:01 ttyUSB0

when now:

crw-rw---- 1 root dialout 188, 0 Jul 15 17:53 ttyUSB0

I don’t understand the “T” meaning

Any idea?

Andrea

ariela · July 15, 2016, 4:01pm

Chris,

it seems now working …

Fibaro Wall Plug recognised and ready

but Danfoss is Unknown Device. Is it in the db? Do you need to do something, or I need?

Thanks

Andrea

chris · July 15, 2016, 4:04pm

What is the device model, and what is the type/id that is shown in the device attributes?

ariela · July 15, 2016, 4:10pm

mmm

this is a Danfoss LC-13 Thermostat valve.

but I can’t see device attributes nor xml file.

chris · July 15, 2016, 4:11pm

This means that it hasn’t yet downloaded this data from the device. You will need to wake up the device a few times to allow the binding to configure it.

ariela · July 15, 2016, 4:55pm

very strange problem here.

thermostat node 7 and node 9 are ok

thermostat node 8 was difficult, label recognised but unknown device.
At the end node 8 has proper description, but now when I click on button on the same device, the system is finding another node (10) that has correct label but “unknown device”.

OMG

ariela · July 15, 2016, 7:24pm

Now it seems everything’s working fine, I did the same inclusion multiple times, and now it works.

just a question, Chris.

Now I have 1-2-3-4-5-6-7 and 9-10-11 nodes, 8 is missing. Any possibility to reuse/modify the number 8?

thank you very much
Andrea

chris · July 15, 2016, 7:30pm

There is a issue that I know of that might have caused this.

github.com/eclipse-archived/smarthome

Unable to get information or update properties on existing inbox entry

opened 07:05PM - 01 Jul 16 UTC

closed 12:16PM - 16 Aug 16 UTC

cdjackson

enhancement Core Critical

As was discussed [here](https://github.com/eclipse/smarthome/pull/1213) (see [co…mment](https://github.com/eclipse/smarthome/pull/1213#issuecomment-200056170)) there is no way to get information, or even the existence of an existing inbox entry. This means that when I discover the entry a second time, if at that time I have less information about the device than I might have known earlier, this information gets overwritten by the new inbox entry. The problem in ZWave stems from the issue I outlined in the other issue -: 1) When ZWave starts, all I know is the node number, so I add a thing called Node X. The only property I know at this time is the node ID, so this is added. 2) Later, I might get more information, and then I'd give it a new label, and a few more properties. 3) Next time the binding starts, because I don't know if the thing already exists in the inbox, I add the thing again - given we're at the same stage as 1 above. The issue is then that I loose all the properties previously stored in the node other than the node ID. There needs to be a way to update an existing entry, or to get information on this entry as we previously discussed in the referenced issue. I believe that this is causing the single biggest problem with ZWave binding at the moment (or most reported issue at least).

No - there is currently no way to change the node numbering. This is allocated by the controller…