we are doing integration with lutron QS System using r04 modules?
First the integration was working well... but after I updated the Pro3 to the latest firmware the connection with lutron processors missed and it always waiting,? unknown and sometimes connected .. but we cannot control lutron anymore?
I found that the new firmware blocks the telent port 23?
and can not be enabled again .. the true blue support mentioned that I need to generate a license... I am not sure if this will fix the problem or not ...?
then I tried to use rmc3 processor with the old firmware and purchased after jul 2019 ... but the same no connection available with lutron ...?
can any one help what are we missing out here ??

开云体育

Firmware blocking the telnet port is not the problem. You need a Lutron 3rd party lighting license from Crestron. They are free now just have to submit your processor info to them. If you look in your error log after a boot it will have a message about certain MAC addresses that need a license.?

I've actually run into 2 projects where the processor had a current license and had been operating fine.? Upon updating firmware, for whatever reason, the lighting stopped working and reverted back to pre-license operation.? Nothing worked and we actually had to remove the applied license (PITA - consists of prompt commands), rename the hostname (although we were told this didn't matter in the key generation), and have a new license key generated for the processor.? Once applied, it started working again.

Day in the life...
--
Ryan Baldwin
CEO | XS Design Studios
rbaldwin@...
760.712.2240

I just RMA'd a AV3 because it would stop talking to Lutron.? Delete license, get a new one and everything was good for 6 months until it did it again.? Same fix as before.? They sent me an advanced replacement, which I thought was a bstock, that had a new SN structure.? As of this year and processor that SN starts with a minimum of 20xxxxxx does not require a license.? Easy way to tell if it is the license.? Open a cmd window and ping the Lutron processor, if that is good.? Then open toolbox text console and ping the lutron processor.? I Bet it fails.? Use text console to delete the license, then go through the process of getting a new license.

thanks dears for information?

I will second what Gablerjohn said I went thru the exact same situation. But if your processor can ping the Lutron even sometimes, then its probably not going to be the license. The few times I had license issues I could never successfully ping the Lutron. Were there any changes on the Lutron side? If they updated the Lutron QS version it may have been to a version that requires something other than the old lutron/lutron telnet login, and you are locking out the comms due to old unsupported credentials.?

Lutron made a change at v15 I think, I know this applies to QS15.4 (RA2 12.7) and newer so if you upgraded Lutron this may be your issue. You can no longer use the default login as you did in the past. You will need to create a new telnet login in Lutron and use that for integration, and it cannot be lutron:lutron.

Hi Guys,

We have continually had issues with the third party lighting licensing on Crestron processors.
The Crestron processors block communications based on the MAC address of third party lighting systems such as Lutron, Vantage etc.

The way we implement our systems now is to put the lighting controllers on a separate VLAN and configure inter-VLAN routing in our routers/switches between our "Control" VLAN and "Lighting" VLAN.
This way, the MAC address is not passed across VLAN's so Crestron will not block connections to the lighting controllers.
This also eliminates the need to request the third party lighting license from Crestron.

In some cases where we have enabled authentication on the Crestron processors (which blocks the telnet port) we have configured Lutron to use a different port for telenet and set the port on the TCP/IP connection in the Crestron program to this new port.
We have never had a problem with this method to date.

Hope this helps,

Rob Maher.
Liquid Automation NZ.