I've been a long-time user of Keyboard Maestro, particularly relying on its image recognition functionality for various automations. Generally, I've got it set up correctly, and it works like a charm, identifying objects as expected.
However, I've been encountering a strange and frustrating issue. After I close the app or shut down my computer, upon restarting, the image recognition doesn't trigger at all, even though I've made no changes to the settings. This inconsistency is baffling because I test it extensively and everything works perfectly fine, but then, out of the blue, it just stops responding.
Has anyone else experienced this? It's like the settings hold correctly for a session, and then somehow, they seem to "forget" their configuration, requiring me to retune the whole setup. I'm at a loss here and could really use some insights.
Here's what I've tried so far:
Double-checking that the triggers and actions are set up correctly.
Testing the image recognition multiple times in a session, where it works without fail.
Ensuring there are no updates or changes to my system that could affect Keyboard Maestro's performance.
But, despite all this, the issue persists randomly after a system restart or app relaunch. Any advice or troubleshooting tips would be greatly appreciated. Has anyone solved a similar problem?
You said when it doesn't work you have to "retune the whole setup." I don't know what that means. Define "retune" for me please. This is important because you claim that retuning it fixes it. So if you explain what you are doing that fixes it, I may be able to spot the problem. Better yet, if you are willing, show the Find Image action or condition that you are using.
Thanks for highlighting the need for more details in my previous message.
By 'retuning the whole setup,' I'm referring to adjusting the 'fuzziness' value in the image recognition tool. Typically, I find a 'sweet spot' for this value, where the tool recognizes images with 100% accuracy. However, the issue arises when I restart my computer after a day or two. Even without altering the fuzziness setting, the tool fails to recognize images as it did before. This inconsistency requires me to recalibrate the fuzziness value each time to find a new optimal setting.
I hope this clarifies my earlier statement about the inconsistency in our image recognition system's performance.
Okay. Since you haven't indicated which version of KM you are using, I have to ask. Which version of KM are you using? When I was using KM v10, I would sometimes have to restart the engine, and for reasons unknown, Find Image would work much better. Therefore, I recommend that you wait for the problem to occur, restart the KM image, and see if that fixes the problem. If it fixes the problem, then I recommend that you upgrade to v11, where I have not yet experienced that problem.
Your symptom could certainly be caused by using the option "Unique" instead of "Best." Check that setting. It's always harder to troubleshoot any problem when I can't see the code. But I do have a lot of experience with Find Image.