Ups 
Thank you so much for the solution for, but unfortunately, It still doesn't seem like to be the case for me because I use English as a system language.
And to explain more how it doesn't work, on this [Compact AirPods Widget], after I put the name, it'll show "success" icon like a half second before it turns grey again like the pic I show below
v
v
v
The left one is from [Compact AirPods Widget]
The right one is from [C2]
OMG... I use a universal clipboard to copy the name of my AirPods from the iPhone to make sure it has the exact same name, and it WORKS NOW !!!!
It is so beautiful ~~~~
Thanks you @Caliguvara and @yuuiko so much, I feel so dumb now
2 Likes
@Bluetus Glad you got that working!
Could you send the names you tried and then the name that worked?
An error window should pop up informing you of the error but it didn’t seem to appear for you. Or did it?
If it didn’t then I have something to fixup 
I used "Bluetus's AirPod" in my Mac, and it doesn't work
because the real name is "Bluetus’s iPhone"
Yes, after failed to connect, it has no error box,
and on the touch bar it just turns grey like the AirPods doesn't connect,
but if I try to tap the icon again on my touch bar
It will show that you could not find your AirPods box and ask me to restart the widget.
I'm not sure if that the expected behavior or the error box should show right after the widget can't find my AirPods.
1 Like
Fixed the icon that changed as soon as any other BT device was connected
Remember when it always looked like this as soon as any device was connected?
It seems to me that the lines
[…]
repeat numberOfDevices times --loop through each devices checking for Connected string
if item counter of myList contains LclAirPodsName then
if item counter of myList contains "Connected: Yes" then
return checkBattery()
else if item counter of myList contains "Connected: No" then
return " "
[…]
Create a loop that causes the checkBattery to run as soon as any device of the list returned a "Connected: Yes".
I didn't find a solution to fix that.
So I ended up checking the output of the checkBattery, and if its output is just a return, I'd actually return just space, in order to change the script's icon to "not connected".
The end of the script looks like this now:
It works perfectly fine, but there might be a "smoother" solution for it?
Here the corrected .json
AirPods Widget.json (67.1 KB)
1 Like
@Caliguvara did you change any variable or named trigger connections? I'm compiling a preset to post in the top post.
Nope, just the end of the script, the highlighted part
Went from "return...."
To "set....if....return.. etc"
So, uh, this is weird, but I haven't been able to connect my AirPods to my Mac at all over the last few weeks. I've tried so many troubleshooting steps, but my Mac is, for some reason, refusing the make the AirPods the audio output. They connect via Bluetooth just fine, but macOS chokes when trying to switch to it as the audio output.
This is why I haven't been able to test anything here yet.
I've tried everything short of uninstalling some of my critical audio apps. I'm kind of hoping it's just a macOS beta issue, because I seem to recall it only popping up when the last Mojave beta went out.
I had to re-pair them recently to make them work again. Also resetting the bluetooth module sometimes helps (hold cmd+option while clicking the bluetooth menu in the menubar, then use the debug menu)
//edit: sorry: shift+option
The weird issue is that they connect. If you look at the Bluetooth menu, they're connected. The system then tries to switch to the AirPods as the audio output (you can tell this because the volume icon in the menu bar pulses back and forth). After about 30 seconds it will fail and revert to the previous audio output.
Unpairing/repairing and resetting the BT module haven't helped because the issue doesn't seem to be with the connection.
I had a similar issue when I still had my LG 5k Ultrafine monitor that had some electrical shielding issues - it broke the Airpods but they still showed up as connected in the Bluetooth menu.
Oof, I have only tried to connect my AirPods within proximity to an UltraFine 5K... I sure hope that isn't the cause. My secondary machine isn't connected to an UltraFine, so I'll see if my AirPods can connect to it in just a sec. Then, if it works, it should be a matter of figuring out what the configuration difference between my two machines is.
They effortlessly connected to my secondary Mac. Hoo boy...
For the record, all of my UltraFines have the shielding fix. I'm gonna do a bit more digging, I find it difficult to believe that my monitors only just started causing issues with my AirPods a few weeks ago. Plus, I've been playing Phoenix Wright 
: Ace Attorney 
for Nintendo Switch so I am feeling investigative.
EDIT: Uh... my AirPods connected to my primary Mac just now. What the heck?! I didn't even change anything. Now I'll never know what the cause was, grr!
ah okay, my ultrafine did it from the beginning and didn't have the shielding fix!
Oh ho ho 
I have found a clue! My AirPods disconnected again! But only when I started trying to play audio!
Something is crashing when trying to play audio through the AirPods... it's gotta be one of my audio apps like Sound Control. Time to start uninstalling things. This only happens on my primary machine, the secondary one is able to play audio through the AirPods just fine.
Anyways, I'll work on this feature from my secondary machine for now, haha 
I've got this problem now too... tried the latest version no luck. Anybody have a fix?