Leaving Fibaro for an other system?

[kiwi 2]

I have migrated from MCV Vera 3 for the same reason I already seen there : unstability of zwave network, slowness, and update that took more than 6 months to get a fscking zwave module to be supported.

There is some issues sometimes with Fibraro HC2 but very less than I had with Vera3...

Lua support is more easy than the Vera, and even if we cannot do some things directly from scene (like Net.fHTTP, PLEASE fibaro ... do something), in general this box is really nice.

If I wish to change box, it should be for a KNX system. But maybe in my next house that I will build from scratch.

[Starbug 0]

It is very pnp / straightforward

Yes it will definitely help you to increase range, technically you can install HCL in a different country and to manage everything like a single system

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

Attached screenshot

Thanks Shapa, really appreciate your responses and this is something I was always interested in doing.

One final question if I may. I see you have split your z-wave devices with lighting on one HCL and security on the other. Can z-wave devices on one HCL make use of routing via a device thats on the other HCL. Im thinking if I had all my lighting on one HCL like you have and then a motion sensor on the other HCL, the lighting modules are routable but most sensors are battery and not routable. Or are all your devices within 1 hop range of the HCL's

Thanks!

[candrea77 26]

but most sensors are battery and not routable.

As I understand the battery-operated devices can't act as a router ..... but their signal can be routed.

Can someone please explain if my assumption is true or not ?

[Starbug 0]

As I understand the battery-operated devices can't act as a router ..... but their signal can be routed.

Can someone please explain if my assumption is true or not ?

Thats correct, the signal from battery devices can be routed by a mains powered routing capable device such as the fibaro dimmer or relay.

I am interested to know if say a fibaro dimmer associated to one HCL could route a signal for say a fibaro motion sensor (Battery) thats associated to another HCL.

If I start to split my devices between two HCL then do I have to be careful to ensure I have enough routing capable devices associated to each HCL to ensure full range.

[Guest shapa]

z-wave devices from a different network can not route through another one. This is the key - to stop flooding by splitting by parts.

I resolved the issue by purchasing some amount of cheap TKB sockets to use as repeaters (also using to manage some electrical devices) - one per floor is more than enough

Please login or register to see this link.

[ Added: 2014-06-19, 23:20 ]

candrea77, yes, battery devices can not route but can be routed (I've got a lot of routed battery devices - door sensors, etc)

[hardik_hrc 1]

If I use power with motion sensor would it make any difference in routing?

[Guest shapa]

Some sensors - yes (like 3 in 1 homeeser / etc).

Fibaro - no, it is completely unaware regarding non-battery option.

[MSB 0]

I took the step and moved over to an AEON labs Zstick S2 and domoticz. So far so good. Actually I pretty much like a lot more than the fibaro. The thing is blazing fast, loadtime for admingui is fast and lightweight without beeing ugly.

Only thing not working good is the Fibaro motion Sensors...But its going to soon.

[byackee 0]

I leave fibaro for openhab/habmin/cometvisu.

bye all

Please login or register to see this image.

/emoticons/default_icon_mrgreen.gif" alt=":mrgreen:" />

[ Added: 2014-06-30, 13:10 ]

I leave fibaro for openhab/habmin/greent.

bye all

Please login or register to see this image.

/emoticons/default_icon_mrgreen.gif" alt=":mrgreen:" />

[chrisv_s 1]

I have to say that I am still a fan of Fibaro. I tried out HS2 and HS3 and whilst there was plenty of functionality, the interface was very clunky and reliability seemed to be an issue with only a few devices. Fibaro seemed to have taken the more "Apple" approach by keeping things straight forward and attractive at the front end and so far my system has run with very few issues for months and I have ~30 devices. The phone/ipad app is a bit naff so I'm going to custom build my own but there is a fair amount of personal choice in that decision.

However, let me jump on the band wagon with the general annoyance about this long old wait for Version 4 to be released! We've all been waiting months, some even years, for this update to come out and realise some of the potential that Fibaro have marketed. I haven't seen an update for my system come out for many weeks now so I'm keeping my fingers crossed that this update is days away from release!!! Please Fibaro, manage our expectations with this...

[waveuk 0]

After 5 month with Fibaro, waiting to get the functionalities promised when I bought my HCL, I placed today an order for a Vera 3.

While Fibaro has good things I feel customers are not treated fairly with the lack of feedback, transparency and empty promises.

I maybe wrong but v4 looks far away considering the state of the alphas.

Without plugins HCL is too basic and restricted without LUA. The HCL costed me 100 pounds more than what I am paying for the Vera. I paid a premium expecting a better product/customer service.

Maybe I am also disaponted with Vera. Their customer service is basic but a more open product allows to base their success on the community and not just promises.

I will see what I do with my HCL...

[Guest shapa]

Just tested UI7 (vera3) - a lot of work made and it seems that finally MicasaVerde moving ahead really fast.

Virtually, every few days new software builds available (in case you know how to find them

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />) )

