What to check before deploying LoRaWAN lighting control
A pilot checklist covering luminaires, connectivity, failure behaviour and maintenance responsibilities.
Prepared by DATPOL, 4 October 2026. This guidance supports scoping, discussions and acceptance; it does not replace a design or the specific equipment manual. This British English version concerns services and properties in Poland.
Check the complete communication path
The luminaire controller, gateway and network server are separate parts of the solution. Verify radio coverage on site. Seeing a device in an application does not itself prove that a command changed the light output. Identify the acknowledgements and measurements the hardware actually provides.
Specify failure behaviour
Describe operation after loss of connectivity, power failure and restart. Require a description of any local schedule and manual operation. Do not assume all controllers provide the same functions.
Accept the pilot before expansion
Test representative locations and scenarios. Agree updates, account ownership, data export and ongoing costs. Describe lighting and any camera power supply separately so switching a lighting circuit cannot unintentionally stop equipment that needs continuous power.
Practical checklist
- Luminaire and controller compatibility.
- Coverage test results.
- Local and manual operation.
- Acceptance tests and ongoing costs.
Next steps and references
DATPOL service scope and supporting material
LoRa Alliance — back-end interfaces
Support requests: DATPOL24. Do not include passwords or secrets in the form.

No comments to display
No comments to display