Devices not configured after migration

[Blackmurray77 0]

Hi, after the migration from HC2 to HC3 i see almost all devices from HC2, but all of them are "not configured" no of the device is working. The devices are in the configuration queue, but after more than 12 hours nothing happened. Can somebody help? Print screen attached. Thx.

 

Please login or register to see this attachment.

[Bruno50 0]

Hello,

 

I have exactly the same issue. All devices are "not configured" after migration from HC2  to HC3. Did you get a solution ?

thanks.

[Blackmurray77 0]

Hello,

 

unfortunatelly no. I had to newly configure all the devices

 

 

[Johnvigna 0]

Same problem, I hope it's not necessary to reach every device and that it can be done from the switches. Any advice?

[JDF 0]

The solution is not to fund incomplete products or take on manual work yourself. In just a "few" years, HC3 will also reach its End-of-Life (EOL) stage without support. It’s time to vote with your actions—and your money. The company has already abandoned users by neglecting HC2, and it’s unlikely they’ve changed their approach for HC3. In fact, before EOL, they removed features that previously worked well.

[Sankotronic 2,249]

Hello @JDF ,

 

What you wrote is pure speculation, and it is known that speculation is mother of mistakes (fu.. ups).

I still have HC2 with FW 4.630 that is controlling my house without any issues, except those ones that I coded

 

1 hour ago, JDF said:

The company has already abandoned users by neglecting HC2, and it’s unlikely they’ve changed their approach for HC3. In fact, before EOL, they removed features that previously worked well.

 

Well, that was expected since HC2 is EOL and there will be no more updates. It is not Fibaro specific, but all companies does that with their EOL devices.

 

I'm more interested in your assumption that Fibaro removed features that previously worked. Can you be more specific on which features do you refer to? I ask, because I didn't noticed any features removed from my HC2 since last update 4.630.

 

If you referred to HC3, then they are still actively working on improvements, and I can agree that improvements are going slow, having z-wave engine 3.0 and ZigBee still in beta, but that is not entirely depending on them.

 

[JDF 0]

14 minutes ago, Sankotronic said:

Hello @JDF ,

 

What you wrote is pure speculation, and it is known that speculation is mother of mistakes (fu.. ups).

I still have HC2 with FW 4.630 that is controlling my house without any issues, except those ones that I coded

 

 

Well, that was expected since HC2 is EOL and there will be no more updates. It is not Fibaro specific, but all companies does that with their EOL devices.

 

I'm more interested in your assumption that Fibaro removed features that previously worked. Can you be more specific on which features do you refer to? I ask, because I didn't noticed any features removed from my HC2 since last update 4.630.

 

If you referred to HC3, then they are still actively working on improvements, and I can agree that improvements are going slow, having z-wave engine 3.0 and ZigBee still in beta, but that is not entirely depending on them.

 

They removed the Setpoint option for Heatit thermostats. While the setpoint functionality itself still works, it isn’t visible in newer apps like Yubii (the last working app for HC2). However, you can create a virtual device to control it—a workaround I’ve implemented for some older clients. The setpoint remains visible in older apps, such as Fibaro for tablets, but not in newer ones.

I’ve submitted numerous tickets about this issue, but the support team seems unable or unwilling to address it. Their suggestion to use Fibaro’s heating panel is flawed because it overwrites all Heatit changes.

I feel I can’t trust or recommend such company. HC3 has its own unresolved issues that should have been fixed before release. Or better yet, fix the current errors on HC2 before you release a new problematic version.

[Sankotronic 2,249]

2 minutes ago, JDF said:

They removed the Setpoint option for Heatit thermostats. While the setpoint functionality itself still works, it isn’t visible in newer apps like Yubii (the last working app for HC2). However, you can create a virtual device to control it—a workaround I’ve implemented for some older clients. The setpoint remains visible in older apps, such as Fibaro for tablets, but not in newer ones.

 

Hi @JDF ,

For HC2 I'm still using old app which is much better than the old Yubii app. Yubii app suppose to be compatible with both HC2 and HC3, but for me it never worked well with HC2.

Now for HC3 Yubii Home app is much better, so you can forget Yubii app and I think Fibaro will forget it if they already didn't.

 

8 minutes ago, JDF said:

I’ve submitted numerous tickets about this issue, but the support team seems unable or unwilling to address it. Their suggestion to use Fibaro’s heating panel is flawed because it overwrites all Heatit changes.

Even Yubii app never worked with my HC2 setup, I never submitted any tickets, since I knew that it is just made as test if they can support both platforms, but that was experiment that was never finished properly, but for some people it served its purpose. Now they have Yubii Home app that is not that bad for newer gateways, while old Fibaro Home app is more than usable with the old platform. Maybe it doesn't look fancy and modern, but it works which is more than enough for me.

 

11 minutes ago, JDF said:

I feel I can’t trust or recommend such company. HC3 has its own unresolved issues that should have been fixed before release. Or better yet, fix the current errors on HC2 before you release a new problematic version.

 

Well, in that case there are many others you will loose trust too. For many years I believed that my neighbor grass is much greener than mine, but that was only when I was standing on my lawn. Of course, on the other hand it is not bad to experiment with other grass, it might be beneficial at the end it might really became much better for your expectations.

[JDF 0]

Fibaro for tablet has been removed from the app stores - we use it on devices that still support it. But it doesn't work with newer devices... So its still a no-go. Fact is that they ended HC2 support much earlier by not fixing its errors and introduced new errors - made a "test" yubii app that does not work as well... I tried to point out these and other errors many times - when HC wasn't EOL. Sure others have also their problems too but fibaro takes the cake imho. Why buy another half assed product?

Edited March 11 by JDF