How did you go back to 1248? I too need to do this because 1320 is giving me nothing but issues/errors at the moment 
[quote=“Egbert, post:38, topic:188243”][quote=“mcv.johnm, post:36, topic:188243”]Egbert,
If you are sure that notifications has been disabled from My Modes → Edit modes, and if you are still having problems don’t hesitate to contact customer care via phone or email.[/quote]
John,
Thanks for putting me in the right direction. I never used My-Modes, but i saw that in this new firmware (1.7.649) now DEFAULT ALL notifications for me as only user were set to yes. I disabled that to No and so far so good :)[/quote]
Can anyone please tell me how to do this with a Vera Edge
Thanks
Both of my CT100 thermostats intermittently show “Can’t Detect Device” but seem to respond normally to scene changes and external scripting. Two of the four Ecolink PIRs are doing the same thing but again, appear to be functioning normally. Aeon repeaters and Linear switches all show as “Unknown category”.
Update: Intermatic plugs now intermittently dropping out and failing with “Cannot contact device, error code: 1…”. Both legs on the Aeon HEM have disappeared.
[quote=“George, post:32, topic:188243”]Hi guys,
Just wanted to make some clarifications :
-
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]
After a few hours, I am now finding this post almost comical.
“1. 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.”
I am observing the exact opposite. My system was working just fine with all of my devices being reachable at all time by removing the nightly heal. Now with the self healing, I am losing devices one after another day and night. I lost 3 overnight, one this morning and now another one while at work. Why do you feel the need to nightly heal a perfectly working zwave network? Why not do a heal/reconfigure only when something has changed?
I am also observing a few other issues: I am getting a lot of false alarms on my motion sensors which I was not getting yesterday. One of my 4 in 1 Aeotec failed to untrip and seems to no longer update at all. I will test further when I get back home but this seems to be another failed release.
Wow. Dashboard just greeted me with “22 devices not responding” out of nowhere. Guess thats the auto “heal” at work…
I think I figured out the problem with the false alarms on the motion sensor. It is Vision/Monoprice sensor with a temperature reading. Every time the temperature changes on the sensor, the vera considers it tripped…
My second sensor of the same type doesn’t have false alarms because the vera stopped updating its temperature. Nice…
This is a catastrophic release on the Zwave management side. I will be downgrading.
I have 5 Monoprice PIR sensors with temp sensor enabled via the iDoorcontact plugin. I’m not experiencing any of the issues you are describing. The temperature sensors are updating and even have the new icon. As do the PIR ones. But no false alarms. I’m running a Vera 3 with the 7.0.10.
I am on a vera edge.
I am now seeing none of my motion sensors with multiple outputs behaving correctly. I have 2 aeon 4 in 1 and 2 Monoprices.
The secondary sensors do not update at all except for one which constantly gives false alarms not when it updates but when the update incurs a change in temperature.
From waiting a bit the sensors which dropped indeed do come back. The heal is not nightly, it seems to be constantly running in the background. My impatience tends to make me want to go and do a reconfigure when they drop off but it may not be necessary. Maybe I’ll wait for another day and see if it all works out. In the meantime my siren keeps on going off.
[quote=“anhman”][quote=“George, post:32, topic:188243”]Hi guys,
Just wanted to make some clarifications :
-
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]
After a few hours, I am now finding this post almost comical.
“1. 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.”
I am observing the exact opposite. My system was working just fine with all of my devices being reachable at all time by removing the nightly heal. Now with the self healing, I am losing devices one after another day and night. I lost 3 overnight, one this morning and now another one while at work. Why do you feel the need to nightly heal a perfectly working zwave network? Why not do a heal/reconfigure only when something has changed?
I am also observing a few other issues: I am getting a lot of false alarms on my motion sensors which I was not getting yesterday. One of my 4 in 1 Aeotec failed to untrip and seems to no longer update at all. I will test further when I get back home but this seems to be another failed release.[/quote]
Same here. I’ve always disabled the nightly heal as I could never understand the need when my network is working perfectly.
To be fair, I don’t care if this is how the new Z-Wave firmware works now but its the lack of detail that frustrates me with such a significant change. For example, I would like to know:
-
When does the heal occur (it is clearly happening more frequently than nightly)
-
Can we disable it? Ie, I know we can’t right now via the gui but could it?
-
Can we trigger it manually?
-
Do custom (manual) routes still have any effect?
-
How do we heal just a single node (like we used to)?
There is definitely something happening as hours past. Now I am starting to see my 4 in 1s updating. One of the two seem to falsely trigger and not be able to untrigger though. Although I have not triggered the second one to test.
It’s great to see new firmware updates currently on a monthly basis. This can only be a positive for MCV.
This update changed my country to the USA but my city and timezone remained as previously set.
I needed to install a FGRM-222 Fibaro roller-shutter. Selected that particular device in the menus presented. I was then presented with install instructions in French as follows :-:
(RS Wizard 2-1a) Pour commencer, vous devez d?monter l'interrupteur existant. Rien de plus simple, il faut tirer sur l'enjoliveur assez fort pour le d?clipser, puis d?visser l?interrupteur de son pot d'encastrement.
(RS Wizard 2-1b) Les micro-modules pour volet roulant Fibaro s'utilisent au choix avec un interrupteur m?canique pour volet roulant (bi-stable) ou un bouton poussoir (mono-stable NO) simple ou double. Si la diff?rence entre ces diff?rents interrupteurs n'est pas claire pour vous, nous vous conseillons de lire cet article.
(RS Wizard 2-3a) Le l?appareil va ?tre automatiquement d?tect?. Si cette d?tection n?a pas fonctionn?, cliquez rapidement 3 fois sur le bouton d?association comme indiqu? ci-dessous avec un objet pointu. Plusieurs tentatives sont parfois n?cessaires.
At the appropriate point I clicked the Fibaro module button three times. At no time did the browser indicate any install success, infact no acknowledgement of my efforts at all. Regardless, after a Luup engine restart, the device had in fact installed sucessfully.
So not particularly user friendly while installing this module.
After doing some testing today, I have drawn a couple of conclusions:
Observations:
- Running scenes or simple Zwave commands have become extremely slow. The delay between command and execution ranges from none to 1min delay. It is getting absurd. My commands to wifi devices are all instantaneous indicating that it is clearly a zwave only problem.
- I am getting a rolling “can’t detect device” randomly on all my door sensors. I have quite a few of them.
- My door sensors and motion sensors randomly fail to trip or untrip. Example: I have a garage door opener and a garage door tilt sensor. I sometimes close the garage door and find the sensor still tripped. I reopen and reclose the garage door and now it untrips. Likewise for motion sensors. When it fails to untrip, I can just walk back in front of the sensor and walk away to untrip it.
- My temperature, humidity or light sensors only update intermittently.
Conclusion:
I think, the vera is now constantly running a heal making the Zwave busier than needed and therefore increasing the probability of dropping messages. It causes it to lose signals from devices when they trip or untrip. Delays commands and sometimes loses them when the delay is too long. I have a lot of devices and had none of these problems with 7.0.9. I am downgrading.
Thanks but no thanks, this firmware made zwave much less reliable.
Am I the only one still using the data mine plugin? Well, on v649 the graphing page goes nowhere,… Just a win7 spinning wheel.
Otherwise this has been the cleanest upgrade for me so far… Excepting the extremely tragic (and comical) forced reversion to nightly heals, with no option for manual heal. And rather than a convincing reason for this shafting, we get a response that I interpreted more like “this is how we force the old nightly heals on you suckers … No more turning it off… Whether that helped you or not”.
Edit: I waited long enough (3-4 mind or so) and data mine eventually came up.
A lot of people use DataMine - it works great, once installed correctly.
MCV must have had a major App Store problem. My DataMine software is now many revisions in the past. Like pre Jan 2013. Download the file L_DataMine1.lua and see if you can find the variable dmLuaVersion eg:
local dmLuaVersion = If not, you now have an ancient version of dataMine.
Other people are having problems with other plugins - old versions appearing out of thin air. This is a major disaster for MCV but not necessarily a firmware release problem.
Have more than 70 devices (euro) - all is ok. I had only one issue with the Aeotec Siren, but i simply deleted #255 variable about hard reset and all went ok. 
My VeraEdge is a new unit just replaced my old Vera3 unit that did not wake up one morning. It took me more than two weeks to overcome the migration issue of my old UI5 backup to UI7 7.0.9 until it was rather stable. For this I have used quite a lot the Repair Process which proved well. I could see which device was not configured or with low strength ranking and would exclude and include again and run Repair. I have 60+ real devices totaling some 130 entities including the plugins, Apps and sons so it was quite an achievement to do this migration from a dead Vera3 Ui5 to VeraEdge Ui7 with re installing (only) 10 physical devices (I still had other issues with some plugin compatibility - Ping Sensor…). In the flow of dealing with this (I try to stable this system and leave it until Vera plus will be out…) I decided to take the new 7.0.10 upgrade. At first it looked OK then in two days system became completely useless and at some point I even got a message saying there is no Zwave capability for the unit… Later it became completely dead - I could not communicate with the unit at all! I saw in another thread someone described his unit went dead he tried recovering it with Vera Support and they announced it dead (he will most probably get a new VeraEdge). Sweating I decided to hard reset the unit and downgrade back to 7.0.9 and restore my previous backup + Zwave network. Lucky me it went well and its seems to be OK now. I think its important to have the capability to monitor the connectivity status and level of each device (by going through the repair table) + the ability to run a repair / heal process when YOU think its required (I do not do this at night because it starts operating my A/C units while repairing).
As a general remark I find smart guys (like RTS) who do not move away from something that is working OK for them to get into trouble. For me I will try moving to a new version only a year from now or when moving to a much stronger hardware.
My home system is using a Vera 3 on UI5.
7.0.9 was looking like a good release to me … It was the first release that addressed all of my personal high priority bug fixes (Tested on Vera Lite and Vera Edge)
I have not bought any of the new Z-Wave plus devices … but there are a few I am interested in using … So I really want to move up to the Edge.
My intention was to upgrade after my high priority issues were resolved and there were two good releases in a row!!
I guess it’s at least September now before I will move forward.
I’ve just reverted back to the previous version, looking back at the first post in this thread “not brave”.
I’ll wait until there are no bugs, oh wait a minute, that seems to be normal for this software… isn’t sarcasm wonderful.
I cant say I know why… but my fix was this
Keep this firmware but restore my system from a backup and the but things back to the way they were before the upgrade… but leaving the new firmware in place…
So I am just back to dealing with the same old issues…
So so sick of this…
For those with powermax alarms issues this also fixes this problem if after you go and disable auto updates on that plugin… Without any warning, they also updated that plugin. They didn’t even increment the version number… But if you install the old version, your powermax issues will go away
Downgrading without having to reconfigure any of my devices seems to have worked.
Assuming that all the devices which lost connection and recovered were actually reconfigured by 7.0.10, it seems like at least the reconfiguration was backward compatible.