A software support change is a reason to review the control system, not to assume the air conditioner has failed. Identify the installed hardware, the functions you use and the local operating options before deciding on a replacement.

The dates in Truma's announcement

In its 20 August 2026 announcement, Truma said updates and maintenance releases for the iNet System App would stop on 1 January 2027, followed by the end of service and support for that app and the iNet Box on 1 January 2028. Truma also said existing functions can remain usable, with restrictions depending on circumstances including network coverage and configuration.

Separate three kinds of problem

First, a remote connection problem may prevent a phone from reaching the vehicle. Second, an application or control compatibility issue may affect commands or displayed information. Third, the cooling equipment itself may have a fault. These problems need different checks; replacing a rooftop unit will not necessarily resolve a communication problem.

Record what still works at the vehicle and what fails remotely. Note any displayed messages and when the issue occurs. Give the dealer the installed model numbers and the application version rather than describing the entire system simply as “the AC app.”

Build a useful upgrade request

Ask for an itemized list of components required for your vehicle. Confirm whether the existing air conditioner and other connected appliances are supported, which functions will change, and what commissioning is included. Obtain the continuing-service terms for remote access, including what remains available without that service.

Plan the installation around a period when the vehicle can be tested before travel. After any change, verify local controls, temperature adjustment, mode selection and the intended remote functions. Keep the upgrade record with the vehicle documentation for the next owner or service technician.

A broader lesson for RV buyers

Connected comfort equipment has both a hardware lifecycle and a software-service lifecycle. A purchasing checklist should ask about update support, local operation, replacement controls and diagnostic access. These questions apply to future projects regardless of brand.

Do not describe an announced support deadline as an automatic shutdown date. The practical next step is a configuration-specific review with the supplier, using the current official notice and the actual components in the vehicle.

Write down the installed hardware first

The first task is a written inventory, not a purchase. Vehicles differ in which components are present, which appliances are paired and which phone or tablet runs the application. A dealer can only propose a configuration-specific path when the current setup is described precisely. An upgrade request that starts from a complete component list receives a more accurate quotation and avoids ordering parts that duplicate functions you already have.

Collect this information at the vehicle rather than from memory. Photograph the rating plates and labels, note where each component is mounted and copy identifiers exactly. Store the notes with the vehicle documents so a service technician or the next owner can find them. The list below covers the items that matter most for a support-change review.

  • The iNet Box, its mounting location and the serial number printed on its label.
  • The version of the iNet System App installed on each phone you use.
  • Every appliance shown in the paired-device list, including the air conditioner.
  • The model of any fixed control panel mounted in the living area.
  • The operating system version of each phone used for remote commands.
  • The network connection the vehicle relies on at its usual parking spot.
  • Any routers, repeaters or hotspots involved in that connection.
  • Photos of the installation as found, before anything is moved or replaced.
  • The purchase or installation date of each component, as far as records show.
  • The name of the workshop that fitted the equipment, if you know it.
  • The page in the vehicle handbook where the system is described, if it appears.

With the inventory complete, separate observations from conclusions. Write what you see — an error message, a delay, a command that never arrives — before deciding what it means. Service personnel can act on observations; a vague summary such as “the app is broken” forces them to start the diagnosis from zero. The same notes protect you if equipment is later replaced and a fault reappears.

Treat the inventory as a living document rather than a one-time exercise. Every time a component is added, replaced or reconfigured, update the list the same day and re-photograph the labels you touched. An inventory that drifts out of date is worse than none at all, because the next reader cannot tell which entries are current. Before any dealer visit, spend ten minutes checking that the list still matches the vehicle; that check costs almost nothing and prevents quotations built around hardware you no longer own.

A local-control test that separates the systems

The most useful test costs nothing: operate the air conditioner from the fixed controls inside the vehicle while the phone stays in airplane mode. This shows which functions depend on the remote link and which live entirely within the vehicle. If local operation works, the cooling hardware and its basic control path are functioning, and the open question is connectivity and software.

  1. Park the vehicle safely and power the system normally.
  2. Put the phone in airplane mode so no remote link is possible.
  3. Start the air conditioner from the fixed control panel.
  4. Change the temperature setpoint and confirm the unit responds.
  5. Switch between operating modes and listen for correct behavior.
  6. Power-cycle the iNet Box and repeat the local checks.
  7. Restore the network connection and send one remote command.
  8. Record every result together with the time it was observed.
  9. Repeat the local checks at a second parking spot before you conclude anything.

Interpret the results in three columns: works locally, works remotely, fails both. A unit that cools and responds locally but refuses remote commands points toward the communication chain — box, application, network or account. A unit that fails locally as well is a service case for the cooling equipment itself. Bring these notes to the dealer; they shorten the diagnosis considerably.

