Thanks for taking your time, > an mqtt driver that feeds weewx with data from any mqtt broker would > useful for many use cases. >
Definitely. > (1) publish each observation, e.g., /telemetry/outside_temperature with > data 32.3 > This would be my usecase. > what topic structure does openhab expect? Actually in my approach it wouldn't matter, because the weather data is already in openHAB via mqtt through a mosquitto broker, but to answer that: Weather data, f.e. outside temperature is sent from DS18B20 sensor via one wire protocol over wifi to an esp8266 (esp easy firmware <http://www.esp8266.nu/index.php/TemperatureSensor> loaded), in addition to that it is published from the esp8266 via implemented mqtt support to a broker, from the broker it is imported to openhab via openHAB mqtt binding which can be configured to any topic. An import looks like: Number TemperatureOutside "Temperature [%.1f °C]" { mqtt="<[mosquitto:/esp8266three/temperature:state:default]" } so the topic is /esp8266three/temperature or any other you may have configured. > what other mqtt topic topologies have you seen? Despite from weather data (light intensity, pressure, humidity, temperature) you are able to control relays, switches, displays, analog in- or outputs and many many more, take a look here under "Applications" <http://www.esp8266.nu/index.php/Main_Page>. And this is only the espeasy firmware, there are many more firmwares available for the esp8266, including arduino ide based or for lua scripting. And: it's dirty cheap, the esp8266 with a temperature sensor comes to less than 10 Euro. So I thought: if the weather data is already present on a mqtt broker, there may be a function to import those to weewx ... ;-) -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
