I am wondering if i setup lutron controls on my lutron pro hub and have it hardwired will it control the lights if the hub is down for some reason? The WAF (wife acceptance factor) says i need everything still working even if i have the hub off for some reason (both hubitat and lutron pro hub).
So with that...does it work?
also any combo units that will control both fan and lights if the wires exist?
Lutron Switches, Dimmers, and Fan Controllers will continue to function as manual controllable devices if Hubitat and/or The SmartBridge Pro is offline for any reason.
The only device that I know of that works with Hubitat to control both fan and light is the Zigbee Hampton Bay Fan Controller (HBFC) available from Home Depot. Plenty of threads already that discuss this device that you can read through. The biggest thing to know is that you MUST use a Zigbee repeater device in the same room as the HBFC.
If you have two separate switches already, Iād go with a separate dimmer and fan controller. I use a hardwired HBFC with a Pico remote in place of the old switch as I only had a single switched line to the fan.
The HBFC with hardwiring and a pico seems to be a very common solution. I've got two HBFC's in my living room, and knock on wood, nobody has turned them off since I installed the HBFCs.
I've considered a couple of Zooz Zen-21 or Zen 26's to replace the dumb switches, and just doing an If-Then condition to ensure the switch is on when my automation is set to start, but so far that seems like over engineering....so far.
I suggest leaving the switch but putting a cover on it in case you ever need to reset it due to power outage like shown. I have a Pico on a pedestal that controls the fan and light.
does the device generate any logs in Hubitat when it's activated physically or via the lutron app?
you may have to enable debug logging on your lutron telnet device to see these if they exist...
Edit: After giving it a while or turning on the debug. I am now able to control the device from the device page which I wasn't after initial install. So problem solved itself apparently.