No problem. Hopefully it’s helpful to somebody. Hopefully it’s helpful to me! Still can’t be 100% sure my continued luck with the uptime is due to changing this, but so far so good. Looking at my Docker logs, I can see that before that setting, I was having to start the script 2-4 times/day. The last time I did that now was immediately after I posted that first screenshot, which was 3 days ago. I suppose I could see if it reaches a week milestone of uptime and then experiment with turning the setting back on to see if it crashes anything.
I will say, looking at the current output of the terminal on my LutronPi Docker, I have several entries where it says the button was “held:”
Lutron Pico mode: push/hold
Sending to SmartThings @ 192.168.86.81:39500
Lutron Bridge 01F281B0, Device=9, Button Code=2 Op=4
Lutron Pico mode: push/hold
01F281B0:9:2 button was released in 304 ms (held)
I can, assure you, however, those buttons were not held at all. Even the ones that say “pushed” are very close to the line, (236 ms, 300 ms–the 300 one being curious because it registers 304 as a hold)…
I’m the one using these, and there’s just absolutely no holding going on. --Especially as I’ve been aware that it could be causing the issue. I find it dubious that I’m anywhere close to 300 ms, and if I am, that should definitely not be considered a hold. I’m lightly clicking.
Just throwing it out there for reference, in case anyone is inspired to adjust anything based on my findings.
As for the Hubitat stuff: thanks for the suggestion. I find that, in pretty much every custom DTH thread on SmartThings Community, you have people who announce that they’re done with ST, and they’ve moved to Hubitat, or HomeAssistant, or OpenHab, and all their troubles are gone. I have to say, I’m doubtful that any one solution is perfect, and there are tradeoffs everywhere. ST has its hooks pretty deep in me, with my pool controller, Nest, all my Google Home/Chromecast/GoogleCast devices interfaced, my Lutron setup, ActionTiles running on multiple mounted tablets and touch switches in the house…not to mention the ever-growing tweaking and customizing I’m doing with WebCoRe. And I’m very happy with the reliability. I’m sure there are some ways to replicate some of what I have going here on another platform, but I’m very happy with it so far, and starting over and rethinking every one of these would take the fun out of this for me.
Honestly the only current headache I’ve had with ST is the LutronPi instability, and that only matters if I want to use Picos to control non-Lutron stuff. The official Lutron integration worked perfectly (and I do have plenty of official/hard-linked Lutron stuff to work with). At the moment, the entire Bridge Pro/Pico/LutronPi setup is only running 2 pico remotes. In the grand scheme of everything I have going on in my smart home, it’s pretty minor. Would be just as easy to replace those picos with $20 Android phones from WalMart running ActionTiles full-time.
But don’t think I’m not keeping an ear to the ground on the Hubitat/OpenHab stuff. As for local control: that’s one reason I got the Lutron stuff to begin with. The Picos that are linked to switches and dimmers don’t rely on network/cloud interaction. They just do their job first, instantly, and that gets reported up to the cloud after the fact. It all works without internet connection, and it’s perfectly instant. I’ve been through several phases with lighting and learned the value of instant-on-off and interactive dimming that isn’t reliant on the cloud, an app, a server, etc. That’s where Caseta shines. The use of the picos to run non-Lutron stuff is just a bonus. It would cost me quite a bit less than the price of a Hubitat hub to replace the 2 non-Lutron devices I’m controlling with picos at the moment with their Lutron equivalents (and I’d still have the devices I replaced to use elsewhere, or could sell them).
Anyway. Glad I could share, hope it helped, thanks for the reco, just sharing my perspective on it at this time.
