Curtain Control Hunter Douglas (ESI) Not fully supported

I have a curtain from Forest shuttle with a Hunter Douglas (ESI) z-wave control. I presume it is a dbmz device in a Forest package.

http://elec-solutions.com/products/z-wave/dbmz.html

I can sync it to Indigo also control it but I can not:

- No updates when manually oparated
- No associations - device does not show up in the list in Indigo
- No Modify Parameters - device does not show up in the list in Indigo
- Problems with optimizing network- no ack message and after some time it is connecting
- Sometimes actions form Indigo are not working. No connection.

Is it possible to give this device fully support in Indigo. Now as we are on I7 I suppose this will be much easier than before.


Z-Wave Indigo Device "Gordijn Keuken" Z-Wave Properties:
Indigo Z-Wave Version: 2.0.31
Node ID: 17
Model: Multiposition Motor Control
Model ID: 46470002
Manufacturer: Electronic Solutions
Manufacturer ID: 0033
Protocol Version: 2.67
Application Version: 1.00
Model Definition Version: 0
Library Type: 3
Class Name: Multiposition Motor Control
Class Hierarchy: 04 : 11 : 03
Command Class Base: 26
Command Versions: 20v1 26v1 86v1 2Bv1 2Cv1 72v1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing
Neighbors: 1, 3, 4, 5, 6, 7, 8, 9, 10, 13, 15, 16, 18, 20, 21, 24, 26, 27, 28, 29, 31, 34, 44, 46, 48, 49, 61, 63, 65, 70, 76, 77, 78, 79, 82, 83, 84, 86, 87, 88, 89, 90, 92, 95, 96, 97, 98, 99, 103, 104, 107, 112, 114, 115, 116, 118
Associations: - none -
Config Values: - none -

[matt (support)]

The module is not reporting to Indigo that is supports associations or configuration parameters.

Glancing at the manual online I do see that it has some configuration parameters.

It is either not reporting its command classes correctly (a few modules have this problem), or the sync operation didn't complete 100% successfully. So try re-syncing it again a couple of times and copy/paste the Event Log results. If it is misreporting its capabilities then we can add a device definition to Indigo to force those options to be available.

Matt - Thanks for looking into the issue. I dit multiple syncs and this is the result in the log:

