I am not getting a heal report after running the heal process. In fact, it appears that the heal process is not running to completion. Am I the only one having trouble with this?
Welcome to the 50+ club (devices that is)
Probably what is happening here is Vera is running out of memory to complete the task and dumping the log file in the process. When was the last time you got a full report, how many devices did you have at that time?
Try a repair to one node and see if you get a report.
JOD.
It has been several months since I got a full report. I did an update neighborhood on a node that has plenty of neighbors and got a report. When you said repair is that what you meant? I do not know whether to be happy or sad. I have sent at least four trouble tickets to Micasaverde about this problem, and I could not get a response. I know they read these posts, and I hope they will respond either acknowledging this problem or if they think it’s something else, letting us know. I have been having problems with some of my outdoor modules that are the most distant from my Vera2. A couple of them will not configure and several more will not respond to commands. I cannot relocate Vera2 to a more central area because it would require running cabling through the ceiling of the first floor of my two-story house . I have been trying to add devices where I perceived a breakdown in communication over the mesh network. If your theory is correct, these extra devices are just adding to the problem. Does anyone have a solution?
It is my theory and it is my experience and I hope I am wrong and would love to have an in depth conversation on this subject. Actually, this should be a topic on it’s own.
For the purpose of your post and my theory as to why you are not getting logs and the heal is not completing it’s the limitation of Vera and internal memory. Have you noticed the conversations of using multiple Vera’s in the posts? Hmmmm…Why would you need multiple engines? Food for thought.
JOD.
Hey Jod, I’m pulling my hair out over the heal thing and wondering if you know more about the process, I have 51 devices counting the child devices on the system but I cant get them all to keep thier neighbors at the same time, I can “update neighbors” on any single node and get good results, but as i go one to another they start disappearing from the ones i did earlier, if i do the whole network at once i get a some with all the neighbors and some with just a few
Everything you said is normal.
To put it simply. When you do an update neighbor node scenario you are asking that node to broadcast a signal to have every node that can hear it send a reply. Great, now you have a list of every node that replied. Does the node you are updating really need to communicate with some of those nodes in the list to talk with Vera? Maybe some are way out in left field, so they are dropped.
The complicated part is the message & route (packet) and what role a particular node plays in the entire system. Vera is the Controller and holds all the routing tables, it knows which devices need to talk to what in order to reach the destination. Some devices like the Trane thermostat act as routing slaves and can read the message in the packet and help route it. Other devices are just slaves and only act to pass the packet along to whichever node accepts it. Think of the entire system like ATT. Vera is the Central Office, the thermostat is the exchange and the light switch is your phone.
I hope that helps.
JOD.
That helps alot thanks, so if a node is closer to vera than other nodes it would be normal for it to eventually show just “1” as it’s only neighbor? still it’s odd that after every “repair network” the results are different, one time a particular node might maintain 3 or 4 neighbors and the next time 1 or 2
That’s correct.
Another way to look at it is to stand at a node and look towards Vera. What nodes do you see? those nodes would more than likely be in the list, anything behind you would be excluded. The message wants to pass in somewhat of a straight line to and from Vera, you should not see nodes in your list that would be a hop going backwards to then go forward to Vera.
As far as the list of nodes changing each time you do a heal depends on many factors. The routes can change due to latency in the system (some nodes may not wake up as fast as they did the last time or wake up in the same order, or maybe they were actually working turning lights on or off at the time the message was trying to be delivered) Vera made the adjustement and picked the shortest / quickest route at the time of the heal. Thats why its best to do heals when the system is not busy.
JOD.
excellent information! Thanks so much 