There is a trick for this. Pair it to a phantom switch and make Hubitat use the device as the trigger. By phantom switch, I mean a device that is added, paired to the occ sensor, and then physically removed. The switch (which is no longer powered or even in your house) will still have it's state communicated over telnet. Expensive, but if you know somebody who also has Radio Ra 2 switches, it works. There does seem to be a delay though - if you have Hubitat use the Lutron sensor (which is actually the phantom switch) to turn on a real Lutron switch, it can take 3-4 seconds for the action to happen. Seems like the it's an issue with telnet - something is causing a delay.
Maybe I should back up and explain what I’m trying to do in this specific case with Lutron and Hubitat. I have Hue bulbs in a few rooms. I would like to program scenes to Pico Remotes to control the Hue bulbs using Hubitat, including dimmer and color settings. It was my impression that this could be done in Hubitat. Research there led me to requirement to obtain the Caseta Pro bridge. I’m almost at my limit with Caseta devices, so rather than throw more money at Caseta, I’m looking at stepping up to Radio RA2 instead.
Yes, once you have them added to the main repeater Hubitat can talk to them. However, you need to know their "integration id" number. Ordinarily you get this from the Essentials software. There is another method to find the number:
Connect to the main repeater with a telnet session from a terminal app on you PC. Credentials are username: lutron, password: integration. Then hit a button on one of your Picos or other devices. For a Pico you will see a message on telnet that looks like
~DEVICE,12,2,3
The 12 in that example is the integration id. The 2 is which button was pushed, and 3 means pushed.
Other devices may look like this:
~OUTPUT,5,1,100
In that one, the 5 is the integration id. This was a switch turned on.
Then you can setup the Lutron Integration app, giving the devices names, identifying them with the integration id, and selecting what type of device it is. This creates virtual devices in the Hubitat system that correspond to the Lutron devices, and behave accordingly.
2 Likes
Perfect, thanks for that explanation, all clear now... just ordered my HE
1 Like
Sorry to return here but I've searched high and low, deleted and re-added devices and having no luck. I'm all done with RA2, have Inclusive software, integration report and can setup a 1 Pico remote system (for now), I can see the PIco in Telnet.
Set it up in Hubitat:
Created a simple automation with the remote:
But the button press does nothing to the lights. I confirmed I can control the lights within Hubitat. It seems like there is a breakdown between HE and Lutron, see below, wouldn't there be activity on one of those (last column)?
I also noticed the DNI for the Lutron Telnet and Devices seems to be changing, I'm pretty sure one of them last night was _89. Not sure if this is normal behavior or not.
It sounds as though your Lutron Integration installation is messed up. Please show a screenshot of the Lutron Integration app, and of its app status page.
Adding to this, Hubitat is definitely seeing button press on the Pico, it is logging activity on the device:
But Telnet logs no activity as you can see here:
Not sure if this is normal or not.
I have also tried removing and re-adding Lutron Integration, the device and the simple lighting rule. I also tried moving my Main Repeater, wiring directly into my router (instead of via a few switches). None of this has worked, although I noticed that when moving the Main Repeater on the network, the Pico1 device on Hubitat stopped registering activity until I removed and added it back again.
What is the Lutron Devices device?
I need to see the Lutron Integration app status. Have you given the main repeater a static IP? If not, you should do so. Also, have you tried connecting to the main repeater by telnet? Login credentials are user: lutron, password: integration. You should be able to see the Pico button presses there, and be sure you have the correct id# for the Pico. It will be the first number shown on one of those button presses.
What you showed above was the app status for Lutron Integrator. Need to see for Lutron Integration.
Where do I find the Integration app? When I click the button to install new built-in app this is all I see:
As for telnet, yes I can connect, sent a screen shot of that in a prior message. Button presses are there and I am using the correct id# for the Pico. The Main Repeater is using a static IP.
First you install Lutron Integrator. Then Lutron Integrator will give you the option to install Lutron Integration.
Then you use that to include your Pico and any other devices you want to use in Hubitat.
Ok I got it working. Had nothing to do with the Integrator/Integration. Hubitat Pico button numbers are different from Lutron - I had the simple lighting rule set to buttons 2/4 on/off and Hubitat sees them as buttons 1/5 for some reason. I found the Hubitat button number under Pico device - Events. Will rely on that events page to guide me on button numbers going forward. Thanks for all of your help!
@bravenel as the Lutron expert 
Can you please assist me on the below?
I have the RA2 main repeater installed and working properly with my Lutron devices. I have also set up the username: lutron and password: integration in the Essentials software.
To have it working on Hubitat should I have a smart bridge pro? I ask it because I cannot find any “Advanced/integration/Telnet support” link in my Lutron app.
I tested adding a pico and Hubitat is logging its activities but it is not working. Any suggestions on how I should proceed?
Thanks!
The Smart Bridge Pro is for Caséta. The RA2 equivalent for this purpose is the Main Repeater. You do not need to enable telnet specifically, though if you set up or upgraded your system recently, you need to make sure the formerly default username and password remain or are added (which it sounds like you did) in the RA2 Essentials (or Inclusive) software. This software can also get you the integration report with the Lutron device IDs you need to set up the telnet integration (under Reports > Integration, as you undoubtedly remember from the training).
It actually sounds like you have everything set up. I'm not sure what you mean with "logging its activities but not working." Did you use the Lutron Integrator app to create devices in Hubitat for each of the Lutron devices you want to integrate? (This is where the Lutron device ID comes into play: you match it up, either manually or with the wizard, with the type of Hubitat device you want to create based on it.) The RA2 integration report is quite large and has a lot of spaces for scenes and things you might not be using, so if you're just trying to add a couple devices, you might have better luck just looking at live logs for the Lutron Telnet device in Hubitat ("dev"456" in my example below) and getting the device ID from its logs. For example, if you press a button on a Pico, you'll see something like this get logged:
dev:456 - rcvd: DEVICE,23,8,4
The "23" (first number you see in the actual log text) is the device ID for that Pico. It's in the integration report, too, just buried under a lot of columns. 
I changed to the formely default username and password and now it is working! Simple as it is 
Thanks for your suggestions!
1 Like
im having a similar issue, i have the latest Ra2 Inclusive, setup lutron/integration in the software, static IP on the main repeater, added the Lutron integration app, setup a keypad, but i get no status as far as hubitat seeing it.
-
in the integration app you will set up at least 1 device - the main repeater. It will show as "k,1,Main Repeater" in the integration app. Your keypad will show as something like: "k,11,Kitchen Keypad". The device number must be the same as from the Lutron integration report from the Inclusive software. Each device will also be listed in the Devices list.
-
Check the Hubitat logs. The integrator app also creates a device (in the Devices section) for Telnet communication. You should see log entries for any actions that occur on your Lutron system listed under the Telnet device. The device ID should match the one from the integration app. For example, a push of button 1 from the keypad above would show as "DEVICE,11,1,3"
It sounds like you are starting a new hub/Lutron installation. If things don't work try deleting the apps and devices (Telnet, main repeater, keypads, dimmers, picos) and starting over.
Use a computer with a terminal app, and see in you can login to the main repeater with its IP address, username: lutron, password: integration. Only if this works will Hubitat work.
Hi, When I try to enter "lutron" and "integration" with a terminal app (Putty), I get Bad Login.
Where can I change these ? (can it be changed ?)
Hubitat, the main repeater all use reserved addresses.
This is what I get in my logs:
dev:12020-09-01 12:12:30.057 debugheartbeat- message sent...
dev:12020-09-01 12:12:30.053 debugts- ct:1598980350045, lhb: 1598980350045, age: 58043
dev:12020-09-01 12:12:30.046 debuggetReTry- reTryCount:0
dev:12020-09-01 12:11:32.104 infoTelnet connection to Lutron interface established
dev:12020-09-01 12:11:31.037 debugtxt: bad login
dev:12020-09-01 12:11:31.033 debugraw:[32, 98, 97, 100, 32, 108, 111, 103, 105, 110]
dev:12020-09-01 12:11:30.060 debugheartbeat- message sent...
dev:12020-09-01 12:11:30.056 debugts- ct:1598980290051, lhb: 1598980290051, age: 60006
dev:12020-09-01 12:11:30.052 debuggetReTry- reTryCount:0
dev:12020-09-01 12:10:30.078 errorTelnet connection dropped...
dev:12020-09-01 12:10:30.075 debuggetReTry- reTryCount:1
dev:12020-09-01 12:10:30.072 debugtelnetStatus- error: send error: Broken pipe (Write failed)
dev:12020-09-01 12:10:30.057 debugheartbeat- message sent...
dev:12020-09-01 12:10:30.053 debugts- ct:1598980230045, lhb: 1598980230045, age: 59990
dev:12020-09-01 12:10:30.046 debuggetReTry- reTryCount:0
dev:12020-09-01 12:09:30.106 warnTelnet is restarting...
dev:12020-09-01 12:09:30.102 debugtelnetStatus- error: receive error: Stream is closed
dev:12020-09-01 12:09:30.071 debugheartbeat- message sent...