Z-Wave Syncing - started for "Gordijn Woonkamer"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 12 01 01 6B
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 FD D3 99 5E 06 28 01 40 21 78 EE CB C3 97 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 DE
Z-Wave Debug . . getNodeNeighbors: nodeId 018, neighbors: 1, 3, 4, 5, 6, 7, 8, 9, 10, 13, 15, 16, 17, 20, 21, 24, 26, 27, 28, 29, 31, 34, 35, 44, 46, 49, 63, 65, 70, 76, 77, 78, 79, 82, 83, 84, 86, 87, 88, 89, 90, 92, 95, 96, 97, 98, 103, 104, 105, 106, 107, 109, 112, 114, 115, 116, 118
Z-Wave Syncing - retrieved module neighbors list: 1, 3, 4, 5, 6, 7, 8, 9, 10, 13, 15, 16, 17, 20, 21, 24, 26, 27, 28, 29, 31, 34, 35, 44, 46, 49, 63, 65, 70, 76, 77, 78, 79, 82, 83, 84, 86, 87, 88, 89, 90, 92, 95, 96, 97, 98, 103, 104, 105, 106, 107, 109, 112, 114, 115, 116, 118
Z-Wave Syncing - assigning return route to "018 - Gordijn Woonkamer"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 12 01 AF
Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD
Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 00 BD
Z-Wave Debug . . assignReturnRoute: node 018, success 1
Z-Wave Syncing - assigned return route
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 12 24 37 98
Z-Wave Debug RCVD nodeInfoFrame: 01 0E 00 49 84 12 08 04 11 03 26 86 72 2B 2C E5
Z-Wave Debug . . nodeInfoFrame: node 018, combined class list: 20v1 26v1 86v1 2Bv1 2Cv1 72v1
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 12 02 72 04 25 38 9E
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 12 08 72 05 00 33 46 47 00 02 A8
Z-Wave Debug . . requestManufactureInfo: node 018, manufacturerId 0033, productId 46470002
Z-Wave Debug . . requestManufactureInfo: Electronic Solutions, Multiposition Motor Control
Z-Wave Syncing - retrieved manufacture and model names: Electronic Solutions - 0033, Multiposition Motor Control - 46470002
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 31 06 31 05 04 22 00 05 D7
Z-Wave Debug . . requestVarSensorStatus: node 049, endpoint None, type 4, raw value 2200...
Z-Wave Debug . . requestVarSensorStatus: 0.5 W (float: 0.500000)
Z-Wave Debug received "Boiler" power load to 0.5 W
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 12 02 86 11 25 39 7E
Z-Wave Debug RCVD requestVersInfoGen: 01 0D 00 04 00 12 07 86 12 03 02 43 01 00 34
Z-Wave Debug . . requestVersInfoGen: node 018, protoVers 2.67, appVers 1.00
Z-Wave Syncing - retrieved protocol version 2.67, app version 1.00
Z-Wave Debug SENT requestVersInfoCmdClass: 01 0A 00 13 12 03 86 13 26 25 3A 5B
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 0A 00 04 00 12 04 86 14 26 01 52
Z-Wave Debug . . requestVersInfoCmdClass: node 018, class command 26 using version 1
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Mulitlevel Switch : Multiposition Motor Control (04 : 11 : 03, base 26)
Z-Wave Syncing - retrieved command classes: 20v1 26v1 86v1 2Bv1 2Cv1 72v1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing
Z-Wave Syncing - complete

[matt (support)]

I don't see in the manual, nor does the device doesn't report in the Event Log, support for associations.

The manual does, however, show configuration parameters. But the log shows the module does not respond to the configuration command class (0x70).

Try turning on debug logging (Interfaces->Z-Wave->Configure... menu item) then use the Interfaces->Z-Wave->Send Raw Command menu item to send the following to the module:

0x70 0x05 0x01

Also try:

0x70 0x05 0x02
0x70 0x05 0x03

What is the Event Log results?

Also, with the debug logging still enabled, are any commands sent to Indigo when you manually press the open/close buttons on the module itself?

0x70 0x05 0x01

Also try:

0x70 0x05 0x02
0x70 0x05 0x03

What is the Event Log results?

Z-Wave sent "Gordijn Woonkamer" raw command [70 05 01]
Z-Wave Debug RCVD requestMeterLevel: 01 10 00 04 00 14 0A 32 02 21 44 00 00 0C 2A 00 00 86
Z-Wave Debug . . requestMeterLevel: node 020, endpoint None, meterType 01, raw value 4400...
Z-Wave Debug . . requestMeterLevel: 31.14 kWh (float: 31.140000)
Z-Wave Debug received "HIFI Wall Plug" energy total to 31.14 kWh
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 14 06 31 05 04 22 03 28 DC
Z-Wave Debug . . requestVarSensorStatus: node 020, endpoint None, type 4, raw value 2203...
Z-Wave Debug . . requestVarSensorStatus: 80.8 W (float: 80.800000)
Z-Wave Debug received "HIFI Wall Plug" power load to 80.8 W

