OK I’m confused… prior to ver 1338 I was able to add/exclude and update my HA09’s with relative ease. I happen to change a switch and needed to re-program the new device address via scene into my bedroom controller. When I look at UI4 gui I get the following message indicating that Vera see the controller but indicates it can’t go into learn mode, message is read bottom oldest to top newest.
“Found an existing node
Node found. Add new devices now… Failed to go into learn mode. Retrying…Found an existing node Node found. Add new devices now… Failed to go into learn mode. Retrying…Added node 62 Device: 95 Node found. Add new devices now…”
Here are the steps that I’ve done;
depress the little button on Vera back to “include”, verified via UI4 gui
depress the “include” button for 5 seconds on the HA09 remote, get the flashing green and red lights
depress the “off” on position 1, the remote begins to flash
Vera add the new device and then failed to go into learn mode, and the retries several times before timing out.
remote green light just flashes.
I’ve replace the controller’s batteries (just in case), I’ve also verified the same problem using a second controller (my wife’s). Any help would be greatly appreciated as I now have two bedside controllers FUBAR! Mike
“Failed to go into learn mode” is a Vera issue and claimed to be a general Z-Wave issue. It’s not an issue of the remote.
Just keep trying and usually it goes through eventually. Try to not have scenes running at the time you are adding devices, this generates extra Z-Wave traffic and prevents Vera from entering learn mode.
From the scenario you posted, It looks as though Vera did find the existing node but didn’t transfer the scenes, Vera probably timed out. If you do the includes via the dashboard, you can adjust the time out period to give it more time to complete.
@JOD, I’ve tried to multiple times with no sucess, reading an earlier post @csherwood999 suggest switching back to 2.78 to include/update, once one is able to complete the include process then switching back to 3.2. Your thoughts? Mike
[quote=“csherwood999, post:3, topic:168402”]Vera firmware is 1.1.1245.
It appears to be a z-wave 3.2 vs 2.78. I switched it back to 2.78 and the include worked the first time (tried about 25 times on 3.2). Worked on all of my sensors in 2.78 mode. Switched back to 3.2 after the includes and all is well :). Might be a bug in new firmware? [/quote]
I don’t know about that, maybe a coincidence? Im running 2.78 and occasionally have the same issue, so it’s not anything different in that regard between 2.78 & 3.20.
If you have tried with increasing the time out through the dashboard and still can’t include, I would suggest a tech support ticket.
It’s an ongoing issue we need to get resolved that’s for sure. Maybe we can ask MCV for a definitive answer as to the cause, but I don’t know of any fix for a user other than persistence.
@JOD, confirmed it, I deselected 3.2 and waited for the VERA dust to settle out… Immediately I was able to include and transfer scenes to both HA09 controllers as I did in earlier FW versions!! ??? I’m wondering if my flaky CA9000 sensors are suffering for the same issue, I will attempt to re-include them and see if they start working better… Mike
Is that literally all you did: uncheck 3.20? Or did you also restore a backup, including dongle, made when you were running 2.78? (The Z-Wave database format is different with 3.20, so just downgrading to 2.78 seems scary to me.)
Did you migrate your existing network from 2.78 to 3.20 using the ‘hack’?
oTi@, I only unchecked 3.20 option. I did not restore a backup. Understand the concern about downgrading…
I did originally migrate fro 2.78 to 3.20 using the hack. I will probably use it again if I move back to 3.20. I though this issue was resolved, reading earlier post several other users ran into the same problem.
MCV I submitted a problem ticket, as @JOD indicated would like some advise. Mike
Update, as previously discussed… I first excluded my CA9000 sensors and then re-included them, they all seem to be working as they previously did meaning that they quickly included and configured and work consistently. The general observation that I’ve seen is that if you had included/configured prior to switching to 3.2 your sensor seem to continue to work once you convert to 3.20, but if for any reason you needed to exclude/include or move you CA9000 I’ve witnessed flaky performance ??? (sensors not being able to configure, sensors tripping but not reseting, unable to locate nearby neighbors). Anyone else seen similar issues? I know flaky is not a good term but it described what I’ve been seeing with my sensors when I converted to 1338/3.2, Mike
MCV, I’ve still not heard anything re my submitted problem ticket. Mike
[quote=“MNB, post:7, topic:169115”]oTi@, I only unchecked 3.20 option. I did not restore a backup. Understand the concern about downgrading…
I did originally migrate fro 2.78 to 3.20 using the hack.[/quote]
I see. Don’t know if this helps, but I just tried including an HA09 (.1338 / 3.20) and it seems to have been successful. (Or at least I was able to manually assign a button to a device; did not try scenes.)
@mcvflorin, thanxs for the comeback. I submitted the ticket on 9/9 via the “Tech Support Tab” it went through and compressed copies of my logs and ect. I did not pay attention but is there a ticket number, if so how does one retrieve it? As to submitting a ticket six weeks ago by my recollection the 9/9 ticket is my 1st and only for this year. I’ve tried to use the forum from most of my inquires, thanxs Mike
@oTi, I do not know why I was having the issue other than it was definitely repeatable. I will try and revert back to 3.2 (this weekend) to see if somehow I too will have the same success as your having with 3.2.
@JOD, Ugh if it was in my JUNK file I typically purge it…My Bad! Maybe before I attempt to revert back to 3.2 I attempt to re-submitt a trouble ticket with my current logs and then we should be able to do a simple compare for any anomalies. Just a thought. Mike
You should have received a confirmation email within minutes of submitting the ticket to the email address you have on file or receive notifications at.
I have the same problem. I have a new Vera 2 (since three weeks) which I setup on 3.2 since I got it. No problems so far.
But now I have one new device (a battery powered wall switch (controller) from Duewi) which I can not pair due to the “failed to go into learn mode” issue.
Shall I just uncheck the 3.2 box (without any other action such as reset etc)?
Well, I converted back to 3.20 with no apparent side effects (in other words everything is still functioning). What I have not done is attempted to see if I can duplicate my original problem HA09 failed to go into learn mode (didn’t have the time to fuss with it). Will attempt later this week and advise on my VERA exploits… ;D Mike
All I did was use the hack which completed as expected and then switched to 3.2 option.
Hm, I’m not sure if I can follow you…
I’m currently on 3.2 and was never on 2.78. So, shall I now just uncheck the 3.2 option to fix my problem?
Do I need to do anything else (apply a hack or setup the z-wave database again or what else)??!? ???
Hm, I’m not sure if I can follow you…
I’m currently on 3.2 and was never on 2.78. So, shall I now just uncheck the 3.2 option to fix my problem?
Do I need to do anything else (apply a hack or setup the z-wave database again or what else)??!? ???
Thanks,
GeeZay[/quote]
In my case all I did was uncheck the box, nothing else
@GeeZay, my apologies for not being clearer, I simply just un-selected 3.2 option. Nothing more, If your looking for a technical reason as to how it works pass, someone from MCV will have chime in with the technical what for all. All I know is that I was able to include with my HA09 being able to transfer the various scenes. Mike
Looks like @pgrover516 had similar problem/resolution. Now am I advising you to do the same? I will caution you although it work for my situation, you should first perform the necessary backups prior to proceeding and be prepared in the event that something could corrupt your z-wave config/devices. Mike