UI7 looks very nice, a lot of advantages.

"VERA UI7 RELEASE CANDIDATE

Today we are making publicly available a Release Candidate of the Vera UI7 firmware. This new software contains a variety of feature enhancements, device compatibility updates, and overall performance improvements. The ‘release candidate’ label indicates that this update is well tested but would benefit from additional community testing before it is distributed automatically to all of […]"

[floor2282 0]

Dear,

I have the same problem.

I am now waiting for a few months on a version that offers more support for multiple z-wave products, but it only takes too long.

Please login or register to see this image.

/emoticons/default_icon_evil.gif" alt=":evil:" />

Please login or register to see this image.

/emoticons/default_icon_evil.gif" alt=":evil:" />

Maybe you (Fibaro) should spend less time on the product movies, and just make sure that the firmware and apps just function well.

I hope you now once what to do something, otherwise our company to look at other products.

Please login or register to see this image.

/emoticons/default_icon_evil.gif" alt=":evil:" />

Please login or register to see this image.

/emoticons/default_icon_evil.gif" alt=":evil:" />

Please login or register to see this image.

/emoticons/default_icon_evil.gif" alt=":evil:" />

[remcoploeg 10]

floor2282,

It doesn't matter what we ask, the never give a good reply on the roadmap. If I see the feedback on the alpha it will take months for Fibaro to get a good stable product.

It's a pitty, with a great community, that Fibaro doesn't give any clear dates. It's more an open end. I am really on the edge to switch, I don't want, but with no information or dates, I have to go.

[Guest shapa]

"it will take months for Fibaro to get a good stable product."

You are wrong. To be realistic - at least 1-2 years.

Some major bugs not fixed for >1 year, many of them are really easy to fix.

[deanrparry 19]

"it will take months for Fibaro to get a good stable product."

You are wrong. To be realistic - at least 1-2 years.

Some major bugs not fixed for >1 year, many of them are really easy to fix.

Ridiculous bugs being left unfixed and adding stupid brackets to scenes or moving cameras to plugins (a mess)

It is what it is... We can all moan until the cows come home but it falls on deaf ears! Fibaro do what they want its designed like an open source hobbyist project yet is closed source and secretive!

Odd combination in my opinion... 3.951 is pretty good and stable... But still has crazy simple bugs!

[stevenvd 51]

they have a good vision, but I agree on the problem that they are mostly focused on "new features" instead of first stabalizing and perfecting the standard product. Most people would be more happy with just a stable product and wait longer for new features, than half finished work and many half finished features....

Still, the product has improved heaps compared to a year ago. but if they would focus just a few days on some simple bugs many many people would be very happy. Just to state, it took 1,5 years to properly support the greenwave.... and even longer for the x minutes before and after sunset /sunrise.

Small simple list:

Alarm panel enter siren

Block scene "else" statements

proper northq and aeon labs device templates.

visible system logging

more complex:

energy panel "house consumption"

[dhanjel 7]

Has anyone tried the Stack Box? Sounds interesting, and cheap.

Please login or register to see this link.

[sercasyr 0]

I use OpenHAB with several Fibaro devices with very very few issues.

I don't see the need to buy a Home Center, when I can do the same with a simple computer or even a Raspberry Pi.

 

I am a big fan of Fibaro products. They are well designed and seem better built and thought than those of their competition.

 

Nevertheless, they follow a STUPID APPLE-LIKE POLICY towards the customers.

They don't take customers as a priority, as they ignore their requests.

For instance, it makes no sense that the firmware of their devices is not available at the web and cannot be upgraded with a PC.

They make you buy a Home Center (that you may not need at all) to upgrade the firmware. I told Fibaro and I was totally ignored...

 

I sometimes think that they don't care if the customers are satisfied or not. They just care about the product.

It is a pitty, because their products are really good, but they should know that the customer is more important than the products.

They may have a lot of pretty little products, but if they keep treating customers like this, nobody will want to buy them.

 

I hope that Fibaro changes its policy.

With the quality and good desing of their products they could rule the domotics market. They just need to start realizing that the customer is not always stupid and buys only what he/she needs, and not what the company wants...