How it works
From the switch in the unit to your screen
A one-minute read with diagrams. To check the technical side, switch to "Technical" mode or open the details under each step.
- Devices in the unitHDL Buspro, one bus line per unit
- TingEdgeSits in the electrical panel, translates data to a common standard
- TingStay cloudStores data, manages permissions, sends alerts
- Console and appsWeb, guest app, staff app
Status, readings, events go upCommands, configuration come down
In the unit: all devices share one line
Lights, air conditioning, curtains, power and water meters, door sensors and presence sensors all connect to a bus line dedicated to that unit. No two units share a line.
Technical details
- The in-unit control system is HDL Buspro, considerably cheaper than KNX and well suited to portfolios of many small units.
- Each unit has its own bus line. The bus is not exposed to the shared building network, so one unit cannot listen to or accidentally control another.
- TingEdge reads every device on the bus and maps it to a common data standard (following the KNX approach to data types). Adding KNX or third-party devices later does not require changes to the Console or apps.
What TingEdge can read and control:
| Device | Data |
|---|---|
| Lights | on/off, brightness |
| Air conditioner | on/off, mode, setpoint, room temperature |
| Curtains | open/close, position in percent |
| Power meter | kWh reading, current power draw |
| Water meter | reading in m3 |
| Door sensor | door open or closed |
| Presence sensor | whether anyone is in the unit |
| Water leak, smoke, heat | instant alert |
TingEdge: the controller in the electrical panel
Each unit has one TingEdge. It reads every device on the bus, translates the data into a common format, runs energy-saving scenes on its own and logs everything, even when the internet is down.
Technical details
- Hardware (target spec): a small DIN-rail Linux computer in the electrical panel, isolated RS485 port to the bus, wired network with Wi-Fi backup, 24 V supply from the panel, and a battery-backed clock that keeps correct time while offline. The hardware is still in development.
- Power-loss tolerant: the operating system runs read-only, and data waiting to be sent sits in a separate storage area. Software updates are delivered remotely and roll back to the previous version on failure.
- Scenes run locally: welcome on check-in, load shedding when guests are out, post-check-out handling, long vacancy, air con limits, timers, night mode.
- Every time a scene acts, TingEdge reports the reason, so the operator knows why the lights went off.
- When the front desk switches a device on manually, scenes do not override it for the configured period.
Connectivity: TingEdge dials out, nothing opens in
TingEdge connects out to the cloud over the existing internet line. No ports need to be opened on the building router, so there is no path from outside straight into the unit.
Technical details
- TingEdge opens an encrypted outbound connection to the cloud. The building router needs no open ports and no static IP.
- Every message carries its own sequence number. The cloud uses it to reject duplicates, and TingEdge knows which messages arrived so it can clear them from the queue.
- Message timestamps come from the TingEdge clock, so events that happen while offline keep their correct time.
- Update rates: status is sent as soon as it changes; power draw every minute; meter readings every 15 minutes; TingEdge "heartbeat" every minute.
- Power and water are sent as cumulative readings, like a meter, so a few hours offline does not lose any consumption.
You tap, the unit acts, the screen confirms
Every command from the Console or an app has its own ID and is tracked until the device actually changes state. You know the command ran, not just that it was sent.
Technical details
- Every command goes through four states: logged, sent down, received by TingEdge, device changed. If it does not succeed, the command reports an error or expires.
- Commands have a time limit, 60 seconds by default. An expired command never runs, so a stale command cannot switch the lights on at midnight.
- Configuration changes, restarts, software updates, and issuing and revoking door codes all use the same mechanism.
- Tested with a simulated TingEdge (same software, virtual bus): about 0.5 seconds from the tap in the Console to the device changing state.
Door locks: access is granted to the stay, not to the lock
Door codes are generated per stay and expire at check-out. The system works only with the concept of "access", so switching lock brands does not change how you operate.
Technical details
- The first phase uses TTLock locks through the manufacturer platform, under the operator's written authorization. NeoLock and locks wired directly to TingEdge will follow.
- All lock brands map to the same access log format: who opened, by what means (PIN, card, app, mechanical key), and when.
- TTLock offline PIN codes cannot be revoked before they expire. The system records the code type so the operator knows which codes can be revoked immediately.
- Remote unlocking is always written to the audit log.
Offline: the unit keeps running, no data is lost
Locks still accept PIN codes and in-unit scenes keep running on the TingEdge. All changes are stored locally and sent once the connection is back, with no duplicates and nothing missed.
Technical details
- Data waiting to be sent is kept on the TingEdge for up to 7 days. Once the connection is back, it is sent in the original order.
- Results with a simulated TingEdge: after a disconnect and reconnect, everything was delivered with no duplicates; after a restart during an outage, the data was still there and sent on the next connection.
- The cloud flags the unit as disconnected and raises an alert once the allowed time is exceeded; when the connection returns, the alert closes automatically.
- A door opened during an outage is not seen by the cloud right away, but the event is sent later with its exact time.
Install and activate with one code
The technician mounts the TingEdge in the electrical panel, the operator enters the activation code in the Console, and the unit appears. Configuration is prepared from a unit template and pushed down, with no manual setup box by box.
Technical details
- Each TingEdge leaves the factory with a serial number and an activation code.
- The operator enters the activation code in the Console to assign the TingEdge to a unit. The code can be used only once.
- The TingEdge receives its own identity and the configuration of the unit template.
- When an TingEdge is replaced or moved, the data history stays with the unit.
- The device list for the unit is scanned and reported by the TingEdge itself. The Console only assigns names and locations.
- Configuration is written once per unit template and pushed to many units, with "pending" and "applied" states.
- Technicians can view diagnostic data remotely, which cuts down on site visits.
Each party sees only its own data
Many operators share the platform, but their data is kept separate. Within one operator, staff see only the units assigned to them.
Technical details
- Each operator has its own data space. View and edit permissions are checked on the server, not just by hiding buttons in the interface.
- Permissions are assigned by role and by location. Locking a staff account takes effect immediately.
- Records are never deleted or edited directly; every adjustment leaves a trace. The audit log is included in every plan.
- Guest documents are stored on servers located in Vietnam. The Enterprise plan includes a dedicated server with a 99.9% uptime commitment.
Technical questions
What is TingEdge and where is it installed?
TingEdge is a small device installed in the electrical panel of each unit. It reads the status of every device on the bus, runs in-unit scenes on its own and sends data to the TingStay cloud. Each unit has its own TingEdge.
Which connection standard does TingStay use inside the unit?
Devices in the unit use HDL Buspro, with a separate bus line per unit; no two units share wiring. Power and water meters connect over RS485, and door locks communicate over Wi-Fi or Bluetooth.
Do I need to open router ports or rent a static IP?
No. TingEdge connects out to the cloud over the unit's existing internet line. No router ports are opened, so there is no path from outside into the building network.
How do I know a remote command was carried out?
Every command has its own ID and goes through four steps: logged, sent down, received by TingEdge, device state changed. The screen reports success only when the device has actually changed. If a command does not complete, you get an error notification.
What can the system read in the unit?
Lights (on/off, brightness), air conditioning (mode, setpoint, room temperature), curtains, power meter (kWh, power draw), water meter, door sensor, presence sensor, and water leak, smoke and heat alerts, depending on the devices installed in the unit.
How do door locks connect to the system?
In the first phase TingStay works with TTLock locks. Door codes are created per stay and loaded onto the lock, and they expire at check-out. The code lives on the lock, so guests can still open the door when the internet is down.
How long do installation and activation take?
Installation takes at most 1 day per unit if the electrical infrastructure is ready, with configuration and testing completed the same day. The operator then enters the activation code in the Console and the unit appears.
Can other operators see my data?
No. Many operators share the platform, but their data is kept separate. Within your organization, staff see only the units assigned to them. Guest documents are stored on servers located in Vietnam.
Want to see TingEdge running for real?
NEXT HOME has a simulated TingEdge running with the Console for a two-way demo: switch on lights, open a door, cut the connection and watch it catch up. Book a session to see it live.