Exploring Hubitat's Local Execution for Enhanced Automation

Hi everyone, I’m really excited to dive into Hubitat after hearing so much about its local execution capabilities. As someone who’s been tinkering with smart home setups for a while, the idea of having automations run directly on the hub without relying on the cloud is incredibly appealing. It promises faster responses and less dependency on internet connectivity, which is a big plus for reliability.

I recently migrated from ST (SmartThings) and was disappointed to find that most of my 32 webCoRE pistons couldn’t leverage local execution effectively. This experience has made me curious about how Hubitat handles local execution, especially when using Community Device Drivers. I’ve noticed that many of my devices, like Inovelli, Sonoff, and Kwikset, are supported in Hubitat, but I’m wondering if there are any limitations when it comes to automations involving these devices. Specifically, does the use of Community Device Drivers require execution to be processed in the cloud, or can it still run locally?

I’m also exploring how to integrate multiple brands seamlessly. For instance, I have a mix of Zigbee and Z-Wave devices, and I’d love to create automations that work across these protocols without hiccups. Has anyone successfully done this and could share their setup or tips?

Another aspect I’m curious about is the debugging process. With so many devices and automations, it’s essential to pinpoint issues quickly. I’ve heard about using log levels to troubleshoot, but I’m not entirely sure how to configure them effectively without being overwhelmed by logs. Any advice or best practices on this front would be invaluable.

I’m looking forward to hearing from the community—whether it’s about overcoming similar challenges, sharing success stories, or offering technical insights. Let’s collaborate to make the most out of Hubitat’s capabilities!