Support

Bugs are tracked in the open.

Every app has a public issue tracker on GitHub. File a bug or request a feature there and you can watch it move — what's already reported, what's queued for the next release, and what I've decided against, with the reason attached. One developer, no ticket system, no bot asking whether that resolved your issue.



Issue tracker
Windows · Microsoft Store

BLEam

Broadcast your Teams presence with a Bluetooth RGB light.

Filing a report that gets fixed

Look before you write

Search the open issues first. If it's already there, add what you know — a second set of steps, a different light, a screenshot — to that thread rather than starting a new one. Duplicates get merged, and merging is where carefully written details go to die.

What to include

The app version, your Windows version, and the make of your Bluetooth light if the problem involves it. Then the useful part: what you expected, what happened instead, and the steps that reproduce it. Steps are worth more than everything else in the report combined.

What happens next

I read everything, usually reply within one to three days, and label the issue so you can see where it stands. Crashes and anything that loses your settings go first. If I'm not going to build a request, I'll say so on the thread instead of leaving it open for three years out of politeness.

Before you file

The light won't pair

Check that Bluetooth is on, that the light isn't still paired to your phone — most of them only hold one connection — and that Windows itself can see it in Settings, Bluetooth & devices. If Windows can't find it, BLEam can't either.

The color is wrong or stuck

Confirm Teams is running and showing the status you expect. BLEam reads presence from your PC, so if Teams thinks you're available, so does the lamp — and it is, in its literal-minded way, telling the truth.

Refunds and billing

Purchases go through the Microsoft Store, so refunds do too — request one through your Microsoft account order history. Do tell me what went wrong as well, so the next person doesn't have to.

Still stuck?

Open an issue anyway. A vague report from a real person beats a perfect one nobody wrote — I'd rather work the details out with you on the thread than never hear about it at all.