This page is a list of various Insteon user use cases. These are activities that a user might attempt along with a description of the associated steps. This list should serve two goals:

1. Discussion of the relative merits of each use case and the associated steps
2. Provide input to those that might try to test the Insteon code after changes

Table of Contents Use Cases Add a new device to network Remove a device from network Change out a device with a replacement Voice Commands PLM Dimmable Device PLM scene

1. Edit the .mht definition file to add the device and any scene associations
2. Restart MH or reload code
3. Device: link to interface
4. PLM: sync links

1. Device: unlink with interface
2. Edit the .mht definition file to remove the device and any scene associations
3. Restart MH or reload code
4. PLM: delete orphan links

1. Device: unlink with interface
2. Edit the .mht definition file to change the device ID
3. Restart MH or reload code
4. Device: link to interface
5. PLM: sync links
6. PLM: delete orphan links

• complete linking as responder:
• initiate linking as controller: Same as holding down the PLM set button. The PLM will "learn" a device if the device set button is also held down
• cancel linking: Take the PLM out of linking mode
• delete link with PLM:
• scan link table: Dump the MH aldb table for the PLM and re-read from the PLM

log links: List all the PLM links in the MH aldb table

• delete orphan links: Compare the MH objects (devices and scenes) to the MH aldb tables of every device and PLM; initiate delete requests if additional links are found. Note that this process ignores two types of manual links; links where the PLM group 1 is a controller to the device and links where the device is a controller to the PLM.
• AUDIT - delete orphan links: Audit of the above process.
• scan all device link tables: Initiate a scan of all devices and the PLM. This will dump the MH stored aldb and re-read the device.
• sync all links: Compare the MH objects (devices and scenes) to the MH aldb tables of every device and PLM; initiate add requests if the devices are missing links. Note that this process adds some links that are not specified in the .mht files, specifically links where the device is a controller to the PLM.
• AUDIT - sync call links: Audit of the above process.
• log all device ALDB status: Lists various device attributes including hop count, engine version, ALDB type, ALDB health, and ALDB scan time.

• sync links:
• link to interface:
• unlink with interface:
• status:
• get engine version:
• scan link table:
• log links:

• sync links:
• initiate linking as controller:
• cancel linking: