module endpoint type lookup failed

Hi, I have currently installed a trial version of Indigo on my Dad's Mac. He is using Z-Wave capable switches from Merten. They operate fine using Domoticz on a Raspi.
I excluded them on the Raspi and included them on Indigo. It is successfully recognized, it actually even recognizes it as "Merten Wall Shutter" but the last step does not identify any device type at all. This leaves us with an included Z-Wave Device, but no buttons to actually control the device (in this case shut or open the blinds). Z-Wave Debug below. Is there a way to actually assign the device type manually, e.g. by modifying some xml file or similar?

Regards,
Andreas

Z-Wave Debug intiatingSyncUI (timeout in 1500 seconds)
Z-Wave Debug SENT enterInclusionMode: 01 04 00 4A C1 70
Z-Wave Debug RCVD enterInclusionMode: 06 (ACK)
Z-Wave started controller inclusion mode
Z-Wave Debug RCVD inclusionMode ready: 01 07 00 4A 03 01 00 00 B0
Z-Wave Debug RCVD inclusionMode node found: 01 07 00 4A 03 02 00 00 B3
Z-Wave Debug RCVD inclusionMode adding slave node: 01 17 00 4A 03 03 09 10 04 09 00 72 86 70 60 85 8E 26 50 31 9E 75 EF 50 4A
Z-Wave Debug RCVD inclusionMode node respondCmds: 72 86 70 60 85 8E 26 50 31 9E 75
Z-Wave Debug RCVD inclusionMode node added: 01 07 00 4A 03 05 09 00 BD
Z-Wave Debug SENT exitInclusionMode: 01 04 00 4A 05 B4
Z-Wave Debug RCVD exitInclusionMode: 06 (ACK)
Z-Wave Debug RCVD inclusionMode finished: 01 07 00 4A 03 06 09 00 BE
Z-Wave Debug SENT getNodeProtocolInfo: 01 04 00 41 09 B3
Z-Wave Debug RCVD getNodeProtocolInfo: 01 09 01 41 C9 0C 00 04 09 00 7E (no inbound callback)
Z-Wave Debug . . getNodeProtocolInfo: node 009, class name: Window Covering
Z-Wave Debug . . getNodeProtocolInfo: class hierarchy: Routing Slave : Window Covering : -- (04 : 09 : 00)
Z-Wave Debug . . getNodeProtocolInfo: base class command: 00
Z-Wave Debug . . getNodeProtocolInfo: supported class commands: 20 60 85 86 70 8E 50 31 72 75 26 9E
Z-Wave Debug . . getNodeProtocolInfo: encrypt class commands:
Z-Wave Debug . . getNodeProtocolInfo: features: routing
Z-Wave controller included module: 009 - Window Covering
Z-Wave stopped controller inclusion mode
Z-Wave Syncing - started for "009 - Window Covering"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 09 01 01 70
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 4C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 (no inbound callback)
Z-Wave Debug . . getNodeNeighbors: nodeId 009, neighbors: 3, 4, 7
Z-Wave Syncing - retrieved module neighbors list: 3, 4, 7
Z-Wave Syncing - assigning return route to "009 - Window Covering"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 09 01 B4
Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD (no inbound callback)
Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 00 BD
Z-Wave Debug . . assignReturnRoute: node 009, success 1
Z-Wave Syncing - assigned return route
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 09 24 42 F6
Z-Wave Debug RCVD nodeInfoFrame: 01 16 00 49 84 09 10 04 09 00 72 86 70 60 85 8E 26 50 31 9E 75 EF 50 CC
Z-Wave Debug . . nodeInfoFrame: node 009, combined class list: 20v1 60v1 85v1 86v1 70v1 8Ev1 50v1 31v1 72v1 75v1 26v1 9Ev1
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 09 02 72 04 25 43 FE
Z-Wave Debug RCVD requestManufactureInfo: 01 07 00 13 43 00 00 06 AE (node ACK)
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 09 08 72 05 00 7A 40 04 00 01 BC
Z-Wave Debug . . requestManufactureInfo: node 009, manufacturerId 007A, productId 40040001
Z-Wave Debug . . requestManufactureInfo: Merten, Wall Shutter Module
Z-Wave Syncing - retrieved manufacture and model names: Merten - 007A, Wall Shutter Module - 40040001
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 09 02 86 11 25 44 18
Z-Wave Debug RCVD requestVersInfoGen: 01 07 00 13 44 00 00 9D 32 (node ACK)
Z-Wave Debug RCVD requestVersInfoGen: 01 0D 00 04 00 09 07 86 12 06 02 1B 02 03 72
Z-Wave Debug . . requestVersInfoGen: node 009, protoVers 2.27, appVers 2.03
Z-Wave Syncing - retrieved protocol version 2.27, app version 2.03
Z-Wave Debug SENT requestVersInfoCmdClass: 01 0A 00 13 09 03 86 13 60 25 45 79
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 07 00 13 45 00 00 05 AB (node ACK)
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 0A 00 04 00 09 04 86 14 60 02 0C
Z-Wave Debug . . requestVersInfoCmdClass: node 009, class command 60 using version 2
Z-Wave Debug . . requestVersInfoCmdClass: node 009, combined class list: 20v1 60v2 85v1 86v1 70v1 8Ev1 50v1 31v1 72v1 75v1 26v1 9Ev1
Z-Wave Debug SENT requestVersInfoCmdClass: 01 0A 00 13 09 03 86 13 31 25 46 2B
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 07 00 13 46 00 00 06 AB (node ACK)
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 0A 00 04 00 09 04 86 14 31 01 5E
Z-Wave Debug . . requestVersInfoCmdClass: node 009, class command 31 using version 1
Z-Wave Debug SENT requestVersInfoCmdClass: 01 0A 00 13 09 03 86 13 26 25 47 3D
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 07 00 13 47 00 00 05 A9 (node ACK)
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 0A 00 04 00 09 04 86 14 26 01 49
Z-Wave Debug . . requestVersInfoCmdClass: node 009, class command 26 using version 1
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Window Covering : -- (04 : 09 : 00, base 00)
Z-Wave Syncing - retrieved command classes: 20v1 60v2 85v1 86v1 70v1 8Ev1 50v1 31v1 72v1 75v1 26v1 9Ev1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing
Z-Wave Debug SENT requestMultiEndPointInfo: 01 09 00 13 09 02 60 07 25 48 E4
Z-Wave Debug RCVD requestMultiEndPointInfo: 01 07 00 13 48 00 00 05 A6 (node ACK)
Z-Wave Debug RCVD requestMultiEndPointInfo: 01 0A 00 04 00 09 04 60 08 00 02 96
Z-Wave Debug . . requestMultiEndPointInfo: node 009, numEndPoints 2, sameClass False, notStatic False
Z-Wave Debug SENT requestMultiEndPointDetails: 01 0A 00 13 09 03 60 09 01 25 49 E8
Z-Wave Debug RCVD requestMultiEndPointDetails: 01 07 00 13 49 00 00 06 A4 (node ACK)
Z-Wave Debug RCVD requestMultiEndPointDetails: 01 12 00 04 00 09 0C 60 0A 01 09 00 72 86 26 50 31 9E 75 D6
Z-Wave Debug . . requestMultiEndPointDetails: node 009, endPoint 1, notStatic False, class hierarchy 09 : 00
Z-Wave Debug . . requestMultiEndPointDetails: node 009, combined multi-endpoint types: 1:(09 : 00)
Z-Wave Debug . . requestMultiEndPointDetails: node 009, combined multi-endpoint classes: 1:[72 86 26 50 31 9E 75]
Z-Wave Debug SENT requestMultiEndPointDetails: 01 0A 00 13 09 03 60 09 02 25 4A E8
Z-Wave Debug RCVD requestMultiEndPointDetails: 01 07 00 13 4A 00 00 05 A4 (node ACK)
Z-Wave Debug RCVD requestMultiEndPointDetails: 01 10 00 04 00 09 0A 60 0A 02 09 00 72 86 26 50 75 7E
Z-Wave Debug . . requestMultiEndPointDetails: node 009, endPoint 2, notStatic False, class hierarchy 09 : 00
Z-Wave Debug . . requestMultiEndPointDetails: node 009, combined multi-endpoint types: 1:(09 : 00), 2:(09 : 00)
Z-Wave Debug . . requestMultiEndPointDetails: node 009, combined multi-endpoint classes: 1:[72 86 26 50 31 9E 75], 2:[72 86 26 50 75]
Z-Wave Syncing - retrieved multi-endpoint types: 1:(09 : 00), 2:(09 : 00)
Z-Wave Syncing - retrieved multi-endpoint classes: 1:[72 86 26 50 31 9E 75], 2:[72 86 26 50 75]
Z-Wave Debug device "009 - Window Covering" module endpoint type lookup failed (skipping)
Z-Wave Debug device "009 - Window Covering" module endpoint type lookup failed (skipping)
Z-Wave Debug SENT requestAssociationGroupCount: 01 09 00 13 09 02 85 05 25 4B 00
Z-Wave Debug RCVD requestAssociationGroupCount: 01 07 00 13 4B 00 00 05 A5 (node ACK)
Z-Wave Debug RCVD requestAssociationGroupCount: 01 09 00 04 00 09 03 85 06 02 79
Z-Wave Debug . . requestAssociationGroupCount: node 009, group count: 2
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 09 03 85 02 01 25 4C 03
Z-Wave Debug RCVD requestAssociations: 01 07 00 13 4C 00 00 06 A1 (node ACK)
Z-Wave Debug RCVD requestAssociations: 01 0B 00 04 00 09 05 85 03 01 05 00 7E
Z-Wave Debug . . requestAssociations: node 009, group: 1, num associations: 0, max associations: 5, replies left: 0
Z-Wave Debug . . requestAssociations: node 009, group: 1, associations: []
Z-Wave Syncing - retrieved group 1 associations: []
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 09 03 85 02 02 25 4D 01
Z-Wave Debug RCVD requestAssociations: 01 07 00 13 4D 00 00 05 A3 (node ACK)
Z-Wave Debug RCVD requestAssociations: 01 0B 00 04 00 09 05 85 03 02 05 00 7D
Z-Wave Debug . . requestAssociations: node 009, group: 2, num associations: 0, max associations: 5, replies left: 0
Z-Wave Debug . . requestAssociations: node 009, group: 2, associations: []
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Debug SENT addInterfaceAssociation: 01 0B 00 13 09 04 85 01 01 01 25 4E 05
Z-Wave Debug RCVD addInterfaceAssociation: 01 07 00 13 4E 00 00 06 A3 (node ACK)
Z-Wave Syncing - added group 1 association to interface
Z-Wave Debug . . addInterfaceAssociation: node 009, group: 1, associations: [1]
Z-Wave Syncing - created device "009 - Wall Shutter Module"
Z-Wave Syncing - complete
Z-Wave Debug device "009 - Wall Shutter Module" module endpoint type lookup failed (skipping)
Z-Wave Debug device "009 - Wall Shutter Module" module endpoint type lookup failed (skipping)
Z-Wave Debug terminatingSyncUI