Timing matters when you read the results. Note how long the unit takes to cool the interior after a hot start, whether the setpoint holds for the full period you use it, and whether behavior changes late in the evening when network traffic differs. A single successful command proves the chain exists, not that it is dependable. Run the sequence twice on different days before you describe a function as working; intermittent faults otherwise disappear the moment a technician arrives.

Common mistakes after a support announcement

Support-timeline news triggers predictable errors. Most come from treating one announcement as several different facts at once, or from spending money before the problem is identified. The list below pairs each frequent mistake with its correction, so you can check your own plan against it before contacting a dealer or ordering replacement hardware.

  • Treating an end-of-service date as a shutdown date. The announcement states existing functions can remain usable with restrictions; verify your own configuration instead of discarding working equipment on the strength of a headline.
  • Replacing the air conditioner to fix an application problem. Cooling hardware and remote-control software fail independently; run the local-control test before ordering anything.
  • Buying a replacement control box before compatibility is confirmed. Ask which components your vehicle actually needs, in writing, using the inventory from the previous section.
  • Deleting the application and its saved data in frustration. Screenshots and stored settings are evidence for the review; keep them until the matter is closed.
  • Waiting until travel season to act. Configuration changes are easier to test when the vehicle is available for several days, not the evening before departure.
  • Assuming a replacement will look and behave the same. Successor control systems rarely reproduce every screen and routine; list the three functions you use most and confirm each one before committing.
  • Relying on one person who knows the setup. Write the configuration down so a partner, a technician or a buyer can operate the vehicle without a private briefing.

Notice that none of these mistakes involves buying the wrong brand. They are failures of sequencing — acting on a headline, on a guess, or on a sales suggestion before the vehicle has been tested. The correction is the same in every case: establish what you have, establish what fails, and only then discuss what to replace. Following that order usually reduces the scope of the work rather than increasing it.

One further mistake deserves its own line because it is invisible until later: accepting a verbal scope. “We will sort the remote control out” is not a scope. Ask for the sentence in the quotation that names the functions to be restored, the tests that will prove them and the date by which the work is finished. A written scope also makes a second visit easier to justify if something behaves differently once the vehicle is back in normal use, far from the workshop bench.

Terms used in support notices

Support documents rely on a small vocabulary that rewards precise reading. The definitions below are generic industry usage; they help you match each phrase in the announcement to a concrete consequence for your vehicle. When a dealer uses a different definition, ask for that definition in writing so both sides describe the same commitment.

Maintenance release: a software update that corrects errors or makes small improvements to an application or connected device. After the announced cut-off date, no further releases are issued for the named app, so known issues will not be fixed.

End of service and support: the point after which the manufacturer stops issuing releases and stops handling support requests for the named products. Questions then shift to the dealer or installer who sold and fitted the equipment.

Paired device: an appliance registered to communicate through the box, such as the air conditioner. Pairing relationships determine which upgrades touch which appliances, which is why the paired-device list belongs in your inventory.

Commissioning: the structured first run of an installed or upgraded system, in which every function is checked and the results are recorded. A commissioning step should appear in any quotation for control hardware.

Restrictions: conditions — the announcement names network coverage and configuration — under which a function may work partially or not at all. Restrictions are why an identical hardware setup can behave differently at two parking spots.

Remote control: any function you operate from outside line of sight of the vehicle, typically through the application. Remote control depends on the vehicle-side device, the network and the account working together, so it has more failure points than a button pressed at the panel inside the cabin.

Local operation: everything you can do at the fixed controls inside the vehicle. A support change affects local operation only if the changed hardware sits in that path, which is why the local-control test is the reference point for every later decision.

Configuration deserves special attention because the announcement names it as a condition for restrictions. In practice, configuration covers which appliances are paired, which firmware each device carries and how the network is set up. Two owners can therefore read the same notice and experience opposite outcomes, and neither is wrong. This is the strongest argument for keeping your own inventory current: it is the only way to show a dealer how your configuration differs from the average case described in general documentation.

Who does what in the review

The owner records the inventory, runs the local-control test and keeps the documentation current. Nobody knows the parking spots, the travel pattern and the failure history better than the person who uses the vehicle. This record is the owner's contribution to every later conversation, and it cannot be reconstructed by a workshop on short notice.

The dealer matches that record against current product information, proposes an itemized set of components and performs the installation and commissioning. Ask the dealer to confirm in writing which existing appliances remain supported after the change and which functions will differ from what you use today.

