I’m almost finished replacing all of my switches with Z-Wave hardware. I moved some Z-Wave switches (let’s call them 1 & 2) from one place to another because I wanted to replace them with dimmers. 1 & 2 are now installed in a different location & all switches are working well. However, I have a Monster/Leviton 4-button scene controller that was working before I moved 1 & 2, and now it is not. Adding the new dimmers and moving 1 & 2 to another location are the only changes I made. After moving 1 & 2, I updated neighbor nodes and everything was fine, but I was getting this in the Vera interface:
I followed the Leviton instructions to de-associate the switch, factory reset it, and then re-associate it; not a fun task, but it seemed to work as far as the step-by-step instructions go. However, I still have the above status for this controller in Vera.
Please help! Everything else is working really well.
“Unable to get any information on node”. I’ve tried reconfiguring. I’m wondering if I’ll have to remove the node & re-pair it. Any other ideas?[/quote]I was getting this for a while. Repairing didn’t help, nor did a network reset. Letting it sit for a while worked.
I’m sure it’s pure coincidence, or maybe it’s the introduction of a new device, but I had some communication issues this weekend. could not communicate with some nodes in a certain part of the house. I moved one failing outdoor module inside, about 10 feet from it’s permanent position, and it worked. I moved it a few feet near another failing dimmer, and it didn’t work. My setup has been flawless and untouched for months. The ONLY change was the introduction of the monster controller. But after a day, everything is back to normal. I have disabled the nightly heal, have a 2500 sq ft split level house, and communication has never been an issue.
Either zwave can get flaky sometimes, or the older monster modules do something to the network. I don’t know. But all is well now.
Well, as far as it being a “distance” issue, I still have control over another switch in the same box as the scene controller. My condo is configured a bit like Intrepid’s house, from the sounds of it. The scene controller in question is installed at the front door (in a 3-gang box and within a foot the Kwikset), and Vera is on the “2nd” floor.
This morning, all appeared OK until I tried to enable one of the events associated with the buttons (undoing what I did in post #3 above) and I received the message:
“Failed at: Special associations”
I guess I’ll just give it time & pretend it’s not there for a while; which is difficult, since I cut out the old 2-gang box to install it in a 3-gang, and I have to walk by it every time I leave my place…
OK, chalk this up to a learning experience–maybe. If you can picture it, Vera sits in my entertainment center on the middle floor of my place; behind the entertainment center is a wall, and behind that wall are stairs going down & left to my front door. On the side of the wall opposite Vera, I plugged in my last remaining plug-in module, added it, and updated neighbors for everyone. Now the scene controller is working just fine (after checking the boxes to enable events on each of the four scenes). Maybe it just needed time; maybe it just needed an intermediate node. I dunno. It’s working now, though… and I need some more plug-in modules.
It has been my experience that things take time with Vera, and I end up being impatient and wondering why I am not seeing or getting the response I desire and I mess with the process (either hitting buttons in the UI, or power cycling, etc). If we waited 15-30 minutes between every change we made and then looked back at what you did but in fastfoward, it would look like Vera is responsive and took changes like a champ.
I don’t think the network is doing anything by itself, but just that it is being given time, left alone, where it can finish what it has to do. The UI messages aren’t telling us the entire story and interactions and polling between Z-Wave device and Vera take time. Treat changes in Vera like you are surfing the internet on 14-28k dial-up and go make a sandwich. Just my experience.
My problem has returned, but I don’t know why; I haven’t changed any of the hardware in my network in a few weeks. I still have a plug-in module serving as an intermediate node.
Then, one at a time, I checked the “event” box for a scene, then saved and waited for the scene controller. I was successful in “setting special associations” for the first two scenes (check box, save, wait… good). When I checked the third box, I got a “failed at setting special association” error, so I unchecked all of the event checkboxes again, saved, and got the error shown on the screen shot.
I’m tired of this. I wish it would just work correctly. When I get around to it, I guess I’ll just remove the device from the network and try again.
Spoke too soon; now I have issues on the OTHER scene controller. Obviously, proximity is not a problem, since I’m staring at Vera and at the installed scene controller as I sit here on my couch, and they’re about 10 feet apart.
I’m having the same issue trying to add a Yale Lock. Vera is right next to the lock, I’ve tried adding it, removing it, but it seems to spend a a lot of time purging associations, only to fail.
I’m running 1.1.1362 and using an Aeon Labs Z-Stick Series 2.
The system is try to configure your node. Modify the node and click on system tab and click on configure node right now. At this point it is try to talk to the node. It needs to be awake. Go to it and use it to wake it up . Otherwise just wait as this should not be a concern. It only does one node at a time
Best Home Automation shopping experience. Shop at Ezlo!
![http://i.imgur.com/nAU7i.png[/url]](http://i.imgur.com/nAU7i.png%5B/url%5D){kind=link}