[matt (support)]

Hi Andreas,

We'll need to add a device definition to Indigo for this one. Can you describe the capabilities for the module? Does it control 2 shutters/blinds? I ask because it defines 2 endpoints, which is one of the reasons Indigo's dynamic device defining didn't automatically work for it.

Hi Matt,

attached as much information as I could gather.

The flush socket is just dumb electricity. The z-wave function is actually integrated in the cover. I also found a data sheet with parameters. Last not least, I also found the device in the z-wave alliance's. library (link attached).
Reference would be "Merten 5045 - Window Covering Actuator". Additional Digits 5 and 6 are used for different colors only.
https://products.z-wavealliance.org/pro ... quencyId=1

Additional information:
- The module only supports one single shutter/blind
- it can open or shut the blinds; hitting the switch during shutting/opening stops the blind at the current position
- not sure, but as far as I can tell it is stateless, i.e. it cannot be polled to tell the current blinds' position and it is actually unaware of it
- apart from controlling the motor it has also an additional extension capability for a sun sensor by means of sticking a fiber-based cable to the window and connecting it with the switch. (we don't use it currently

Hope this gives enough information.

Also, I hope you don't mind me asking, if this is a big thing to add, i.e. matter of days or if it would be added potentially to some later release of Indigo?

Many Thanks in Advance,
Andreas

Hi Andreas

New device definitions aren’t going to be that quick unless there’s a release due imminently and it’s a quick tweak to a definition to include it.

That said, I’ve several Zwave plugins published and I’m on with another for generic Window/Blind controls that will work fine with your new module. If the wind blows in the right direction, I’ll have it out by the start/end of the weekend.

Peter


Sent from my iPhone using Tapatalk Pro

Have a go with https://github.com/howartp84/ZWaveWindo ... /tag/1.0.1

It has basic up/down support for the basic window/blind coverings that use Switch Multilevel)

