list of issues in my HC2 setup

[goran 9]

Hello!

I've been using HC2 and various devices (about 25, mostly Fibaro) for about a year now. Below are a few examples of the issues I'm having. I know that many or all of these problems are already known but they don't seem to get fixed so I'm not sure what to do next. I'm currently using 3.591 Beta but I've been having most of these problem since day one and in all HC2 software versions I've ever tested. All the issues have been reproduced with the devices physically on top of the HC2 box without any other electronics nearby. I have adjusted the polling interval and various sensor report intervals to decrease the zwave traffic to a minimum.

* When rebooting the HC2, The lastBreached value of all the Fibaro motion sensors and Fibaro flood sensors get messed up. Some will get Thu Jan 1 01:00:00 1970 and some will get some value from weeks or months back (possibly the value of the very first breach?). Sometimes the lastBreached value for the Fibaro motion sensors also get changed (without rebooting) for apparently no reason at all, to some of the values mentioned above.

* The Fibaro flood sensors sometimes enter breach mode and then immediately enter safe mode at the very same second or one second after. This happens when the device is not at all in contact with water or even moisture. 4 of my 10 flood sensors have done this at least once. A couple of them do this about once every two weeks and they have been verified to be completely dry every time.

* The Fibaro motion sensors sometimes they turn into temperature sensors and never recover. This is despite of the recommended workarounds such as increased polling interval.

* The Fibaro motion sensors sometimes get stuck in breached mode. Sometimes they recover after a while but sometimes they require a complete reset/exclude/include.

* I'm using a scene where a light turns on/off according to the light sensor in a Fibaro motion sensor and on sunny days it turns on/off like crazy. The light readings go back and forth several thousand lux upon every reading. Possibly the same issue as

Please login or register to see this link.

I realize that in such small device you have to live with issues like that but perhaps this could be mentioned in the specification.

* Three of my Fibaro wall plugs are completely dead (and I mean completely dead/broken, not just marked as a dead device). Just after a few weeks of normal usage. I've tried the reset procedure according to the manual but I get no reaction. Is there anything else to try?

* I can see that several people have asked about outside usage for the Fibaro motion sensor but I can't see any answer. The manual does not mention anything about it but the advertisement video seems to suggest that it can be used outside. I tried to mount one sensor outside (protected under a roof) but I get many movement alarms every time it rains even with the sensitivity at a very low level. Is this supposed to work? Is it water proof?

* I have a scene that turns off a few lights connected to Fibaro wall plugs by calling the turnOff() function once a day. About every other day, one or more devices will fail to turn off. As an illustration I have this debug code:

fibaro:call(10, "turnOff");

fibaro:sleep(5000);

local new_status = tonumber(fibaro:getValue(10, "value"));

if (new_status == 0) then

fibaro:debug("turnoff ok");

else

fibaro:debug("turnoff failed");

end

This will often result in a "turnoff failed". The wall plugs are physically very close to the HC2. What I have to do is turnOff, sleep, turnOff, sleep, turnOff... until successful. When turning on and off from the GUI I've never noticed any problem.

Probably same issue as

Please login or register to see this link.

and I have tried all the workaround suggestions without success.

* This is probably my most important problem. When including a brand new device, many of the device parameters initially get completely apparently random values that are not the ones marked as default. This happens every single time on the Fibaro smoke sensors, Fibaro flood sensors and Fibaro door sensors. I always put my new device physically very close to the HC2 then including them and doing the initial configuration. Several of my Fibaro Smoke sensors and Fibaro flood sensors even got the "Accoustic and visual alarms inactive" parameter set! This is of course not the default value and I'm glad that I actually noticed this after a while.

* Many times It's very hard to reconfigure a value of a device, even though HC2 obviously communicates with it. I can see in the log that the parameter is set but after a few minutes when reloading, the parameters are back to the old values. Seems to be the same issue as in

Please login or register to see this link.

* Several devices, like the Fibaro motion sensor and flood sensor, requires a HC2 reboot after being included or it will not report any breaches.

And finally a few minor GUI related issues:

* When editing a scene using building blocks you have to scroll the browser window to the right position beforehand or the navigation menu popup may not be visible (some entries will often be outside of the visible screen). Of course you never know beforehand where the menu will pop up, so you have to test, then close the menu and scroll to the right position, and then navigate in the menu again. With many devices the popup lists gets pretty long which makes this system really frustrating to use.

* When editing the values for a device under the Advanced tab, like its description, writing anything with the "s" letter will immediately switch to the "General" tab. So you have to switch back to continue writing.

* It would be nice to have a normal visible scroll bar in the Event panel. Right now there seems to be a tiny invisible scroll bar to the right that you can use with the mouse if you don't want to use the keyboard arrows.

* Some actions in certain conditions will result in a 403 - Access forbidden, without telling you what the problem really is (e.g. trying to save the code for a scene that is already running).

* Some of the Aeon Labs motion sensors have the "motion detected" icon shown for days even though it has gone back to "safe" mode according to the event log a long time ago.

* One of my Aeon motion sensors has a broken icon (the image link points to /fibaro/icons/czujnik_ruchu/czujnik_ruchu.png which does not exist). It is setup exactly as the other ones which have the correct icon.

Any help to fix any of these issues is much appreciated.

[MalvinYNJ 4]

No issues on 3.590. 10 devices since almost a year ago. Didn't update at all since updates were all buggy.

[goran 9]

About the Aeon motion sensor having a broken icon, I checked it closer and it turns out that it too has been permanently turned into a temperature sensor in HC2.

My system will soon be mostly a bunch of useless fake temperature sensors... I guess there is still no fix for this and the answer is still to wait indefinitely for the next release? (a week? a month? a year?)

[ Added: 2014-08-29, 19:28 ]

Since I started this thread, two more of my Fibaro wall plugs have died. This means I now have 5 of them unplugged collecting dust. The worst part is that I can't return them and get new ones because they are not allowed to be sold in Sweden. Money down the drain.