speedy

I got the Q/A document about 2 weeks ago. I haven't seen any changelogs. Restoring backup from HC2 to HC3 is devices only.

I think we have to agree to disagree on this point ?

Don't want to put anyones mood down, but from official Q/A (80 questions) document from my supplier from Fibaro this is stated: From Q/A document: Will there be any way to migrate from HC2 or HCL to Home Center 3? " With HC3 update 5.021 planned for 20.02.2020, an update for HC2 and HCL will be released, allowing for migration of devices from these units to HC3 (without reconfiguring or removing them). The migration will also transfer their name. Of course, although we are working on this element, there may be situations that we are not able to predict and the conversion of some devices will end in failure. The whole process will be based on the exchange of controllers to keep the Z-Wave network settings unchanged. HC3 will become the default controller with Node ID = 1 to which other devices will report changes. " So, if they haven't solved migration in 2 weeks then it's still devices only.

Really agree, moving devices is the easy part (we still don't know when or how well this will be supported anyhow). HC3 doesn't have any features but Z-wave as of now and will implement during this year.. Knowing Fibaro, this will take to 2021 easy and to solve bugs that comes with the new system. We have to buy a new controller (HC3) and learn a new way of doing things and recode the whole system = I can buy something else that supports Z-wave that is better supported and works today! The exsisting z-wave devices still work, so its the same work but exchenged for something else. I have been looking into Control4 before (not used it), have you used it? Amen!

It's only devices. So, yeah, if moving devices is someones biggest issue and you have zero code, VD, plugins, scenes etc etc then that helps. You still have to redo your entire system.

Amen! +1000 And I'm a certified installer. Eventually they tire you down (not answering, or my personal favourite, giving non-answers that are not relevant) so you don't have the time and energy to respond.

Doesn't Fibaro want to make money? Absolutely UNBELIEVABLE that this is not possible. A migration tool from HC2 to HC3 should be built in from day 1 even when starting to think of a HC3! If I can use all the same components om a HC2 as a HC3 then there should be no excuse for not having a migration tool. And even if som things are not supported, create a report that sums all those devices up. A simple list with "Unsupported apps and devices". The biggest system I have installed has around 150 devices, 250 scenes and LOTS of custom lua and VD´s that controls everything, alarm, light, garage, rental apartments, cameras, sonos, HUE and more. So now you are saying, "yeah, we will support this for now, but if you want to upgrade then you have to rebuild you entire system.." What happens when the HC2 is not supported anymore, and not sold? So now his whole house stops working?! So where is the "save" in money and ease of use that was the main thing? But ok, I get it. NEVER use Fibaro again and do it with a real brand like Crestron, lutron or similar, at least you know it will be supported properly with future upgrades possible. With this behaviour, what happens with HC4, same thing? It's now not financially viable to buy Fibaro if this is the way we have to "upgrade" our systems for future use (rebuilding everything from scratch). Wow, just wow...

Thank you, installed directly, i had a previous version before. It has really helped me in finding devices with trouble! Fantastic work from your side! Wow, amazing. This is what Fibaro should have done from the start along with your script. Hopefully Fibaro makes all these features standard under the "diagnostics panel" in the GUI. But, i will not get my hopes up The users on this forum delivers above and beyond of what we have been asking from Fibaro for years.

Yes, you are surely right. I found devices with troubles thanks to your fantastic script, so thank you for that! And it also shows the importance of this advice, but without your script i would never "know" for sure. Now that i think about it, this should be a standard feature built in to Fibaro firmware. If a device is sending > then X reports during Y amount of time then give a error message in the GUI. Just as when scenes execute over the MAX scene count. After adjusting the whole system and showing that result to Fibaro and still having the same issues, well then the advice is still good, but something else is happening. When is the right time ? You you are right, but due to my settings and all the lovely people trying to solve issues it flooded my work inbox, so i accidentally unsubscribed from the thread and now i can't seem to get back *Sorry for my late reply, work, life and other things got in the way.

Yes, a setting will be too complicated for the average user so, for arguments sake lets say 1 time every day. Yes its a workaround, as there is no "fix". It is a workaround that works so i would consider this a fix as there would be no more ghosting. But i agree with you, replace the chip is the best solution, but for all the devices out there, we need a workaround. I have been using Fibaro since 2013, i am a certified installer and have been in contact with Fibaro so many times over the years. Also in close contact with my countrys official supplier and have visited their office many times and reported, reported, reported. Still over a year later we still have the same freeze issues with Fibaro API for example. I have been ignored so many times over the years, sending logs, video, code examples etc. Finally they just stop answering (after they say you have polling enabled or my favourite " You should decrease all reports – wake ups, energy measurements, temperature etc. It is necessary." that is the problem or similar) You then show that you have 20 reports per day in energy for every device and have polling set for 4000 sec and almost no temp reports but still have the same issues with freeze, then you hear nothing back. I have my own company and smart home business so this is VERY close to my heart. My final straw was when the freeze issue entered the system in november 2017 and has not been fixed since even with a crazy amount of reports. So i can assure you, they are not working on it and it's been proven to me over and over again. I no longer install Fibaro because of it since nov 2017, only for a selected people where i can explain that it has issues, and are you OK with this happening? As evidence, that Ghosting thread is now over 2 YEARS old, and there is still not a workaround provided from Fibaro even with workarounds provided to them. Why? They don't have to (and cant). I have supplied a fix to my customers with ghosting issues using the LUA code, so can Fibaro. We shouldn't have to do this stuff, Fibaro should.

Hi @VampArt and @jakub.jezek . A easy fix form Fibaros side would also to add a 2nd variable that holds the "actual" associations when they are saved from GUI. Those can not be fetched from a device but only saved through GUI in the Homecenter. So if there is a difference between the device associations in the device and the 2nd variable then there are illegal associations and so Homecenter fixes the issue and sends a message about it. So there is a really easy fix, but Fibaro as always doesn't want to fix problems. I have mentioned it before, but, this is Fibaro we are talking about. We are left with ghost things happening in systems, lights turning on when they should not and so on. Even if there is an SDK problem, its still Faros devices and so they should fix it and they can. Only thing left is to fix it ourselfs, really sad when there is a really easy fix. I have implemented this script with customers to run 1time a day at night and automatically fix issues if they are any, it's the only solution. I just can't understand why Fibaro is so reluctant to fix this issue.

This is not allowed according to the manual. It is not a resistive load. Now, you can use this solution, it will work but depending on relay or situation the Fibaro relay might break as its not designd for it.

You are not allowed to use any LED light at all, no matter what type... Only resistive loads are allowed, (regular lightbulbs, radiators that doesent have digital thermostats etc) Thats it! So its very limited in its usage. Anything with transformers, electronics, inductive loads (motors, sprinkled actuators, relays, contractors, blinds, garage door, chargers) you can not use (or is not allowed) according to the manual. Now, you can use it, but its not designed for it and sometimes they break (as you have seen) and sometimes they work (as you also have seen) its a lottery.