Troubleshooting Faq

B-Sense Troubleshooting / FAQ

This page is for the most common setup and first-run problems.

Use it after:

Documentation Menu

1. I Flashed The Device But I Still See No Data

Check these first:

  1. Confirm the device connected to Wi-Fi.
  2. Confirm you entered the correct host / URL.
  3. Confirm you entered the correct token / secret / API key.
  4. Confirm you are using one path only:

– Nightscout – or B-Sense Cloud

  1. Restart the device once.

Most first-run failures come from:

  • wrong host
  • wrong token
  • mixed Nightscout and B-Sense Cloud settings
  • Wi-Fi not actually connected

What you should do before changing several settings:

  • write down which path you selected
  • note whether the local setup page still opens
  • note whether the device ever showed one successful reading

2. I See Data Once, Then It Stops Updating

Possible causes:

  • upstream data source stopped updating
  • Wi-Fi dropped
  • host became temporarily unreachable
  • credentials are valid but the upstream path is not delivering new readings

What to do:

  1. Check whether your phone/app/cloud source is still updating.
  2. Check whether the device still has Wi-Fi.
  3. Restart the device once.
  4. If the problem repeats, note:

– the last successful reading time – whether the device still shows Wi-Fi – which path you use now – whether the value on screen stays frozen or disappears

3. The Device Shows Stale Data

Stale usually means the device still has an old reading, but no newer one arrived within the expected time.

Check:

  • is your upstream source still sending fresh values?
  • is the configured host reachable?
  • is the current path still the one you intended?

If the setup worked before and only later became stale:

  1. restart once
  2. check Wi-Fi
  3. verify the host and token again only if the issue repeats

If the device is still reaching the API but not showing a newer value, capture:

  • the last value shown on screen
  • the last update time shown on screen if available
  • whether a restart immediately fixes it

4. The Device Cannot Connect To Wi-Fi

Check:

  • the SSID is correct
  • the password is correct
  • the network is available where the device is being used
  • the device is not too far from the access point

If needed:

  1. flash again only if the Wi-Fi setup flow itself is broken
  2. otherwise re-open the device settings and correct the saved Wi-Fi details

Do not reflash first if the board already opens the local setup page. In that case the faster path is usually fixing saved Wi-Fi details.

5. Which Host / Token Should I Enter?

That depends on your chosen path.

If you use Nightscout

Use:

  • your Nightscout URL
  • your Nightscout upload credential: API_SECRET or a write-capable token

If you use B-Sense Cloud

Use:

  • the B-Sense host / URL for your current path
  • the B-Sense Cloud API key or access secret used by that path

If the xDrip+ Base API URL is needed again, the current B-Sense Cloud format is:

  • https://YOUR_BSENSE_API_KEY@api-b-sense.hismis.com/api/v1/

Do not mix the two.

Common mistake:

  • Nightscout host + B-Sense token
  • or B-Sense host + Nightscout token
  • or xDrip+ upload configured with a Nightscout readable token instead of an upload-capable secret/token

Fast rule:

  • if you are unsure, clear the mental model first and decide which one path you are using before editing values again

6. I Am Not Sure Which Data Path I Chose

Start over from the simplest rule:

  • choose one path only for the first working setup

Recommended order:

  1. decide the path
  2. save the path credentials
  3. verify the first live reading
  4. only then change extra display settings

7. The Flasher Does Not Complete

Check:

  • the USB cable supports data, not only charging
  • the correct serial/USB device is selected
  • you are using the Web Flasher page directly

If the first install keeps failing:

  1. reconnect the board
  2. refresh the flasher page
  3. try again with erase enabled

8. The Device Works, But I Want To Change Units Or Layout

Do this only after the first successful live reading.

Current configurable areas include:

  • glucose unit (mmol/L / mg/dL)
  • screen layout
  • night mode / brightness
  • OTA update check

If something stops working after changes:

  1. return to the last known good settings
  2. restart once
  3. recheck the data-path settings if the problem is not purely visual

If you changed several things at once and are no longer sure what caused the problem, undo the cosmetic changes first and return to the last known working path setup.

9. I Cannot Open The Local Device Setup Page

Check:

  • the device is still powered
  • the device is still on Wi-Fi
  • you are opening the device’s local IP, not the public B-Sense website

Try this order:

  1. use the flasher’s Visit Device link if available
  2. reopen the last known device IP
  3. restart the board once
  4. if needed, reconnect Wi-Fi and try again

10. The Time Or Date Looks Wrong

Usually this means:

  • the device has not synced time from the network yet
  • the time zone is wrong
  • Wi-Fi was not available long enough for time sync

What to do:

  1. confirm Wi-Fi is connected
  2. check the Settings tab time zone
  3. wait a short time after the network is stable
  4. restart once if the time still does not update

11. The Display Unit Looks Wrong

If the number looks unexpected, first check whether the device is showing:

  • mmol/L
  • or mg/dL

Fix path:

  1. open the local web Settings tab or the mini menu
  2. confirm the selected glucose unit
  3. make sure you are not mentally reading an mg/dL screen as mmol/L, or the other way around

12. OTA Update List Is Empty Or Looks Wrong

Check:

  • Wi-Fi is connected
  • the device can still reach the update host
  • you reopened the status/update view after the network recovered

If only one version is listed, that can still be normal when the current device already sees the latest available manifest entry.

13. OTA Update Does Not Start

Check:

  • the device has Wi-Fi
  • the device can reach the update host
  • you are selecting a valid listed version

If needed:

  1. reconnect Wi-Fi
  2. reopen the update list
  3. try again

Do not treat OTA as the first fix for a device that still has basic connection problems. Stable Wi-Fi and a known-good data path should come first.

14. I Use iPhone. Is It Supported?

Current public baseline:

  • Apple / iPhone compatibility is not yet treated as confirmed

Right now the main compatibility direction is:

  • Android path where xDrip+ can be installed and used

If you want your Apple-side setup reviewed later, use the updates/tester form and include:

  • phone model
  • iOS version
  • CGM model
  • app/data path you use now

15. What Is The Safest Known-Good Setup Right Now?

Current baseline:

  1. ESP32 2.8 inch touch ST7789 CYD board
  2. latest firmware from the Web Flasher
  3. Wi-Fi connected
  4. Android path with xDrip+ available
  5. one data path only
  6. Nightscout-compatible upstream source

16. What Information Should I Capture Before Asking For Help?

Capture these first:

  • what board you used
  • whether Wi-Fi is connected
  • which data path you chose
  • which host / URL you entered
  • whether the device ever showed one successful reading
  • what type of issue it is:

– no data – stale data – Wi-Fi problem – flashing problem – OTA problem

  • current firmware version from the Status tab
  • current glucose unit on screen
  • whether the local setup page still opens

17. Quick FAQ

Do I need both Nightscout and B-Sense Cloud?

No. Use one path for the first setup.

Should I change layouts before the first successful reading?

No. First make the core data path work.

If the device stops updating once, should I restart?

Yes. One restart is the first fast recovery step.

Is every phone compatible?

No. Do not assume universal compatibility.

Is every ESP32 display board supported?

No. The current primary board is the ESP32 2.8 inch touch ST7789 CYD board.

Do I need to use Pro Features before the device works?

No. First get one stable live reading. Treat Pro Features as a later advanced display-tuning step.

Related Pages