Table of Contents
@Home
Introduction
The @Home controller redirects output commands to an MQTT broker.
The topics and commands are object specific.
Setup
Host
Broker hostname or IP.
Port
Broker port number; Default 1883.
Output
Interface ID
The @Home Interface ID.
Topic
The complete publish and subscribe topic.
Parameter
The second ON/OFF fields represent the command string for ON and OFF. (User variables are supported.)
On this screen shot "1" for ON, and "0" for OFF.
Server Trace
20190726.140121.294 r9999I 00C2D000 OHOME 0181 publish: [relais1/schalte] [1]
20190726.140121.294 r9999B 00C2D000 OMQTT 0357 send PUBLISH: Topic=relais1/schalte(1) Payload=1 ID=2 totalLen=22 nrLenBytes=0 topicLen=15
20190726.140121.294 r0000B 00C2D000 OMQTT *trace dump( 0x51D0DAE0: length=22 )
offset: 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F |ASCII...........|
--------------------------------------------------------- |----------------|
00000000: 33 14 00 0F 72 65 6C 61 69 73 31 2F 73 63 68 61 |3...relais1/scha|
00000010: 6C 74 65 00 02 31 |lte..1 |
Sensor
Interface ID
The @Home Interface ID.
Address Topic
The complete subscribe topic.
Type
Register.
Generated variables
A variable will be generated for every reported register type.
The variable name is formatted like this:
reg<type>_<sensorID>
Example for sensor s47 humidity:
reg4_s47
| Type | Description | Units |
|---|---|---|
| 0 | Default general value | Integer |
| 1 | Temperature | 0.01 °C |
| 2 | Light level | Lux |
| 3 | Button | Number |
| 4 | Humidity | 0.01 % |
| 5 | Pressure | mBar |
HTTP Output
As alternative to MQTT it is possible to address outputs directly by the HTTP protocol.
Interface ID
The @Home Interface ID.
Topic
The hostname prefixed with http:
http://hostname
Parameter
The second ON/OFF fields represent the command string for ON and OFF. (User variables are supported.)
Example
The Off command:
GET /30000/00
The On command:
GET /30000/01