Quest 3 beeping constantly when the charge on my Elite Strap with Battery runs out?

The headset battery should not run down before the headstrap. Your headstrap was still at 100% so it was clearly not sending any charge to the main battery, meaning that the cable from the ES/B was not making a proper connection. Power-off the headset, unplug all cables and charger, reset the ES/B (press and hold its button for at least 12 seconds), plug everything back in, charge the headset to 100%, then see how it goes.

It would appear that resetting the elite strap with battery does not solve the problem of the very annoying bleeps whenever the battery gets low on charge.  I didn't unplug it this time and it beeped for 5-6 times before, I guess, figuring out that I wasn't the slightest bit interested in what it had to tell me.

As I have only just noticed this recently, I suspect that it is highly likely to be an "undocumented feature" of a recent update and that, hopefully, it will get fixed in the not too distant future.  

After finally managing to get past the looping update issue, that was preventing me moving up from 78.1027, my hopes that this issue would also have been fixed have come to nought.  I've still to check whether an undocumented setting might have been added to the Quest 3, to silence this apparent notification, but it is still breaking the immersion by bleeping whenever the Elite Strap with Battery gets low/empty on charge.

A very nice chap/chapess from Meta Quest Support has replied to my "cry for help", with a few suggestions, including a link for me to sideload an update to a version of the firmware that might fix it.  I don't know what version this will be, but I'm not really bothered if it fixes the issue.  :)

It's getting late here, so I'll probably try that update tomorrow, when my brain is a little fresher.  I've tried the other suggestions, without success, but the fact that the strap battery appears to be working as it should, apart from the annoying beeping, makes me really think that this is a firmware issue, rather than a hardware issue.  I'm hoping that whatever firmware version is used, for the update, it does the trick.

The "BEEPING" issue is not a Notification Issue,  I mean yes 31.41 notifications every 5.92s will make anybody ready for instant lobotomy with a rusty ice pick. Anyway the problem is that the Quest3 is Rapidly Connecting and Disconnecting from the USB, 

I had USB  C to C Link Cable with red(3.2) USB-A adapter at the PC plugging into a red USB-A 3.2(gen2) 10Gbs, this was great for PC connection but did not have enough power to keep the Quest charged. Though I could play a really long time it would eventually get low bat. So I got new Link Cable  that has an additional USB-C connector input dedicated just for power supply.  The USB-C front port on my Case is  not actual USB-C, They just plug a USB-C Port into one of the USB-2.0 or 3.0 headers on the MB. Even then, you would think a USB-C 3.2 (gen2) PD port you should be able to Sync and charge with the C--C Link cable. anyway one time when I plugged link cable in and i got the Ding Ding Ding Ding over and over, it was really bad, but when I Unplugged the C-C cord that was just for power the USB immediately stopped, I been tolerating Air link and STEAM VR since. And I hear when setup good that Virtual Desktop is the way to go. So maybe  I would check the cords/connections/ports, ect.. and trying different cords and plugs. 

By way of an update, the suggested fixes were not successful and it would appear that my headset already had the latest OS software installed, V79.1027, so no joy there either.

I did notice however, albeit a bit later than I should,  that the "beep" issued sounds exactly the same as the one produced when I plug my ES/B into my headset.  I'm guessing a bit here, but might that mean that once the ES/B charge runs down, it gets disconnected and then reconnected again, repeatedly?

I do appear to be in a very small minority of owners suffering from this issue, so either others have yet to notice it, they're being very shy about telling anyone or it's just me?

Small minority issues, I'd expect, might point more towards being hardware related, which I'd be more comfortable with, if the headset wasn't so reliable about when and how it "fails".   For example, if it was a dodgy connection between headset and ES/B, then surely it'd be happening more at random and with an ever-increasing regularity? 

It is an odd one, for sure.  :)

Well, it would appear that I can almost mark this one as resolved, as following a bit of troubleshooting, with the very helpful Meta Help Desk peeps, an RMA has been approved and I should be getting the replacement in 2-5 working days.  \o/

I haven't received any information about the exact cause of the issue, but as the solution is to replace the ES/B, it'd probably be something to do with the firmware in the ES/B, possibly in how it interfaces with the latest Quest 3 OS software.   Just a guess.  :)

Thanks to all of the Meta peeps that helped to hopefully sort this one out.

Although there appears to have been an improvement, in that I now only get one or two beeps when the charge in the ES/B runs down, it's still not apparently fully solved.

This issue now appears to have been narrowed down to either a fault with the USB socket on the Quest 3 or, more likely, something that has been changed in the Quest 3 OS software.

It would be interesting to hear from any other ES/B users, who might have started to suffer from this issue, in the past 3-4 months.  I had stopped using my Quest 3, for any length of time during the recent UK hot spells, so would not have run the ES/B battery down to zero.

My Quest is now on V79.1031, but if there is a problem in the OS software, the devs will presumably need to know about it before they can fix it.  Unless, of course, they somehow fix it in a similar way to the manner in which it was apparently introduced, that is as an unexpected feature of changes elsewhere. 

Whatever the cause, I guess I'll now need to raise another ticket.  :(

Thanks for replying.

Does it beep all of the time or just when the charge on the ES/B gets low? 

I've just re-opened my ticket, so let's see whether Meta can find a solution that might help both of us.

I'll provide updates and hopefully be able to post about an actual solution, sooner rather than later.

Thanks for that. 

If Meta support are not able to find a solution, either adopting your approach of leaving the ES/B charging cable connected and/or just putting up with the beeping will probably be my best options.