The Z-wave network heal was removed, as stated by others, because the new firmware update enables a self healing routine every night and you’ll notice that devices which were previously not reachable during the day they will be accessible the following day. The heal option was removed as it no longer worked correctly and with the new firmware could cause communication issues with the devices.
For anyone who’s not viewing the updated icons for the devices you’ll need to refresh the browser page and clear the cache. If you still experience issue you can contact support by email or phone.
For anyone who’s experiencing issues with operating their devices, these should be resolved by the z-wave chip during the nightly routing update. If you still experience issues with them one day after the update please contact us by phone or email, and enable tech support so we can quickly look into it.
Platform Status: status.getvera.com
USA Toll Free: +1 (866) 966-2272
International: +1 (702) 487-9770
Email: support@getvera.com
Web: support.getvera.com
Hours of Operation: Monday ? Friday 12:00am to 6:00pm Pacific Time[/quote]
I have problem in my scene with last update ,when vera edge restart show error in lua script every time ,then making restart and restart 3-4 times lua error message disappear and scene work again but after 1 day or less crashing again , I make discover , problem seem to be in scheduled scene , try to make any scheduled scene triggered 10s or 1min and when luup restart show error
I have 10 CT100 (actually CT101 purchased from Lowes for their Iris system) thermostats spread across 2 Vera Edge units in my home. When I did the upgrade to UI7 2 months ago, I noticed that I lost my battery indicators for all of them (no C-wire to power). I also noticed that when they were off, the area on the GUI where you set the temp showed 0F for half of them, while others were blank. Definitely not good. After speaking with Vera support (who were helpful in assisting my other issues), I figured out my problem. When I first added my thermostats to Vera, I didn’t select the Thermostat device, instead I selected “Add Generic Z-Wave Device”. I unpaired and paired again but this time as a thermostat CT100. Now, I have battery indicators again on all, “0 degrees F” does not appear on any when they are off, AND I no longer get the errors “Can’t detect device” anymore. I hope this helps![/quote]
I’ve actually never been able to do a full power add with the CT100. I always have to unplug my controller and take it right next to the CT100 and manually add it. I’m unsure if it adds as a generic device at that point. I’ll try what you suggested when I get home.
I have 10 CT100 (actually CT101 purchased from Lowes for their Iris system) thermostats spread across 2 Vera Edge units in my home. When I did the upgrade to UI7 2 months ago, I noticed that I lost my battery indicators for all of them (no C-wire to power). I also noticed that when they were off, the area on the GUI where you set the temp showed 0F for half of them, while others were blank. Definitely not good. After speaking with Vera support (who were helpful in assisting my other issues), I figured out my problem. When I first added my thermostats to Vera, I didn’t select the Thermostat device, instead I selected “Add Generic Z-Wave Device”. I unpaired and paired again but this time as a thermostat CT100. Now, I have battery indicators again on all, “0 degrees F” does not appear on any when they are off, AND I no longer get the errors “Can’t detect device” anymore. I hope this helps![/quote]
I’ve actually never been able to do a full power add with the CT100. I always have to unplug my controller and take it right next to the CT100 and manually add it. I’m unsure if it adds as a generic device at that point. I’ll try what you suggested when I get home.[/quote]
Just so you know, my Vera Edge units stayed where they were and the furthest thermostat is about 50 feet away and worked without a problem.
I set up the WiFi on my Vera Edge to permit access before roaming the house to pair the various devices. Then when I power it up, I connect with a tablet computer and access the full UI. It helps to be able to control the whole process.
since updating, I’ve had a lot of trouble communicating with the generic GE light switches (e.g., 12722). The lights are turned on or off but vera cannot seem to verify a successful signal and fails to report the current state. I have a LOT of these switches, and it continues to be a problem only for two specific switches. I think it has something to do with the new way it treats network heal?
greater concern is that the vera android app no longer pulls down proper information from my Honeywell thermostat (TH8320ZW). It reads 0 degrees F. when I login to vera edge through the web page, it pulls down the actual temperature.
both of these issues occurred as soon as I updated the vera firmware.
Had to factory reset my VeraLite after trying to update to this firmware. When restoring from the backup my settings came back but none of my hardware device came back only the app based device work. Has anyone ran into this issue?
Another one the downgraded after the upgrade caused nothing but issues. The nightly, automatic heal; lots of offline devices; my Aeotec siren that wouldn’t work. Ugh.
When you downgrade i.e from UI7 .10 to .9 … then you need to restore from a previously save backup made with .9
Backups are NOT guaranteed to be backward compatible.
I wonder what is the dollar cost, if we were to total up all the hours we spent fixing our systems that were not broken before a new firmware upgrade?
Perhaps MCV would be willing to pay each of us to test their releases. I must have wasted 4 hours now, upgrading , chasing rolling devices that appear, then reappear, creating havoc with my PLEG if I run a PLEG status, it then removes a device , which might re-appear, requiring numerious fixes or restores to my PLEGs.
Has anyone been brave enough to test Fibaro HC2? My wife asked “are there better systems”? I explained the grass is sometimes greener, but then it too burns out in August…
If it were not for PLEG, I would jump ship. I’ll hit CES again in 2017, there were some great , (expensive) options. I’ll pay $~ 1,000 for a unit that works, is well supported, and well tested, and yes, goes through proper CAT and regression testing. How much have each of us already spent if we total up our time?
Would like to hear from Fibaro HC2 users, if any out there
[quote=“wezley69, post:23, topic:188243”]My Enerwave PIR’s are mad. LEDs stay lit and don’t trigger on motion. I thought it might be related to the SmartSwitch plugin but I removed it and rebooted. LEDs on the PIRs (3) all behaved the same. Unpairing and repairing only worked for a brief period of time before the LEDs went solid again and no motion triggering. The firmware definitely affected the Enerwaves in a bad way.
Reverted to 1.7.1248 - All is good again.
I have the exact same issue with my two Enerwave ZWN-BPC motion sensors.
Each morning all sensors work again (from the auto-heal), but the moment they are triggered they remain solid. The only thing I have not done yet is to unpair them, and repair them, but then I have to redo a ton of scenes that rely on those sensors.
Is going back to older firmware really the only option?
is there a single post that collects all of the reported/known issues? I’d like to keep tabs on it, but fishing through a forum thread isn’t cutting it for meh.
This version lost connection with my door lock, I receive the message “Can’t Detect Device” , someone can help me return to the previous version 1.7.619.
I upgraded the Vera Lite at my vacation condo - seems to have worked well (very simple network … few devices and no plug-ins). On my Vera 3 at home the upgrade went ok, but it was constantly trying to configure zwave and could no longer talk to my DSC alarm. I removed a plugin that also seemed to be struggling (smartswitch), but that didn’t help. About 2 days later Vera is now completely f’d. It looks like it’s in a reboot cycle. Green light comes on, then it starts flashing green/yellow for about 45 seconds, and then it lights up the first 4 lights for a second and then starts the whole thing over. What are my options at this point?
I ran mine for about a week on new firmware and didn’t have any problems with DSC, only with it loosing devices. I have reverted and all is well again for several days.
