The dreaded "Failed To Go Into Learn Mode"

Hello,

Just got my Vera2. I’ve upgrade to firmware 1.1.1245 and Z-Wave 3.20, and I’m raring to add my first device.

However, I got the dreaded “Failed To Go Into Learn Mode” error. The problem seems common enough here, but I’ve searched all the threads and found no definitive answer.

I’ve restored to factory defaults, reset my Z-Wave network (even though I have no other Z-Wave devices on), rebooted many times, etc. No joy.

Any thoughts before I contact support, which I’m dreading a bit after reading through these forums?

– Charles

Charles,

Would you double check that firmware number for me?

JOD.

Sure, I confirmed that the firmware version above is correct.

Update: I tried again this morning, and now the device can learn. That’s nice, but the non-deterministic behavior is a bit creepy. Any thoughts on what got messed up in the first place, and how the problem magically went away?

– Charles

The word is that it’s a known and common Z-Wave quirk. But it’s very disheartening…

Since you have the most recent version that not even the beta testers have seen, is there anything new on the Z-Wave Options tab or Advanced tab such as changing controller roles from Secondary to Primary?

JOD.

Failed to go into learn mode is a Z-Wave quirk. It’s out of Vera’s control. We’ve seen it with the 2.78 Z-Wave firmware, and when you migrate from 2.78 to 3.20, because the conversion from 2.78 → 3.20 is undocumented and not guaranteed. However, once you’ve done a ‘ZWave network reset’ with 3.20, then you have a clean 3.20 network, and we haven’t seen this yet. So we’ve assumed this is fixed in the Z-Wave 3.20. You indicated the problem occurred AFTER doing a network reset. This is particularly troubling because it would indicate the problem is still not fixed. Can you email me directly your serial number? aaron [at] mios dot com I want to check the archived logs and confirm if this is really the case. Thanks.

I also encountered this exact same problem. I updated to the 1.1.1245 and z-wave firmware to 3.20. I did a complete zwave network reset and restored factory defaults (after mios & z-wave firmware were both upgraded with reboot in between). So it seemed like everything was completely ‘clean’ and I was starting a fresh network.