Create a Window Controller device, point it at your actual Zwave device. At the moment it doesn't do anything other than pass the commands onto the actual device, but when I get to publishing state and position, it will be displayed in the Window Controller.

Then Actions > ZWave Window Controller > ...

I'll be adding multiple endpoints, different command sets (Basic, Window Covering and others thay may popup)

Peter

You guys are incredible!!! It works well at first glance. Thank you so very much. It saves us from replacing the flush sockets.
(and of course we will acquire the license

I'll let you know if I hit anything unexpected.

Best Regards,
Andreas

The Stop Command seems to have a bug.
Open and Close works fine.

Z-Wave Window Controller Error plugin does not define method cmdStop.

Regards,
Andreas

Oops

https://github.com/howartp84/ZWaveWindo ... /tag/1.0.2

Peter

[matt (support)]

Great works – thanks Peter!

Stop Command working now!

Thanks
Andreas

[matt (support)]

Indigo 7.5 is now available and includes preliminary (untested) support for the Merten Wall Shutter Module (5045). Let me know if the 2 devices it defines work correctly.

I just noticed that 7.5 has the support for the wall shutters...fabulous. I will try it, but I am remote from the installation, so it will take a while! I have not yet upgraded to 7.5:
Could you advise on how to re-assign the current installation to the supported device. Currently, it is part of the z-wave mesh and is controlled via the generic blinds plugin you provided.
Can I somehow "update" the device information and remove the generic plugin logic or do I need to go via an exclude/include process in z-wave?
Best Regards,
Andreas

[matt (support)]

You shouldn't need to exclude / re-include it, but you will need to re-sync it in Indigo. It might then change the number or order of devices shown in the device dialog (the tabbed panels). If it does, then you will probably need to modify any logic in Indigo (Trigger, Actions, Control Pages, etc.) that referenced the old devices to make sure they are referencing the correct device. You may not need to change anything, but it is possible you'll need to re-select the correct device after the re-sync.