Running UI7. Recently noticed that my outlet in my shed about 50’ from from Vera3 was no longer able to communicate. Checked Vera3 and found something like unable to transmit. Error 1. After spending a couple hours trying to re-associate the outlet to no avail, I searched and found others having a similar problem after the July update. I downgraded to I think 6.1.9 and reset everything, the outlet came back. I upgraded to the October update and again lost the outlet. The way I finally got it back was to unpair the outlet by selecting another device and then activating it to upair it. I then was able to add it back. It then worked for a day, before getting lost again. Same problem with unable to communicate. I checked it’s neighbors and it was blank. There is one switch within the same distance as the Vera3. This thing worked for more than a year and one of the latest upgrades seems to have caused it go flaky. I’m sure I can upair and add it back again, but c’mon! This used to work fine.
Yeah I stuck at 1.7.619. Maybe the November update has the Sigma changes worked out. When heal disappeared it made me nervous. My Vera3 is rock solid. No restarts and no lost devices ever and I have devices spread all over. The furthest is ~200ft to the dock. The only time luup restarts is when I am developing and restart it on purpose or the monthly restart occurs.
I stayed on 1.7.619 because I don’t have the time right now to figure out how configuration and routing is done with the new Sigma firmware. I was hoping that information would become clear as others upgraded. I know not the pioneering spirit. I have read other posts where there seems to be some indication that the heal and configuration is performed more dynamically so the neighbor node listing exposed in Vera is not used for routing anymore.
To be an optimized mesh the classic algorithms for routing need to know about potential neighboring nodes so I would assume that this information is buried somewhere within the device and it is just not visible in Vera anymore. If it is not doing that it is no longer a mesh, rather it is a broadcast network and every device would retransmit the signal until the target addressable node gets ahold of it. Haven’t looked at mesh networking in a long time so perhaps there is a different theory.
Anyone messed around enough with the new routing scheme to shine a light on it?
And magically, the shed outlet is working again. 5 or 6 neighbors are listed in the neighbors variable now. I turned off what I think is the automatic heal in the Z-wave settings. Does unchecking “By default Vera should automatically configure devices” actually disable the automatic heal each night and should my outlet continue to remain working now?
Actually, these are two different steps. From playing around with this and observing what is going on (at least in 1.7.619). Configuration is the step that sets the neighbors. The heal step pings each of the neighbors to determine which is the most efficient route and sets the order into the Autoroute field. This may be different when not using Vera routing. The neighbor with the lowest timing will be the one that is used first.
For instance
0-5x,3-15x,4-15,10-15
means that it will try device 4 then 10 when communicating. 0 and 3 are failed routes as indicated by the x.
Interesting though I have not had a heal since july but I am not sure how I turned that off.
Since the heal is now dynamic, I think Vera doesn’t get told about it and as such does not update that system variable. Mine also lists last heal as July 2nd but I know I’ve had heals since then as I lost a few sensors that came back the next day.
I’m not sure if the new Sigma firmware uses Vera’s routing (autoroute) or has it’s own internal routing table. Not about to spend $3K+ on a sigma zwave dev kit to find out.
[quote=“BOFH, post:7, topic:189743”]Since the heal is now dynamic, I think Vera doesn’t get told about it and as such does not update that system variable. Mine also lists last heal as July 2nd but I know I’ve had heals since then as I lost a few sensors that came back the next day.
I’m not sure if the new Sigma firmware uses Vera’s routing (autoroute) or has it’s own internal routing table. Not about to spend $3K+ on a sigma zwave dev kit to find out. ;)[/quote]
I’m pretty sure it was changed to a dynamic heal after 1.7.619 when the new Sigma firmware was implemented. Maybe the automatic heal was removed for 1.7.619 (blessing in disguise) but I can still perform a manual heal. All signs seem to point to Vera routing for 1.7.619 and below and my logs no longer contain the nightly heals like they used to.
At least I have some level of understanding for the Vera routing. The Z-wave routing is an utter mystery. If you do have an issue, and I currently do not, figuring out what to fix could be an exercise in using your forehead to pound nails. Although, I’m typically ok with that, I draw the line at using my eye socket to pull out the bent ones.
All I really want is for the thing to stop trying to “fix” things when it’s working? If I don’t have a sensor or device that is not responding, don’t heal or change anything. This outlet going in and out is a real pain in the A$$. It’s the only one and obviously the Vera3 is doing something every night for it to go away and then come back. When it’s gone, it’s G-O-N-E. I cannot talk to it at all. I can unpair it and add it back and it works, but unless I do that, it’s like it’s just lost. Then it comes back one morning and I can talk to to it over and over again. My shed is not moving. My vera3 is not moving. Something in this stupid firmware is doing something and it’s broken whatever it is.
Best Home Automation shopping experience. Shop at Ezlo!
