10-29-2019, 05:27 PM
(This post was last modified: 10-29-2019, 05:30 PM by gReatAutomation.)
(10-29-2019, 12:52 PM)Dean Roddey Wrote: Oh, OK. So the integration id is the output. I was thinking it had to have something to target the visor guy itself and that the int. id was that, then you need a component id for each of the outputs? Can you only have one visor and so each output just gets an integration id and that's it? If so, that's really inconsistent but I guess it would work.
The four outputs are maintained / momentary Contact Closure Outputs (CCO) that can control up to four (4) garage doors or motorized gates.
You can also add 2 Contact Closure Inputs (CCI) and 6 programmed Keypad buttons. The 6 programmed keypad buttons can be mapped to the 1 of 2 Visor Control Transmitter buttons. And the Visor Control Receiver can support multiple Visor Control Transmitters (up to 10).
So you could have a Visor Control Transmitter button with Away or Home, for example, programmed that would then allow you to press the button then have CQC take actions for Home or Away. There are a litany of things that could be done with this.
Ultimately, would be good to ensure this is supported. It's all on PDF page 140.
Happy to ship you my Visor Control Receiver for testing. I got it off eBay.
![[Image: Screen-Shot-2019-10-29-at-21-03-23.jpg]](https://i.ibb.co/gjPwTYX/Screen-Shot-2019-10-29-at-21-03-23.jpg)