Hotel television integration · on duty at every hour
It is three in the morning. Your guest wants their bill.
Nobody is on the desk. The television in the room could answer — except LG Pro:Centric expects a property management system to talk to, and RMS Cloud does not speak that language. Niteporter sits in the middle: LG Pro:Centric ↔ Niteporter ↔ RMS Cloud API (PMS / RMS) — Revenue Management System, also known as Property Management System — so the screen knows who is staying there, what they owe, and what they can order, every hour of the night.
Named for the one member of staff still awake at three in the morning, when a guest wants their bill. Runs in Docker on one server, serving every property you operate.
The gap it closes
Both systems are perfectly good. They were simply never built to meet — and it is the guest at 3am, and the one member of staff still awake, who pay for that.
The TV does not know who is in the room
Without a PMS interface, Pro:Centric cannot greet a guest by name, set their language, or tell whether the room is occupied at all.
Niteporter answers with the current reservation, so the screen greets the guest and switches to their language on arrival.
No bill, so no express checkout
Guests queue at reception to see a total they could have read in bed. Every one of those conversations is a staff minute spent on something a screen can do.
An itemised folio on the television, and checkout from the room — with the total re-checked against RMS before it goes through.
Nothing on the TV can be sold
A movie, a late checkout, a channel package — none of it can reach the folio, so either it is not offered or somebody keys it in by hand afterwards.
Purchases post straight to the guest's account, under a sundry you name, so the invoice line reads properly and nobody re-keys anything.
Requests go nowhere
A guest asking for towels through the television is only useful if that becomes a task in front of the housekeeper who acts on it.
Every request becomes a task against the reservation in RMS, routed to the department that handles it.
What it does
Six Pro:Centric interfaces, one deployment. Turn on the ones a property actually runs.
Guest folio and checkout
Name, language and balance on the screen; an itemised bill; checkout from the room, with the total verified against a fresh figure from RMS before it completes.
How it works →Charge to room
Purchases post to the guest's account against the sundry you choose, so the line on their invoice reads the way you wrote it. A lost response is reconciled rather than retried, so nothing is ever charged twice.
How it works →Concierge requests
Your own menu of amenities, laundry, shuttles and wake-up calls. Each request is raised as a task against the reservation in RMS, routed to the right department.
How it works →Pay channels
Sell a channel package from the concierge menu and the entitlement is granted, timed and revoked automatically.
How it works →Room control
Lights, curtains and climate described per room type, with scenes that fire on check-in and check-out.
How it works →Casting and travel
Screen casting tied to the current guest, and a bookable catalogue of tours and tickets that can be charged straight to the room.
How it works →And for the people on shift
The six interfaces above are what the guest sees. These are what the desk gets — built on the same connection, with nothing extra to install.
Messages to a room
Write to one television or every occupied room from the portal. It rides the same event stream as check-in, so a message queued while Pro:Centric is unreachable is delivered when it returns — and the set reports back when the guest has read it.
How it works →Guest feedback that reaches somebody
A rating from the television, while the guest is still in the building. A good one is filed and left alone; a poor one raises a task for the duty manager. A complaint you can still fix is worth more than a review you cannot.
How it works →Faults routed away from housekeeping
LG has no maintenance category — a broken kettle arrives looking like a request for towels. Route a menu item to its own department and a reported fault reaches maintenance instead.
How it works →The night, on one page
Who arrived, who left, what was charged from a television, what was asked for and never closed, and whether any events are stuck undelivered. Assembled from what the broker already recorded — it reads the night, it does not run it. RMS keeps its own audit.
How it works →Handover notes
A note for whoever is on next, pinned where they will see it. Deliberately prose rather than a form — a handover forced into fields is a handover nobody writes.
How it works →Built for the hours nobody is watching
An RMS outage does not black out the TVs
Niteporter holds its own copy of who is in each room, so guests keep seeing details. Only the paths that move money are refused while RMS is unreachable — nothing is posted blind.
Works without webhooks
Reconciliation polling is a supported mode, not a fallback hack. It is the only mode an RMS training database allows, so you can commission a property before touching live data.
Every property from one deployment
Add a hotel without a restart. Each one is isolated from the others at the database level, so a group can be served from a single server without its properties seeing each other's guests.
Your team changes it, not ours
A web portal for the concierge menu, what is sellable, room control, the travel catalogue and timings. Every change is recorded with who made it. Credentials stay out of it entirely.
Being built next: ordering by QR code from the guest's own phone, a digital compendium, text messages to guests, and one dashboard across a whole group. See where each of those has got to.
Both sides of the integration
The path is fixed: LG Pro:Centric ↔ Niteporter ↔ your PMS. Niteporter speaks LG's published Pro:Centric external server contract on one side and the property management system's own API on the other — RMS Cloud today, and Mews in beta. Nothing is scraped, screen-driven or reverse-engineered: every side is spoken as its vendor documents it.
LG Electronics — Pro:Centric
All six external server roles: PMS, concierge, pay channels, room control, casting and travel service. Built against LG's own interface guidance, so a property's Pro:Centric server is configured exactly as LG describes.
lg.com
RMS Cloud
The PMS / RMS on the far side of Niteporter — Revenue Management System, also known as Property Management System. Reservations, areas, transactions and traces through the documented REST API, inside RMS's published rate limits with headroom to spare. Works against a training database first, so nothing touches live bookings until you say so.
rmscloud.comMews Beta
The second PMS Niteporter speaks, through the Mews Connector API: reservations, bills, charges, check-out and staff tasks. A Mews hotel gets the same six television roles an RMS one does, from the same broker.
In beta, which here means built and tested but running in fewer hotels than the RMS side. We commission it with you rather than leaving you to it, and we would rather hear early than have you work around something.
mews.comLG, Pro:Centric and the LG logo are trademarks of LG Electronics Inc. RMS and RMS Cloud are trademarks of RMS. Mews is a trademark of Mews Systems B.V. Named here to describe what Niteporter is compatible with; no endorsement or affiliation is implied.
Pricing
One monthly price per property, set by how many rooms it has. Every interface is included — folio and checkout, charge to room, concierge, pay channels, room control and casting and travel — along with the portal, hosting, backups and updates. Nothing is charged per feature or per television.
| Rooms at a property | Monthly |
|---|---|
| Up to 20 | A$149 |
| 21 – 50 | A$299 |
| 51 – 100 | A$599 |
| 101 – 200 | A$999 |
| More than 200 | Custom |
Each property is priced on its own band, so a group is the sum of its hotels rather than a negotiation. New signups collect a card and trial for 14 days before the first charge.
What it would cost you
Enterprise
For groups, unusual estates and anything above 200 rooms. Priced individually rather than pushed into a band that does not fit:
- Setup fee — commissioning, property configuration and cutover.
- Integration fee — work specific to your estate: a second PMS, a door or room-control system, or a report only you need.
- Annual support — a named contact, agreed response times, and a say in what gets built next.
Prices in Australian dollars, excluding GST. Integration partners and resellers earn 15% margin — apply to resell.
Ready to look at it properly?
The quickest way to judge it is against your own RMS training database, which needs no production credentials and cannot touch live reservations. Then leave it running overnight and see what it did while you were asleep.