Detection of the switch closure should not be an issue for the EZIO devices since the inputs are sampled several times per second. Even when “debouncing” is on, the effective sampling is over 10 times per second. The generated message is a broadcast and we’d like to know where it is missed. Unfortunately we don’t have Indigo set up but we’ll attempt to investigate. Meanwhile tell us:
– What version of firmware is reported by the EZIO2X4?
– Does debouncing the input make a difference in missing events?
– Is the input linked to another Insteon device and thus sending a group message on activation?
This is the same problem that I encountered (and reported to Al) a while back; I have firmware v. 1.7.
>> Does debouncing the input make a difference in missing events?
The Indigo UI only allows you to set input debounce for analog inputs; In retrospect, that doesn’t make a lot of sense…
>> Is the input linked to another Insteon device and thus sending a >>group message on activation?
No — just to the PowerLinc.
Let me know if you need more details…