2016-12-03 12:21:24.062 Z-Wave sent "Gordijn Woonkamer" raw command [70 05 02]
2016-12-03 12:21:28.724 OWServer Getting OWServer data...
2016-12-03 12:21:28.993 Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 31 06 31 05 04 22 00 05 D7
2016-12-03 12:21:28.994 Z-Wave Debug . . requestVarSensorStatus: node 049, endpoint None, type 4, raw value 2200...
2016-12-03 12:21:28.995 Z-Wave Debug . . requestVarSensorStatus: 0.5 W (float: 0.500000)
2016-12-03 12:21:28.996 Z-Wave Debug received "Boiler" power load to 0.5 W
2016-12-03 12:21:29.122 OWServer Total of 1 servers polled.
2016-12-03 12:21:29.124 OWServer Total of 4 devices updated.
2016-12-03 12:21:29.125 OWServer OWServer data parsed successfully.
2016-12-03 12:21:29.682 Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 14 06 31 05 04 22 02 A0 55
2016-12-03 12:21:29.683 Z-Wave Debug . . requestVarSensorStatus: node 020, endpoint None, type 4, raw value 2202...
2016-12-03 12:21:29.684 Z-Wave Debug . . requestVarSensorStatus: 67.2 W (float: 67.200000)
2016-12-03 12:21:29.685 Z-Wave Debug received "HIFI Wall Plug" power load to 67.2 W
2016-12-03 12:21:30.685 Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 03 06 31 05 04 22 01 B3 52
2016-12-03 12:21:30.687 Z-Wave Debug . . requestVarSensorStatus: node 003, endpoint None, type 4, raw value 2201...
2016-12-03 12:21:30.688 Z-Wave Debug . . requestVarSensorStatus: 43.5 W (float: 43.500000)
2016-12-03 12:21:30.688 Z-Wave Debug received "Espresso Machine" power load to 43.5 W
2016-12-03 12:21:30.760 Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 14 06 31 05 04 22 01 DD 2B
2016-12-03 12:21:30.761 Z-Wave Debug . . requestVarSensorStatus: node 020, endpoint None, type 4, raw value 2201...
2016-12-03 12:21:30.762 Z-Wave Debug . . requestVarSensorStatus: 47.7 W (float: 47.700000)
2016-12-03 12:21:30.763 Z-Wave Debug received "HIFI Wall Plug" power load to 47.7 W
2016-12-03 12:21:30.985 Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 31 06 31 05 04 22 00 06 D4
2016-12-03 12:21:30.987 Z-Wave Debug . . requestVarSensorStatus: node 049, endpoint None, type 4, raw value 2200...
2016-12-03 12:21:30.988 Z-Wave Debug . . requestVarSensorStatus: 0.6 W (float: 0.600000)
2016-12-03 12:21:30.988 Z-Wave Debug received "Boiler" power load to 0.6 W
2016-12-03 12:21:31.638 Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 03 06 31 05 04 22 2E FD 33
2016-12-03 12:21:31.639 Z-Wave Debug . . requestVarSensorStatus: node 003, endpoint None, type 4, raw value 222E...
2016-12-03 12:21:31.640 Z-Wave Debug . . requestVarSensorStatus: 1202.9 W (float: 1202.900000)
2016-12-03 12:21:31.641 Z-Wave Debug received "Espresso Machine" power load to 1202.9 W
2016-12-03 12:21:33.982 Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 31 06 31 05 04 22 00 05 D7
2016-12-03 12:21:33.984 Z-Wave Debug . . requestVarSensorStatus: node 049, endpoint None, type 4, raw value 2200...
2016-12-03 12:21:33.984 Z-Wave Debug . . requestVarSensorStatus: 0.5 W (float: 0.500000)
2016-12-03 12:21:33.985 Z-Wave Debug received "Boiler" power load to 0.5 W
2016-12-03 12:21:34.985 Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 31 06 31 05 04 22 00 06 D4
2016-12-03 12:21:34.986 Z-Wave Debug . . requestVarSensorStatus: node 049, endpoint None, type 4, raw value 2200...
2016-12-03 12:21:34.987 Z-Wave Debug . . requestVarSensorStatus: 0.6 W (float: 0.600000)
2016-12-03 12:21:34.988 Z-Wave Debug received "Boiler" power load to 0.6 W
2016-12-03 12:21:35.541 Z-Wave Debug SENT sendRawZwaveCommand: 01 0A 00 13 12 03 70 05 03 25 75 D1
2016-12-03 12:21:35.566 Z-Wave sent "Gordijn Woonkamer" raw command [70 05 03]
2016-12-03 12:21:36.635 Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 03 06 31 05 04 22 01 67 86
2016-12-03 12:21:36.636 Z-Wave Debug . . requestVarSensorStatus: node 003, endpoint None, type 4, raw value 2201...
2016-12-03 12:21:36.637 Z-Wave Debug . . requestVarSensorStatus: 35.9 W (float: 35.900000)
2016-12-03 12:21:36.638 Z-Wave Debug received "Espresso Machine" power load to 35.9 W
2016-12-03 12:21:37.637 Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 03 06 31 05 04 22 00 19 F9
2016-12-03 12:21:37.638 Z-Wave Debug . . requestVarSensorStatus: node 003, endpoint None, type 4, raw value 2200...
2016-12-03 12:21:37.639 Z-Wave Debug . . requestVarSensorStatus: 2.5 W (float: 2.500000)
2016-12-03 12:21:37.640 Z-Wave Debug received "Espresso Machine" power load to 2.5 W
2016-12-03 12:21:37.985 Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 31 06 31 05 04 22 00 05 D7
2016-12-03 12:21:37.987 Z-Wave Debug . . requestVarSensorStatus: node 049, endpoint None, type 4, raw value 2200...
2016-12-03 12:21:37.988 Z-Wave Debug . . requestVarSensorStatus: 0.5 W (float: 0.500000)
2016-12-03 12:21:37.988 Z-Wave Debug received "Boiler" power load to 0.5 W
2016-12-03 12:21:50.660 Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 14 06 31 05 04 22 02 41 B4
2016-12-03 12:21:50.662 Z-Wave Debug . . requestVarSensorStatus: node 020, endpoint None, type 4, raw value 2202...
2016-12-03 12:21:50.663 Z-Wave Debug . . requestVarSensorStatus: 57.7 W (float: 57.700000)
2016-12-03 12:21:50.664 Z-Wave Debug received "HIFI Wall Plug" power load to 57.7 W

