kAssist

The problem

A well-equipped home ends up with as many apps as it has brands. Each one controls its own bulbs and knows nothing about the rest.

• The bulbs speak Zigbee, the blinds Z-Wave, the freezer socket WiFi — and none of them speak to each other.
• Every brand brings its own app, its own account and a detour through its own cloud.
• Nobody knows what uses what, or how much the solar array actually covers.
• A simple rule — "if nobody is home, switch everything off" — means connecting all of it first.

What kAssist does today

Everything below works today. The demonstration screens rely on a fully virtual home — one site, two floors, six rooms, eighteen devices, a camera and an inverter, all simulated — and kAssist is also tested on real installations, with real sensors and devices: Zigbee bulbs and motion sensors, connected speakers, badge readers.

The house on one screen

Devices are grouped by room, with their state and a direct switch. The counters at the top — total, online, offline, rooms in use — sum up the estate, and those covering devices open the full list.

One inventory, whatever the protocol

Zigbee, Z-Wave, Matter/Thread, WiFi, BLE, Broadlink infrared, Govee, WiiM and Chromecast all feed into the same registry, with the same normalised capabilities — switch, dim, open, measure. That is what lets a scene mix a Zigbee bulb and a Z-Wave blind seamlessly.

Rooms, floors, and a plan

Site, zone, room: the hierarchy organises devices and scopes the rules. The floor plan places each device by drag and drop and makes its state readable at a glance.

Scenes, and rules that fire them

A scene chains commands — dim the lamp, close the blind, cut the socket — with delays in between. An automation is built as WHEN / IF / THEN: a sensor, a time or an external call fires it, a condition filters, an action runs. Execution is delegated to Kore’s rule engine rather than rewritten.

An alarm built on the sensors already there

The modes — disarmed, home, away, night, panic — rely on the contact and motion sensors already in the house, grouped into zones, with entry and exit delays, a PIN and an event log. A camera in the room concerned can attach its snapshot to the alert.

Presence, and what it triggers

The mode of the house — home, away, night — is set from the screen or left to the phone: a geolocation application calls a dedicated webhook on every entry into and exit from a zone, and the token can be regenerated on demand. Comings and goings are logged by zone and by user, and a holiday simulation drives devices at random for as long as the house stays empty.

What the house uses, in euros

Devices able to measure report their power; the total becomes kilowatt-hours, a cost and grams of CO₂ from the tariff and carbon factor set for the household. The breakdown is shown by room and by device.

Solar, all the way to the surplus

Huawei, Fronius, SMA, GoodWe and Enphase inverters are polled continuously: production, consumption, battery, import and export. A regulator can send the surplus to a load — water heater, battery, car charger — instead of selling it back.

The radio stays at home

kAssist never connects to a broker directly: a Kore agent sitting on the local network carries the collectors — mqtt, matter, ble, wiim, cast, broadlink, govee, solar, nfc, among others — and forwards device states. The hub can therefore run elsewhere, remotely included, without the devices leaving the house.

On a phone, with nothing to install

The screens adapt to narrow displays, and the app installs from the browser. Offline it still opens, but without data: the local cache keeps the interface, never the readings.

What the exploration showed

kAssist was first built to test the Kore platform outside its usual ground — management, forms, reference data. Home automation means real time, hardware that fails and unreliable networks.

Frequently asked questions