Mexico City residences are shaped by altitude, by courtyards, and by an architectural inheritance that runs from colonial through mid-century modern to the present. The light at 2,200 metres has its own quality; the rainy season has its own rhythm; the pattern of a household here, where domestic staff and family share the space across long days, is its own thing.
We programme for that. Scenes that read the household’s actual patterns rather than a North American suburban default. Climate logic written for Mexico City’s thin, dry air. Quiet courtyard transitions where the system fades into the architecture rather than calling attention to itself. Custom Crestron, written natively, by the senior engineer attached to the residence.
Three things, consistently — whether the residence is in Polanco, Lomas, San Ángel, or further afield.
One named programmer attached to the residence for the life of the system. The same person writes the lighting scenes, the touchpanel layout, and the climate logic — and returns when the household’s pattern changes.
No middleware abstraction. Crestron written natively on SIMPL / SIMPL# / C# or CH5; Lutron HomeWorks written natively on its own toolchain; the two systems tied together at the scene engine, not at a translation layer.
Handover happens in person, on the residence. Refinement visits over the life of the system happen in person, on the residence. Remote support exists; it does not replace the engineer arriving with the household.
We hold a current programming engagement in Mexico City. The residence is held in confidence.
For households deciding between Crestron Home and a fully custom system, we design and manage on both platforms — the framework we use is published.