LS-GW-100 · LoRa private-network gateway, Ethernet, EU868

Available for enquiryPlaceholder values — engineering sign-off pending

Placeholder values — engineering sign-off pending

The figures on this page are not engineering-approved yet. Treat them as indicative only, and do not base a design, procurement or compliance decision on them.

A compact private-network gateway that holds the schedule, the rule engine and the node registry on premises. Appropriate in an indoor cabinet where routine control should keep running when the cloud or WAN is unavailable.

Holds the local schedule, rule execution and node registry on premises
Local REST API for integration; an outbound MQTT link is optional
Serves the private network; cloud is optional and management-only
Indoor cabinet mounting — antenna placement and clearances must be planned

The datasheet for this revision is not published yet. Ask engineering for the current values.(r0.1-draft)

Request a quote

Specifications

Specifications
Model	`LS-GW-100`
Product family	Gateway and edge controller family
Specification revision	`r0.1-draft`
Supply voltage	12 V / 24 V 50 Hz / 60 Hz
Maximum load	0.5 A
Radio band	`EU868`
Transmit power	14 dBm
Link budget	Placeholder. Site range depends on antenna placement and obstructions.
Measured under	Placeholder — no measured site conditions recorded yet.
Ingress protection	`IP30 (indoor cabinet)`
Operating temperature	0°C … 45°C
Standby current	120 mA
Firmware	`fw-0.1.0`
Protocols and interfaces	LoRa (private network), Ethernet, Local REST API, MQTT (outbound, optional)
Inputs	Digital input
Outputs	Relay output, Ethernet
Mounting	Wall or cabinet mount
Packaging	Single unit carton
Spare parts	Power supply, Antenna kit
Local control	Gateway optional · Cloud for management only

Offline behaviour

Offline behaviour — Operating modes
Requires connectivity	Requires connectivity
Works with or without connectivity	Local schedule and rule execution, Local REST API, Node registry on premises
Degraded behaviour without connectivity	Outbound notifications and remote dashboards are queued until the uplink returns

Certifications

Radio Equipment Directive 2014/53/EUplanned · Roadmap
Certificate identifier
PENDING
Markets
eu
The certificate document is not published yet.
UK Radio Equipment Regulations 2017planned · Roadmap
Certificate identifier
PENDING
Markets
uk
The certificate document is not published yet.
ETSI EN 303 645 consumer IoT security baselinein-progress · Roadmap
Certificate identifier
PENDING
Markets
global
The certificate document is not published yet.

Compatibility

Compatible with

LS-WS-1G
LS-WS-2G
LS-WS-3G
LS-RC-16A
LS-RC-25A
LS-DIN-4CH
LS-SN-TH
LS-SN-MT

Not compatible with

LS-GW-300 as a subordinate node
Reason: Gateways are not designed to be nested. Use one gateway per radio domain.

Notes

Local REST API and on-premises rule execution are available without an internet uplink.
Modbus and BACnet are not exposed by this model.

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.

Related models

Model	Radio band	Maximum load	Supply voltage	Status
LS-GW-300LoRa edge controller, multi-protocol, EU868	`EU868`	0.8 A	12 / 24 V	concept

Model questions

How many devices can one gateway serve, and where should it be installed?

A capacity figure is only meaningful with its conditions, so we give it per project rather than as a blanket number. Capacity depends on the band, the scene, the reporting interval, the antenna, the gateway position and the obstructions on site. The gateway is normally sited in a technical cupboard or a plant room with power and a network feed. Confirm siting and node count through a site-fit request; the supported SKU list and the link conditions are returned with the review.