Mqtt 2.4, GUI configured broker, text item files

Setup, Configuration and Use Items & Sitemaps
10

this is really wrong. 2.4 is very easy to setup without paperUI and I personally recommend to avoid depreciated gui anyways…

OP:
here is how you configure your broker (make it separate file so it won’t be refreshed when you need to change some other things)

Bridge mqtt:broker:home "Mosquitto MQTT Broker" [ 
  host="xx.xx.xx.xx",
  secure=false,
  port=1883,
  qos=0,
  retain=false,
  clientid="someid",
  //certificate="",
  //certificatepin=false,
  //publickey="",
  //publickeypin=false,
  keep_alive_time=30000,
  reconnect_time=60000,
  //lastwill_message="",
  //lastwill_qos=1,
  //lastwill_topic="",
  username="",
  password=""
]

then for example some temp/hum thing

/* attic */
Thing mqtt:topic:AtticClimate   "Attic Climate" (mqtt:broker:home) @ "Attic" {
Channels:
    Type number : temperature   "Temperature"       [ stateTopic="homie/attic/climate/temperature"]
    Type number : humidity      "Humidity"          [ stateTopic="homie/attic/climate/humidity"]
}

and item

/* attic */
Number  Attic_Temperature       "Temperature [%.1f °C]"     <temperature>   (gStore10, gAT)                                                     { channel = "mqtt:topic:AtticClimate:temperature" }
Number  Attic_Humidity          "Humidity [%.0f %%]"        <humidity>      (gStore10, gAT)                                                     { channel = "mqtt:topic:AtticClimate:humidity" }

as you can see I’m using homie convention, so those things will be autodiscovered by OH, but I’m not using it at all, as I don’t feel very comfortable to not have any reliable and intuitive backup/control over it via paperUI… files are easy to maintain and easy to backup.

just my 2cents

1 Like