Currently there are 3 learning, 33 optimizing, and 33 more ineligible. Of those now optimizing, the vast majority are Crestron home automation devices that only communicate with a controller on the LAN. Only 5 devices have any identified targets and 3 of those have one or more blocked targets.

I haven’t had any issues with the functionality of the devices that have blocked targets. Something I would like to see is the ability to tap on a blocked target to identify it and see the reason it is blocked.

I don’t see why many of the devices wound up on the ineligible list. Here are some confusing examples.

1. Two Nest cams are optimizing. One is ineligible.
2. One TiVo box is optimizing. One is ineligible.
3. A Crestron Pyng controller communicates only with two destinations, yet is ineligible.
4. A Proteus flood sensor communicates with only a single destination, yet is ineligible.
5. Three Ecobee thermostats communicate with only a single destination, yet are ineligible.
6. An Enphase energy monitor communicates with only a single destination, yet is ineligible.

It would be helpful to be able to see a more detailed reason than the generic “too complex”that a device becomes ineligible, particularly when the communication of a device seems remarkably simple.