Try the following:

• Place the die on the charger with highest number UP. Plug the charger in via USB-C.
• If the die turns on, then let it charge for 15-30 minutes.
• If it doesn't turn on right away, then close the lid and let it chare for 24 hours. Certain models have a factory firmware bug that prevents the die from charging at full strength.
• When the die wakes up, update the firmware with the Pixels app. This will fix the slow charging permanently.

This usually means that the die is in the wrong orientation and the induction coil isn't receiving enough power to recharge the battery.

Make sure you have positioned the die with the highest face up.

When a battery is fully drained, the red charging indicator does not turn on. After a few minutes on the charger it should activate. If not, verify the case charging indicator light is on. This can be seen through the bottom or side of the case.

Confirm all cables are securely connected and the dice insert tray is pressed fully into the base of the charger. Confirm dice are positioned with the charging face down, remove and replace to reposition within insert tray.

Most often, this is the result of the die not getting turned off by the small magnet inside the lid of the case.

Once again, make sure that the highest face is up and close the lid. In that state the dice should maintain their charge for months.

Try to connect the dice using the Pixels app to verify battery level. If they are charged and displaying roll results, check the active profile as it may have no rules related to light colors or animations.

Desktop motherboards technically support BLE, but the range is often terrible. The BLE radio shares bandwidth and antennas with WiFi, and most desktop antennas are optimized for WiFi, not Bluetooth.

Your die can only connect to one device at a time. If the Pixels app on your phone is connected to the die, your computer won't be able to establish a connection.

Before trying to connect on your PC (for Roll20, Foundry, D&D Beyond, etc.), close the Pixels app on your phone or disconnect the die from it first.

This catches people constantly. Modern motherboards have WiFi antenna connectors on the back. If you never attached the antennas (those little T-shaped things that came with your motherboard), your Bluetooth signal is basically nonexistent.

• Check the back of your PC for WiFi antenna connectors. Attach the antennas. This alone fixes the problem for many people.

Hold your die very close - like, touching-the-antenna close - to your computer's Bluetooth source. Try to connect. If it works at point-blank range but not from across the desk, your issue is signal strength, not compatibility.

The community consensus is clear: buy a dedicated USB Bluetooth dongle. BT 4.0 minimum, BT 5.0+ recommended.

Mac users report more frequent BLE disconnects than Windows users.

The Foundry VTT community has developed a heartbeat mechanism that keeps the connection alive.

Check the Foundry integration channel on Discord for the latest.

You must use Chrome or a Chromium-based browser (Edge works). Firefox and Safari do NOT support Web Bluetooth.

If you self-host, community members have written scripts that automate the HTTPS setup. Check the Foundry integration channel on the Pixels Discord for the latest links and guides.

Make sure you have a game open (not the lobby).

The dice enters sleep mode after about 30 minutes of inactivity to save battery. If you happen to be watching the dice, they will flash blue before dropping the connection.

Most integrations take advantage of the library's auto-reconnect feature, and that is all you should need.

You may need to refresh the page or click reconnect.

Enable the heartbeat reconnect setting (v1.0.3+) and the Chrome flag

chrome://flags/#enable-web-bluetooth-new-permissions-backend

A heartbeat PR addresses frequent disconnects specifically on macOS.

This was a known bug fixed in an app patch. The app now resets die settings after firmware updates to fix incorrect roll values on D4 and D6.

Make sure your Pixels app is up to date. The app supports over-the-air patches; the next time you open it, it may self-update.

The Pixels app (v2.5+) can recover dice that encountered errors during firmware updates.

The firmware is built to recover from interrupted updates.

Try these steps:

1. Put the die on the charger for a few minutes to ensure it has power.
2. Open the Pixels app and try the update again.
3. If it still fails, try from a different phone, some Bluetooth stacks handle BLE differently.

If an update causes issues (like breaking a VTT integration), you can roll back to an older firmware version. This requires the Nordic DFU (Device Firmware Update) tool and firmware files from the Pixels GitHub repository.

The Pixels GitHub hosts firmware files and instructions for manual updates.

Community members have successfully used this to fix issues - for example, rolling back from a beta firmware that caused Foundry integration problems, then updating to the stable release.