Tired of dead nodes and false alarms

[rdeswart 2]

I am getting tired of dead nodes, somewhere out of the blue i get 5-6 dead nodes every day, and still have false alarms on smoke sensors en flood sensors, i tried normal versions and beta version, but the problems didn't solve

When is Fibaro releases a stable version, they are doing nothing, al least we don't see or hear anything, only marketing who tells how good there system is, but i don't think so.

Anyone who share this with me, or know a solution?

[Dino 0]

J.nowacki,

It has been a day. Any news? I mean this forum is also a support channel from fibaro. So why aren't you answering these questions?

Something to hide? Or are you busy making a flash movie about the next new Fibaro product show everything a customer wants but just does not work in practice.

Sorry for you guys who dis but I am so glad that I didn't bought the smoke sensor and the motion sensor from fibaro. Giving fals alarms, a lux sensor which is not a lux sensor. Turing into a temperature sensor etc etc.

[dhanjel 7]

They asked for contact information to you, why not give it and talk to them and maybe they can help. Then you can update the forum or they will once the proper information and situation is understood.

A negative tone like yours certainly won't get you anywhere.

And as an argument, you mentioned "all" the people here complaining.

From my experience, pretty much no end user registers at a forum just to say "thanks for a great product", so the statistics is widely misleading.

(I've sold my HC2 a month a go and tried a couple of different open source solutions, none was near the stability or functional as Fibaro, so I'm coming back)

[Dino 0]

People can say a negative tone would not help. I agree, but I would say I have reason to be negative because their isn't anything to be positive about. Besides their isn't anything better out their. But that isn't an excuse for Fibaro to sell products which do not function as being specificated or presented. I have been misleaded over and over again by Fibaro. Even you have sold your system. So you should know.

Secondly I do not have any hope for fibaro, certainly not with the big company's who know how to make quality products are coming in 1 or 2 years, so I do not want go anywehere with them. And who knows, maybe new customers are being warned by these posts.

Customers should be warned that they are buying a beta product and they take the risk of spending hughe amount of time figuring out that they do not have a proper working system.

Using it for basic light switch is fine but just do not trust it to controle alarms, fire alarms, opening or closing doors etc.

And yes I have had several contacts with support in the past about various issues. They just were not able to help. Besides, please restore the system. Please include exlude the device. I also have send many e-mails to support and didn't got any answer from them so that's why I do not see any reason to contact to them directly f they are not answering my questions in public.

[j.nowacki 5]

Dino, answers for your questions in mentioned topics:

Please login or register to see this link.

Please login or register to see this link.

FIBARO RGBW module works with PASSIVE sensors. It was mentioned on the forum numerous times. You can look up more information about it on the net. Basically it means that RGBW PROVIDES voltage to sensor output. So raise of voltage when connected to rgbw is natural and it is simply the way passive sensors work. Sensor's output just "sinks" the voltage provided by RGBW. Some of the active sensors might work as well, but it depends on their construction, that is why we recommend passive ones.

Please login or register to see this link.

Ipad is powerful device, but when many actions need to taken in the same time it is possible that some lags occurs. We did not manage to recreate such situation in our tests. Please clear all energy metering history on your HC and check if lags still occurs. Also large number of RGBW modules controlled by app can cause delays. Further diagnostic might need remote access to view whole setup.

Re-adding and re-configuring devices is necessary when all parameters were not send properly.

[Dino 0]

J.nowacki,

Thank you very much for your reply. Indeed your RGBW module works best with Passive sensors. The answer on that one came after many e-mail's from my side and mvrekum to your support organisation. WE have posted that answer on this forum for the first time. But hey sometimes figuring something out takes some time. I just wanted to ask you to update the manual but I just see that you have a new more clear manual than the one I got when I bought mine last year. But I stil mis that it is best suited for passieve sensors in you manual.

Ok so in february I figured out that passive sensors work better. Sold my active Windsensor bought a passive one and I bought a lux sensor. A lux sensor, the servodan 43-198, which was recommended by Fibaro on their website. Link below. That should work!! I set the settings of the servodan to the settings 300lux - 30.000lux. Put in the parameters of the rgbw 0v as 300lux and 10v as 30000 lux. As explained before on this forum. But than the problem; In complete darkness it does not drop 2400 lux. On your advise I meased the devices and indeed in complete darknes the sensor sends 0,245 volt into the rgbw module.

So I have 2 QUESTIONS. The first one has been asked in other post as well but didn't get an answer, but as we have a dialogue right now I trust you are going to answer this time

Please login or register to see this image.

/emoticons/default_icon_wink.gif" alt=";-)" />:

1. I use a lux sensor which is recommended on your website, see link below, but does not work as expected. Could you please help. It is a passive sensor as I don't think you would recommend an active one.

Please login or register to see this link.

2. It seems that within 8 months you have brought a version 2.3 of the RGBW module on the market. Could you please explain the difference. Would it work better with 0-10v sensors

Please login or register to see this image.

/emoticons/default_icon_wink.gif" alt=";-)" />

[j.nowacki 5]

Dino, remotely I cannot investigate reason your sensor acts that way. The easiest way to make it work properly is kind of manual calibration. Cover your sensor so no light will be detected. Measure voltage on sensor's output and enter it in proper field in configuration, e.g. if you have 0.2V at covered sensor, enter that value as 300 lx in RGBW. Then expose it on very strong light and note measured value as 3000 lx.

The latest version is 2.22, it did not introduced any updates in that matter.

[rdeswart 2]

I agree with Dino, Fibaro is putting too much time in marketing instead of developing stable software.

Its a shame, but don't think they come far this way

[Dannyboy 12]

+1

[Dino 0]

Putting a Beta in the air which is just an Alpha. Sure beta's have issues but for what I read in the beta post people can't say this is beta.

And than a Facebook message for the US which is showing an apple. Is fibaro thinking they can compare them self to Apple.......?

Oh and for your info. This weekend I have replaced 7 fibaro (1.4) devices. Took me 6 hours and geuss what. Now devices which had never turned up as deadnodes are turning up as deadnodes. I I am think of putting more Fibaro devices in my house to get an even stronger mesh network

Please login or register to see this image.

/emoticons/default_icon_wink.gif" alt=";-)" />. Or should I exlude/include al my devices again....

[rdeswart 2]

And there we go again, i thought i install the latest beta 3907, and what u think?

more dead nodes then ever, and again 2 times false alarm from the flood sensor.

Getting really tired of it

Please login or register to see this image.

/emoticons/default_icon_cry.gif" alt=":cry:" />

Please login or register to see this image.

/emoticons/default_icon_mad.gif" alt=":-x" />