Cleaning Up Insteon Hub 2 (2245-222) For Migration to OpenHAB 3

[nhoe...@sinet.ca]

I had configured the Insteon Hub 2 using the Insteon Android app.  Fortunately, I only have a small number of dimmers/switches/door sensors/leak detectors.  I had set up one schedule using the Insteon app that appears to use group x'0a' and was testing an 8-button mini remote that appears to use group x'10' to control a dimmer module.  

Now that the Insteon servers are gone, what is the best way to clean up the Hub 2?  The simplest solution would be to factory reset it and relink the various devices, but there are conflicting stories as to whether the hubs are bricked by this process.  I could use insteon-terminal to clean up references to x'0a' and x'10' groups but I do not know if the Insteon Hub will continue trying to communicate with these groups.  Lastly, I could manually unlink and relink the devices.  The Insteon documentation suggests that schedules disappear when all linked devices are removed.

Any suggestions would be greatly appreciated!

[nhoe...@sinet.ca]

Although I found one post that suggested backing up the hub database using Insteon Terminal, doing a factory reset of the hub, and then restoring the database, I decided to play it safe and manually unlink everything - I do not have a spare hub and Insteon equipment is getting expensive.  

The unlinking process often left link records in either the hub or the devices, even after multiple unlink attempts.   Often, the Insteon Terminal removeController/removeResponder (on the device) or removeResponderOrController (on the hub) commands would clear the links.  Some were stubborn but a removeDevice worked.  I had a motion sensor that was still linked to an Insteon PLM (long gone) and none of these commands worked - I ended up factory resetting the motion sensor.

I then linked each of the devices to the hub, first initiating the links from the hub, and then from the device.  The hub and device databases were now clean without any duplicated links or groups.