Lutron Integrator Devices Not Showing Up

🛎️ Get Help
1

I am at my wits end. I have added, removed re-added, rebooted, reset and re-added my lutron caseta devices and can’t get them to show up in my Hubitat.

  • I have the Bridge Pro2
  • I have rebooted the bridge at least twice and later reset it to factory default
  • I have rebooted the Hubitat several times
  • I have deleted and re-added the Lutron Integrator app before every new attempt to get the devices to show up
  • I have tried manually entering the devices through the configuration list and the interactive setup
  • I have checked and rechecked the IP address on the Lutron bridge
  • I have checked the telnet settings on the Bridge. I have toggled it on and then off.
  • I can ping the bridge from the Hubitat
  • My network is an Eero and the Hubitat and lutron are attached with network cables to adjacent ports on a 5-port GB switch attached to the main router. Their IP addresses are 2 apart (.74 and .76). The subnet mask showing on the bridge is, oddly enough, 255.255.252.0. I don’t see a place to change the subnet mask on the Hubitat. Based on my knowledge of networking, it shouldn’t be an issue with their IP addresses being two apart and on the same switch. Ero doesn’t give access to this kind of config.

I have some questions to help me understand what is going on.
*when I create the app, is the Hubitat communicating with the lutron bridge to confirm any of the configuration settings?
*If the lutron integrator app were working correctly, and I entered an incorrect device type, ID and name, would it still show up on the Hubitat devices page as an option?
*Is there any way to manually test any switch by software “flipping it” to make sure you are connected? Is there a console that you can send commands?
*Does Hubitat only open a connection with the lutron bridge when it needs to do something. Is there ever a login or socket? Is it only message-based and at time of an action?

2

My guess is a connectivity issue caused by the subnet mask. I think we have seen this before.

1 Like
3

One way you could see the connectivity between the Lutron and the Hubitat would be to look at the logs of the Lutron Telnet device that is created on the Hubitat when you install the integration app.

Here is a sample of what it looks like (during normal device operation):

image
image789Ă—937 106 KB

4

Hubitat opens and persists a Telnet connection to the Lutron Caseta SmartBridge Pro. All communications is then handled over this Telnet session. This allows for real-time status updates in both directions.

1 Like
5

Make sure you have it toggled back on

Make sure those addresses are set as static DHCP reservations on the router. Note you should do this for any device that is to be controlled by Hubitat.

No, no error checking

Yes, there is no error checking

Yes, as posted above you can check the Hubitat Telnet device logs. Flip some switches/dimmers manually. Hubitat should see the communication. You can send your own commands, but you need a Telnet client on your computer. It's easy to add, but not a standard part of either Windows or MacOS. The Telnet commands for dimmers are pretty simple and are documented on page 143 of:

For a dimmer you'll see something like 'OUTPUT,38,1,75.00' That represents setting integration ID 38 (device number from the integration report) to 75%.

1 Like
6

I found a workaround, and I can’t decide if it will be problematic. In the eero network app that controls the router and mesh network devices, I set port forwarding for port 23 (the telnet port) to always forward to the lutron bridge. Now it works.

This suggests that the eero network blocks telnet (not surprising). Eero doesn’t provide access to a great deal of the configuration, so it doesn’t appear to be possible to turn off that default firewall setting. This may be a problem if I get some other bridge.

2 Likes
7

Can you put your Lutron hub in the same switch as the Hubitat Hub. That way they will communicate without any disruption from WIFI bridges?

I would keep both on the same network and not use port forwarding.

8

You may want to check that you didn't just open a hole to let in the WWW.

1 Like
9

Good point. I probably just invited the whole world to turn my lights on and off.

10

Looking for you now.... :rofl:

11

They are on the same unmanaged switch. They are even in adjacent ports. Haha

12

Are they both on the same class C network (10.1.1.X) and have the same gateway?

13

Can you post the IP address and gateway of both hubs. Also I have found that if your switch is not rebooted when the router is rebooted you do risk an IP conflict so try rebooting the router(s) and then powering the switch on and off.

All of my router reboots always include a switch reboot.

14

I'm using Caseta telnet with HE, all on my (single) Eero Pro 6 - never have had an issue with any of it.

My Eero setup is very vanilla / stock -- outside of reserving IPs in the app, I've never touched any of the other networking options.

15

I have three stations on my eero mesh. That is known to cause some issues. My sonos has been flaky at times. I haven’t worked that out either. From what I understand, each of the separate mesh repeaters has some functions that are similar to those of a router and this can cause problems when devices communicate between repeaters on the LAN. I am still working on that.

16

So I seem to have it figured out. I manually configured the network to be have only 254 addresses (there are a few used for the management of eero) and set the subnet mask to the more typical 255.255.255.0.

I won’t have the larger 1024 devices available to me, but at least it all works now.

1 Like
17

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.