Maintenance and Support — Algarve

An integrated house is not an appliance that is delivered and forgotten. It is a system of several dozen devices, most of them connected to services that change without asking, in a building that stands empty for much of the year in a climate that is hard on electronics.

Handover is the beginning of that system’s life, not the end of the project. This page describes what we do afterwards — including for properties we did not install.

What actually breaks

Rarely the thing people expect. The wired control bus in a properly installed KNX property is close to inert: no moving parts, no cloud dependency, decades of service life. What generates almost every support call is at the edges:

• Services that change underneath you. A streaming provider updates its app, a manufacturer retires a cloud platform, a music service changes how it authenticates. Nothing in the house failed; the world outside it moved.
• Firmware updates. A television updates itself overnight and renegotiates its video link differently, and by morning the projector shows a black screen. This is by some distance the most common audiovisual fault, and it is triggered by an update nobody requested.
• The internet provider. A router swapped during a fault visit takes the network configuration with it, and remote access, cameras and control all stop at once. The technician who did it was solving a different problem.
• Consumables with a life. Batteries in wireless sensors and remotes, uninterruptible supply batteries at roughly three to five years, recording drives, cooling fans and projector lamps or filters. All of these are predictable and none of them announce themselves.
• The environment. Salt air on coastal properties, dust and pollen inland, summer heat in a sealed equipment cupboard, and lightning. Heat is the quiet one: equipment in an unventilated cupboard does not fail immediately, it simply lives a fraction of its expected life.

Almost everything on that list is either detectable in advance or preventable. Which is the whole argument for a maintenance relationship rather than a phone number.

Watching the house from outside it

Most Algarve properties we look after are occupied for a few weeks or months a year. For that pattern, waiting for the owner to report a fault means the fault is discovered on arrival, at the worst possible moment, by the people least able to do anything about it.

We install systems that can be monitored remotely, and we watch the things that give warning: devices that have gone offline, recording drives reporting errors, the temperature inside the rack, uninterruptible supplies running on battery or reporting a failed one, the internet connection dropping repeatedly, and control processors restarting when nothing should be restarting them.

The result is ordinary but valuable: a failed access point identified and often restored remotely on a Tuesday, rather than found by a family on a Friday night in August. And when a visit is genuinely needed, it happens while the house is empty, with the part already ordered.

Before arrival we run a pre-arrival check — heating and cooling responding, hot water, cameras and alarm healthy, network and remote access verified, televisions and audio reaching their services, the charger operational. It takes an hour remotely and prevents most of what would otherwise become a first-evening emergency.

Remote first, on site when it is needed

The great majority of issues are diagnosed and resolved without anyone travelling — a service re-authenticated, a device restarted in the right order, a configuration restored. That is only possible when the property was built to allow it: secure remote access that does not depend on exposing anything to the internet, equipment that reports its own state, and documentation good enough that whoever picks up the call knows what is in the rack.

Where a visit is required, we cover the Algarve from Faro.

Updates are a decision, not an event

A house should not update itself. Firmware and software updates fix real problems and occasionally create larger ones, and the moment for a control processor to change version is not the night before guests arrive.

We hold updates for the property, apply them deliberately, in a sensible order, with the configuration backed up first and a way back if the new version behaves differently. Where a device insists on updating itself — televisions being the persistent offenders — we account for it in the design so that the effect is contained.

Backups of the system’s configuration are taken and kept off the property. A control processor that fails can then be replaced and restored in an afternoon. Without those backups, the same failure means reprogramming from nothing, and reconstructing a house’s scenes and logic from memory costs many times what the hardware did.

The system belongs to the owner

This is the position we take, and it is worth stating plainly because the industry does not always share it.

The programming of a KNX installation lives in a project file. That file — along with the as-built documentation, the addressing scheme, the rack layout and the credentials — belongs to the owner of the property, and we hand it over. A house whose configuration exists only on one company’s laptop is a house that cannot be serviced by anyone else, cannot be extended by anyone else, and loses value quietly at the moment of sale.

Practically, it means the owner can change supplier. We would rather be kept because the service is good than because leaving is impossible. It also means the buyer of a house we worked on inherits something documented instead of a mystery — and in this market, houses change hands often.

Taking over a system somebody else installed

A substantial part of this work is properties where the original integrator has stopped responding, closed, or left the region. It is a solvable situation, and it is worth being realistic about how.

Where documentation exists — the KNX project file, or the control system’s configuration — takeover is straightforward. We review it, correct what needs correcting, and continue.

Where it does not, which is common, the system still exists and still works, and the information can be recovered. The bus can be scanned to enumerate the devices and their addresses, the rack and cabling can be surveyed and traced, and behaviour can be observed and recorded. The result is a rebuilt set of documentation that describes what is actually installed. It takes effort, it is not free, and it is a one-off — after it, the property is supportable again, by us or by anyone.

What we will say honestly at the survey is where a system is not worth continuing: equipment long out of production with no spares path, or a design that cannot do what the household now needs. In those cases, the useful answer is a staged replacement plan with priorities and costs, not an open-ended attempt to keep something alive.

If you have a house in the Algarve with a control system nobody is looking after, a survey is the sensible first step, and it produces a written picture of what you have either way.

Ageing, spares and obsolescence

Every product line ends. The devices in a house installed today will, at some point over the next fifteen years, stop being manufactured — and the ones most exposed are the consumer-facing ones, not the infrastructure.

Handled deliberately, this is a non-event: knowing which components are approaching end of life, holding critical spares for the items that would stop the house working, and replacing on a plan rather than on a failure. Handled by ignoring it, the same situation arrives as an emergency in August, with the part unavailable.

This is also why we favour open, wired standards for the parts of a property that are difficult to change — KNX for control, structured cabling for the network, DALI for lighting. Those decisions are what allow a component to be swapped in twenty years without touching the rest, and they are made at design.

What a maintenance relationship covers

1. Remote monitoring of the systems that give advance warning, with intervention before the household notices.
2. Pre-arrival checks for properties used seasonally.
3. Managed updates, applied deliberately with backups and a way back.
4. Periodic on-site inspection — rack condition and ventilation, protection devices, batteries and consumables, camera cleaning and focus, and physical checks that cannot be done remotely.
5. Support for the household and for the people who manage the property day to day.
6. Changes and additions as the house is used differently over time.
7. Documentation kept current, so that what is on file still describes what is installed.

Working with iHome

We have been installing and supporting technical systems in Algarve properties since 2006, as an official Control4 dealer and certified KNX partner, nationally awarded for our integration work. Some of the systems we look after we installed; many we did not.

The advantage of a single team across electrical, network, audiovisual, lighting and shading, security and energy is that a fault does not become an argument about whose responsibility it is. There is one number to call and one company accountable for the answer.

Call (+351) 289 090 900 or email geral@ihome.pt.