mirror of
https://github.com/openhab/openhab-addons.git
synced 2025-01-10 23:22:02 +01:00
22b28bf674
* [mqtt.generic] separate command parsing from cached value updating fixes #12150 Previously, Value.update would parse the command, _and_ update the cached value with that command. Which means that when sending a command towards MQTT (instead of processing an update from MQTT), the cached value was unintentionally updated. This prevented the REFRESH command from returning the most recent value received from the device. Separating the two concerns also makes the test more obvious what they are testing, and vastly simplified a kludgy workaround that RollershutterValue was using to be able to process Commands that aren't States. Signed-off-by: Cody Cutrer <cody@cutrer.us> * [mqtt.generic] split Value::parseCommand into parseMessage so that a particular value type subclass can have varying implementations if it desires --------- Signed-off-by: Cody Cutrer <cody@cutrer.us> |
||
|---|---|---|
| .. | ||
| src | ||
| NOTICE | ||
| pom.xml | ||
| README.md | ||
MQTT Homie Binding
NOTE: This binding is provided by the MQTT binding, and therefore no explicit installation is necessary beyond installing the MQTT binding.
Devices that follow the Homie convention 3.x and better are auto-discovered and represented by this binding and the Homie Thing.
Find the next table to understand the topology mapping from Homie to the Framework:
| Homie | Framework | Example MQTT topic |
|---|---|---|
| Device | Thing | homie/super-car |
| Node | Channel Group | homie/super-car/engine |
| Property | Channel | homie/super-car/engine/temperature |
System trigger channels are supported using non-retained properties, with enum data type and with the following formats:
- Format: "PRESSED,RELEASED" -> system.rawbutton
- Format: "SHORT_PRESSED,DOUBLE_PRESSED,LONG_PRESSED" -> system.button
- Format: "DIR1_PRESSED,DIR1_RELEASED,DIR2_PRESSED,DIR2_RELEASED" -> system.rawrocker