Also, with the debug logging still enabled, are any commands sent to Indigo when you manually press the open/close buttons on the module itself?

No also manually press it does not report back. Only polling gives me status.

[matt (support)]

Those commands are requesting that the module return the configuration parameter values for parameters 1, 2, and 3.

You have a bunch of Z-Wave traffic going on there. I'm not sure if that is just because those devices happen to be changing their power usage around that time or not. If not, then you should change the parameters on those devices so they aren't reporting so frequently, otherwise you might have some collisions and decreased reliability for the entire network. It is possible, but somewhat doubtful, that the DBMZ did try or did eventually report back the config values but it wasn't shown in the Event Log snippets you included because of all the traffic.

So based on all this it doesn't look like the module supports associations or configurations. I suspect you have an older firmware version of the DBMZ than what the manual you linked to above is referring to. Or maybe it is an entirely different model. Regardless, from the looks of it though it doesn't support the functionality as outlined in the manual you linked to.

Thanks for the advice regarding the z-wave network traffic.

I have contacted Forest. The curtain company and indeed it is a repackaged ABMZ device. Not the DMBZ which I thought. They have send me the attached manual.

If you think that configuring parameters and associations should work based upon the manual could it indeed be a firmware issue or can I do some more troubleshooting.


http://elec-solutions.com/images/storie ... Manual.pdf

[matt (support)]

That manual doesn't mention associations either, but it does also specify configuration parameters that should work (parameters #1, 2, and 3). Based on your previous attempt at sending those raw commands:

0x70 0x05 0x01
0x70 0x05 0x02
0x70 0x05 0x03

it didn't respond to requests to retrieve the values. If you want to try again (hopefully with less noise from other Z-Wave traffic) we can double check to make sure nothing is being returned. If there isn't then I'm not sure what the problem is, but maybe you have an older firmware version that doesn't support the configuration commands.