Fitting work has its own sequence, and asking about it reveals how much care a proposal contains. A thorough plan covers removal of the old components, reuse or replacement of cabling, sealing of any roof or wall penetration, pairing of each appliance and a test of every function before the vehicle leaves. A thin proposal jumps straight to the box model and a price. The difference rarely shows on the invoice, but it decides whether the first trip after the change runs quietly or turns into a return visit.

The equipment supplier publishes official notices and current documentation. After the announced end of service, remote service through the affected products continues only under whatever terms are offered at that time. Where remote access matters to you, ask for the continuing-service terms explicitly; an informal assurance at the counter does not survive staff changes.

Between these roles sits the handover of records. When the dealer finishes work, the owner should receive the commissioning record, new serial numbers and a short description of anything that behaves differently. When the owner later sells the vehicle, that file passes to the buyer along with the inventory. A review conducted this way leaves a paper trail instead of folklore, and every party can point to a document rather than a memory when a question arises.

Acceptance criteria for an upgraded control setup

Whatever replacement path you choose, agree in advance on what “finished” means. The checklist below turns a vague promise of “everything will work like before” into testable items. Walk through it with the installer while the vehicle is still in the workshop, so missing items are corrected on the spot rather than discovered before a trip.

  • The fixed control panel starts the air conditioner and changes the setpoint.
  • Mode selection behaves the way it did before the change.
  • Each intended remote function works from your normal parking spot.
  • The system recovers control after a deliberate power interruption.
  • Every displayed message has been seen once and explained.
  • New serial numbers and the commissioning record are filed with the vehicle documents.
  • Continuing-service terms for remote access are in writing.
  • The installer walks you through the controls once, in person, before you leave.
  • You know which single action to take first if the remote link fails on a trip.
  • You have the name and number of the person who will handle a follow-up question.

Sign off against this list before paying the final invoice, and keep a copy with the vehicle papers. If the review expands into a larger comfort or equipment project, the RV air-conditioning upgrade guide and the parking AC buying guide cover the hardware side — cooling capacity, power supply and installation — in the same structured way.

Finally, decide how much remote control is actually worth to you. Owners who spend most nights at the same pitch with reliable local power may need very little; owners who leave pets or equipment aboard and check temperatures from work need much more. That judgment belongs in the requirement, not in the quotation, because a supplier can only price what has been asked for. Write the sentence that describes your worst case, and check the proposed setup against that sentence rather than against a feature list.

Plan one retest after the first real trip. Equipment that passed on the workshop bench can meet a different reality on the road — a shaded pitch, a crowded campsite network, a longer cooling run than any bench test simulated. Book half an hour after you return to walk the acceptance list once more, note anything that has changed and file the second record next to the first. Two consistent records make future service conversations short; a single record leaves every later fault open to argument.

Next step

Compare the available configurations in the Vethy product catalog, then request the current model-specific documentation before selecting a unit.

Sources and method

Frequently asked questions

Will my Truma air conditioner stop working when iNet Box support ends?

The announcement does not say the cooling equipment stops working. It separates two things: updates for the iNet System App end on 1 January 2027, and service and support for the app and the iNet Box end on 1 January 2028, while existing functions can remain usable with restrictions depending on circumstances such as network coverage and configuration. Cooling is a hardware function with its own local controls. Run the local-control test at the vehicle to confirm what still operates without the remote link, and record the results before drawing any conclusion.

How do I tell whether the fault is the app, the box or the air conditioner?

Use the three-column method from the local-control test. If the air conditioner starts and responds from the fixed panel while the phone is in airplane mode, the cooling equipment and its basic control path are working, and the problem sits in the remote chain — the box, the application, the network or the account. If the unit fails locally as well, treat it as a service case for the cooling equipment and book an inspection. Give the dealer the recorded observations, the model numbers and the application version rather than a general description of the system.

What should I ask a dealer before replacing the iNet Box?

Ask for an itemized list of the components required for your specific vehicle, and a written statement of which existing appliances — including the air conditioner — remain supported after the change. Confirm which functions will behave differently, whether commissioning is included, and what the continuing-service terms for remote access are once the announced end of service has passed. Request that the answers reference the component list from your inventory, so the quotation cannot silently assume equipment you do not have.

Can remote control keep working after the announced dates?

The announcement says existing functions can remain usable, with restrictions depending on circumstances including network coverage and configuration. That wording means remote control is not guaranteed, not that it is switched off. Treat remote access after those dates as an open question for your configuration: test it from your usual parking spots, ask the dealer about any successor or continuing-service arrangement, and keep the fixed panel as the primary control path. Plan trips assuming the local controls, not the app, are the reliable option.