Zipato shutter switch not working

Hardware Home Automation
1

I got a Zipato shutter controller (this one: https://www.intellihome.be/en/zipato-z-wave-plus-micro-module-controller-eu.html)

Installation went fine, the switch itself still works as before, including the module in the z-wave network went very smooth. However, when I try to trigger the module from openhab, nothing happens. habmin shows that the node is alive and that a signal was received.

any clues on where to look?

openhab 1.8.3
z-wave binding 1.8.0

config item:
Rollershutter MasterBedroomShutterSide “Rolluik slaapkamer zijkant [(%d)]” { zwave=“9:command=switch_multilevel,invert_state=false,invert_percent=false” }

config sitemap:
Slider item=MasterBedroomShutterSide label=“Slaapkamer rolluik zijkant” icon=“rollershutter” sendFrequency=400

2

That’s a pretty old binding, first thing I would do is update to the latest snapshot.
https://openhab-ci.innoq.io/jenkins/view/openHAB/job/openhab-1/org.openhab.binding$org.openhab.binding.zwave/
If it still does not work provide a debug log.

3

just updated to the latest one over VPN, it does show a bunch more properties in habmin so I’m carefully optimistic, but I won’t be able to test it until tonight. thx for the tip :slight_smile:

4

still not working, here’s a snippet from the debug log:

17:16:21.844 [DEBUG] [o.i.r.i.resources.ItemResource:205 ] - Received HTTP POST request at ‘items/MasterBedroomShutterSide/’ with value ‘30’.
17:16:21.857 [DEBUG] [ZWaveMultiLevelSwitchConverter:185 ] - Multilevel Switch MultiLevelPercentCommandConverter
17:16:21.860 [DEBUG] [veMultiLevelSwitchCommandClass:166 ] - NODE 9: Creating new message for command SWITCH_MULTILEVEL_SET
17:16:21.866 [DEBUG] [o.b.z.i.protocol.SerialMessage:115 ] - NODE 9: Creating empty message of class = SendData (0x13), type = Request (0x00)
17:16:21.873 [DEBUG] [b.z.i.protocol.ZWaveController:976 ] - Callback ID = 29
17:16:21.883 [DEBUG] [b.z.i.protocol.ZWaveController:651 ] - Enqueueing message. Queue length = 1
17:16:21.883 [DEBUG] [WaveController$ZWaveSendThread:1295 ] - Took message from queue for sending. Queue length = 0
17:16:21.896 [DEBUG] [o.b.z.i.protocol.SerialMessage:255 ] - Assembled message buffer = 01 0A 00 13 09 03 26 01 1E 25 1D ED
17:16:21.901 [DEBUG] [WaveController$ZWaveSendThread:1355 ] - NODE 9: Sending REQUEST Message = 01 0A 00 13 09 03 26 01 1E 25 1D ED
17:16:21.913 [DEBUG] [eController$ZWaveReceiveThread:1601 ] - Receive Message = 01 04 01 13 01 E8
17:16:21.924 [DEBUG] [b.z.i.protocol.ZWaveController:1244 ] - Receive queue TAKE: Length=0
17:16:21.924 [DEBUG] [eController$ZWaveReceiveThread:1517 ] - Receive queue ADD: Length=1
17:16:21.927 [DEBUG] [o.b.z.i.protocol.SerialMessage:255 ] - Assembled message buffer = 01 04 01 13 01 E8
17:16:21.930 [DEBUG] [b.z.i.protocol.ZWaveController:1245 ] - Process Message = 01 04 01 13 01 E8
17:16:21.933 [DEBUG] [b.z.i.protocol.ZWaveController:200 ] - Message: class = SendData (0x13), type = Response (0x01), payload = 01 , callbackid = 0
17:16:21.936 [DEBUG] [b.z.i.p.s.SendDataMessageClass:39 ] - NODE 9: Sent Data successfully placed on stack.
17:16:21.940 [DEBUG] [eController$ZWaveReceiveThread:1601 ] - Receive Message = 01 05 00 13 1D 00 F4
17:16:21.949 [DEBUG] [b.z.i.protocol.ZWaveController:1244 ] - Receive queue TAKE: Length=0
17:16:21.955 [DEBUG] [o.b.z.i.protocol.SerialMessage:255 ] - Assembled message buffer = 01 07 00 13 1D 00 00 00 F6
17:16:21.958 [DEBUG] [b.z.i.protocol.ZWaveController:1245 ] - Process Message = 01 07 00 13 1D 00 00 00 F6
17:16:21.961 [DEBUG] [b.z.i.protocol.ZWaveController:200 ] - Message: class = SendData (0x13), type = Request (0x00), payload = 1D 00 , callbackid = 0
17:16:21.962 [DEBUG] [eController$ZWaveReceiveThread:1517 ] - Receive queue ADD: Length=0
17:16:21.970 [DEBUG] [b.z.i.p.s.SendDataMessageClass:74 ] - NODE 9: SendData Request. CallBack ID = 29, Status = Transmission complete and ACK received(0)
17:16:21.979 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:83 ] - Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 09 03 26 01 1E , callbackid = 29
17:16:21.983 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:84 ] - Recv message Message: class = SendData (0x13), type = Request (0x00), payload = 1D 00 , callbackid = 0
17:16:21.988 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:85 ] - Checking transaction complete: Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 09 03 26 01 1E , callbackid = 29
17:16:21.994 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:96 ] - Checking transaction complete: Recv message Message: class = SendData (0x13), type = Request (0x00), payload = 1D 00 , callbackid = 0
17:16:21.997 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:99 ] - Checking transaction complete: class=SendData, callback id=29, expected=SendData, cancelled=false transaction complete!
17:16:22.001 [DEBUG] [b.z.i.protocol.ZWaveController:668 ] - NODE 9: Notifying event listeners: ZWaveTransactionCompletedEvent
17:16:22.005 [DEBUG] [.z.internal.ZWaveActiveBinding:455 ] - ZwaveIncomingEvent
17:16:22.008 [DEBUG] [WaveController$ZWaveSendThread:1430 ] - NODE 9: Response processed for callback id 29 after 104ms/2827ms.

