Insteon Setup and Controller Software

Last updated: November 08 2018 20:30:00

Insteon Device Discovery Explained

Full Featured, Fully Functional Trial Software

Insteon Device Discovery

Here the device ID 0b fe a5 has been entered with group 5 selected. A click on the [Join/Create Group] button saves the Insteon device to the PLM database and IonW records the results as well. IonW software will query the new device (0b fe a5) for device type and capabilities. Upon verification for device type, IonW software will read the device links database. Each Insteon device stores a links database. The links database is also referred to as an All-Link-Database (ALDB). Devices which have pre-existing links (to other Insteon devices), allow software discovery for other devices pre-existing on the Insteon device network.

Image for New Insteon device entry

The screen shot above shows the first few devices found in the 0b fe a5 All-Link-Database (ALDB) are links tp KeypadLinc controllers. Upon listing the discovered Insteon devices found from the 0b fe a5 All-Link-Database (ALDB), IonW software queries each discovered device for type, capabilities, and reads respective ALDB. Device discovery through software is limited to the pre-existing links found in Insteon devices.

In the above screenshot it shows two wireless devices have been discovered. 1- Motion Sensor 13 f7 29, and 1 TriggerLinc 11 b8 2c. Upon initial discovery by reading other Insteon device ALDB, the IonW software cannot know a device is wireless, but does save un-answered commands (query for device type), for instance, for use upon device activity. For the screenshot I went ahead and activated the motion sensor, and opened the TriggerLinc contacts. IonW sees the wireless device activity and re-sends held commands for those devices. The result is device discovery complete for the two wireless devices. Wireless devices are active during their respective event. Communications with the wireless device takes place during a short window of time (1 or 2 seconds) where the wireless device listens. IonW sends its previously un answered command when a device is active, makes the device type discovery. IonW software knows to hold future commands for wireless devices. IonW general activity log will display commands for wireless devices as held, waiting for device activity.

Image of device discovery log display

Insteon device discovery reading All-Link-Database (ALDB)

Insteon device discovery reading All-Link-Database (ALDB)

The two un-read device type in the screenshot above are 11 ae 92 and 0a 37 6c. Both are RemoteLinc devices. IonW software does not know this yet. A press of the 11 ae 92 DIM BUTTON, results in device type and capabilities discovery. This intern leads to the device ALDB reading, and any previously un-discovered device ID to be found, and added to area 251. Area 251 is hard coded into the IonW software as where all newly discovered Insteon devices end up. From area 251 devices can be put into new or existing groups using either Drag and Drop or the [Join/Create Group] button.

Image for Wireless device discovery

Image for Wireless device discovery

IonW sees the DIM button press from the 11 ae 92 device, gets device type information, and records this information both to the PLM and the IonW software database. IonW software will attempt to read the 11 ae 92 RemoteLinc All-Link-Database (ALDB), by holding the command ready for next activity from this wireless device. Wireless devices such as RemoteLinc need activation. Commands for wireless devices are stored waiting for device activity. o Wireless Activation o For RemoteLinc: Press DIM button. For Motion Sensor: Press set button, or activate motion.

back to top