Built for the life
of the property.
A dependable home is more than a list of compatible devices. HomeHub connects installation, verification, daily operation, explanation and support into one visible system.
From first survey to
everyday support.
A handover that can be proved.
The installation should move as one job from discovery to room assignment, live testing and customer ownership.
Guided setup and gated commissioning
Home naming, administrator creation, real-device discovery, adoption, firmware checks and a commissioning checklist already run on the hub. Handover remains blocked when a required live diagnostic fails.
One resumable installer job
Add survey-to-BOM planning, QR identification, batch adoption, reusable property templates, offline progress and a signed handover record with expiring installer access.
Every routine has an outcome.
Reliable automation records whether the intended result was confirmed, delayed, partially completed or safely stopped.
Simulation, timing discipline and safe recovery
When–If–Then rules support dry-runs, condition evidence, cooldowns, missed-schedule catch-up and measured schedule punctuality. Command tracking separates intent from device confirmation.
Execution policies per automation
Make retry, duplicate, offline-device, maximum-delay and partial-scene policies explicit. Persist unfinished runs, detect conflicts before activation and show reliability per automation.
Support, described precisely.
A device name is not enough. HomeHub evaluates capability, protocol, firmware and the quality of physical confirmation.
One capability model across open protocols
Matter, Zigbee, MQTT, KNX, BACnet, Modbus, ONVIF and local vendor paths normalize into a common device model. Conformance tests verify round trips rather than optimistic echoes.
Capability-level compatibility cards
Publish verified, best-effort and unsupported functions separately, including latency, local operation, electrical rating, regional SKU and the exact combination tested.
The failure tells its own story.
Homeowners need a useful sentence. Installers need the evidence underneath it. Both should come from the same record.
Readable rule and device explanations
HomeHub records the trigger, evaluated conditions, outcome, cause of the last state change, freshness and the automations that could have acted.
21:03:00 “Porch on motion” conditions passed
21:03:00 Command sent to Porch Light
21:03:01 Device confirmed ON
Outcome: completed after one retry
One complete command trace
Carry a correlation identity from sensor to rule, driver, retry and response; add stable failure codes, comparison with the last success, privacy redaction and reviewed support export.
Support with permission, not surveillance.
The home remains locally controlled. Remote service is a temporary, auditable window opened by the customer.
Outbound relay, health and fleet visibility
The hub can connect outward without an inbound port. Diagnostics cover storage, devices, commands, drivers, firmware and schedule health; fleet monitoring can stop a bad rollout after its canary.
Time-bound diagnostic sessions
Add customer-approved health sharing, temporary read-only investigation and scoped repair sessions, with a previewable bundle and a complete access record.
Designed for conditions here.
Indian readiness includes the electrical system, connectivity, locally sold devices, service network and language.
An India-focused product foundation
HomeHub uses Indian pricing and property examples, supports hub-local time zones and sunrise logic, keeps core control off the internet, and addresses pumps, tanks, split ACs, meters, UPS-backed hubs and retrofits.
Regional product and service readiness
Add English and Hindi first, mixed-language voice, Indian formats, inverter and generator states, local SKU validation, city-based spares and field support.
Certify the system, not the logo.
A dependable property is a combination of hub, power, network, radio, driver, endpoint and firmware.
Hardware and firmware certification
HomeHub grades every adopted device against a tested manifest, treats newer untested firmware as drift, and defines Tier 1 kits whose physical devices must remain present and pass the device lab.
Property-level combination identities
Certify complete reference builds, acceptable substitutions, topology and limits. Resolve each installation to exact certified, approved substitution, drift, custom engineered or unsupported.
Verified at handover.
Understood in operation.
Specify the combination, test the installation, monitor the outcome, explain the exception and give support the evidence to resolve it.