Cheap ZWave.Me Key Fob / Devolo Home Control 9360 / Fibaro POPE009204 Device Type

Devices & Integrations Community Created Device Types
1

I picked up on of these Zwave.Me Key Fob’s recently at the time it only cost £27 inc delivery from amazon. but i can see other sites selling this for £33 inc delivery so its still one of the cheapest zwave key fobs around its also sold as a Devolo Home Control 9360 & Fibaro POPE009204 as well, and is a really good size, its not bulky at all.

anyway it would not work with ST, but i have created an initial device type. it does work really well and will recognise pushed, held and double clicked values, meaning you can assign 12 different actions to the remote.

to assist in using this i have amended ST’s Button Controller App to now have a double click field to configure, i have tested this also and it works great.

I hope this helps someone out, i have just got my orders in for more before they sell out :smile:

Enjoy

https://github.com/fuzzysb/SmartThings/blob/master/DeviceTypes/fuzzysb/ZWave.Me%20KeyFob/zmwave.me_keyfob.groovy

The smart app will allow double clicks to be used

1 Like
2

I have just seen that @adamv created a device type & smartapp that dims, but doesn’t include double click. i do wish i had spotted that as it would have saved me some time :), but i suppose now you have two options, one to assign 12 actions to the remote, and another for dimming lighting control.

I wanted mine, more for security and lock control than lighting.

3

Hi, thanks for the code - was just what I was looking for…except it doesn’t work for me :frowning:
Would you be willing to help? I am getting these errors if they mean anything:

`
e4920dc0-eeb9-4167-a18a-692a68119047

        19:42:43:
        error
        groovy.lang.MissingMethodException: No signature of 
    method: script1452799895725364840908.zwaveEvent() is applicable for 
    argument types: 
    (physicalgraph.zwave.commands.securityv1.SecurityMessageEncapsulation) 
    values: [SecurityMessageEncapsulation(commandByte: [31, 0, 2], 
    commandClassIdentifier: 91, commandIdentifier: 3, reserved13: 0, 
    secondFrame: false, sequenceCounter: 0, sequenced: false)]
    Possible 
    solutions: 
    zwaveEvent(physicalgraph.zwave.commands.batteryv1.BatteryReport), 
    zwaveEvent(physicalgraph.zwave.commands.sceneactivationv1.SceneActivationSet),
     zwaveEvent(physicalgraph.zwave.commands.wakeupv1.WakeUpNotification), 
    createEvent(java.util.Map) @ line 114

        
            e4920dc0-eeb9-4167-a18a-692a68119047
        
        19:42:43:
        debug
        Parsed Command: 
    SecurityMessageEncapsulation(commandByte: [31, 0, 2], 
    commandClassIdentifier: 91, commandIdentifier: 3, reserved13: 0, 
    secondFrame: false, sequenceCounter: 0, sequenced: false)

        
            e4920dc0-eeb9-4167-a18a-692a68119047
        
        19:42:43:
        debug
        RAW command: zw device: 11, command: 9881, payload: 00 5B 03 1F 00 02 

        
            e4920dc0-eeb9-4167-a18a-692a68119047
        
        19:42:42:
        error
        groovy.lang.MissingMethodException: No signature of 
    method: script1452799895725364840908.zwaveEvent() is applicable for 
    argument types: 
    (physicalgraph.zwave.commands.securityv1.SecurityMessageEncapsulation) 
    values: [SecurityMessageEncapsulation(commandByte: [31, 0, 2], 
    commandClassIdentifier: 91, commandIdentifier: 3, reserved13: 0, 
    secondFrame: false, sequenceCounter: 0, sequenced: false)]
    Possible 
    solutions: 
    zwaveEvent(physicalgraph.zwave.commands.batteryv1.BatteryReport), 
    zwaveEvent(physicalgraph.zwave.commands.sceneactivationv1.SceneActivationSet),
     zwaveEvent(physicalgraph.zwave.commands.wakeupv1.WakeUpNotification), 
    createEvent(java.util.Map) @ line 114

        
            e4920dc0-eeb9-4167-a18a-692a68119047
        
        19:42:42:
        debug
        Parsed Command: 
    SecurityMessageEncapsulation(commandByte: [31, 0, 2], 
    commandClassIdentifier: 91, commandIdentifier: 3, reserved13: 0, 
    secondFrame: false, sequenceCounter: 0, sequenced: false)

        
            e4920dc0-eeb9-4167-a18a-692a68119047
        
        19:42:42:
        debug
        RAW command: zw device: 11, command: 9881, payload: 00 5B 03 1F 00 02 

        
            e4920dc0-eeb9-4167-a18a-692a68119047
        
        19:42:42:
        error
        groovy.lang.MissingMethodException: No signature of 
    method: script1452799895725364840908.zwaveEvent() is applicable for 
    argument types: 
    (physicalgraph.zwave.commands.securityv1.SecurityMessageEncapsulation) 
    values: [SecurityMessageEncapsulation(commandByte: [31, 0, 2], 
    commandClassIdentifier: 91, commandIdentifier: 3, reserved13: 0, 
    secondFrame: false, sequenceCounter: 0, sequenced: false)]
    Possible 
    solutions: 
    zwaveEvent(physicalgraph.zwave.commands.batteryv1.BatteryReport), 
    zwaveEvent(physicalgraph.zwave.commands.sceneactivationv1.SceneActivationSet),
     zwaveEvent(physicalgraph.zwave.commands.wakeupv1.WakeUpNotification), 
    createEvent(java.util.Map) @ line 114

        
            e4920dc0-eeb9-4167-a18a-692a68119047
        
        19:42:42:
        debug
        Parsed Command: 
    SecurityMessageEncapsulation(commandByte: [31, 0, 2], 
    commandClassIdentifier: 91, commandIdentifier: 3, reserved13: 0, 
    secondFrame: false, sequenceCounter: 0, sequenced: false)

        
            e4920dc0-eeb9-4167-a18a-692a68119047
        
        19:42:42:
        debug
        RAW command: zw device: 11, command: 9881, payload: 00 5B 03 1F 00 02

`

