Auto-discovery and one-click onboarding
The gateway broadcasts discovery requests periodically; any reply carrying port information becomes an entry. One click on “Add” in the web UI completes onboarding — no manual IP entry.
4G Cellular · Ethernet · WiFi AP · 4×RS-485
LineFishRelay Cloud GatewayCloud-Edge
Bring the relay boards scattered across a building under one controllable entry point. LineFish connects upstream to the cloud platform over an encrypted persistent link, and downstream auto-discovers and manages LNX-6xx actuators — relay boards can be wired, or join the gateway's own WiFi; a ready-to-use local web console is built in, and the three upstream links back each other up.
Auto-discovery · one-click onboarding
Encrypted cloud channel
Full / incremental reporting
32 actuators
608 wireless access
Port address group control
Application-area OTA
Bilingual web console
WiFi is the gateway's own hotspot (SSID = LineFish device serial number): relay boards can join wirelessly and phones can connect directly for on-site commissioning; the 4G module is optional per project.
4G cellular
32 actuators
Encrypted cloud
4×RS-485
32Actuators per gateway
4RS-485 buses
3Ethernet / WiFi / 4G
3 sReady after power-up
System Architecture
One gateway connects cloud, boards and scenes
Northbound it serves the cloud platform and local browsers; southbound it manages relay boards and 485 devices over a proprietary protocol. A command travels from the cloud down to a specific port, and status returns along the very same path.
Core Capabilities
Take “remote control” apart — every layer done right
From discovering devices and managing points, to reporting to the cloud and surviving a network failure, LineFish builds the parts that usually break on site into the product itself.
32 actuators, every channel controllable
One gateway manages up to 32 LNX-6xx units with 8 or 12 channels each; port names, port addresses, online state and switch values share one model.
4 × RS-485 buses
Four independent buses, each with transceiver and surge protection, ready for proprietary field devices; frame formats are configured by template, without code changes.
Encrypted channel straight to the cloud
An encrypted persistent connection to the cloud platform uses a key pre-loaded in the device, so nothing has to be configured on site; device ID and WiFi SSID match, so no labels are needed.
Full / incremental reporting
A periodic full report keeps the cloud in sync, while any state change triggers an incremental report immediately; messages are merged per device and by peripheral.id, keeping 4G traffic under control.
Three uplinks, backing each other up
Ethernet first, 4G as fallback, WiFi AP for on-site access; a dropped dial-up retries automatically and traffic returns to the primary link once it recovers.
Local web management
Open the device address in a browser to set up networking, discover devices, view ports, send commands and upgrade — with one-click Chinese/English switching.
Application-area OTA upgrade
The application runs in its own area; an uploaded package is verified, written and activated by restart. If verification fails, the previous version is used automatically.
Wireless actuator access
The gateway provides its own hotspot, so 608-series boards can join without a cable. Ceilings, shafts and retrofits are covered too — wired and wireless devices share one table and one polling loop.
Feature Deep Dive
Six key scenarios, broken down step by step
From discovery and wireless access to reporting, failover, local operation and upgrade — the diagrams below show what actually happens at each layer.
01 · Discovery
Plug in the cable and it finds the boards itself
The gateway broadcasts discovery requests periodically, and any reply carrying port information enters the discovery list. Only after you confirm it once in the web UI does the device become visible to the cloud. Discovery and onboarding are separate, so other devices are never mistaken for relay boards.
- Two criteria: the model must be LNX-6 series and the reply must carry port numbers or a port mask.
- Passive discovery: heartbeats only refresh the online state and never overwrite existing port state.
- Link locking: the link and address at onboarding are recorded, so traffic from another link cannot “steal” the device.
- Periodic polling: after onboarding each unit is polled in turn; exceeding the offline threshold marks it offline and reports it.
02 · Cloud Reporting
Report only what changed, spend data where it matters
A periodic full report keeps cloud data from drifting; the moment a port changes, an incremental report is triggered. An incremental message carries only the devices that changed, and the cloud merges by device ID — real-time without burning through the 4G plan.
- Periodic safety net: a full report every 600 seconds by default, replacing the whole set so no error accumulates over time.
- Report on change: switching, online/offline and onboarding changes are flagged for reporting and cleared once sent.
- Message merging: states from several devices are combined into one message, avoiding a storm of tiny packets.
- Predictable traffic: at 32 units × 8 channels, normal monthly traffic is in the order of a hundred megabytes.
03 · Uplink Failover
When the cable dies, 4G takes over
Ethernet, 4G and WiFi can coexist. The gateway picks the egress by priority, retries a failed dial-up automatically and switches back when the link recovers. Local web access and the on-site buttons keep working throughout, so relays never stop in the wrong state.
- Default route first: wired is preferred when available — steadier bandwidth, and it does not consume data.
- 4G fallback: after a dropped dial-up the gateway redials at a fixed interval, with no manual intervention.
- WiFi AP: the device runs its own hotspot for on-site phone commissioning; the SSID matches the serial number.
- Session rebuild: after a failover the session is rebuilt and one full report is sent, so the cloud is never blind for long.
04 · Local Web Console
No cloud account needed — the job gets done on site
Enter the device address in a browser to reach the console: view the discovery list, onboard devices, check port names and addresses, switch channels individually, change the reporting mode and upload an upgrade package. The interface switches between Chinese and English, so export projects can use it directly.
- Devices page: discover, onboard, add manually and remove — one unit at a time, clearly.
- Ports view: port name, port address and current state, with group commands by address.
- Network page: separate Ethernet / 4G / WiFi sections with live dial-up and signal status.
- System page: device information, configuration backup, application-area upgrade and restart.
05 · OTA Update
Change one feature, without reflashing the whole device
The application runs separately from system firmware and configuration. Upload one package to update gateway features; the upload is validated for header, length and checksum first, and nothing is written unless every check passes — so a power cut cannot brick the unit.
- Partition isolation: the application is stored separately, so upgrades never touch system firmware or configuration.
- Verify before writing: header, length and checksum must all pass first — a bad package carries zero risk.
- Safe rollback: if writing fails or verification does not pass, startup falls back to the previous built-in version.
- Configuration kept: only the application and pages are replaced; device, port and network settings are preserved.
06 · Wireless Access
No cable needed — 608 boards can still join
The gateway provides its own hotspot; once a 608-series board associates with it, the board is auto-discovered, onboarded and polled exactly like a wired device. In ceilings, risers and building retrofits, saving one cable often decides whether the job is feasible at all.
- No cabling: the relay board only needs local power — no extra network cable back to the telecoms room.
- Auto-discovery: wireless devices appear in the same discovery list, with an identical onboarding flow.
- Same data model: port state, port name and address are reported exactly as for wired units.
- Mixed networks: wired and wireless can coexist, chosen per site condition and per device.
Deployment
Three common deployments, chosen by site conditions
The same firmware can sit on a building network, run standalone on a single 4G SIM, or work entirely offline inside a local network.
Wired primary + 4G backup
The gateway joins the building LAN and uplinks over cable; 4G stands by and takes over only when wired fails. Suited to malls, offices and hotels that already run a network.
4G standalone
For plant rooms, pump houses and outdoor points without a usable network, insert a 4G SIM and the gateway is online. Its WiFi hotspot lets phones connect directly for configuration — no temporary cabling.
Offline LAN deployment
It works without any cloud: the local web console and a LAN master control it over the proprietary protocol, and port state, names and addresses are all stored on the device.
| Scale reference | Typical configuration | Notes |
|---|---|---|
| Estimated by actuator count | ||
| Small (1–4 units) | Single gateway + wired / 4G | Single-cabinet lighting or one floor of distribution; every channel visible in the cloud |
| Medium (5–16 units) | Single gateway + wired primary | Multiple floors or zones; cross-device parallel and group control by port address |
| Large (17–32 units) | Single gateway + wired + 4G backup | Whole building or campus; enable incremental reporting to control trafficSplit across gateways as you approach the limit |
| Very large (> 32 units) | Multiple gateways, partitioned | Split by building or zone; the cloud aggregates per device |
About capacity: one gateway manages up to 32 actuators, and the usable channel count depends on the actuator model (LNX-608 has 8 channels, LNX-612 has 12). RS-485 and WiFi pass-through devices can be mixed with Ethernet devices and are managed through the same “device + port” model.
Applications
From one floor to an entire campus
Wherever relay boards need to be seen remotely and controlled centrally, LineFish can be the entry point that is always online.
Commercial & office
Manage lighting circuits by floor and zone, push opening-hours and holiday schedules from the cloud, and spot faulty circuits immediately.
Hotel guest rooms
Centralised management of room distribution and card-key circuits: power-off on check-out and faulty-circuit location both done remotely.
Schools & hospitals
Circuit-level control for classrooms, wards and public areas, with schedules for end-of-day shutdown and equipment power-off.
Campuses & landscapes
Points spread across buildings with mixed 4G and wired links; landscape lighting switches by sunset time, cutting site inspections.
Plant & pump rooms
Switch fans, pumps and auxiliary equipment remotely, collect running status through RS-485 devices and report faults automatically.
Distributed distribution
Relay boards across cabinets, floors and buildings gathered into one place, with logical parallel and group control by port address.
Specifications
Technical specifications
General specifications of the LineFish gateway; refer to the ordering documentation and product nameplate for exact interfaces and options.
Used together with LNX-608 / LNX-612 multi-channel relay switch actuators it provides full port name, port address and status capability; refer to the datasheet for 3G / 4G bands, operating temperature and dimensions. Contact LINETX sales and technical support for selection help.
Get Started
Bring every relay circuit into the same network
Tell us how many relays are on site, what network is available and whether metering is required, and we will align the gateway, actuators and cloud configuration in one go.