Something not working? We've got you covered.

Bluetooth OBD-II adapter won't pair common fix

Most ELM327-based Bluetooth adapters (the $10–$30 dongles on Amazon) use Bluetooth Classic, not Bluetooth Low Energy (BLE). That distinction matters because your phone pairs them differently.

• Adapter needs power first. Plug the adapter into the OBD-II port (usually below the steering column, driver's side) and turn the ignition to "On" or "Run" — the adapter's LED should blink or go solid.
• Pair from your phone's Bluetooth settings, not the app. Open your phone's Settings → Bluetooth, find the adapter (usually "OBDII", "OBD2", "Vlink", or similar), tap it, enter PIN 1234 or 0000 if prompted.
• Only pair once. After initial pairing, the adapter shows as a saved device. You don't need to re-pair each time — just make sure Bluetooth is on.
• One phone at a time. If someone else's phone is already connected, yours will fail silently. Have them disconnect or "forget" the adapter first.

Wi-Fi OBD-II adapter not connecting Wi-Fi adapters

Wi-Fi OBD adapters create their own little Wi-Fi network (usually named "OBDLink", "WiFi_OBDII", "CLKDevices", or "V-LINK"). Your phone joins that network to talk to the adapter — which means you temporarily lose internet while connected.

• Join the adapter's Wi-Fi network. Go to your phone's Wi-Fi settings and connect to the adapter's SSID.
• Ignore the "no internet" warning. Android and iOS may warn you or auto-disconnect because the adapter network has no internet. Tap "Stay connected" or "Use this network anyway."
• Disable mobile data auto-switch. On Android: Settings → Wi-Fi → Advanced → turn off "Switch to mobile data automatically." On iPhone: tap the (i) next to the network and disable "Low Data Mode."
• IP address matters. Most adapters use 192.168.0.10:35000 — Chip.IT uses this default. If your adapter uses a different IP (check its manual), update it in the OBD settings.

Can't find the OBD-II port location guide

Every car and light truck sold in the US since 1996 has an OBD-II port. It's a 16-pin trapezoidal connector, usually within arm's reach of the driver.

• Most common spot: Under the dashboard, left of the steering column, often behind a small cover panel.
• Second most common: Under the dashboard, right of the steering column or near the center console.
• Some trucks/SUVs: Above the gas pedal or behind a panel near the driver's left knee.
• Older vehicles (1996–2003): May be behind a pop-out panel or ashtray.
• Motorcycles, ATVs, mowers: Most do NOT have OBD-II ports. Some newer motorcycles (2020+) have limited OBD support — check your owner's manual.

OBD reader connects but shows no data or wrong data common

The adapter paired, Chip.IT says "connected," but the gauges aren't moving or you're seeing all zeros. This usually means the adapter is talking but the car isn't responding to the right protocol.

• Engine must be running. Most OBD-II sensors only report live data when the engine is actually running — not just ignition-on.
• Protocol mismatch. Try setting the protocol to "Auto" in OBD settings. If that doesn't work, try each protocol manually (ISO 9141, KWP2000, CAN 11-bit, CAN 29-bit).
• Cheap adapter quirks. Some ultra-budget ELM327 clones only support a subset of PIDs. If your adapter works with another app but not with Chip.IT, try a different adapter.
• Intermittent data. Loose OBD port connection — push the adapter firmly into the port until it clicks or seats fully.
• Vehicle compatibility. Diesel engines, hybrid-electric vehicles, and some European imports may report fewer PIDs. This is normal — the car just doesn't broadcast those sensors.

Phone doesn't detect the chip when writing most common

When you're programming a new Chip.IT sticker, the phone's NFC needs to touch (or get within a few millimeters of) the chip. The most common problem is simply holding the phone in the wrong spot.

• Remove your phone case. Thick cases, wallet cases, and cases with metal plates/magnets block NFC signals. Pop the case off and try bare.
• Place the chip on a flat surface — a table, a book, your leg — then bring the phone down onto it. Chip.IT stickers have a built-in on-metal backing, so metal surfaces work fine.
• Hold still for 2–3 seconds. Don't tap and pull away — hold the phone steady against the chip until you feel a vibration or the screen confirms the write.
• NFC must be enabled. On Android: Settings → Connected devices → Connection preferences → NFC → On. On iPhone: NFC is always on for reading (iPhone 7+), but writing requires the NFC Tools app or Chip.IT's writer panel.

"This chip is already paired" error ownership

Chip.IT locks each NFC tag to the first user who pairs it. This prevents someone from stealing a chip off your vehicle and claiming it as theirs. If you're seeing this error, one of three things happened:

• You already paired it. Check Settings → My NFC chips — it may already be in your list, just unassigned to a vehicle.
• Someone else paired it first. If you bought the chip secondhand or got it from a friend, the previous owner needs to release it from their account first.
• It came pre-programmed. Some NFC stickers come with data already on them from the manufacturer. These need to be erased first — use NFC Tools (free app) to format/erase the chip, then try pairing again in Chip.IT.

Moving a chip from one vehicle to another quick swap

Sold the truck but keeping the chip? No problem — you don't need to re-write the physical sticker. Just reassign it in the app.

• Go to Settings → My NFC chips.
• Find the chip (it shows the currently assigned vehicle).
• Tap Reassign and pick the new vehicle.
• The physical sticker now opens the new vehicle's page — no re-encoding, no peeling it off.

How to get a reliable NFC tap every time technique

NFC has a very short range — about 1–4 cm (half an inch to an inch and a half). Both the phone and the chip have small coil antennas that need to overlap. Think of it like lining up two magnets.

• Flat contact is best. Place the flat back of your phone directly onto the flat chip sticker. Don't angle or tilt — maximize surface contact.
• Slow down. Don't flick your phone past the sticker. Place it, hold for 1–2 seconds, wait for the vibration/chime.
• Screen can be off. On most Android phones and all iPhones (XS and later), NFC reads work even with the screen locked. Just tap and the notification appears.
• Remove thick cases. Silicone and thin plastic cases are fine. Wallet cases, metal cases, and cases with built-in magnets or card holders will block the signal.
• PopSockets and ring holders: If they're directly over the NFC antenna, they add distance. Move the chip position so it aligns with an area of the phone back that isn't obstructed.

Every phone puts its NFC antenna in a slightly different place. Here's where the antenna is on the most popular devices — this is the spot you want to line up with the Chip.IT sticker.

The golden rule: flat, accessible, phone-friendly placement

Chip.IT stickers are thin, flexible adhesive circles with a built-in on-metal ferrite backing — so they work on any surface, including bare steel and aluminum. The main things to think about are flatness (so a phone can lay flush) and accessibility (so you can actually reach the chip when you need it).

• The phone needs to reach it. The flat back of a phone must press flush against the sticker. Pick a spot where you can lay a phone flat — not a tight crevice or curved surface where only the phone's edge touches.
• Metal is fine. Unlike generic NFC stickers, Chip.IT chips include a ferrite (on-metal) backing layer that shields the antenna from metal interference. Stick them directly on steel body panels, aluminum dash panels, tool boxes — they all work.
• Temperature matters. NFC chips survive extreme cold and heat (rated to 200°F / 93°C), but the adhesive can soften in 140°F+ heat. Avoid placing chips on surfaces that bake in direct sun, like the top of a dashboard in Arizona.
• Clean first. Wipe the surface with rubbing alcohol before sticking — dust and oil weaken the adhesive bond.

Places to avoid heads up

Chip.IT's on-metal backing means metal is no longer off-limits — but a few spots still cause problems:

• On curved surfaces. The sticker can conform to mild curves, but if the phone can't lay flat against it, the read distance drops to near-zero.
• On the engine block or near hot components. The chip survives heat, but the adhesive fails and the sticker falls off.
• Under multiple layers of material. Each layer between the phone and chip reduces signal strength. One thin panel is fine; two panels stacked is iffy.
• Behind chrome badges or thick trim. The on-metal backing works against flat metal underneath the chip, but a thick chrome or aluminum badge on top (between the chip and your phone) still blocks the signal. Put the chip next to badges, not behind them.
• Exterior surfaces exposed to pressure washers. The adhesive holds up to rain, but a direct hit from a pressure washer can peel it.
• Tight crevices or recesses. If you can't get the flat back of a phone flush against the chip, it won't read reliably. Make sure there's enough clearance for a phone.

"Add to Home Screen" not showing PWA install

Chip.IT is a Progressive Web App (PWA) — it installs from the browser, not an app store. But the install prompt can be picky about when it shows up.

• Use Chrome (Android) or Safari (iPhone). Other browsers may not support PWA install. Firefox and Edge on Android work too, but Chrome is most reliable.
• You must visit via HTTPS. The install prompt only appears on secure connections — this is always the case on mychipit.com, but if you see "http://" something is wrong with your network.
• The prompt may have been dismissed. If you tapped "Not now" before, Chrome won't ask again for a while. Use the manual method instead.

Can't log in or session keeps expiring account access

Common login problems and their fixes:

• Wrong email. Check for typos. If you signed up with Google, use the same Gmail address.
• "Session expired" after closing the app. Your browser may be clearing cookies on exit. Go to your browser's privacy settings and add an exception for mychipit.com.
• Password reset email not arriving. Check spam/junk. The email comes from noreply@mychipit.com — add it to your contacts. Gmail users: check the "Promotions" and "All Mail" tabs.
• Logged out after updating the PWA. This occasionally happens when the service worker updates. Just log in again — your data is safe on the server.
• App-open PIN forgotten. On the PIN lock screen, tap Forgot PIN — a reset link is emailed to your account email.

App shows "Offline" or pages won't load connectivity

Chip.IT works offline for pages you've already visited, but there are limits:

• First visit needs internet. You must load a page at least once online before it's cached for offline use.
• Photos and new data need a connection. Offline mode shows what's been cached. New uploads, new service logs, and real-time OBD data require an active connection.
• Stale service worker. Sometimes the cached version gets stuck. Force-refresh: close all Chip.IT tabs, reopen, or in Chrome DevTools → Application → Service Workers → "Update on reload."

Not receiving push notifications common

Push notifications rely on a chain: Chip.IT → push server → your device's OS → your browser/PWA. If any link in that chain breaks, the notification won't arrive.

• Permission not granted. Your browser must have notification permission for mychipit.com. Check: Settings → Site settings → Notifications → mychipit.com → Allow.
• Phone-level block. Even if the browser allows it, your phone's notification settings can block the browser itself. On Android: Settings → Apps → Chrome → Notifications → Allow. On iPhone: Settings → Safari → Notifications (iOS 16.4+).
• Do Not Disturb. If DND is on, notifications are silenced. They'll appear in your notification history when DND turns off.
• Battery saver / power optimization. Aggressive battery savers (especially on Xiaomi, Samsung, Huawei, and OnePlus) kill background processes including push. Exempt Chrome/Chip.IT from battery optimization.
• PWA not installed. Push notifications work best when Chip.IT is installed as a PWA. Browser-only notifications are less reliable because the browser may be killed in the background.

Setting up for success from day one

Follow these practices and Chip.IT works like a well-oiled machine:

• Add your VIN immediately. VIN unlocks auto-decode (year/make/model), recall checks, and DTC lookups tailored to your vehicle. It takes 30 seconds and makes everything else better.
• Set a current mileage baseline. Every reminder and service interval depends on an accurate odometer reading. Update it every time you log a service.
• Update your odometer once a month. Even if you haven't done a service, a monthly mileage update keeps mileage-based reminders accurate. The dashboard nudges you if it's been 30+ days.
• Use templates for common jobs. Oil change, tire rotation, brakes — the templates set sensible "next due" intervals automatically. Use the "Custom" template for anything unusual.
• Photo everything. Receipts fade. Handwriting smudges. A phone photo of the receipt, the parts box, and the odometer after each service creates an unassailable record.
• Pair a chip on every vehicle. Even if you're the only one who touches the vehicle. One tap from any phone opens the full history — invaluable when you're at the parts counter and can't remember the last filter you used.
• Install as a PWA. The installed app loads faster, works offline, and gets push notifications reliably. It takes 10 seconds.
• Set both PINs if you share a phone. The app-open PIN keeps casual browsers out. The service PIN keeps logged-in users from deleting history by accident.
• Keep your email current. Password resets, share invites, transfer confirmations, and service reminders all go to your account email. If you change email addresses, update it in Settings.
• Check recalls once a quarter. New recalls are issued regularly. A quick check from the vehicle's page takes 5 seconds and could catch a safety issue before it becomes a problem.

Getting the best OBD-II experience power user

Your OBD-II adapter can do more than just read check-engine codes. Here's how to get the most out of it:

• Don't leave the adapter plugged in 24/7. Most ELM327 adapters draw a small current even when the car is off. Over days or weeks, this can drain your battery. Plug it in when you need it, unplug when you're done.
• Read codes before clearing them. When the check-engine light comes on, read the code first, save it to your vehicle's history in Chip.IT, THEN clear it if you want. If the light comes back, you have a record of the progression.
• Use freeze-frame data. Many codes include freeze-frame info (RPM, coolant temp, speed at the time the code set). This tells your mechanic exactly what the car was doing when the problem occurred — gold for diagnosis.
• Monitor live data on test drives. After a repair, watch the relevant sensor on the OBD Dashboard while driving. Coolant temp stable? O2 sensors switching? This confirms the fix worked.
• Log what the code was, not just "check engine light." In your service history, always record the actual code (P0420, P0301, etc.) and the description. "Check engine light — P0420 catalyst efficiency below threshold" is infinitely more useful than "CEL on" when you look back in 2 years.

NFC chip care & longevity chip care

• Chips last forever (electrically). NFC stickers have no battery — they're powered by the phone's NFC field. There's nothing to wear out or recharge.
• On-metal backing built in. Every Chip.IT sticker has a ferrite layer so you can stick it on any surface — steel, aluminum, iron, plastic, glass — without signal loss.
• Adhesive is the weak link. The chip itself will outlive your vehicle, but the adhesive can fail in extreme heat, moisture, or if the surface wasn't clean. If a sticker starts peeling, carefully peel it off and re-adhere with fresh double-sided tape or a dab of superglue around the edges.
• Don't bend or crease the chip. The antenna coil inside is a thin copper trace. A hard crease can break it. Mild flexing (conforming to a slight curve) is fine.
• Waterproof enough for vehicles. NTAG215 chips (what Chip.IT uses) are sealed and resist rain, car washes, and humidity. Direct submersion for extended periods isn't recommended, but splash and rain are no problem.
• One chip per vehicle is enough. You can pair multiple chips to the same vehicle if you want (e.g., one inside, one on the fuel door), but one well-placed chip covers most use cases.

If you've worked through the steps above and something still isn't right, we're here to help. When you reach out, please include:

• Your phone model and OS version (e.g., "Samsung Galaxy S24, Android 15").
• Your browser (e.g., "Chrome 125" or "Safari on iPhone 15").
• What you were trying to do and what happened instead.
• Screenshots or screen recordings if possible — a picture is worth a thousand support tickets.
• OBD adapter model (if the issue involves OBD-II connectivity).

Email us at support@mychipit.com — we typically respond within 24 hours.