Applies to: Standard Bivy Stick identified by FCC B66-ACRBV2 in the 21-page ACR guide. Not Bivy Stick MESH/B66-ACRBV3. The guide has no printed revision identified; its April 2024 URL is not a firmware version or release date. Match the device label and current app before using menu names.
Match your symptom
| What you see | What to do next |
|---|
Work through these checks
Name the light before interpreting its color
Record whether the observation is on Power, Signal or Status. The same color has different meanings on these separate lights. Capture steady versus flashing behavior and the app state at the same time; “green light” alone is not enough evidence of message delivery.
What the result means: Use existing messages and account status for these checks. Keep private messages, phone numbers and location links out of public reports. Do not activate SOS, buy service or open the device as a troubleshooting test. If this is an actual emergency, follow the official emergency procedure instead.
Check the phone handoff
A flashing green Status light is the manual’s indication that a received satellite message has not yet transferred to the phone. Check the paired phone’s Bluetooth connection and open the Bivy app. Preserve the message’s arrival time before interpreting a missing notification as lost satellite reception.
What the result means: Use existing messages and account status for these checks. Keep private messages, phone numbers and location links out of public reports. Do not activate SOS, buy service or open the device as a troubleshooting test. If this is an actual emergency, follow the official emergency procedure instead.
Separate pending send from completion
For an existing outbound message, compare its app state with the Status light and sky visibility. The guide associates yellow with pending satellite transmission; completion changes the app’s Sending state to a timestamp. Preserve those transitions. A transmission indication does not prove the intended person read or acknowledged the message.
What the result means: Use existing messages and account status for these checks. Keep private messages, phone numbers and location links out of public reports. Do not activate SOS, buy service or open the device as a troubleshooting test. If this is an actual emergency, follow the official emergency procedure instead.
Preserve service state and the first failure
Record the exact device identity, app version, active/inactive account display and whether the failure is receiving, sending or phone transfer. Give official support a private timeline before reinstalling the app or changing account settings. This keeps a Bluetooth problem separate from provisioning and provides a useful baseline for support.
What the result means: Use existing messages and account status for these checks. Keep private messages, phone numbers and location links out of public reports. Do not activate SOS, buy service or open the device as a troubleshooting test. If this is an actual emergency, follow the official emergency procedure instead.
When to stop and get help
Use existing messages and account status for these checks. Keep private messages, phone numbers and location links out of public reports. Do not activate SOS, buy service or open the device as a troubleshooting test. If this is an actual emergency, follow the official emergency procedure instead.
What to tell support
Use existing messages and account status for these checks. Keep private messages, phone numbers and location links out of public reports. Do not activate SOS, buy service or open the device as a troubleshooting test. If this is an actual emergency, follow the official emergency procedure instead.
Original troubleshooting guidance based on the official sources below. Menu names can change. This is an independent guide, not a manufacturer service bulletin or a bench-tested repair.