Zipato remote?

I picked up a Zipato keyfob remote: https://www.zipato.com/product/keyfob-5-remote

I've added it as a device, but I can't figure out how to get the button presses to be events that Indigo can react to. I set up device 1 (Indigo/Z-Stick) as a responding device for all nine of its groups, but I don't see anything in the logs when I press a button.

What am I missing?

(Device properties attached)

[matt (support)]

That module doesn't have a device definition in Indigo yet. Do you have a PDF manual or technical docs for it? Their web site doesn't seem to have anything.

Also, try turning on Indigo's Z-Wave debug logging checkbox (via the Interfaces->Z-Wave->Configure... menu item) and see if any commands are logged in the Event Log window when you press the buttons on it. If there are then you can use the Z-Wave Scene Controller plugin to create Triggers for them.

Unfortunately, no, I don't have any technical documentation for this device. I (mistakenly) assumed that Z-Wave remotes/buttons/controllers followed some known device spec.

I haven't gotten the Scene Controller plug-in to react usefully. With debugging enabled, when I press any button I get:

Code: Select all

   Z-Wave Scene Controller Debug   Node ID 37 found in controllerIDs

The remote does have Z-Wave address #37, but nothing here about the button ID.

Enabling raw Z-Wave debugging, here's what I see for each of the buttons (before and after pressing the center toggle, which changes from "button 1-4" mode to "button 5-8" mode.

Code: Select all

button 1/5:   Z-Wave Debug      RCVD requestReply1: 01 0E 00 04 00 25 08 94 01 8F 00 00 00 00 03 C1 (hex)
button 2/6:   Z-Wave Debug      RCVD requestReply1: 01 0E 00 04 00 25 08 94 01 B3 00 00 00 00 04 FA (hex)
button 3/7:   Z-Wave Debug      RCVD requestReply1: 01 0E 00 04 00 25 08 94 01 C4 00 00 00 00 02 8B (hex)
button 4/8:   Z-Wave Debug      RCVD requestReply1: 01 0E 00 04 00 25 08 94 01 CD 00 00 00 00 05 85 (hex)
toggle: nothing
button 1/5:   Z-Wave Debug      RCVD requestReply1: 01 0E 00 04 00 25 08 94 01 54 00 00 00 00 13 0A (hex)
button 2/6:   Z-Wave Debug      RCVD requestReply1: 01 0E 00 04 00 25 08 94 01 5C 00 00 00 00 16 07 (hex)
button 3/7:   Z-Wave Debug      RCVD requestReply1: 01 0E 00 04 00 25 08 94 01 6E 00 00 00 00 14 37 (hex)
button 4/8:   Z-Wave Debug      RCVD requestReply1: 01 0E 00 04 00 25 08 94 01 7A 00 00 00 00 17 20 (hex)


I don't have a working knowledge of raw Z-Wave (is there a handy reference anywhere?), but I see:

byte 6 is the source address (device 37, 0x25)
byte 10 is an incrementing sequence number (+1 for each time I press)
byte 15 is the button ID
byte 16 varies... a checksum?

What kinds of commands are these?

Ah ha. Some poking around led me to a couple of useful documents: Z-Way controller reference which mentioned that the 0x94 in that is "SimpleAVControl".

Then I found these: these manuals (sadly, not first-party hosted) which seem to be for different brandings of this device, and they mention that configuration parameter 7 switches between AV control and lighting control.

So I set param 7 to 65 (it had been at 64.. I set it to 65 to preserve whatever bit 6 was doing. If I just set it to 1 it was the same as below plus a battery status update on every press), and now the scene controller has a lot more to say when I press a button.

Code: Select all

   Z-Wave Debug                    RCVD basicSetState: 01 09 00 04 00 25 03 20 01 FF 0A
   Z-Wave Debug                    . .  basicSetState: node 037, endpoint None, value 255 (no node dispatch)
   Z-Wave Scene Controller Debug   Node ID 37 found in controllerIDs
   Z-Wave Scene Controller Debug   -----
   Z-Wave Scene Controller Debug   On/Off Command received:
   Z-Wave Scene Controller Debug   Raw command: 01 09 00 04 00 25 03 20 01 FF 0A
   Z-Wave Scene Controller Debug   Node:      37
   Z-Wave Scene Controller Debug   NodeID:    37
   Z-Wave Scene Controller Debug   ActionRaw: 1
   Z-Wave Scene Controller Debug   Button:    1
   Z-Wave Scene Controller Debug   ActionID:  11
   Z-Wave Scene Controller Debug   Action:    On
   Z-Wave Scene Controller Debug   403 i: 0
   Z-Wave Scene Controller Debug   410 dA List: deviceAddress
   Z-Wave Scene Controller Debug   414 dAddress: 1793583826
   Z-Wave Scene Controller Debug   421 dDev: address : 37


But it does exactly that - same button number, same action - for all of the buttons. So my thinking now is that it's just sending an "On" command to whatever association group it has for that button, and since I set that to 1 for everything, it's sending the same command to the Z-Stick for everything.

Maybe I'd be better off in AV mode and matching raw commands?

Matching AV commands seems to work.

Found the paper manual, which does seem to match the links above. I have a scan of the manual, though I can't attach PDFs here.

[matt (support)]

As you discovered, we need to add support to Indigo for the SimpleAVControl Command Class (0x94). This is more than a device definition change, so I'll add it to the Z-Wave feature request list.

I'm not sure why it is sending the same scene button number for all buttons. Definitely doesn't seem like it should do that.

Sounds like you were able to catch the commands with the Trigger to match the raw Z-Wave packets you identified?