Posts: 40,483
Threads: 491
Joined: Aug 2002
10-29-2019, 12:52 PM
(This post was last modified: 10-29-2019, 12:54 PM by Dean Roddey.)
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.
Dean Roddey
Explorans limites defectum
Posts: 720
Threads: 124
Joined: May 2019
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)
Posts: 40,483
Threads: 491
Joined: Aug 2002
It's just that, normally with something like this, you have an integration id which is the thing itself, and then if it has multiple sub-thingies inside it, those are component ids. So a light has a zero component id because there's just a light. A keypad has an integration id then the LEDs inside it have component ids (with a particular LED being addressed by a combination of the two.) But it looks like the visor thing itself is not separately addressable and you just give integration ids directly to the various bits inside it.
It's just inconsistent relative to the way the other bits work, so I was questioning whether I was reading it right.
Dean Roddey
Explorans limites defectum
Posts: 720
Threads: 124
Joined: May 2019
Hey Dean wanted to follow up on this on as well to ensure the functionality described in my other post is intended. You have to set the switch value to the opposite of its current value for it to activate the output. That is, if the value of the switch is True, then you have to set it to False, and vice versa in order for it to activate the output.
https://www.charmedquark.com/vb_forums/s...#pid155966
Posts: 720
Threads: 124
Joined: May 2019
Posts: 226
Threads: 27
Joined: Apr 2012
Dean, there are other devices that can be added to the RA2 ecosystem, which will act as outputs. The model is LMJ-CCO1-24-B which was only available to Inclusive level until recently. There is an RF switch and 0-10V dimmer version of similar devices. These will show up and will act as any other dimmer, switch, output etc when added and programmed to RA2
Posts: 426
Threads: 39
Joined: May 2006
Dean, while you're in the RadioRA2/Caseta driver could you add support for the Fan Controller and Shade Controller? Thanks.
Posts: 40,483
Threads: 491
Joined: Aug 2002
I have what I think are the required changes for Visor contact closures for the back end driver. I'll need to update the client side driver as well. Then I'll have to connect to someone's system who has one since these changes are too much to trust just doing it by eye.
Dean Roddey
Explorans limites defectum
Posts: 720
Threads: 124
Joined: May 2019
(11-13-2019, 04:45 PM)Dean Roddey Wrote: I have what I think are the required changes for Visor contact closures for the back end driver. I'll need to update the client side driver as well. Then I'll have to connect to someone's system who has one since these changes are too much to trust just doing it by eye.
You can access my system for the Visor controls, just let me know (PM me).
Posts: 40,483
Threads: 491
Joined: Aug 2002
Tomorrow evening would be ok. I have the client side driver updates done. In this case it's IP, so just a port forward. You can change the login info after I'm done. I'll need to know the integration ids of your contact closures. And of course you'll have to stop your local driver so that I can get to the RA2 system.
Dean Roddey
Explorans limites defectum
