Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


  • 0

KeyFob Waiting for wakeup to configure device on Vera


lokodomo

Question

Hi all,

 

Recently I got me a VeraSecure to replace our X10 security system and planning to replace our smart devices by Fibaro Z-wave Plus devices. I got a Fibaro KeyFob FGKF-601 to arm and disarm the system. I added it to the VeraSecure controller running the latest firmware 1.7.4971 (7.31) by selecting the Fibaro KeyFob FGKF-601 from the picklist of supported devices in the Vera Web UI. Pairing was confirmed by the green LED of the keyfob and the device showed up in the Vera Web UI with a message 'Waiting for wakeup to configure device...'. Since nothing happened after a while I woke up the keyfob using the o and + buttons, confirmed by the keyfob LED pulsing white twice. In the Web UI still nothing happened though. I searched the Internet to fix this problem, but unfortunately I was not able to find a straightforward answer. I tried some resolutions like unpair and repair, I also tried 'Configure node right now' from the Web UI to no avail. At some moment the Vera Web UI showed the battery drained to 39 percent, so there must have been some communication. When I tried to reset the keyfob, neither the menu reset nor the emergency reset worked. Pressing any button resulted in the LED blinking red. After the supplier contacted Fibaro the keyfob turned out to be defective and it was replaced. Yesterday I added the new keyfob to the VeraSecure controller and the Vera Web UI again showed the same message 'Waiting for wakeup to configure device...'. I was afraid to drain the battery again or even damage the keyfob, so I patiently waited overnight, having the keyfob on top of the VeraSecure controller, hoping automatic wake up should make a difference. Today in the web UI the device still shows 'Waiting for wakeup to configure device...'. On the dashboard it shows the message 'Device NOT reponding - Device status'. My other Fibaro devices like FGDW-002 and FGSD-002 work fine with the VeraSecure controller. I really have no clue what to do since I am new to both Vera and Z-wave. I hope someone can help me.

 

Thank you in advance,

 

Louis

Please login or register to see this attachment.

Please login or register to see this attachment.

Link to comment
Share on other sites

8 answers to this question

Recommended Posts

  • 1
2 hours ago, lokodomo said:

so I patiently waited overnight, having the keyfob on top of the VeraSecure controller, hoping automatic wake up should make a difference

I don't know about Vera But I can say, by default, this device has its wake up interval set to zero which means it never wakes up automatically. This is done to save battery.

  • Thanks 1
