Skip to content

Mitsubishi AC control · commercial

Tnode

A small module behind the air conditioner that puts the unit on your phone. Control, schedules, temperature history and maintenance alerts for offices, shops, clinics and any commercial space that runs Mitsubishi units — with no wall controller to walk to and no building-management project to fund.

  • Mitsubishi MBus
  • Works without the internet
  • Schedules & history
  • No third-party cloud

The gap it fills

Between a wall controller and a building-management system

A wall controller does one unit, from one spot, with no record of anything. A building-management system does everything, for a price and a timeline that only makes sense above a certain size. Most commercial buildings sit in between, and end up with neither — a row of units running on whatever setting somebody last touched.

Tnode is a module that fits behind the unit and connects to its own service port — the same interface the manufacturer’s controller uses. From there it is on your network, on your phone, on a schedule, and keeping its own history. Installation is an electrician and an afternoon, not a project.

It comes from the same engineering we do for hotels. The difference is that a hotel needs a bus, a gateway and a front desk. An office needs a phone.

AC compatibility
Mitsubishi Electric, MBus
Interface
MBus
Network
Wi-Fi 2.4 GHz
Local control
Direct, on the LAN
Remote control
Via TES-operated service
Setpoint range
16–31 °C, 0.5° steps
On-board history
~90 days detail, 3 yr hourly
Firmware updates
Signed, over the air

One module per indoor unit. Existing wiring is untouched — the module connects to the unit’s service connector.

Phone local no internet TES service when away Tnode schedules · history stored on the module MBus Mitsubishi indoor unit Local control keeps working when the line to the outside world does not

Capabilities

What it does

Control from your phone

Power, mode, setpoint, fan speed and both vane axes — everything the wall controller does, from an app. One unit or every unit in the building.

Works without the internet

The module announces itself on the local network and the app talks to it directly. Your building keeps working when the line to the outside world does not — which is not true of most connected thermostats.

Schedules

Working hours, weekends, holidays and out-of-hours setback, set per unit or per zone. The building stops paying to cool an empty floor at nine on a Sunday evening.

History on the device

Room temperature, setpoint and runtime are logged on the module itself — months of detail and years of hourly summary — so the record survives a server outage and does not depend on a subscription.

Maintenance signals

Filter status, fault codes and a unit that is running but not reaching setpoint — surfaced as alerts rather than discovered when somebody complains.

Updates over the air

Signed firmware updates with rollback protection, so a module installed above a ceiling tile never needs to be reached again.

No third-party cloud

Remote access runs through infrastructure we operate ourselves. Your building data is not being brokered through somebody else’s platform, and the service does not disappear when a vendor changes direction.

Fleet portal

For an estate rather than an office: every module across every site, with live state, history, staged firmware rollouts and device lifecycle in one place.

Local first

The building should not stop working because a server did

Most connected air-conditioning controllers route every button press through a vendor’s cloud. When that cloud has a bad day, so does your building. We built this the other way round.

01

Same network, direct

The module advertises itself on the local network. Your phone finds it and talks to it directly — no round trip to a server, no waiting on anyone’s uptime.

02

Away from the building

Off the local network, the app switches to the remote path automatically and tells you which one it is using. The same commands, the same result.

03

Line goes down

Local control keeps working through an internet outage, because it never needed the internet. Schedules on the module keep running regardless.

Remote access is ours, not rented. The service the app connects to when you are away from the building is infrastructure we run. There is no third-party IoT platform in the path, which means no data brokered through someone else’s account and no product that stops working when a vendor changes their pricing.

Control surface

Everything the unit exposes

Not a reduced subset. If the manufacturer’s own controller can set it, so can the app — and everything the unit reports is read back.

Power

Range
On / off

Mode

Range
Cool, heat, dry, fan, auto

Setpoint

Range
16–31 °C in half-degree steps where the unit supports it

Fan

Range
Auto, quiet, and the unit’s speed range

Vertical vane

Range
Auto, fixed positions, swing

Horizontal vane

Range
Full left-to-right range plus swing

Room temperature

Range
Read live from the unit’s own sensor

Fault codes

Range
Read and translated to readable descriptions

Field support varies slightly across unit revisions. Anything a particular model does not implement is hidden rather than shown as a control that does nothing.

Where it fits

Built for buildings without a facilities team

Offices & workspaces

Meeting rooms that get left running, floors cooled through the weekend, and a facilities manager with no way to see either. Tnode puts every unit on a schedule and every schedule on a phone.

Retail & restaurants

Trading hours that change, staff who adjust the setpoint and forget, and an energy bill nobody can attribute. Set the policy once and let the units hold it.

Clinics & small institutions

Rooms with a comfort requirement and no building-management budget. Per-unit control and a record of what the temperature actually was, without a BMS project.

Property managers

Multiple small sites, none of them big enough to justify their own system. The fleet portal covers all of them from one login.

Status

Where Tnode is right now

Tnode is in development. We would rather tell you that than sell you a launch date, so here is what is built and what is coming.

Mobile app

Android first, iOS following

Voice assistants

Alexa and Google Home

Fleet portal

Multi-site management and staged rollouts

If you have a site that would suit an early deployment, tell us about it. Pilot installations get direct access to the engineering team and shape what ships.

Interested in an early deployment?

Tell us how many indoor units you have and which Mitsubishi models. We will confirm compatibility and talk through what a pilot on your site would look like.