Fibaro is the only one available every where in Europe. Qubino had very similar problems with Vera.
It’s true that Fibaro does implement advanced features in very creative ways, but mios is very slow at supporting them. Fgs 223 support came after 2,5 years on the market. I fear the new roller shutter 3 and smart implant will follow a very similar route, while other platforms get support in months if not weeks.
I wonder if Vera sends the command twice? That could ”toggle” the status and explain why the device shuts off immediately.
Anyone know how to check the traffic?
My VP is now seing my audio amp as a motion sensor.
This update is a joke
I do not think it was ready to be a release candidate. They might have pushed it out because of all the users bitching.
How do you call this ”local flashing” feature from Vera? With some luup command?
No, it is a simple configuration that works fine with HomeSeer and Fibaro, but not VeraPlus.
1 Like
I have 2 VeraSecures, and both needed support using SSH to get them back online after the firmware upgrade. In my home system, after the firmware update, it dropped one of the Veralink (2gig DW10) contacts a few times, and the front door lock today (less than 20 feet from the vera).
Setting direct device associations is broken in this release!!!
Strange, works for me but be sure reload browser to update screen.
OK, so not completely broken but…
In my case, I had set an advanced param (successfully) on the device on which the association was set and after this, it would no longer trigger a state change on the target (associated) device. Removing the the param and removing, then re-adding the association did not help. I had to completely delete the device, re-pair and then re-add the association to get it working again.
There’s still a bug there but I’m glad I figured out a way around it.
And they wouldn’t have been bitching if there had been any sort of release in the previous six months, or if they hadn’t promised something by April.
It’s their own undoing.
1 Like
The association is a property of the zwave network. Its purpose is to make devices work directly without going through the vera or any other controller. The vera and its firmware has nothing to do with it. If the association stopped working, it is likely that it somehow got reconfigured or the device itself crashed or lost its association. I see this regularly (every few months) on some of my leviton scene controllers and aeotec devices forcing me to power cycle them.
Not sure how you got to this. Audio amp I suppose is integrated through a plugin?
1 Like
Update. I haven’t had any issues since making this change.
Could you please share the parameter setting you used for this?
EDIT: never mind, found it.
0x50 (80) It will send the Hail CC/configuration report CC when the state of garage door is changed:
Value=0，reserved.
Value=1，send Hail CC。
Value=2，send Barrier operator report CC。
1 Like
Yep that’s the correct info.
Cheers. And thanks for the heads up on this. I was having similar problems to you intermittently and this solves it.
1 Like
No dramas, it’s always good to share with fellow Vera users. I’m always finding great info here. 
1 Like
Yep, through Yamaha Network Control plugin. Never had this kind of problem before… Rebooted VP and… Mysteriously, my Audio amp became an Audio amp again…
Likely a read error causing the vera to have to think it had missing files. Not a firmware issue then. More of a hardware reliability fluke.