colorRGB: This channel handles color values in RGB format.switch: This channel represents an on/off state of a given topic and can send an on/off value to a given topic.contact: This channel represents an open/close state of a given topic.dimmer: This channel handles numeric values as percentages.number: This channel can show the received number on the given topic and can send a number to a given topic.string: This channel can show the received text on the given topic and can send text to a given topic.You can add the following channels: # Supported Channels Remember that you need a configured broker Thing first! On each of those things you can add an arbitrary number of channels. Of so called "Generic MQTT Things" to organize yourself. # Supported Thingsīecause of the very generic structure of MQTT, this binding allows you to add an arbitrary number Please have a look at the specific openHAB bindings. That it has the MQTT convention Homie or HomeAssistant implemented. If you use an open source IoT device, the chances are high, A sensor would only have a state topic,īecause every manufacturer can device on his own on which topic his devices publish, thisīinding can unfortunately not provide any auto-discovery means. This pattern is very common, that you have a command and a state topic. The manufacturer specified that this value canīe found on "device123/brightness". In openHAB we call that a command topic.Īnd now assume that we have a mobile phone (or openHAB itself) and we register with the MQTT broker,Īnd want to retrieve the current brightness value. The manufacturer decided to accept newīrightness values on "device123/brightness/set". It has a unique id amongst all light bulbs, say "device123". Let's assume there is an MQTT capable light bulb. A topic can look like this: "mydevice/temperature". Instead it subscribes to specific topics. If a client subscribes to a broker, it is certainly not interested in all published messages. Therefore you must have configured a Broker Thing first via the MQTT Broker Binding! # MQTT Topics OpenHAB itself is not an MQTT Broker and needs to connect to one as a regular client. When a device (a client) wants to receive data from the broker, we call this operation a “subscribe”.When a device (a client) wants to send data to the broker, we call this operation a “publish”.MQTT servers are called brokers and the clients are simply the connected devices. It is designed as a lightweight messaging protocol that uses publish/subscribe operations to exchange data between clients and the server. It stands for Message Queuing Telemetry Transport. MQTT is one of the most commonly used protocols in IoT (Internet of Things) projects.
0 kommentar(er)
