Lutron RadioRA2 Driver and Lutron Visor Control

[Dean Roddey]

OK, give this guy a try. As always, import, then do a reconfig on the driver to pick up changes.

[gReatAutomation]

Thanks. I'll have a look at it.

[gReatAutomation]

Thanks Dean. Am I supposed to use a specific option? I thought there would be a "Contact Closure" option. The options available are the same as previous:



The package imports fine:



I even deleted the driver and re-added it but Contact Closure is not in the driver info:

[Dean Roddey]

Oh, duh! Just sending you the driver pack won't help. The client driver was updated as well and it's a C++ driver so it can't be gotten except with a new code drop. Let me see where I stand. I have a number of changes. I need to take a look at the Dune driver, then maybe I can do a new drop.

[gReatAutomation]

Sure no problemo. Thanks.

[gReatAutomation]

Hey Dean, just following up on this to learn when there would be a new drop.

[Dean Roddey]

Not yet. Because I'm doing this Linux stuff, the changes I'm making are much more fundamental than normal. So it takes a lot more time to test for a release, which means I can't do them as quickly as normal. And I'm also trying to make sure that something someone reported is either taken care of not my fault and it's a tricky one to be sure of (also made worse by the more fundamental changes I'm making, which are that much more suspect any time something appears iffy.) Of course the irony is that then it ends up being in some code that's been around forever, but you always suspect the stuff you've been changing and spend your time trying to blame that.

[gReatAutomation]

Understood thanks for the context.

[Dean Roddey]

So I'm not seeing any discrepancy between the driver's reported set point values and the ones shown on the thermo, either when setting them via the thermo interface or via the driver. I've been running them up a degree at a time, which would show up any rounding issue at some point when it hit the needed magic value, and they continue to agree.

There is a five second delay or so since the thermo doesn't immediately set the new set point. It waits until it's pretty sure you aren't going to make another change. But then it sends outs the value and they seem always agree for me.

[gReatAutomation]

Updated thread: https://www.charmedquark.com/vb_forums/s...?tid=10936