Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


  • 0

Question

Posted

Dear Members,

We've released new software version,

Changelog:

- Bug fixes

- Preparing the Home Center 2 to a new method of updating

- Changes required for the co-operation with the application on the iPad

Recommended Posts

  • 0
Guest Kuuno
Posted

One thing to consider is that the team writing code andndeveloping hc2 is definetly not the team building new sensors. Ofcourse there is cooperation but both teams still do their line.

I dont think that the case that new sensors come out make the HC2 software development much slower.

Now the fact that there is no roadmap available for us or new updates do not come as the people on forum want then its the case of project management of development team

  • 0
Guest IPWorkx
Posted

Guys,

I'm getting an upgrade error #6. Also rebooted the box.

Any ideas?

Greetz

  • 0
Posted
One thing to consider is that the team writing code andndeveloping hc2 is definetly not the team building new sensors. Ofcourse there is cooperation but both teams still do their line.

I dont think that the case that new sensors come out make the HC2 software development much slower.

Now the fact that there is no roadmap available for us or new updates do not come as the people on forum want then its the case of project management of development team

Kuuno, I actually think that's a fair comment. However, I would say Fibaro needs to choose what its priorities are if it wants to succeed. The company chooses how it spends its capital, and at the moment that feels like it is directed towards building a Fibaro system to rival Lutron and the like. Unfortunately, I don't think that's what most of us hoped to achieve with the HC2, we were looking for a universal controller that supports all Z-wave devices, as almost all other Z wave controllers seem to.

I really hope this thread will seem silly in a few months, and the HC2 will achieve that objective. I'm particularly frustrated, as I am planning to start retailing home automation gear in the UK, and given the price point and the potential of the HC2, I thought it would make an ideal brain for HA systems here.

I would say that the Sales Director for Fibaro coming on to the forums has invigorated the support to some degree, but I (like many others) would like some commitments about which devices are supported, and when we can expect others to be (if at all).

  • 0
Guest hotrot_net
Posted

Jonny, jeromefr28, elmips

I totally agree with you guys. I already have 3 mulit sensors of 3 different manufactures NOT WORKING..!!

Every !#@$@# time there's an upgrade I keep my fingers crosed that they're gonna work this time.

As I told in this topic

Please login or register to see this link.

I'm gettings sick of extra features etc.. I want more compatibility and a more stable product.

I paid €499,- for a piece of hardware that after almost a year is not able to keep zwave products online. DEAD NODE..!! how can it be dead if I with a click on a link bring it online.! Is not able to conect a 10 of % of all zwave products out there. Where a company makes a lot of promisses that they brake as soon as you have bought the product.

When will this product be working as promissed?

  • 0
Posted

Boys Boys Boys and girls,

Cool, i agree but you help Fibaro to evaluate and create a good tool .

Wait one or two weeks to have the new release and work together !

  • 0
Posted
Boys Boys Boys and girls,

Cool, i agree but you help Fibaro to evaluate and create a good tool .

Wait one or two weeks to have the new release and work together !

I didn't think I was signing up for helping fibaro to evaluate a new tool. I thought I was buying a finished product. As yet, fibaro haven't given (publicly) any timelines to when devices will be compatible or not.

I hope you are right though pascal!

  • 0
Posted
Boys Boys Boys and girls,

Cool, i agree but you help Fibaro to evaluate and create a good tool .

Wait one or two weeks to have the new release and work together !

I didn't think I was signing up for helping fibaro to evaluate a new tool. I thought I was buying a finished product. As yet, fibaro haven't given (publicly) any timelines to when devices will be compatible or not.

I hope you are right though pascal!

Jonny,

I'm sure that for end of this year you will be happy .

I think with zwave the big problem is not Fibaro, but the method to set all the new devices compatible with the controller ... that is the problem ... i think the best solution is to open the method to add new devices with a driver module ...

Kind regards

Pascal

  • 0
Posted

Absolutely right Pascal,

We have a product here that entered the market with their own controller bearing the "Z-wave Alliance" logo. They wrote their own command classes and told everyone the Z-wave certification was "Awaiting approval". It took nine months for us to figure out what they had done and a lot of wasted time. Their replacement devices are due to arrive here in 3 weeks and I bet they automatically integrate. They even put their own "IP" cameras on the market and restricted the MAC addresses to their controllers...

Some people just aren't playing along.... Of course everyone just blames the controller software

  • 0
Posted
Absolutely right Pascal,

We have a product here that entered the market with their own controller bearing the "Z-wave Alliance" logo. They wrote their own command classes and told everyone the Z-wave certification was "Awaiting approval". It took nine months for us to figure out what they had done and a lot of wasted time. Their replacement devices are due to arrive here in 3 weeks and I bet they automatically integrate. They even put their own "IP" cameras on the market and restricted the MAC addresses to their controllers...

Some people just aren't playing along.... Of course everyone just blames the controller software

Can you please explain what you wrote above in more detail?

Are you suggesting in this comment that Fibaro still does not have z-wave certification?

"They wrote their own command classes and told everyone the Z-wave certification was "Awaiting approval". It took nine months for us to figure out what they had done and a lot of wasted time"

