InnerWeb
Skip to main content

QR scanner on a tablet camera in the training hall: implementation notes

A QR scanner in a tablet browser works either from day one or not at all: HTTPS, camera permission, firewall rules and handling of the browser's detector make the difference. Below is the order of work for the integrator and OT IT, with the pitfalls that stop a pilot in the training hall.

4
separate scanner error messages

Order of work before the first day

For the integrator and OT IT, the safest order is: an HTTPS address, firewall rules, choice of browser, camera permissions, full flow test. Each step depends on the previous one, so do not move on until the previous one has been confirmed on the tablet in the hall.

A training hall is not an office: a different network, different lighting, a tablet in a mount. Tests from a laptop in the office do not replace a test on the target tablet.

Step 1: HTTPS and a secure context

The QR scanner in the browser requires a secure HTTPS context. An installation shared over plain HTTP under an IP address will not start the camera. The system will then show one of four separate messages: no permission, no camera, insecure context or lack of support.

Prepare a domain name with a certificate trusted by the tablet. If the tablet belongs to the plant, an internal certification authority can be added, but for guest tablets a public certificate remains the solution.

Number of steps and messages for the QR scanner

Number of steps and messages for the QR scannerChart: four preparation steps, four error messages, seven checklist items.02468itemsPreparation stepsPreparation steps: 4 items4Error messagesError messages: 4 items4Checklist itemsChecklist items: 7 items7
Source: and the layout of this page

Step 2: firewall and the scanner library

The camera of the training tablet uses the browser's native barcode detector and, when it is missing, a library loaded from the system's own server instead of an external CDN. The reason is practical: the plant firewall rejects traffic to external networks without a message, so the scanner does not start and nothing indicates the cause.

In deployment practice, check the firewall log to confirm that the tablet connects only to the installation address. If you see rejected connections to other domains, that points to a path that could fail at another moment.

Step 3: camera permission and messages

At the first scan the browser asks for camera permission. On tablets shared in the hall, the permission should be remembered for the address, so that the next person does not have to grant it. Set this in the browser configuration or in the plant's device management policy.

Prepare a short table of messages and actions for staff:

  • No permission: allow the camera in the browser settings.
  • No camera: check that the tablet has a working camera and that no other application is using it.
  • Insecure context: IT checks the address and the certificate.
  • Lack of support: change the browser or use the fallback mode.

Step 4: choice of browser and tests in the hall

Choose one browser for the hall tablets and test the badge scan in it under target conditions: in the hall's lighting, with the code printed on the badge and at different distances. Record the browser and system version, because an update may change the camera's behaviour.

A training screen opened from a badge does not show the company and login form at all, even if the code was not recognized; instead a message and a button to scan again appear. Check this behaviour on the tablet, because it guides the person whose code was not read.

Pitfalls that stop the pilot

The most common causes of delay are organizational rather than technical: a certificate ordered too late, a change of firewall rules that requires a request taking several days, a tablet with the camera blocked by the device policy. Schedule these requests at the start of the timeline.

InnerWeb is a software producer and does not supply tablets or firewalls. We pass the requirements for the browser, the address and the network rules to the plant in writing, and the hardware remains the client's responsibility.

Checklist

Video

Frequently asked questions

Why does the scanner not work over HTTP?

The browser starts the camera only in a secure HTTPS context. The system will show a message about an insecure context.

What if the browser has no code detector?

The system then uses a library loaded from the installation's own server, not from an external CDN, because the plant firewall rejects such traffic.

Does InnerWeb supply tablets?

No. InnerWeb is a software producer. Tablets and the firewall are the client's responsibility.

Preparing a tablet in the training hall?

Book a talk with the integrator: together we will go through the list of requirements for HTTPS, the firewall and the browser.

Let's talk