I have been working on v0.5.0 which has this enhancement implemented. I don't have it released yet, but it is available on the
0.5.0 branch. Would you mind trying this new version? I designed the changes in such a way that updating the plugin should have no effect on existing sensors that were configured using the channel selection.
Would you mind checking that all of your sensors continue to function correctly after the update (and plugin restart) and BEFORE opening any of their configuration windows?
The channel selection menu for each device will now include the hardware identifiers to target if so desired. I believe I have everything processing correctly, but a DS1820 add-on will only show identifiers that are DS1820 devices (the same logic holds for DHT22 sensors). There is also a new plugin menu item called "Log Connected Sensors..." which allows you to select a device and all connected sensors are printed to the log.
The only unknown I have at the moment is the frequency at which the /ext_* topic is published. The plugin devices monitor these topics to extract the known hardware identifiers connected to it. So, if the topic hasn't been published between the time the plugin/device is first started and when configuring a device, then the dropdown menu will not show any hardware identifiers. I believe this topic is updated at the same frequency as the sensor updates, but I'm not sure.
If no hardware identifiers are shown, then one thing to try is performing a "Send Status Request" from the Indigo UI on the host device. That has the same effect as forcing the device to announce, and that might force the device to update the /ext_* topics as well.
Thanks,
Aaron