What do you mean by this comment? All of Fibaro's devices already automatically integrate into HC2?

"Their replacement devices are due to arrive here in 3 weeks and I bet they automatically integrate."

Thanks.

  • 0
Posted
Absolutely right Pascal,

We have a product here that entered the market with their own controller bearing the "Z-wave Alliance" logo. They wrote their own command classes and told everyone the Z-wave certification was "Awaiting approval". It took nine months for us to figure out what they had done and a lot of wasted time. Their replacement devices are due to arrive here in 3 weeks and I bet they automatically integrate. They even put their own "IP" cameras on the market and restricted the MAC addresses to their controllers...

Some people just aren't playing along.... Of course everyone just blames the controller software

Can you please explain what you wrote above in more detail?

Are you suggesting in this comment that Fibaro still does not have z-wave certification?

"They wrote their own command classes and told everyone the Z-wave certification was "Awaiting approval". It took nine months for us to figure out what they had done and a lot of wasted time"

What do you mean by this comment? All of Fibaro's devices already automatically integrate into HC2?

"Their replacement devices are due to arrive here in 3 weeks and I bet they automatically integrate."

Thanks.

Hello I think he spoke not about Fibaro but general .

Fibaro have not IP cameras , Fibaro try to update the compatibility list but it's not easy to make new material , add material from other customers and update some functions about the HC2, so i think the best is wait the new release , Fibaro have a good vision for the futur .

Kind regards

Pascal

  • 0
Posted

JohnnyC's note makes much sense to me and explains what we all experienced so far. All is well and good as long as one stays within the Fibaro product line. A step outside and all falls apart. My latest example and purchase was a HSP02 Motion Detector. Well, setting parameters just doesn't work. So, to me it definitely look and feels like its a 'By Fibaro For Fibaro' rather than a 'Fibaro Controller in support of Z-Wave devices'. 'Awaiting Approval'..amazing that Fbaro Sales (Mr Michal Rodziewicz) doesn't kick into this discussion!

  • 0
Posted

yes but pascal, considering a few things :

- it's not correct to tell there customer the always same "in the next 2 weeks" as they allready know it will not be ready at this time. (we heard that for months !)

- i'm not an investissor of Fibaro, i'm a customer.

- The Z-wave protocol and z-wave ecosystem is a mess. Well, the competitor has the same worrys and can offer a larger compatibility matrix and more recent module support.

Pascal, for my point of view, it isn't very serious to treat there customers this way.

PS : if I could imagine that i'm an investisor (and not a customer), i would already want to know the roadmap or some point in time of developpement process for this homecenter.

For the moment, i'm blind as customer and as investisor...

  • 0
Posted

Everybody....

Some seem to have misunderstood my comments.. The issue was not with Fibaro... It was the other company who created the product who tried to use non-standard zwave command classes. Their product would not work with Fibaro, Vera or any controller other than their own. They also created some similar products to Fibaro and Aeon Labs which would only work with their controller.

The integration of devices requires 2-way communication between the controller manufacturer and the device manufacturer... When there are over 650 products from over 250 companies, you can understand the time it takes to get through this, especially if certain companies such as the one I mentioned above do not follow the standard.

  • 0
Posted
Everybody....

Some seem to have misunderstood my comments.. The issue was not with Fibaro... It was the other company who created the product who tried to use non-standard zwave command classes. Their product would not work with Fibaro, Vera or any controller other than their own. They also created some similar products to Fibaro and Aeon Labs which would only work with their controller.

The integration of devices requires 2-way communication between the controller manufacturer and the device manufacturer... When there are over 650 products from over 250 companies, you can understand the time it takes to get through this, especially if certain companies such as the one I mentioned above do not follow the standard.

JohnnyC,

I'm agree it's my point of view .

First Fibaro create module , then controller to enter correctly on the market and to survive Fibaro need new products so he work on the HC2 update but also on new product tu be continue . Financial part is important to survive and Fibaro take the good way .

Fibaro can produce new updates quickly but on the same time cannot create and inovate for new products and i think if he do that Fibaro cannot survice with updates all days ..

Kind regards

Pascal

  • 0
Posted
Everybody....

Some seem to have misunderstood my comments.. The issue was not with Fibaro... It was the other company who created the product who tried to use non-standard zwave command classes. Their product would not work with Fibaro, Vera or any controller other than their own. They also created some similar products to Fibaro and Aeon Labs which would only work with their controller.

The integration of devices requires 2-way communication between the controller manufacturer and the device manufacturer... When there are over 650 products from over 250 companies, you can understand the time it takes to get through this, especially if certain companies such as the one I mentioned above do not follow the standard.

This makes no sense. Z-Wave is an alliance which is effectively owned by one company. How can the owner of Z-Wave which approves new devices allow a device to be added to the portfolio of 650 or so products if it does not comply. The device should never have been released with Z-Wave certification. Totally irrational.

  • 0
Posted

amilanov, Thats exactly what I said in the first comment I made where the company told everyone the product was "Awaiting Approval"

I checked again with them yesterday and they still cannot provide me with a z-wave certification document however their product and packaging still bears the Z-wave logo

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...