What you are seeing
This fix makes the WiFi code join the network. You will decode the payload, compare every field with the router settings, and rebuild the code in the standard format. Verify the fix by scanning with a phone that has never joined the network, because a phone that already knows the network can hide a payload fault.
Likely causes
1.
Wrong network name in the payload — Quick test: decode the payload and compare the name with the router settings.
2.
Wrong password in the payload — Quick test: join the network manually with the same password.
3.
Wrong security type — Quick test: check the security type in the router settings.
4.
Non-standard payload format — Quick test: decode the payload and compare it with the standard format.
5.
Phone already knows the network differently — Quick test: forget the network on the phone and scan again.
Step-by-step fix
Step 1: Decode the payload and write down the network name, password, and security type it carries.
Step 2: Compare every field with the router settings, including capitalisation and special characters.
Step 3: Join the network manually with the same password. If that fails, the network details are wrong.
Step 4: Forget the network on the test phone so the phone has no saved entry to hide behind.
Step 5: Rebuild the code with the WiFi generator in the standard format, using the verified details.
Step 6: Scan the rebuilt code on a phone that has never joined the network.
Step 7: Retest on two phones, and confirm each one joins the network from the scan alone.
Putting this into practice
In practice, test WiFi codes on a forgetful phone: forget the network, scan, and confirm the join. A phone that already knows the network will join regardless of what the code carries, which hides a broken payload until a real visitor tries it. Record the before-and-after behaviour with the job file, so the fix is provable rather than anecdotal. When the same failure appears again, that record tells you whether the old fix held or a new cause appeared.
Common mistakes to avoid
- Testing a WiFi code on a phone that already knows the network, so a broken payload appears to work.
- Reprinting the full run before a single proof passes, which turns one failure into many.
- Testing on one phone in ideal conditions instead of two phones in the real conditions where a code that scans but the WiFi will not connect will be used.
- Changing the artwork and the placement at the same time, so you cannot tell which change fixed a code that scans but the WiFi will not connect.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- The decoded network name, password, and security type match the router
- The code is built in the standard format
- Two fresh phones join from the scan alone
- The corrected proof passes on two phones in the real conditions
- The fix is recorded in the job file so the next reprint starts from a proven setup
- Every printed copy is checked against the approved proof
- The proof is retested after any later change to the link, design, or placement
Related tools and guides
- [QR payload inspector](/qr-payload-inspector)
- [QR offline verifier](/qr-offline-verifier)
- [WiFi QR code generator](/wifi-qr-code-generator)
- [bulk WiFi QR generator](/bulk-wifi-qr-generator)
- [QR scan log](/qr-scan-log)
- [QR safety checker](/qr-safety-checker)
