ABB Free@Home
Eliona App for ABB Free@home integration
Simply smart. ABB-free@home® transforms the house or the apartment into an intelligent home. Whether blinds, lights, heating, air conditioning, door communication or scenes. Easy to remote control via a switch on the wall, with the laptop or with the smartphone. Very convenient. Extremely comfortable. Very energy efficient. Especially attractive: Only minimal costs are involved when compared with conventional electrical installations.
This app allows accessing ABB Free@home systems directly in Eliona using the ABB ProService portal. Users can monitor values, browse through statistics, control the Free@home devices and, most importantly, interconnect ABB devices with systems from other manufacturers.
Installation
The ABB Free@home App is installed via the App Store in Eliona.
Assets
The ABB Free@home App automatically creates all the necessary asset types and assets. The asset names are kept synchronized from ABB -> Eliona (therefore assets must be renamed in Free@home system. If they are renamed in Eliona, the name will not ve persisted).
Structure assets
The following asset types are created just to create a structure in Eliona:
Floor: Represents a specific level in a building.
Attribute | Description |
---|---|
| Floor Identifier |
| Floor Name |
| Floor Level |
Room: Represents a specific room on a floor.
Attribute | Description |
---|---|
| Room Identifier |
| Room Name |
System: Represents a central system controlling multiple devices.
Attribute | Description | Filterable |
---|---|---|
| System ID | x |
| GAI | x |
| System Name | x |
Device: Represents a specific device in the system. Devices are linked to their respective systems and locations in Eliona asset tree.
Attribute | Description | Filterable |
---|---|---|
| Device Identifier | x |
| GAI | |
| Device Name | x |
| Device Location | |
| Battery percentage (if applicable) | |
| Connectivity status (if applicable) |
Channels
Channels are linked to devices. These channels provide the real functionality:
Here's the updated documentation based on the provided data structure:
Switch: A regular light switch.
Attribute | Description | Subtype |
---|---|---|
| Switch | output |
Dimmer: A channel to control lighting intensity.
Attribute | Description | Subtype |
---|---|---|
| Switch | output |
| Dimmer | output |
HueActuator: A channel to control colored lighting.
Attribute | Description | Subtype |
---|---|---|
| HSV State | input |
| Color Mode State | input |
| Switch | output |
| Dimmer | output |
| HSV Hue | output |
| HSV Saturation | output |
| HSV Value | output |
| Color Temperature | output |
RTC: Room Temperature Controller.
Attribute | Description | Subtype |
---|---|---|
| Current Temperature | input |
| Switch | output |
| Set Temperature | output |
RadiatorThermostat: Thermostat for a radiator.
Attribute | Description | Subtype |
---|---|---|
| Current Temperature | input |
| Status Indication | input |
| Heating Active | input |
| Heating Value | input |
| Switch | output |
| Set Temperature | output |
HeatingActuator: Heating control unit.
Attribute | Description | Subtype |
---|---|---|
| Info Flow | input |
| Actuator Flow | input |
WindowSensor: Sensor to detect window position.
Attribute | Description | Subtype |
---|---|---|
| Position | input |
DoorSensor: Sensor to detect door position.
Attribute | Description | Subtype |
---|---|---|
| Position | input |
MovementSensor: Sensor to detect movement.
Attribute | Description | Subtype |
---|---|---|
| Movement | input |
SmokeDetector: Sensor to detect fire. Note: ABB implements it in a way that makes all fire detectors trigger an alarm at once when one device detects smoke.
Attribute | Description | Subtype |
---|---|---|
| Fire | input |
FloorCallButton: Rings a bell.
Attribute | Description | Subtype |
---|---|---|
| Floor Call | output |
MuteButton: Mutes the floor call button.
Attribute | Description | Subtype |
---|---|---|
| Mute Button | output |
Scene: Represents a scene.
Attribute | Description | Subtype |
---|---|---|
| Set Scene | output |
Wallbox: Car charging station.
Attribute | Description | Subtype |
---|---|---|
| Switch | output |
| Enable | output |
| Installed Power | status |
| Total Energy | input |
| Start Last Charging | input |
| Status | input |
Configuration
The ABB Free@home App is configured by defining one or more authentication credentials. Each configuration requires the following data:
Attribute | Description |
---|---|
| Type of connection. Only "ProService" is currently supported. |
| API key provided by ABB |
| UUID of the ProService organization |
| Flag to enable or disable fetching from this API |
| Interval in seconds for device discovery. This is an expensive operation, should be no lower than 3600 s |
| API query timeout in seconds |
| Filter for asset creation, more details can be found in app's README |
| List of Eliona project ids for which this device should collect data. For each project id, all assets are automatically created in Eliona. |
The configuration is done via a corresponding JSON structure. As an example, the following JSON structure can be used to define an endpoint for app permissions:
Configurations can be created using this structure in Eliona under Apps > ABB Free@home > Settings
. To do this, select the /configs endpoint with the POST method.
After completing configuration, the app starts Continuous Asset Creation. When all discovered devices are created, user is notified about that in Eliona's notification system.
After configuration
After the application is configured, it looks up systems connected to the configured ProService account. On all of these systems, it automatically creates a user called "eliona_ProService" that would later be used when controlling the devices. This account has to be enabled locally on these systems.
To enable the account, log in to the SysAPs, find "User settings" and find a user called "eliona_ProService". Enable this user and ensure it has the correct access rights to control the devices.
Troubleshooting
Defective Device error message
There is an error with some devices, that some datapoint writes cause the system to consider the device "defective". The system then stops sending data to these devices, making them uncontrollable.
The devices are not defective though, the sysAP just needs to be restarted and the devices respond again.
ABB is aware of that error and on a way to fix it. If you run into this issue repeatedly, please let us know about it for a fix.
Troubleshooting using GraphQL
ABB has a GraphQL playground for it's Smart Home API: https://apim.eu.mybuildings.abb.com/adtg-api/v1/graphiql
You can log in to the playground either using your MyBuildings account or your ProService account.
To verify which relation you have to the systems, you can use this query:
Please note that ABB currently does not recommend using the same user account for ProService and MyBuildings portals. It causes some problems that can be worked around, but are not desired.
Requests optimization
ABB implemented a way to analyze resource usage by current user:
We took a lot of effort to bring resource usage down. Still, the app polling for new devices is a very resource-intensive process that can be further optimized if there is a demand for it.
Last updated