Link to comment
Share on other sites

  • 0
  • Inquirer
  • Thank you Peter, good to know it's never going to wake up automatically. I just noticed I forgot to mention that I did do a manual wake up of the keyfob once yesterday using the o and + buttons. It was confimed by the LED but to no avail in the web UI. After that I left it on the VeraSecure controller. I just did another manual wake up but it makes no difference, Vera is still waiting for the device to wake up.

    Link to comment
    Share on other sites

    • 1

    Sorry, no idea. A few weeks ago I tested wake up on my keyfob, I had to wake it up because I changed parameters. My controller is a HC3 and before that I had a HC2. I own three Fib Fobs and never had any problems with wake up. Maybe try to change a parameter or an association group (eg make one of the buttons turn on a relay or a dimmer directly) on Vera, wake it up and check if the device behaves as expected after that. If it doesn't, Vera missed the wake up signal or did something unexpected after inclusion. I also used one of these with other gateway software with no issues.

    • Thanks 1
    Link to comment
    Share on other sites

    • 0

    Ho there. 
    I’m afraid I have bad news for you. I also used to have Vera and I never managed to make KeyFob work with it. Some people at Vera forum say that after about 50-100 manual wake ups they managed to configure it properly, but I did around 150 wake ups and it didn’t help. Check out Vera forum, there is a separate topic about KeyFob. Looks like it is trying to send a lot of data and it just doesn’t manage to. Probably Fibaro uses some proprietary command to keep it awake on own controllers, but it doesn’t work on other controllers of course. 

    • Thanks 1
    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • 2 hours ago, petergebruers said:

    Sorry, no idea. A few weeks ago I tested wake up on my keyfob, I had to wake it up because I changed parameters. My controller is a HC3 and before that I had a HC2. I own three Fib Fobs and never had any problems with wake up. Maybe try to change a parameter or an association group (eg make one of the buttons turn on a relay or a dimmer directly) on Vera, wake it up and check if the device behaves as expected after that. If it doesn't, Vera missed the wake up signal or did something unexpected after inclusion. I also used one of these with other gateway software with no issues.

    I assigned a scene to the square button tab, and woke up the keyfob. Pressing the square button didn't start the scene, nor did the LED blink, although I don't know if it should blink. I chose the green option in the keyfob menu to remove it from the Vera, but forgot to unpair from within the Vera UI. Instead of unpairing Vera suddenly showed the battery level (100%) which at first it didn't. Still showing 'Waiting for wakeup to configure device...'. Then I did unpair the keyfob and paired it again choosing Generic Z-Wave device. Vera detected the device as keyfob and it was paired again, Vera showing 'Waiting for wakeup to configure device...'.. Several manual wake ups didn't work, so I choose the green option in the keyfob menu again, because at least that 's doing something. The battery level showed up again in the Vera UI, this time at 95%. The message now changed to 'Setting special configuration'. I'll do some more wake ups, and hope in the end it will configure much easier. So far it still shows 'Setting special configuration'. I'll get back with the result and the count of wake ups.

     

    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • It's working now.

    I tried some more wake ups and suddenly the interface showed Waiting for wakeup to configure device... again.

    A few more wake ups didn't help, so I tried the green keyfob menu option again without unpairing from Vera UI. The Vera UI showed 'Setting special configuration' again with 72% battery left.

    After that I woke up the keyfob for 125 times, unfortunately without any result.

    Then I thought maybe it's just the Vera web UI being buggy, so I unpaired the keyfob from the Vera App on an iPhone and added it again using the Vera App. The app showed 'Waiting for wakeup to configure device...', so I did.

    After that it showed the battery level 55%.

    I assigned the scene created earlier to the quare button tab and woke up the keyfob again. The the scene ran succesfully and it still works, now 47% battery left, but at least it works.

     

    Thank you both for your responses.

    King regards!

    Link to comment
    Share on other sites

    • 0
    15 hours ago, baskalex said:

    Probably Fibaro uses some proprietary command to keep it awake on own controllers, but it doesn’t work on other controllers of course.

    Nope, that cannot be true, as I wrote before... You may have missed that sentence while reading through this topic...

     

    18 hours ago, petergebruers said:

    I also used one of these with other gateway software with no issues.

     

    I did not mention exactly which ones because the oldest one is "Z-Way by Z-Wave.me

    Please login or register to see this link.

    " and I don't use it any more, it was version 2.X and I did not have any issues with Keyfob. And the other one, I needed to test ;)

     

    The second conttroller is OpenZWave 1.6 and the wake up sequence looks normal.

     

    I've set an association of the "square" button with one of my dimmers, node 9

     

    If the battery drains fast, it is more likely something keeps the device awake, as you can see the end of the process is the controller sending a "No More Information" command (which is standard Z-Wave, see "WakeUpCmd_NoMoreInformation " in the log below.

     

    Tell Vera to buy one of those FGKF-601 and look at the logs, or do a Zniffer capture...

     

    I've marked the important bits in bold and left out some of the detailed debug printing of OZW.

     

    2020-06-07 11:06:39.349 Info, Node012, Association::Set - Adding node 9 to group 3 of node 12
    2020-06-07 11:06:39.349 Detail, 
    2020-06-07 11:06:39.350 Detail, Node012, Queuing (WakeUp) AssociationCmd_Set (Node=12): 0x01, 0x0b, 0x00, 0x13, 0x0c, 0x04, 0x85, 0x01, 0x03, 0x09, 0x25, 0x1e, 0x5a
    2020-06-07 11:06:39.350 Info, Node012, Get Associations for group 3 of node 12
    2020-06-07 11:06:39.350 Detail, 
    2020-06-07 11:06:39.350 Detail, Node012, Queuing (WakeUp) AssociationCmd_Get (Node=12): 0x01, 0x0a, 0x00, 0x13, 0x0c, 0x03, 0x85, 0x02, 0x03, 0x25, 0x1f, 0x57
    2020-06-07 11:06:51.632 Detail, Node012,   Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x0c, 0x02, 0x84, 0x07, 0xbc, 0x00, 0xc0
    2020-06-07 11:06:51.633 Detail, 
    2020-06-07 11:06:51.633 Info, Node012, Received Wakeup Notification from node 12
    2020-06-07 11:06:51.633 Info, Node012,   Node 12 has been marked as awake
    2020-06-07 11:06:51.633 Detail, Node012, Queuing (WakeUp) AssociationCmd_Set (Node=12): 0x01, 0x0b, 0x00, 0x13, 0x0c, 0x04, 0x85, 0x01, 0x03, 0x09, 0x25, 0x1e, 0x5a
    2020-06-07 11:06:51.634 Detail, Node012, Queuing (WakeUp) AssociationCmd_Get (Node=12): 0x01, 0x0a, 0x00, 0x13, 0x0c, 0x03, 0x85, 0x02, 0x03, 0x25, 0x1f, 0x57
    2020-06-07 11:06:51.634 Detail, Node012, Queuing (WakeUp) WakeUpCmd_NoMoreInformation (Node=12): 0x01, 0x09, 0x00, 0x13, 0x0c, 0x02, 0x84, 0x08, 0x25, 0x20, 0x62
    2020-06-07 11:06:51.634 Detail, Node012, Notification: Notification - Node Awake
    2020-06-07 11:06:51.643 Detail, 
    2020-06-07 11:06:51.643 Info, Node012, Sending (WakeUp) message (Callback ID=0x1e, Expected Reply=0x13) - AssociationCmd_Set (Node=12): 0x01, 0x0b, 0x00, 0x13, 0x0c, 0x04, 0x85, 0x01, 0x03, 0x09, 0x25, 0x1e, 0x5a
    ... 
    2020-06-07 11:06:51.752 Detail, Node012, Removing current message
    2020-06-07 11:06:51.752 Detail, 
    2020-06-07 11:06:51.752 Info, Node012, Sending (WakeUp) message (Callback ID=0x1f, Expected Reply=0x04) - AssociationCmd_Get (Node=12): 0x01, 0x0a, 0x00, 0x13, 0x0c, 0x03, 0x85, 0x02, 0x03, 0x25, 0x1f, 0x57
    2020-06-07 11:06:51.752 Info, Node012, Encrypted Flag is 0
    ...
    2020-06-07 11:06:52.181 Info, Node012, Received Association report from node 12, group 3, containing 1 associations
    2020-06-07 11:06:52.181 Info, Node012,   The group contains:
    2020-06-07 11:06:52.181 Info, Node012,     Node 9

    2020-06-07 11:06:52.185 Detail, Node012,   Expected reply and command class was received
    2020-06-07 11:06:52.185 Detail, Node012,   Message transaction complete
    2020-06-07 11:06:52.185 Detail, 
    2020-06-07 11:06:52.185 Detail, Node012, Removing current message
    2020-06-07 11:06:52.186 Detail, Node012, Notification: Group
    2020-06-07 11:06:52.186 Detail, 
    2020-06-07 11:06:52.187 Info, Node012, Sending (WakeUp) message (Callback ID=0x20, Expected Reply=0x13) - WakeUpCmd_NoMoreInformation (Node=12): 0x01, 0x09, 0x00, 0x13, 0x0c, 0x02, 0x84, 0x08, 0x25, 0x20, 0x62
    ...
    2020-06-07 11:06:52.299 Detail, Node012, Notification: Notification - Node Asleep

    (...)

     

    When pressing the button, the light (node 9) turns on and the keyfob also sends a button press to the controller:

    2020-06-07 11:12:55.315 Detail, Node012,   Received: 0x01, 0x0d, 0x00, 0x04, 0x00, 0x0c, 0x05, 0x5b, 0x03, 0x82, 0x80, 0x01, 0xc4, 0x00, 0x60
    2020-06-07 11:12:55.316 Detail, 
    2020-06-07 11:12:55.316 Info, Node012, Received Central Scene set from node 12: scene id=1 with key Attribute 0. Sending event notification.
    2020-06-07 11:12:55.316 Detail, Node012, Initial read of value
    2020-06-07 11:12:55.316 Info, Node012, Automatically Clearing Scene 1 in 1000ms
    2020-06-07 11:12:55.317 Info, Timer: adding event in 1000 ms
    2020-06-07 11:12:55.317 Detail, Timer: waiting with timeout 1000 ms
    2020-06-07 11:12:55.317 Detail, Node012, Notification: ValueChanged CC: COMMAND_CLASS_CENTRAL_SCENE Instance: 1 Index: 1
    2020-06-07 11:12:56.317 Info, Timer: delayed event
    2020-06-07 11:12:56.318 Detail, Node012, Refreshed Value: old value=1, new value=0, type=list
    2020-06-07 11:12:56.318 Detail, Node012, Changes to this value are not verified
    2020-06-07 11:12:56.318 Detail, Timer: waiting with timeout -1 ms
    2020-06-07 11:12:56.318 Detail, Node012, Notification: ValueChanged CC: COMMAND_CLASS_CENTRAL_SCENE Instance: 1 Index: 1

    You can see the light has turned on because node 9 reports its level (99 means it is fully on)


    2020-06-07 11:12:56.608 Detail, Node009,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x09, 0x03, 0x26, 0x03, 0x63, 0xb8, 0x00, 0x04
    2020-06-07 11:12:56.608 Detail, 
    2020-06-07 11:12:56.608 Info, Node009, Received SwitchMultiLevel report: level=99
    2020-06-07 11:12:56.608 Detail, Node009, Refreshed Value: old value=0, new value=99, type=byte
    2020-06-07 11:12:56.608 Detail, Node009, Changes to this value are not verified
    2020-06-07 11:12:56.609 Detail, Node009, Notification: ValueChanged CC: COMMAND_CLASS_SWITCH_MULTILEVEL Instance: 1 Index: 0

     

    If the battery drain cannot be explained by looking at detailed Vera logs (I do not know if they exist and are user accessible, I do not own a Vera gateway) then you can investigate by using z Zniffer

     

     

    13 hours ago, lokodomo said:

    I assigned the scene created earlier to the quare button tab and woke up the keyfob again. The the scene ran succesfully and it still works, now 47% battery left, but at least it works.

    Yeah, battery drain looks a bit high but at least you've made a bit of progress. The battery can sit around that 50% level for a long time, I have 4 Key Fobs in total (on 2 networks) and I cannot remember when I last replaced one of those batteries... I think more than 2 years ago.

    Edited by petergebruers
    Link to comment
    Share on other sites

    • 0
    31 minutes ago, petergebruers said:

    Nope, that cannot be true, as I wrote before... You may have missed that sentence while reading through this topic...

    You obviously have much deeper knowledge, so I won’t even try to argue)

     

    1 hour ago, petergebruers said:

    Tell Vera to buy one of those FGKF-601 and look at the logs, or do a Zniffer capture...

    The topic on Vera forum is like 5 years old already and they are doing nothing with it. Moreover KeyFob is marked as fully compatible on their side and they have template for it. But still it doesn’t work. MiCasa Verde support is not quite there unfortunately. 

    Link to comment
    Share on other sites

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Answer this question...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×
    ×
    • Create New...