Thanks!

4

can you confirm which keyfob you are using? as your replies are coming back as security encapsulated commands which mine does not and the manual for the device does not allow this to be configured.

If this is needed i can add the functions to read the encapsulated values, but i am surprised that yours is responding that way.

5

Hey! thanks for the reply!
Yeah I thought it was using the security method. That makes it sound like I know what I’m talking about haha!
The keyfob looks exactly the same as in your picture. The part number is ZME_KFOB.
Its a z-wave.me keyfob.
It says in the manual if the controller supports secure communication the keyfob will use that communication.
Here is the link
http://www.ebay.co.uk/itm/321967362689?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT
UK based keyfob.
Thanks for your help!

6

ok mine is KME_KFOB2. Hopefully the rest should be the same. I will update the code to receive and send encapsulated security mesages, this wont be until tomorrow though

7

Fingers crossed it will be the same!
That would be great - tomorrow is fine.
I appreciate you helping.

8

Hi,
Just to let you know, I decided to crash course myself and write (well…combine) your controller with the Secure wall controller written by @AdamV
So I have the controller all working now for my keyfob.
I had to change the scene numbers for the keyfob as they seemed to be a new set of numbers for button 3 and 4 though.
I will post the code up on the forum for the keyfob and obviously mention you and AdamV as the original writers!
Thanks!

9

@milesfrankland i literally just finished the device type to include secure comms, it online now.

I am very curious as to what you parameter 1 & 2 are set to, are they set to the value of 0? i know the payload changes if it is set to values of 1 or 2. you can list the current remote parameters on my device type by running the listCurrentParams command from the IDE when the device type is installed on the device.

so my next question is, are the double clicks working on your device type?

Regards

Stuart Buchanan

10

I i received another fob in the mail today, with my device type v1.1, button 1 would not work with this fob with newer firmware.

this updated device type fixes that and it works on both the fobs i have.

I have just updated my device type to v1.2 and its available on the github link above

11

You’ll have to bear with me as I am a new smartthings user! I have found the command box on the device handler page after installing the handler into the device. But when I type what you said into there and press the arrow button it doesn’t do anything. Have I done it correct?

12

You don’t need to type a command, there is a listcurrentparams button you can click just under the configure button once you have installed the device type on the device. But this will only return data once you have put the device into inclusion mode just before you click the button

13

Jackpot:

