Provide a seamless migration/upgrade path from old to new fingbox

When replacing an old fingbox with a new one for any reason (an upgrade from V1 to Vn, a broken one requiring replacement, etc.) you must delete the old network and redo the onboarding procedure for the new one, thus losing several of the configurations you may have done on the old network. The request is to provide a "migration" path allowing to replace an old FingBox with a new one retaining all the network configurations.
8 votes

Active · Last Updated


  • DHufstader
    DHufstader Member Posts: 4
    First Comment Photogenic
    I agree, my original fingbox from kickstarter just died, wouldn't power on at all and just replaced it, the amount of custom information lost in the process is depressing.  it took me  a long time to name everything, set alerts, etc..  I had 150+ devices added.