Skip to main content
FastMind— home
Current language
  • EnglishEnglish
  • DeutschGerman
  • FrançaisFrench
  • NederlandsDutch
  • ItalianoItalian
  • EspañolSpanish
  • PortuguêsPortuguese (Portugal)
  • PolskiPolish
  • ČeštinaCzech
  • SlovenčinaSlovak
  • MagyarHungarian
  • RomânăRomanian
  • БългарскиBulgarian
  • ΕλληνικάGreek
  • HrvatskiCroatian
  • SlovenščinaSlovenian
  • SvenskaSwedish
  • DanskDanish
  • Norsk bokmålNorwegian (Bokmål)
  • SuomiFinnish
  • EestiEstonian
  • LatviešuLatvian
  • LietuviųLithuanian
  • РусскийRussian
  • УкраїнськаUkrainian
  • СрпскиSerbian
  • TürkçeTurkish
  • العربيةArabic
  • עבריתHebrew
  • AfrikaansAfrikaans
  • हिन्दीHindi
  • 日本語Japanese
  • 한국어Korean
  • 简体中文Chinese (Simplified)
  • 繁體中文Chinese (Traditional)
  • ไทยThai
  • Tiếng ViệtVietnamese
  • Bahasa IndonesiaIndonesian
  • Bahasa MelayuMalay
  • Português (Brasil)Portuguese (Brazil)
Site menu

Campsite Control Without Borrowing the Guest Wi-Fi

Reception areas, sanitation blocks, pitch lighting, access gates and service points are one site to run, but guest Wi-Fi is the wrong network to run it on. LoRa links let the operator manage the site over a private network, with local automation limiting the effect of intermittent connectivity.

Site constraints

Guest Wi-Fi is not a control network

The guest network exists so visitors can reach the internet. It is busy, exposed and expected to change, so it is not a sound basis for site operations. A separate private network for control keeps guest traffic and site control from depending on each other.

Long paths and seasonal load

Pitch lighting, sanitation blocks and service points are spread along paths and perimeters, and the cable that reaches them is exposed to weather and movement. Whether a link is reliable depends on the band, the antenna, the mounting, ground and structures between points, and the survey.

Intermittent connectivity

Coastal and rural sites often have a poor or intermittent uplink. Site control and safety lighting have to behave predictably whether or not that uplink is present.

How the system is arranged

A private site network

A gateway sits in reception or a technical room, and switches on site circuits talk to it over LoRa. Access gates, pitch lighting and sanitation block lighting are managed as one site without touching the guest network.

Required, optional and degraded behaviour

Required: the gateway and the local rule set stay on site. Lighting schedules, gate control and manual overrides continue without an uplink.

Optional: cloud management, remote status and outbound alerts are added when the operator wants them. They are a convenience layer over the local rules.

Degraded: if the uplink drops, remote dashboards and alerts pause and queue, while local schedules and gate control continue. If the gateway loses power, affected points fall back to their defined fail states.

Battery-friendly endpoints

Where mains is not available at a point, sensors can be battery powered so no cable has to be run. Battery life depends on the reporting interval, the radio conditions and the temperature, so it is estimated for the specific point after the survey rather than promised in advance.

What you can verify

  • Fewer cable runs along paths and perimeters, where every run is exposed to weather and damage.
  • Site control keeps running when the uplink drops, so lighting and gates are not tied to a remote service.
  • Fault localisation to a single block, pitch or gate rather than the whole site.
  • Seasonal rules can be enabled and disabled locally as the site opens and closes.
  • Access gates, lighting and service points can share one schedule on the same private network.

Who is involved on site

  • Site operator or facilities team

    Site-wide schedules and gate control that work in the closed season and out of hours, without depending on the guest network or an uplink.

  • Electrical contractor or installer

    Enclosure and mounting choices for exposed paths and blocks, plus defined fail states for each circuit.

  • Systems integrator

    A documented local interface so site control can be linked to an existing access or monitoring system where one is present.

Pre-specification checklist

  • Site layout map showing reception, blocks, pitches, gates and service points.
  • Supplies available at each point, and whether a sensor point has mains or needs battery power.
  • Where power and a network feed reach the intended gateway location.
  • Confirmation that guest Wi-Fi and site control are kept as separate networks.
  • Seasonal open and close dates, and the required behaviour out of hours.
  • Who responds to alarms on site, and how quickly.
  • The target radio band and any local radio rules that apply to the site.

Supported SKUs

Availability in your market — Global (English)

Not currently offered in this market

Radio authorisation, electrical approvals or an authorised importer are not in place for this destination. We will confirm the compliance path when you enquire.

Availability follows the market pack, not the language you are reading.

ModelRadio bandMaximum loadSupply voltageStatus
LS-WS-1G1-gang LoRa wall switch, EU868EU86810 A230 Vinquirable
LS-RC-16ADIN-rail LoRa relay controller, 16 A, EU868EU86816 A230 Vinquirable
LS-DIN-4CH4-channel LoRa DIN controller, EU868EU86810 A230 Vinquirable
LS-GW-100LoRa private-network gateway, Ethernet, EU868EU8680.5 A12 / 24 Vinquirable
LS-SN-MTLoRa occupancy sensor, EU868EU8680.05 A3 Vconcept

Next steps

Send this first

Send the site layout, the point list and the notes above through the site-fit request. A first response confirms which points look feasible and where a survey is needed.

What happens next

We return a feasibility note covering gateway siting, the proposed radio layout and any point needing a site visit. A confirmed specification and supported SKU list follow the survey, with the conditions each claim depends on.

Request a project review