Hello, does anybody know why a button press action is not working with MS Teams? The action is not detecting any buttons. This used to work as of last week, then all of the sudden stopped!
I have another box with a very similar setup, and it's working there. All the security settings are exactly the same, too.
Have you compared the Teams app version numbers? Always suspect an app update in these situations...
Exactly the same MS Teams, and the same Keyboard Maestro versions. The only difference is working on my Macbook Pro which I set up a while ago. I just got a new Mac Mini a few days ago, and it's not working there.
All I want to do is setup shortcuts to send reactions in meetings. There are shortcuts in Teams for pretty much everything else.
You're lucky -- it doesn't work on any of my machines, and hasn't since "new" Teams came out!
See if you can make a button-pressing action on that machine that you can then use on the one that can't scan Teams. If that works you could make a collection of useful button presses to use later.
But it may be that if you can't scan, you can't interact either.
If you have, or have considered getting, a Stream Deck there's a Teams plug-in that works through the API and will do reactions (amongst other things) at the press of a button. TBH I gave up trying to get Teams working with KM when I found that out and have fallen back on image detection for Teams functions the plug-in can't handle.
I feel that you and I are on the exact same page, haha!
That's exactly what I tried first, and it didn't work. I exported from the working Macbook Pro and imported into the not-working Mac Mini, but the macro is not working because it can't read MS Teams.
The whole reason I am doing this is because I wanted to automate this with Loupedeck since it does not have a working MS Teams plugin. I might switch to a Stream Deck just because of this.
I like the loupedeck hardware a lot more than stream deck. I got into this whole KM automation because of the loupedeck. I hope I can figure something out before thinking about swapping out hardware.
Oh, I just noticed that Logi updated their Loupedeck plugin to work with the new Teams. I just tested and it works great now. While this does not answer why KM is unable to scan Teams, it does solve the issue for me, and it looks like I will not need KM for this anymore.
In case anybody needs this: https://www.youtube.com/watch?v=XU45MKyp8KU&t=106s
The plugin instructions are not clear. The video is for Logitech MX Creations, but it works the same for Loupedeck (since Logi bought Loupedeck).
KM's scan depends on (I believe) the app's developers properly implementing Apple's Accessibility Frameworks. If they don't then KM, and other utilities such as UI Browser, can't get identifiers for buttons and so can't target them either.
While it might be a permissions thing that's blocking UI access it's more likely that the information simply isn't available -- I'm not surprised you can't do this on your mini, and very surprised you can on the laptop!
The Stream Deck and Loupedeck plugins work via the Teams API -- different mechanism.
