The Lutron App in Hubitat grabbed a new IP address again messing up some automations and once again forcing me to troubleshoot the issue until I figured out this was the problem.
The correct IP address listed in the Lutron App on my phone is also reserved in my router. And in the Lutron App on my phone, I have it set to DHCP, which I think is what I was told to do previously. So.... what else can I do to keep this ip switching thing from happening? I mean it's easy enough to fix once I know that's the problem but I'm not sure why Hubitat thinks its IP is something else.
The app doesn't grab an IP address from anywhere. It uses the IP address entered by the user. The address doesn't change magically.
So, if the address for the bridge in Hubitat differs from that in the Lutron app, there are two possibilities:
Someone changed the address on Hubitat.
The bridge got a new IP address (which is naturally reflected in the Lutron app and router).
Edit: Case-in-point - the IP address of my Caseta Pro bridge hasn't changed in 3.5 years. Despite my having changed routers in that time. I just reserved the same IP address for the bridge's MAC address in the new router.
I’m also confused by this statement. As @aaiyar said, the Hubitat Lutron integration app uses the IP address entered by the user. It doesn’t change on its own.
How did you come to the conclusion that this has apparently happened more than once?
Then I’m confused because, when the Lutron lights stopped responding to Hubitat commands, I went into the Hubitat Lutron App and there it had *.148 listed for the IP address, whereas I had *.146 as a reserved IP for the Lutron Bridge and the Lutron Bridge App in my phone had *.146 also. No one else messes with the Hubitat in my household.
I changed it back to *.146 in the Hubitat Lutron App - easy fix. But I don’t know why this happened again. It used to happen more frequently and it stopped doing it after I discovered these settings and reserved the IP in my router many months ago. And yet, in spite of doing that, it happened again recently - the IP discordance between Hubitat Lutron and the Lutron Bridge, and I have no idea why.
Yes... Please stop saying lutron bridge app., It's confusing because you are making a static ip or DHCP on the lutron hub not the app itself. The app itself has nothing to do with communications, it's an interface so it's a wee bit confusing :). That said You could do a static on the Lutron hub and leave it off the dhcp reservation list on your router since you say this may have happened more than once.
Sorry, I realize my verbiage may not be correct. In the Hubitat integration it gives me the opportunity to change the IP address but I had not messed with that in months.
I guess if it happens again I can try making it a static IP in the Lutron Hub. I’m still just not sure why the IP address in the Hubitat integration would be different from that showing in the Lutron Hub when no one messed with it.
Like others I am confused as to how the address in the HE lutron integration app would change without manual intervention, short of @erktrek's theory about weird database corruption.
However, I can explain what you're seeing a different way, and I think this is where others were looking too. If the IP address on the Lutron bridge itself changed (because it grabbed a new one from your DHCP server, for instance), that change would likely get picked up by the Lutron app on your phone automatically, but not by the HE lutron integration. So it might appear as though the IP address changed on the HE lutron integration where in fact it stayed the same there but changed on the Lutron bridge and the Lutron mobile app.
Don't know if that helps or makes things more confusing...
It’s hard to imagine what else might be going on here.
As far as we all know, the Hubitat Lutron Integrator app requires a manual input for the IP address of the Caseta bridge, RadioRA 2/RA2 Select Main Repeater or Homeworks main unit. There’s simply no mechanism for it to change on its own…
Right but, it changed to the address already reserved for it in my router. And that’s when things stopped working.
The only other thing I can think of is that my Lutron Bridge was always on the *.48 address along with the Integration, even though my router had reserved *.46 for it but… if that were the case, I would assume there would have problems with Lutron long before that.