I tried several reboots and an additional zwave network reset but could not get Vera to go into learn mode. Despite having no devices and showing and having reset the network, I clicked the “hack to migrate 2.78 → 3.20” button on a whim, and that seemed to have fixed it. I was able to start adding devices at node 2 (I presume vera is #1) and go from there. Everything worked very well except for 1 of 3 kwikset locks which paired fine initially but kept failing to configure/communicate shortly thereafter. Since the 3rd or 4th unpairing/repairing, it has been working.

I have been having this issue only for Fortrezz SSA2 Siren. MCV suggested and I did update firmware to 1.1243 and reset the network etc… Still getting the same error only for this device. I’m able to add other devices like hawking motion/door sensors, Light Switches etc…

Is it something related to the Zwave chip inside my vera 2?

Thanks

I to had upgrade to 1245 and firmware 3.2. Then I couldn’t reset my zwave network until I went back to 2.78. Then I mistakenly started pairing devices before upgrading again to 3.2 and the new devices started with #10. Then I reset the zwave network and then upgraded again to 3.2 with all of the recommended selections on that page. Then I got the dreaded message above. I tried rebooting vera2, refreshing my browser with no success. Then I tried the hack without success. Then I tried the method of pairing using the button on the back of vera2 to exclude, then include and then to accept the pairing. (All three steps are important.) It worked very well for me! Also, this time when I started adding devices, they started with #3 instead of #10. I also configure each device after it is paired. Sometimes I have to wait 20-30 sec for the pairing to be complete before I can configure it. When I took vera2 with battery pack to some sensors (door/window/motion), they didn’t configure properly because I couldn’t reboot vera2 in time to do that manually. Vera doesn’t seem to be very good at configuring HRDS1 or Aeon Labs sensors or the ZIR000 motion detector so I configure each one manually after pairing with button on the back of Vera.

my god. what a mess.

when will mcv understand we need some clear cut documentation, this is crazy talk.

wake me up when this thing is out of beta and there is one path, one clear set of instruction for installation and configuration.

i had the same problem yesterday evening.

here is how i did it ( irregardles of where you are and where you come from )

  • go to zwave device and click on RESET Z-wave network.
  • REBOOT vera ( powercycle the damn thing )
  • go to settings and click → Reset to factory defaults. answer yes when asked if you are really sure.
  • do the firmware update ( if required )
  • go to Zwave settings and make sure that 3.20 is checked.
  • Reset the Z-wave network once again and wait for it to complete. this takes a while as it may update the firmware in the zwave thingie.
  • click the ‘hack’ at the bottom of the screen. let that complete.
  • click the reset once more and wait a while
  • and power cycle the thing once more.

you should now have a clean vera with 1.1.1245 firmware and 3.20 z-wave stack. the z-wave memory is initialized and empty.

Now, you can include devices .

Here is how i do this.
I don;t dilly dally around with walking around with vera. Leave it where it is.

Click Add/remove ( the + with the lightbulb ( or exclamation mark if you want ) )
click Z-wave.

Go all the way to the bottom of that screen.

Make sure it reads ‘Add’ ‘Multiple’ ‘High Power’ and set timeout to 600 seconds.
click GO and close that little tab.

Look at the top of the dashboard. there will be a zwave status screen.

Go press buttons now … Don’t do that too quick. vera needs time to process every press. It takes 10 to 15 seconds to do the ‘handshake’ with a device the first time.

I walked around with a tablet and webbrowser open on the dashboard. That way i could see the notfication every time it succesfully detected an item.
Much better feedback than a blinky light … you can actually see the devices appear. When they appear , the handshake is done.

Some items can be slow to handshake. Doorlocks , thermostats need to exchange security keys. that can take 30 seconds or more …

you will see little baloons pop up under the devices that tell you what vera is doing.

Now, when all is done.
go to the top right of the dashboard and look for the red ‘SAVE’ … hit that.

Now you can start organizing by creating 'rooms and labeleing the devices.

When you are done with that → SAVE

now , open each and every single device by clicking on its wrench icon. there is a tab with a button that says ‘Update neighbours’.
Do that for EVERY single one ( this is a manual form of healing ). Keep an eye on the balons popping up. and on the top right corner of the dashboard in the zwave baloon. it will tell you ‘heal successful’ every time.

This establishes all the routes to get from vera to all nodes.

This worked for me. ( after all my other initial troubles that simply would not work )
I may do a step by step guide with screenshots…

Don’t bother clicking the underlined hyperlinks in the vera UI ( like ‘learn more’ or ‘Luup’ or other stuff. they ALL point to outdated information. You are only going to get more confused.)

FYI, recently got this message after updating to wave 3.20. Ran The hack again, rebooted and it went away

I tried to setup a z-wave network on my newly purchased vera2 today, I could not pair anything even though it had the latest firmware update. The procedure in this topic saved my day…

Thanks

I am now having this issue. I started trying to pare some receptacles. I thought it may have been an equipment problem so tried on another known working device and had the same issue. The only thing that changed was I received an update from tech support to make it compatible with aeon labs multi-sensor. Could it be that fix that is causing it? I also did a reset of my network then restored from backup as I have a lot of automations and devices.

***UPDATE: So for the heck of it, I grabbed another plug module, this time an Intermatic Appliance Module (i.e. non-dimming), and it included just fine. My problem below seems to be isolated to the Intermatic Lamp Module (dimming) that I was attempting to include. No idea why there would be a problem - the particular module I’m trying to include was previously on the network in my weekend home. It worked just fine on that Vera Lite - why it won’t include on this one is a mystery. Again, any thoughts/suggestions appreciated.

I’m bumping this topic because I’m experiencing this for the first time now. I’ve searched the forum and have seen a range of suggested solutions, and none of them make sense to me. I’ve been able to add devices without any problem over the past couple of years, the last one being as recently as 3 months ago. Nothing has changed on my Vera Lite. This thread suggests I need to do a complete Network Reset, which doesn’t make sense to me, because I didn’t migrate from 2.78 to 3.20. I built my network fresh already on 3.20, and I certainly don’t want to re-build if I don’t need to.

I’m attempting to add an Intermatic plug module. I’ve re-booted my Vera, and that hasn’t helped. Any new thoughts/ideas on this? There are some newer threads on this topic, but they seem to apply to adding unusual devices, which is why I picked this one for a reply.

Thanks in advance for any suggestions.

Have you tried to remove. . Exclude. . The device?

Sent from my GT-N7100 using Tapatalk

Another Update…

After successfully including the Appliance Module, again, for the heck of it, I tried including the Lamp Module one more time, and it worked! I can only guess that Vera needed to “get to know” the Intermatic modules before being willing to pair up with them. Odd. So I’ve since excluded the Appliance module, and now I’ve got a working Lamp module on my network. So my problem is solved (although I have no clue how).

@konradwalsh - yes, when I couldn’t get the Lamp module to include, I explicitly tried to exclude it a couple times. That didn’t help.

Repair learning mode…

Go to ?SETUP?→?Z-wave Settings?→?Advanced? and click on ?Hack to convert 2.78 to 3.20?. Then you will need to reload the engine by pressing the ?Reload? button from the top right corner.

I’ll dig this thread up because I’m getting this for the first time in… 3-1/2 years of using Vera.

I’m on a fresh 3.20 build on a Vera 3, and I’m trying to add three Leviton relay switches. I keep getting the following message:

Add/Remove : Add new devices now... Failed to go into learn mode. Retrying...Node found.Add new devices now...
While this is going on, the Z-wave indicator on Vera is blinking slowly. If I try to exclude the switch first, Vera indicates it's an "unknown node," and doesn't remove it. Then I go into learn mode, same story.

I’ll start a case, I guess.

I had a very similar problem with Stellaz thermostats. If they have been included earlier in some way then they cannot be included again unless they are factory reset. Just doing an exclude isn’t enough. The support guys had theories about 3.20 etc. But they work fine with the old firmware also.

Skickat fr?n min GT-I9300 via Tapatalk

These are factory fresh, right out of the box.