Well who’s brave enough to be first?
Done ;D
No problem for the moment
Do you know what ? The temperature is with decimal now…
Lost connection to the GDZ. Tried opening and closing the door manually to see if that would refresh it, but no luck.
Upgrade went well!
Too bad it doesn’t fix the issues with the Aeotec multisensor 6
Done. No issue. Last two updates I have had no problems which is a very refreshing change. I am trying to run firmware as native as possible. I have concord, house mode plugin…that’s it.
[quote=“trafex, post:4, topic:188243”]Upgrade went well!
Too bad it doesn’t fix the issues with the Aeotec multisensor 6[/quote]
Aeotec needs to do that and they have to a certian extent. Just buy their z-stick for 30-40.00 and they will send you instructions and software to update it. Same problem with other brand of controllers not just VERA.
I know, but Aeotec also says it can be fixed by Vera. I was hoping that was the case with this update.
I updated and am now stuck with an “ERROR : Error in lua for scenes and events”. Trying to figure out where that comes from… Also my aeotec gen5 siren is stuck on configuring device.
Removed the siren because I suspect the new zwave engine talks differently to it, but now I can’t add it anymore, getting a lot of “the zwave network failed to go into learning mode please wait one minute”…
Update 1: can’t add anything anymore, keep getting “Add/Remove : ERROR: Z-Wave network failed to go into learn mode. Please wait 1 minute and try again.”
Update 2: after a few reboots inclusion mode works again but it seems off for the siren inclusion. The pairing mode kicks in in step 1 whereas it should be starting in step 3. Anyway the device config fails every time now, so I guess the gen5 siren is not supported anymore in the new zwave engine…
Last thing it says is “Add/Remove : Successfully exchanged security keys”
Does anyone know if it fixed the Monoprice garage door sensor problem (won’t change status)
I’ve some devices that are in red in the UI.
Warning ! If you try to reconfigure Fibaro RGBW or Powernode, the children devices are deleted and recreated >:(
Upgrade is OK but where is the Repair Zwave?? I can not see the devices status and signal strength - this is very important!
From the release notes: “A more important aspect that was changed in the 7.10 release was the removal of the old Heal/Repair process which was no longer required with the latest versions of the Z-Wave firmware.”
The Fibaro RGBW main device is no more linked to its children.
If you switch on it, the dimmers for color channels are no more switched on in the UI.
From the release notes: “A more important aspect that was changed in the 7.10 release was the removal of the old Heal/Repair process which was no longer required with the latest versions of the Z-Wave firmware.”[/quote]
Yes I read this prior to installing yet what is their solution when the network is noe working properly? And how can I know where the troubles are?
From the release notes: “A more important aspect that was changed in the 7.10 release was the removal of the old Heal/Repair process which was no longer required with the latest versions of the Z-Wave firmware.”[/quote]
Yes I read this prior to installing yet what is their solution when the network is noe working properly? And how can I know where the troubles are?[/quote]
If your read those changes, it was the z-wave chip manufacture that has changed/updated the way the z-wave network works. So basically all they did was update the z-wave chip firmware to what was current per SIGMA.
http://z-wave.sigmadesigns.com/products
If SIGMA changed up and removed internal z-wave items VERA just removed the physical button on the UI since it would no longer work or do anything. I know the heel for me has caused more problems then it solved with battery devices. After a heel ones that were working went to sleep and never passed or reconfigured after the heel. I think with new z-wave protocalls its more about automagic then a repair button. Let just hope it all works out like it never does. ;D
Looks like this may fix my MonoPrice door sensors staying tripped.
Bug Blocker Vision Door Window sensor ZD2102 - gen3 remains tripped
Bug Blocker Trip-Untrip-Trip not working properly on door/window sensors
As well as hopefully the MonoPrice glass break one.
Bug Blocker Door Window Sensors and Glass Break Sensors cannot be untripped anymore
Guess I’ll have to chance it tonight and see what happens. While I am debugging a Windows 7 to Windows 10 upgrade that’s caused my laptop to be unworkably slow now. 
Things appeared to be okay, but I’ve noticed several issues…
All notifications to users were wiped out.
All associations (Linear 3 way switches) were also wiped out.
All Home Modes reset all sensors to active in all modes, so I was getting burglary messages in Vera when it was in home mode.
So far everything else seems to be working, but those 3 things are pretty major flaws in my opinion.
Update:
Also noticed all Linear 3 way switches are now getting erroneous icons (light bulbs) instead of scene selector icon.
All linear 3 way switches were also renamed with a trailing “1”
Update 2:
The Linear 3 way switches are now also listed int an “Unknown Category.”
Update 3:
Vera auto adds itself to the list of any association groups created so when there is no connection to Vera 3 way switches that use associations become extremely slow to respond.
Update 4 (yes there’s more they broke):
All configuration variables that I have created are now removed. I had added configuration variables to switches and 3 way switches to set things like the LED to nightlight mode, and set the poll update for auxilary switches so they stay in sync… all variables removed from the ui and reset 
Just performed the upgrade about an hour ago and I’m having problems.
I have the Visonic Pro Alarm plugin installed and since the upgrade I’m receiving movement/open/closed notifications from all the alarms sensors (door sensors, PIRs etc). I’m currently getting lots of emails on my phone as my family walk around the house, pretty cool really but once the novelty wears off it is a bit of a pain. The notifications list in each sensor does not have any entries for notifications. I tried adding one to then delete it to see if it made a difference. Is there a hidden way to clear all notifications? Is there a hidden way to view all notifications? From the console maybe?
I have also restored a backup from yesterday, it made no difference.
Any help would be appreciated
All my window cover appear as dimmable lights now
D_WindowCovering1.json contains reference to dimmable light icons as well, so the UI is displaying dimmable lights
@smeg. This can be fixed by setting the sensors to bypass in home mode and armed in away/vacation etc. then you won’t get messages when you are home, but when you are out if a sensor is tripped you will get alerted. I was getting this too since they reset all the home mode settings I had in place and had to redo it all. It can be a pain if you don’t have an automated way to switch to away mode when you are out (I use the elk m1 plugin and created luup code to switch to away mode when I arm the alarm system as I leave and switch it back to home mode when I disarm it when I get home)., but as far as I know that’s the only way to resolve it. I have not done much testing, but I fear I might get daily messages now when I open the door before I can disarm the system, if sso I’ll be looking for a way to fix that.
Another odd bug I noticed is now one of my temp sensors is reporting 1800 watts. It’s battery operated, doesn’t use watts, and I can’t find a way to remove it. Doesn’t affect anything, but it’s an eye sore.