55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:58: debug Parsed 'zw device: 14, command: 7006, payload: 16 01 00 ' to null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:58: debug Parse returned null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:58: debug Keyfob parameter '22' with a byte size of '1' is set to '[0]' 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:58: debug Parsed 'zw device: 14, command: 7006, payload: 15 01 01 ' to null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:58: debug Parse returned null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:58: debug Keyfob parameter '21' with a byte size of '1' is set to '[1]' 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:57: debug Parsed 'zw device: 14, command: 7006, payload: 0E 01 04 ' to null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:57: debug Parse returned null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:57: debug Keyfob parameter '14' with a byte size of '1' is set to '[4]' 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:57: debug Parsed 'zw device: 14, command: 7006, payload: 0D 01 04 ' to null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:57: debug Parse returned null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:57: debug Keyfob parameter '13' with a byte size of '1' is set to '[4]' 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:57: debug Parsed 'zw device: 14, command: 7006, payload: 0C 01 04 ' to null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:57: debug Parse returned null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:57: debug Keyfob parameter '12' with a byte size of '1' is set to '[4]' 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:52: debug Parsed 'zw device: 14, command: 8503, payload: 05 0A 00 01 ' to ['descriptionText':Keyfob: AssociationReport(groupingIdentifier: 5, maxNodesSupported: 10, nodeId: [1], reportsToFollow: 0), 'isStateChange':false, 'displayed':false, 'linkText':'Keyfob'] 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:52: debug Parse returned ['descriptionText':Keyfob: AssociationReport(groupingIdentifier: 5, maxNodesSupported: 10, nodeId: [1], reportsToFollow: 0), 'isStateChange':false, 'displayed':false, 'linkText':'Keyfob'] 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:52: debug return result of Zwave Event 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:52: debug Parsed 'zw device: 14, command: 8503, payload: 04 0A 00 01 ' to ['descriptionText':Keyfob: AssociationReport(groupingIdentifier: 4, maxNodesSupported: 10, nodeId: [1], reportsToFollow: 0), 'isStateChange':false, 'displayed':false, 'linkText':'Keyfob'] 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:52: debug Parse returned ['descriptionText':Keyfob: AssociationReport(groupingIdentifier: 4, maxNodesSupported: 10, nodeId: [1], reportsToFollow: 0), 'isStateChange':false, 'displayed':false, 'linkText':'Keyfob'] 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:52: debug return result of Zwave Event 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:52: debug Parsed 'zw device: 14, command: 8503, payload: 03 0A 00 01 ' to ['descriptionText':Keyfob: AssociationReport(groupingIdentifier: 3, maxNodesSupported: 10, nodeId: [1], reportsToFollow: 0), 'isStateChange':false, 'displayed':false, 'linkText':'Keyfob'] 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:52: debug Parse returned ['descriptionText':Keyfob: AssociationReport(groupingIdentifier: 3, maxNodesSupported: 10, nodeId: [1], reportsToFollow: 0), 'isStateChange':false, 'displayed':false, 'linkText':'Keyfob'] 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:52: debug return result of Zwave Event 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:52: debug Parsed 'zw device: 14, command: 8503, payload: 02 0A 00 01 ' to ['descriptionText':Keyfob: AssociationReport(groupingIdentifier: 2, maxNodesSupported: 10, nodeId: [1], reportsToFollow: 0), 'isStateChange':false, 'displayed':false, 'linkText':'Keyfob'] 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:52: debug Parse returned ['descriptionText':Keyfob: AssociationReport(groupingIdentifier: 2, maxNodesSupported: 10, nodeId: [1], reportsToFollow: 0), 'isStateChange':false, 'displayed':false, 'linkText':'Keyfob'] 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:52: debug return result of Zwave Event 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug Parsed 'zw device: 14, command: 8503, payload: 01 0A 00 ' to ['descriptionText':Keyfob: AssociationReport(groupingIdentifier: 1, maxNodesSupported: 10, nodeId: [], reportsToFollow: 0), 'isStateChange':false, 'displayed':false, 'linkText':'Keyfob'] 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug Parse returned ['descriptionText':Keyfob: AssociationReport(groupingIdentifier: 1, maxNodesSupported: 10, nodeId: [], reportsToFollow: 0), 'isStateChange':false, 'displayed':false, 'linkText':'Keyfob'] 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug return result of Zwave Event 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug Parsed 'zw device: 14, command: 8503, payload: 01 0A 00 ' to ['descriptionText':Keyfob: AssociationReport(groupingIdentifier: 1, maxNodesSupported: 10, nodeId: [], reportsToFollow: 0), 'isStateChange':false, 'displayed':false, 'linkText':'Keyfob'] 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug Parse returned ['descriptionText':Keyfob: AssociationReport(groupingIdentifier: 1, maxNodesSupported: 10, nodeId: [], reportsToFollow: 0), 'isStateChange':false, 'displayed':false, 'linkText':'Keyfob'] 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug return result of Zwave Event 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug Parsed 'zw device: 14, command: 7006, payload: 1E 01 01 ' to null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug Parse returned null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug Keyfob parameter '30' with a byte size of '1' is set to '[1]' 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug Parsed 'zw device: 14, command: 7006, payload: 19 01 00 ' to null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug Parse returned null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug Keyfob parameter '25' with a byte size of '1' is set to '[0]' 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug Parsed 'zw device: 14, command: 7006, payload: 1E 01 01 ' to null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug Parse returned null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug Keyfob parameter '30' with a byte size of '1' is set to '[1]' 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug Parsed 'zw device: 14, command: 7006, payload: 18 01 00 ' to null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug Parse returned null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug Keyfob parameter '24' with a byte size of '1' is set to '[0]' 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:50: debug Parsed 'zw device: 14, command: 7006, payload: 18 01 00 ' to null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:50: debug Parse returned null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:50: debug Keyfob parameter '24' with a byte size of '1' is set to '[0]' 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:49: debug Listing of current parameter settings of Keyfob 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:49: debug Parsed 'zw device: 14, command: 7006, payload: 18 01 00 ' to null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:49: debug Parse returned null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:49: debug Keyfob parameter '24' with a byte size of '1' is set to '[0]' 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:49: debug Parsed 'zw device: 14, command: 7006, payload: 16 01 00 ' to null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:49: debug Parse returned null 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:49: debug Keyfob parameter '22' with a byte size of '1' is set to '[0]' 55a6995e-aac7-4f39-bf7e-9ad27299f793 08:55:31: debug Listing of current parameter settings of Keyfob

