I have a Hub M3 that used to be able to run local automations with FP2 and a third party matter light bulb. However, it looks like new automations are now created as cloud. Or has the naming changed for local automations?
3 Likes
@sven1 It sounds like you’re experiencing a change in how your automations are being categorized in your Aqara Hub M3 setup. Based on the reference information, the Hub M3 is designed to support local automations, allowing them to function even without internet connectivity or direct hub involvement. This capability extends to integrating third-party Matter devices, such as your light bulb, and devices like FP2.
Local automation refers to processing and executing automation functions directly on local devices, such as hubs or gateways, without relying on cloud servers. In the Aqara system, there are distinctions between “gateway local” automation, which happens within a single gateway, and “central local” automation, which can involve multiple devices across different local networks.
If your automations are now appearing as cloud-based, it’s possible there might be a system update or configuration change that has affected how these automations are processed. It might be helpful to check if there have been any updates to the Aqara Home App or your Hub M3 settings that could have impacted this functionality.
I encourage you to explore the settings further or reach out to the community for shared experiences. It’s always possible that there might be new naming conventions or settings adjustments that could clarify this change. If needed, feel free to discuss with other members who might have faced similar situations or provide more details for deeper insights.
@sven1 It’s great that you’re leveraging the Hub M3’s local automation capabilities! Let’s break this down. Local automation refers to processing and executing automation logic on local devices (like gateways) instead of the cloud . The Hub M3 is designed to prioritize local automations, which can function without the internet .
For automations to be localized, they typically need to meet specific conditions. Gateway local automation, for example, requires that conditions and actions involve only one gateway or its sub-devices within the same local network . Central local automation can handle scenarios with multiple M3s across different local networks, but still relies on local processing .
If new automations are defaulting to cloud, it might be due to changes in the automation’s conditions or devices involved (e.g., spanning multiple gateways or non-local network devices). The naming in the app might also reflect these distinctions (e.g., “gateway local” or “central local” vs. cloud).
Have you checked if the new automations involve devices outside the original gateway’s local network or additional conditions that might require cloud processing? Feel free to share more details—this community might have insights!
If you need further clarification, consider reaching out to customer service for specific troubleshooting.
Note: The above is based on available reference information; for precise issues, direct verification with official channels is recommended.
@sven1 It’s great that you’ve been using local automations with your Hub M3—they’re a key strength of the device! From what we know, Aqara’s local automations are typically indicated as “gateway local” or “central local” in the system, depending on whether they’re processed by a single gateway or the central hub . The Hub M3 is designed to prioritize local automations, even functioning without the internet .
If new automations are now showing as cloud-based, it might be worth checking if the automation conditions or devices involved have changed. For example, local automations usually require conditions and actions to stay within the same local network or involve sub-devices of a single gateway . If the setup now includes devices across different networks or third-party devices that aren’t fully integrated locally, it could shift to cloud processing.
If you’re still unsure, feel free to share more details about your current automation setup—other community members might have similar experiences! For further assistance, you can also reach out to our customer service through the Aqara Home App (Profile>Help&Feedback>Customer Service) for personalized support.
Hope this helps get your local automations back on track! 
@sven1 It’s great that you’ve been using local automations with your Hub M3—they’re a key strength of the device! Let’s break this down based on what we know about Aqara’s automation types.
First, local automation is defined as moving logic from the cloud to local devices like gateways or centrals . For the Hub M3, there are two main types: “gateway local” and “central local” automations. “Gateway local” applies when conditions involve one gateway or its sub-devices, and actions are within the same local network . “Central local” works even if automations involve devices across different local networks (as long as each has an M3) .
If new automations are now labeled as “cloud,” it might not be a naming change but a shift in how the system categorizes them. For example, if your new automation involves devices outside the local network of your M3, or integrates with services that require cloud connectivity, it might default to cloud execution. The Hub M3 still prioritizes local automations, but certain conditions (like cross-network setups or third-party services not fully integrated locally) could affect this .
Have you noticed any differences in the conditions or devices used in the new automations compared to the older ones? Sharing more details might help the community troubleshoot together!
If you have further concerns, feel free to reach out to customer service through the Aqara Home App (Profile>Help&Feedback>Customer Service) for more personalized support.