I have an aqara switch set up on my desk to turn the office power on and off… just a simple automation and yet daily sometime in the afternoon it stops working… when I check the automation, its showing as ‘disabled’ and enabling it again brings back the working automation… but why is it going to disabled on its own?
It may be worth looking at the history of the automation. Click on the 3-dot menu next to your automation in the list of automations. Select ‘information’. Then select the history tab. This may show when the automation was disabled. This may narrow down the cause.
Can you post the yaml code?
Otherwise it is a bit tricky to give advice 
So the history is saying the device has gone ‘unavailable’. I have noticed however that I’m also getting some loss of UI connectivity and I wonder if this is perhaps network connectivity related so I’m going to explore that first. Thank you for the feedback so far.
Simple code (redacted device ID’s, always a bit paranoid about IDs)
alias: OfficeDeskPowerSwitchToggle
description: “”
trigger:
- platform: device
device_id: [redacted]
domain: homekit_controller
type: button1
subtype: single_press
condition: []
action: - type: toggle
device_id: [redacted]
entity_id: switch.smart_switch_[redacted]_outlet
domain: switch
mode: single
Despite the inactive post, let me share my case.
I associated my automations to areas, then later I executed scripts that included “general turn off” of areas. Therefore not only lights and thermostats went down but the automations, too.
1 Like
That is to be expected.