14

@milesfrankland I think you must have had concurrent listcurrentparameters running at the same time as there is repeated values. this usually happens if it takes me multiple attempt to get the device into inclusion mode. you do not have option 1 & 2 listed there and the association group reports which should be the first thing returned are in the middle of that list. if it doesn’t go into inclusion mode first time, leave it 2-3 minutes before you attempt again as the hub will be still trying to send the commands for the first attempt.

its a pain as these remotes aren’t the easiest to get into inclusion mode.

if done right your log should start like the below if you are reading from the bottom up

55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug return result of Zwave Event
55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug Parsed 'zw device: 14, command: 8503, payload: 01 0A 00 ’ to [‘descriptionText’:Keyfob: AssociationReport(groupingIdentifier: 1, maxNodesSupported: 10, nodeId: [], reportsToFollow: 0), ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Keyfob’]
55a6995e-aac7-4f39-bf7e-9ad27299f793 08:56:51: debug Parse returned [‘descriptionText’:Keyfob: AssociationReport(groupingIdentifier: 1, maxNodesSupported: 10, nodeId: [], reportsToFollow: 0), ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Keyfob’]
55a6995e-aac7-4f39-bf7e-9ad27299f793 08:55:31: debug Listing of current parameter settings of Keyfob

15

It seems my fob doesnt want to go into learn mode again…
I do remember I had to click the button twice to get it to work so you are probably correct.
I will keep trying!

16

Frank, i have just realised that the second fob i purchased in the manual is according the manual that came with it a ZME_KFOB_S Version 1.0

is that the same as yours?

if so i have found that according to the manual you can get it to list parameters by holding all 4 buttons to get into management mode then press button 2, then click listcurrentparams. this works for that one, but i cannot get back into inclusion it seems unless i reset first.

if that it is the same, my latest device type should now work with yours

Regards

Stuart Buchanan

17

if anyone is interested, these are back on sale for £27.50 inc free delivery in the UK at Amazon