Mijia automation is not executed at all, the door lock is turned on and the light does not light up? I checked these five switches one by one before they worked.
My homecoming scene, where the door lock is opened and the living room lights and air conditioner automatically turn on, has been working fine for more than half a year. Last month I suddenly started to have convulsions. Sometimes the door light would come on for a second, and sometimes the light would still be dark even after I had changed my shoes. The most annoying thing is that at 9pm on Wednesday, I set the "automatically pull the balcony curtains halfway at 9pm every night" and it didn't move at all for three days in a row. My first reaction was the same as many people's: Is the scene broken? Delete it and create a new one. As a result, two were rebuilt and the problem still exists. Later, I went through the five areas of trigger conditions, device online, execution sequence, and family grouping one by one, and then I was able to save both scenes. This article is written in the order I looked it up, and if you follow it, you won’t need to delete most of the scenes.
Don’t delete the scene yet: First go to the execution log to see where it goes
Click Automation in the Mijia App, and there will be an execution log in the upper right corner or in the scene details. Don’t think it’s hidden deep, it’s much faster than blind guessing. In my home's homecoming scene, the log clearly says "triggered, execution failed", but the action of the light below has a red dot in front of it. Looking at the one that draws the curtains regularly, there is no entry in the log, indicating that it has not been triggered at all, and it has nothing to do with whether the equipment is broken or not.
So I later set a rule for myself: First check to see if there is a trigger record. There is a record but the action fails. The problem is probably in the later links. ； There is no record. The problem lies in the trigger condition itself. Deleting scenes and changing devices are all in vain. You can scroll down on "Recent Execution" on the details page, or click "Log" to see the specific time. When encountering a scenario where there are no logs, don’t rush to doubt the gateway. First check whether the time has not arrived yet, or the mobile phone positioning has not returned at all.
first switch: Effective time, repeat rules and mobile phone positioning, 80% of the problems lie here
My scene where the curtains are drawn at 9 o'clock every night seems to be "executed at 21:00". In fact, when I built it, I selected "sunrise and sunset", but I don't know when it was changed to "all day". Some Mijia automatic editing will bring out the default value. If you don’t pay attention when saving, it will run all day long. There is also a type of repetition rules: I only wanted to execute it on weekdays, but it turned out to be "every day". When it didn't work as you wanted on the weekends, you thought it was broken.
There is a more hidden pitfall in the home mode, which is the mobile phone location permission. The door lock does not require positioning to trigger the door opening, but the conditions of "leaving home" and "returning home" rely on the location of the mobile phone. My wife's iPhone previously changed the "location" permission of Mijia to "during use". When she goes out and comes back, the scene when she comes home doesn't like to be triggered. Go to the settings and change Mijia to "Always Allow", then re-mark the "Current Home Location" in the App, and it will be fine for a while. Later, I also discovered that her mobile phone was in low-power mode and the background location updates were slower. It took a long time after entering the house before Mijia judged that she was "home".
The troubleshooting sequence is crude but it works.: First look at the effective time period and repeat rules in the automation details. ； Try the same scene with another mobile phone at home. If it is triggered on both phones, it is a permission issue on your own phone. ； Neither device is triggered, so check the device and conditions again. How to create the specific home mode, I will explain it in this article How to set up Mijia home mode As written in, first set up the basics correctly, and then check for subsequent faults.
second switch: The device appears to be online in the App, but it may actually have been offline for half a day.
This is the part I least expected. The door locks and light bulbs are displayed as online in the App, but when I click on them to control them, sometimes there is no response at the first click, but only after the second click. I originally thought it was because my home's WiFi was slow, but later I found out that the door lock uses Zigbee, which has nothing to do with the half-cent WiFi. Its real entrance is the Aqara M1S gateway. As long as the gateway is still connected to power and the Internet, the App will often mark all the devices connected below it as online, but in fact a certain sub-device may have been offline for more than ten minutes.
My way to judge is to look at the gateway light, and then click on the device details to check the signal. M1S lights up white, which only means the gateway is online ； To find out which door lock and sensor is present, you have to go to the device page to see the last reporting time. My home scene didn't trigger. The last check was that the door lock battery power was only 18%. In order to save power, the Zigbee report was delayed by nearly 20 seconds after closing the door. It’s not that the scene wasn’t triggered, it was only when I walked to the living room that it reported the fact that “the door is closed”.
There is another action worth doing here: Go to the "Device Page" and click on all the Zigbee sensors and door locks at home. If the signal strength is lower than two bars and the last reporting time stopped more than ten minutes ago, change the location or battery first. Don't use the router management page to view these devices. Zigbee devices do not use routers at all. I was before What does Zigbee mean? This is explained clearly here. Half of the devices in the home do not use WiFi. To check offline, you cannot just look at the background of the router.
third switch: In the conditional judgment, "lock" and "lock" are not triggered even if they differ by one word.
The most annoying thing about door lock linkage is conditional events. When I rebuilt the scene, I selected "Door Lock Off", but the lights didn't come on. Later I looked at the log and found that the door lock reported "locked", not "locked". Different brands of locks and different firmware versions will have different event names.: Some are "locked", some are "locked", some are "closed", and there are also "unlocked outside the door" and "unlocked inside the door". If you choose the wrong one, the conditions will never be met, and the App will not report an error to you, but will just quietly not execute it.
There is also a more detailed pit, which is "satisfies all conditions" and "satisfies any condition". My return home scene originally had two conditions checked, "Door lock locked" and "Entry door sensor off". In the middle, the door sensor changed its battery once and failed to reconnect to the network. This means that this condition has never been established, and the entire scene is stuck. Conditions like this are not met every day. If you can put "any condition", just let it go. If you really want to meet them all, first make sure that every sub-device is alive.
When making changes, don’t just look at the Chinese name in the automation details and go to the device page or log to see the actual report. You will see that Xiaomi Door Lock Pro reports "unlocking the door outside" instead of "opening the door" as you thought. Use the original words in the log to build conditions, and you will basically avoid overturning.
fourth switch: If there are too many actions, they will be queued up. Turning on the light slowly does not mean that it is not executed.
The scene of my coming home starts with "open the door → turn on the lights in the living room → turn on the air conditioner → open the curtains". During the first two tests, the light came on very quickly. ； Later, I added a 30-second delay to close the curtains. As a result, the lights occasionally had to wait less than half a minute to turn on. I initially thought that the light was broken, and after checking for a long time, I found that Mijia was actually executing the actions in sequence, and the "30-second delay" in the front would delay the later actions. Wherever you put the "delay", the subsequent actions will wait there.
Later I split the scene into two parts: When one door lock is triggered, the lights and air conditioners are turned on directly. When one door lock is triggered, the curtains are closed with a delay of 30 seconds. If the two don't block each other, the lights will come on immediately, and the curtains should wait. Some Mijia actions can be "executed simultaneously", but not every device supports it, and not every scene can run more than a dozen actions at the same time. When there are too many actions, it is normal for them to be queued for execution, and it is not an automation failure.
When troubleshooting, first look at the completion time of each action in the log. If the log display light is executed only 31 seconds after the door lock is triggered, and there happens to be a 30-second delay in the scene, it is basically a queuing problem. Don't rush to change equipment, move the delay to the end, or split it into two. This idea is the same as when I manage the network for dozens of devices at home.: Don't mix things in one pot, separate things with different response speeds, I'm How to handle dozens of smart home device routers at home I also went through similar pitfalls.
fifth switch: The account and family group are not the same, and "it" in the device list may not be the one in your home.
The last pitfall is the most hidden, especially when the devices at home are tied to several mobile phones. After my cousin's family moved, he sold his old phone. When he logged in to the same Mijia account on his new phone, he could see door locks and lights, and he could create scenes, but the home mode would not be triggered. After checking for a long time, I found that the old mobile phone was still hanging in the home, and it was still located in the old house. Mijia determines "go home" by using the locations of all family members, not just the phone that is logged in. If you don’t delete your old phone, the app will assume that there is always someone at home, and the scene of returning home will naturally not disappear.
The correct approach is to enter "Family Management" to see if the members and devices are all in the same family. Someone uses account A to bind the door lock, and uses account B to scan the code to join the family. The door lock appears in the App, but the actual device belongs to another family. Changing the name, changing the mobile phone, or re-allocating the number may cause the device to be stuck in the old home. It's different from having your account stolen. The device is still in your app, so it's especially easy to ignore. I have written a separate article about account security. How to check if someone else has logged in to my Mijia account? , here we only talk about grouping: Remove the old members, return the device to "My Home", and then go back to the scene and select the device again.
If the equipment was taken from an old house, there is one more step. Unbind first, then long press the gateway or door lock to enter the network distribution mode, and re-add it to the current home. Don't be lazy and just change the room name. The device ID has not changed. The old location is still saved in the automation. The scene looks normal, but it still doesn't recognize it when running.
ending: Just copy my checking sequence.
Now that there is automation in my house that doesn’t work, I won’t delete scenes anymore. Go through these five questions first, and you can find them on the spot seven or eight times out of ten. The order is: First look at the execution log to determine whether it was not triggered or the execution failed. ； Check the effective time, repeat rules and mobile phone positioning again ； Then click on the device page to see the last reported time. Don’t believe the “online” message in the App.” ； Then check the door lock event with the original words in the log ； Finally check family groupings and old members.
In most cases, the equipment is not broken and the gateway is not broken either, but a certain switch is not turned on tightly. If everything is checked and still not triggered, then consider deleting the scene and rebuilding it, or powering off the gateway and restarting it. When there are many smart devices at home, the most feared problem is random resets. After the device ID changes, the normal linkages will also be disconnected. Don't worry, go through the five switches above one by one first, which will save you an entire afternoon in many cases.
