Teldra

MODEL · CONNECT · INHABIT · UNDERSTAND

Your home as a place, not a list of devices.

Teldra connects the architectural model of a home with its smart devices, live observations, interactive 3D, analysis, and high-quality rendering. Portable .teldra projects can now open locally in Studio, render their bundled scene, recover safely, and save back without requiring a server or making browser state canonical.

See how it worksExplore capabilities
IFC-backed building modelStable device identityInteractive spatial twin
home / living room
ROOMLiving room21.4 °C · occupied
LIGHTFloor lamp35% · warm
buildingdevicelive context

THE WORKFLOW

From a floor plan to an inhabited twin.

Teldra is designed as a continuous workflow. You do not rebuild the home for every tool; each view derives from the same architectural and smart-home identity.

  1. 01

    Model the home

    Start from an IFC model or migrate a Sweet Home 3D project into semantic building data.

  2. 02

    Attach the smart home

    Give devices and capabilities stable Teldra identities while external platform IDs remain bindings.

  3. 03

    Explore spatially

    Open a portable .teldra project in Studio, render its bundled scene, and select real building or device identity rather than disconnected dashboard cards.

  4. 04

    Observe and edit

    Inspect read-only live context, edit canonical device information, undo or redo changes, recover safely, and save the .teldra project locally.

  5. 05

    Project the same twin

    Use the same identity for interactive 3D, analytical overlays, offline rendering, diagnostics, and future automation.

Home model→Semantic import→Twin identity→Spatial experience→Live context

CAPABILITIES

Useful in familiar ways—and in ways a normal smart-home dashboard cannot be.

Conventional

What people already expect from home design, visualization, and smart-home tools.

3D smart-home control surface

current / expanding

Navigate rooms and devices spatially instead of hunting through a flat entity list.

BIM-backed home record

current

Keep rooms, walls, openings, fixtures, and stable architectural identity in IFC.

Sweet Home 3D migration

current

Carry Home.xml semantics into IFC rather than freezing the project as an OBJ mesh.

Portable .teldra workflow

current

Open, render, edit, recover, and save a documented local project container directly in the browser.

Device inspection and editing

current

Select canonical devices, edit their authored data, undo/redo, and save through application-owned commands.

Home Assistant connection

current

Bring read-only live observations into the twin while Home Assistant remains an external adapter.

High-quality visualization

current

Move reproducibly between IFC-derived web scenes and Blender/Cycles asset production.

Unconventional

What becomes possible when spatial identity remains intact across systems.

A spatial debugging tool

enabled by current architecture

Trace a device from room → canonical identity → external binding → live observation → renderer instance.

A home provenance ledger

current foundation

Know which source, toolchain, and transformation produced a scene, lightmap, or derived artifact.

A simulation sandbox

ambition

Preview desired state or alternative layouts without confusing simulation with commands sent to physical equipment.

An accessibility map

ambition

Project reachability, interaction zones, device placement, or assisted-living context over the same home geometry.

A maintenance and incident model

ambition

Attach diagnostics, failures, support evidence, and future maintenance history to stable spatial identity.

A local spatial operating layer

long-term ambition

Let automation, visualization, analysis, and authoring share one understandable model of the inhabited environment.

SYSTEM GRAPH

One home, several views of the same identity.

Teldra keeps the building, smart-home identity, live observations, and visualizations connected without turning any renderer or automation platform into the source of truth.

Read the relationships
  • Home model → IFC: becomes semantic building truth.
  • IFC → Twin: anchors rooms, fixtures, and devices.
  • Twin → Studio: drives user editing and inspection.
  • Twin → Babylon: projects an interactive spatial view.
  • Twin → deck.gl: projects analytical overlays.
  • IFC → Blender: feeds offline rendering and baked lighting.
  • Home Assistant → Live state: supplies external observations.
  • Live state → Twin: updates runtime context without replacing identity.

PROJECT HISTORY

A short history with a deliberate sequence.

The public repository history starts on 2 October 2026. Each step adds a new capability without collapsing building truth, device identity, live state, or presentation into one store.

  1. shipped01

    A canonical foundation

    The repository begins by separating architectural truth in IFC from smart-home truth in the Teldra twin, with stable identity and renderer-neutral projections.

  2. shipped02

    Sweet Home 3D becomes semantic

    The migration path reads Home.xml and maps architectural concepts into IFC rather than treating an exported mesh as the building model.

  3. shipped03

    The twin becomes visible

    IFC-derived scenes gain identity-preserving GLB export, Babylon.js rendering, and canonical picking in the SolidJS Studio.

  4. shipped04

    Live state, quality, and persistence

    The project defines live observations, platform budgets, release/security policy, undo/redo, safe saves, recovery, and reproducible toolchain provenance.

  5. shipped05

    Golden Home proves the chain

    A deterministic smart-home fixture ties together SH3D, IFC, twin identity, derived scenes, live-state examples, and cross-runtime tests.

  6. shipped06

    Studio editing arrives

    The first end-to-end editor slice can modify canonical device data, undo and redo changes, track dirty state, and save without making UI state authoritative.

  7. shipped07

    Offline and browser rendering converge

    A pinned Blender/Cycles reference producer is certified through the Babylon browser path so rendered assets carry reproducible provenance.

  8. shipped08

    Selection becomes canonical across Studio

    Viewport picking and the device inspector now share canonical selection, so renderer instances resolve back to the same project identity used by authored data.

  9. shipped09

    Portable projects run in Studio

    The browser can open, edit, undo, recover, save, and render portable .teldra projects, including bundled GLB scenes, while the Home Assistant adapter remains read-only by design.

  10. in progress010

    Gate physical control explicitly

    Authorization-gated Home Assistant control is active work. It is intentionally not presented as shipped until command intent, authorization, acknowledgement, and failure semantics are certified.

AMBITION

A spatial operating layer for the home.

These are project ambitions, not claims that every capability is finished today. The architecture is being built so these directions can emerge without replacing the home model each time.

01

Inhabited, not merely rendered

The end state is a living model where geometry, devices, observations, history, and user intent meet in one spatial experience.

02

Platform without platform lock-in

Home Assistant is first, but runtime semantics are deliberately broader than any one automation ecosystem.

03

From room to evidence

Selection should be able to explain what something is, where it came from, what it is doing, and which representations derive from it.

04

Safe physical agency

Future control should make authorization, user intent, acknowledgements, failures, and uncertain outcomes explicit.

USER ONBOARDING

See what using Teldra would actually feel like.

Follow the user journey from bringing in a home model, to connecting devices, exploring rooms, understanding live context, and working with the twin.

Walk through Teldra