Greek residences are built against light and stone in equal measure. Limewashed walls that read differently across a single afternoon; deep-set windows cut into thick masonry; sea reflections that bounce up under a colonnade and change the room without anyone touching a switch. The household is often international, the staff is often local, and the system has to belong to both without favouring either.
We programme for that. Astronomical timeclocks tuned to the Aegean’s actual sun path. Lutron shading layered against solar load and the orientation of the elevation. Scene language written in the household’s own vocabulary rather than translated from a manufacturer’s. Custom Crestron native; Lutron native; the two tied together at the scene engine.
Three things, consistently — whether the residence is an island property, a mainland estate, or a house in Athens.
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 Greece. 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.