Andreas Motl

Dear Aurélio, thank you for writing in and for the kind words [^usecase]. Well, it would be sweet if Kotori would have support for InfluxDB 2.x, and maybe also other...

Hi again, > In addition to the points you mentioned, [there would also be the [export feature], which would need to be prepared for InfluxDB 2.x, no?]. You are absolutely...

Hi Aurelius, thank you for sharing this detail. Yes, using that client library was planned for supporting InfluxDB 2.x. The section at [1] has some more details about compatibility with...

Hi again, I just want to share some additional thoughts on this topic. I believe, when starting to work on this feature/improvement, we should aim for converging all that InfluxDB-specific...

Hi @LichRene, thanks a stack for your report. #56 will bring more packaging flavors. After we have integrated this, we will also publish .deb packages for arm32v7 and arm64v8 to...

Kotori is not available in ready-made packages for CentOS or any other RPM-based system yet. However, we will be happy to work on it if resources will allow us to...

Hi @18Scoobz, when you look at the configuration snippet of WeeWx's `weewx.conf` [1], you will just have to add a different topic, like ``` topic = weewx/097287c4-6fb0-4aeb-a095-00d65ecb15f7/Leoni/VantagePro2 ``` As you...

Hi @18Scoobz, did you have success submitting measurement data from two or more instances of WeeWX to Kotori? Let me know if you need further assistance. With kind regards, Andreas.

https://github.com/esphome/esphome/pull/719 gives some clues, here it would be for HTTP telemetry, but it can surely be applied to MQTT as well: ```yaml - http_request.post: url: https://api.telegram.org/bot:/sendMessage headers: Content-Type: application/json X-Custom-Header:...

We just heard back from the workbench that this snippet works well: ```yaml time: - platform: sntp id: sntp_time mqtt: broker: foobar on_message: - topic: esp32/bme280 payload: "status" qos: 0...