just meh.
Regarding the Flash Mode issue, I got the following friendly, but uncommitting answers
"The issue is that the device (parent and children devices) communicates with Vera in a secure way so there are several z-wave messages that the device is sending and also Vera is sending several messages to the device(the regular z-wave commands (i.e. turn on/off ) are being encrypted and there are also several authentification messages) and at some point, there are collisions between these z-wave messages and some commands are invalidated.
This issue should be solved in a future firmware update but at the moment I don?t have an ETA and also there is no workaround."
When asked about non-secure mode pairing:
“It?s not possible to pair the device in a non-secure way because the gateway does not have this option implemented so if a z-wave device support secure z-wave command classes it will be paired in a secure way.
We will analyze the possibility of adding this option in the future but for the moment I don?t have an ETA.”
yeah. that’s the same response since 1 year and a half. nothing new at all.
Hi Tillsy,
Did you ever compare configurations between the vera secure pairing and the HomeSeer migration to vera?
Wouldn’t it be possible to change some parameters / variables to get it right with Vera?
Thx,
Bob
Vera,
please pay attention to this issue. It makes the entire zwava network unstable with 1 or more 223’s in the network. If a scene is fired and has trouble with this 223 device of if the 223 device is manually switches (locally) vera has overall lag problems and needs a long time to recover (zwave). Also if I need to turn on an turn off (garage door) with a 223 I get very unresponsive and unreliable communications. Sometimes is ha seconds of delay, most is have >10 seconds up till minutes (!).
What worries me the most is in this post:
http://forum.micasaverde.com/index.php/topic,107895.msg420710.html#msg420710
As per Fibaro devices, I would not say this publicly if I wouldn’t know and even reported myself for a few these issues, that are already in the queue for development. But this needs to be taken with a grain of salt because, in the R&D process of these devices, we are discovering that not all of these issues are actually on Vera’s plate. But even so, we will do our best, and closely collaborate with devices manufacturers, to make sure that these things are sorted. We will update more on this once we get the updates rolling.
@Sender, I’ve brought to the attention of our PM team, your comment and this entire topic. #fingerscrossed
Sorin, thank you. my fingers are all tied up
for whats worth. Getting lots of this:
10/5/2018, 8:17:53 AM warning device:990 has duplicate state id 14 for variables: LastArr , MeterScale
10/5/2018, 8:17:53 AM warning device:990 has duplicate state id 13 for variables: LastNnu , MeterType
Think this will take a long time…
Vera support:
We currently cannot make any promises related to this Device, device integration is handled by our Project Managers based on the actual priority list. Our team is looking to improve the overall performance and stability of our services/products alongside with device integration and other fixes.
That?s why we do not have an exact date or estimated date for now.
I do hope melih reads this…
This thread is one of the reasons I am considering leaving Vera (Others already have left because of this). Fibaro are a very popular lightning controller and using the with Vera is just a nightmare and the fact that this hasn’t been fixed for well over a year now is really something I’d like to see changed with the new company leadership. It’s great to have new and stylish UIs but the basic components need to work flawlessly first.
Really hope to get your response on this.
Thanks!
223 support is a must have. this device (devices) brings my whole zwave network to delay. If the device is touched locally, it sends a status update and the zwave network is then occupied. Having delays in controlling the 223 of about 2-15 seconds is unacceptable. Since I am not alone (many times read topic and many replies) and also stating from Vera support it is on the PM agenda, I urge Vera to come with a solution.
This is the culprit of my entire unstable zwave network.
Please respond.
I already sent this to melih as an evidence of how bad we users were treated regarding new device support. It replied that this will change with the new course - I’ll believe it when I’ll see it.
I can confirm I see the same behavior and that it’s really frustrating. I disabled all the automation involving fgs 223s, and I’m back to 1800 at the moment.
In moment like this, I really wish I’d chosen another controller, but that’s another story - WAF is very low nowadays.
@Vera, @melih, what about the support for this device? Will it ever be!?
Hi
I have also the delay problem when i used scene. I have contact support and he make a delay of 1s betwin the different command i understand if you have a lot of module the delay can be too mutch.
I have this problem since October 2016, so now it’s more than two years. This is so annoying to me that I stopped automating my house any further. I just use it as it is for now and will propably leave to another technology when it comes along.
I just switched to HomeSeer and I must say that I should have done it long time ago 
+Instant inclusion/exclusion of nodes. (When I was removing Fibaro nodes from Vera, it took 5 attempts on average for FGS-222 units)
+No lag of FGS-223 (even in secure mode), scene control support.
+No random freezing of Danfoss LC-13 on wake up.
+Although I hate Visual Basic, scripting is light years better than on Vera (Visual Studio, break points, watches…)
-No scene support for FGD-212 (just one action globally for all dimmers)
-Maybe little more pricey (but well time invested in Vera over past three years wasn’t for free either)
This is becoming so annoying. I’m (again) at a point that I’m evaluating to switch controller to have this device supported. It’s very unfortunate that the most popular device in this category in Europe is not properly supported two years after being released.
The silence is really damaging to Vera’s brand at this moment.
At this point we want to know two things:
- Is there an ambition to fix this issue?
- A timeplan
It’s crisis “ABC” to communicate. Good news or bad news does not matter.
No news is far worse for a brand as it undermines trust. Like in: “Are there other issues that I should consider before buying/expanding Vera?”…
Some update… I am not getting very happy from.
I received yesterday via support:
When it comes to those Fibaro Models it?s very hard to manage it properly due to the device?s nature as well. We can attempt to fix this by changing the current settings of the device into something different, however, we cannot guarantee that this will work as expected.
Our team is working on all integrations step by step, depending on each device and each situation the process could be short of long, even if it seems as an excuse, it?s actually very hard to integrate a device based on all the requirements from each involved part.
Please Enable Tech Support on your controller and provide us with the Generated String. Let us know if we can test the network and and also let us know if we can test any of the Fibaro devices that you have (FGS223).
I responded:
Thank you for taking the time to respond to my email.
I appreciate the effort Vera is putting in device support. But to be honest the output is not very promising.
I do not want to be the live testing device. I have done this many times in the past as you may probably know and that did never work out well in the end. The original issue was mostly solved but other more hard ones were then introduced.
This device (223) is 50 euro. I am sure that if you introduce this to your existing zwave network you will experience the same as all of us.
As said before. This is the only module one can buy in Europe. All others are out of production.
As far as I know and read all over is that this device works well with many other zwave controllers.
I hope for a quick solution.
I stopped looking for a Vera alternative but I started up agian.