Devices migrated from HC2 are unconfigured on HC3, but cannot be removed

[awlieser 14]

Hi all,

I have started the migration process from HC2 to HC3 with most disappointing results - all migrated devices showed as „unconfigured. Soft reconfiguration did not help. So I excluded and re-included each device, but unfortunately the „old“ HC2 devices are still shown and „Force remove“ has no effect.  Any idea how to get rid of the HC2 devices? Thanks!

cheers

Alfons

[Fabir 70]

@awlieserHi, did you already disconncet the power supply from hc2?  If not, try the force remove again.

[awlieser 14]

Hi Fabir, no, the HC2 is still running (z-wave engine resetted) for scene reference purposes.

[Fabir 70]

@awlieserHi, not sure if it helps in this case. I recommend to power down hc2 for the process of deleting the ghost zwave devices on your hc3. After you can start hc2 again.

[awlieser 14]

Hi Fabir, thanks, will try tomorrow!

[awlieser 14]

Hi Fabir, unfortunately that didn't help  Cheers Alfons

Edited February 11, 2023 by awlieser

[Fabir 70]

@awlieserSorry to hear that.

 

If I unterstand correctly, now you have  a number of zwave devices on your hc3 configured working OK. Then the same zwave devices also as unconfiguerd devices.

 

Do you use ZW2 or ZW3 Engine?

Did you try with the force remove button?

Did you go close to the device with the hc3? HC3/HC3L have a very nice feature, called emergency wlan network. I'm using this with my handy set as hotspot. So I can go with the hc to the zwave device (maybe mounted behind a switch or other box) in order to include/exlude.

 

Another suggestion:

Power down hc2

Power down a configured zwave device (it also has an unconfigured sibling)

Then try the force remove button for the unconfigured device

[awlieser 14]

Hi Fabir, cleared the z-wave engine on the HC2 and shut it down. On Hc3 i had to use the z-wave 2 engine while migrating devices. Tried force remove on HC3 - sometimes it works, but only on battery operated devices. All mains powered ghost devices cannot be removed 🙁 Cheers Alfons

Edited February 13, 2023 by awlieser

[Fabir 70]

@awlieserAbout 5 Month ago, I had opend a support ticket about this issue. The fibaro support told me, ZW3 engine was still in alpha status and not recommendet for production.

 

Until a month ago, I had hc3 with the ZW3 engine. Some zwave devices lost connection daily, other sometimes. And other strange behavior happend

 

Now I startet from scratch with ZW2.  All the zwave range issues are gone. Without moving any devices.

 

[awlieser 14]

Hi Fabir, I‘m actually on the z-wave 2 engine (had to switch before migration).

[Fabir 70]

@awlieserOK