5

From my limited point of view nothing looks wrong, if you put that log into the log viewer it looks okay:

zippato.JPG1172×207 24.2 KB

The only difference to my working (although a fibaro rollershutter) config are
Rollershutter FibFGR222_Kitchen_East "Shutter Kitchen East [%d %%]" {zwave="11:command=switch_multilevel,invert_state=false,invert_percent=true"}
the two percent signs in the label definition but actually I don’t think that makes a difference.

I suggest pinging @chris if he has time to take a quick look 


6

What happens if you do a

Switch item=MasterBedroomShutterSide

instead of

Slider item=MasterBedroomShutterSide label="Slaapkamer rolluik zijkant" icon="rollershutter" sendFrequency=400

7

same issue.
I’m actually starting to think that the module is broken, if I use the manual switch I hear the relay clicking inside of the module but for operating via z-wave it contains a separate relay and I never heard that one. Since the command does seem to arrive correctly I would assume to at least hear the click.

I’ve got a second one of those modules waiting to get installed, going to do that somewhere during the weekend and see how that turns out

8

well, I just installed the second module and I’m having the exact same issue


any other ideas?

9

No, sorry . We have to ask @chris

10

Sorry - I don’t see anything wrong from the log. The command is being sent


Have you calibrated the roller shutter? Maybe the device is ignoring commands over zwave if it’s not calibrated or something like that?

11

it’s calibrated yes. with the new one I do see some messages popping up in the log about a missing converter, is a converter needed for these modules?

12

Yes - a converter is always used to convert data types. Maybe you could post the warning?

13

2016-12-06 18:01:41.967 [WARN ] [i.c.ZWaveBinarySwitchConverter] - NODE 9: No converter found for item = MasterBedroomShutterSide, endpoint = 0, ignoring command.

14

Sorry - can you also provide the item definition so we can see what converter and command class it’s trying to use


15

this was my latest attempt:

Rollershutter MasterBedroomShutterSide “Rolluik slaapkamer zijkant [(%d )]” { zwave=“9:invert_state=true” }
Rollershutter MasterBedroomStreetSide “Rolluik slaapkamer straatkant [(%d)]” { zwave=“10:invert_state=true” }

Frame {
Switch item=MasterBedroomShutterSide label=“Rolluik master bedroom zijkant [(%d)]” mappings=[UP=“Omhoog”, STOP=“X”, DOWN=“Omlaag”]
Switch item=MasterBedroomStreetSide label=“Rolluik master bedroom straatkant [(%d)]” mappings=[UP=“Omhoog”, STOP=“X”, DOWN=“Omlaag”]
}

I think the Converter warning showed up when I added Switch_Binary command

16

The problem is probably that you don’t have a command class specified for the MasterBedroomShutterSide item. This means (I think) it will use the BASIC class for sending, and all classes for receiving. I would always recommend to specify the command class you want to use.

17

figured it out, the issue was that the module was set to 2-pushbutton mode, switched the parameter to 1-button and everything started working!

thanks for the assist everyone

1 Like