Search the Community

Hello all! As many of you know I'm developing UHAS (Universal Home Automation System) for Fibaro Home Center 2. This is complex system that should make Fibaro users life easier and give them decent HA without needing to dig into the programming in LUA and also should support 27 different languages with automatic translation of VD's. I use that same system on my HC2 and till firmware 4.140 it was working great. System was responsive and even CPU usage was a bit elevated it was not making my box sweating. After introduction of FW 4.170 everything fall apart. That system was first to introduced lags in the system and also CPU usage get more wild. It was first FW that FORCED me to make complete RECOVERY due to never ending "Starting services". Before 4.170 all problems could be solved by either rebooting or restoring latest backup. Latest betas 4.503 and 4.504 continue to make HC2 less good but introduced new backup system. To make story short, new firmware upgrades are making HC2 less capable but in the same time new backup is introduced that will make it possible to restore it to another gateway. This looks to me like Fibaro is trying to copycat Apple. Apple practice is to introduce new updates to older devices that usually make them slow and annoying forcing users to buy new devices. Is Fibaro trying to do the same? My experience in short with my system (HC2 with 101 included z-wave devices: 4.080 - started to develop UHAS since first preliminary tests proved that this is doable 4.100 - Introduced icon problems so had to rewrite UHAS code that handle that part 4.120 - found problem in UHAS code that could make gateway stuck with API calls due to way how HC2 was handling non existing icons in VD's. Problem could be experienced only after recovery when icons are deleted and backup is restored 4.140 - More than 50 UHAS compatible VD's and almost 20 UHAS compatible scenes are running smoothly on this system with slightly elevated CPU and memory usage. System runs for more than a month without any problems. 4.170 - Same UHAS configuration as on 4.140 is making CPU usage berserk (crazy, more elevated) and lags are introduced to system. Lags are of different length, from 1 to 60 seconds. All z-wave activity is stacked in memory and can be seen happening on GUI but with delay. So it is not z-wave that has lags, but system is not capable of reading all z-wave activity so it is stacked in buffer and then read with lags. 4.180 - same as 4.170. This one should only solve remote connection problem introduced with 4.170 4.503b - more resources are eaten by the system leaving UHAS less space to work. CPU usage is so crazy and jumping so much that I don't even believe it any more. lags in the system get worse or at least was not solved. Also introduced some new debugging like API: Not found etc. which definitely introduced more problems to LUA execution speed. I have completely rebuild my z-wave network on this FW to avoid any trouble caused by older z-wave devices. I can tell you that Fibaro motion sensor 2.8 and D?W sensor version 2.5 are not properly included in this FW 4.504b - All the same. System can became completely unusable due to long lags in the system where z-wave is responsive but system is getting all z-wave activity with lag. At the moment I have no idea what to do next. I have freshly builded HC2 with included 101 z-wave devices with some decent code but doesn't work! Fibaro what is your next move?