Maurice Makaay

Sure thing. Here's a build with the original Dockerfile: ``` Sending build context to Docker daemon 314.9kB Step 1/11 : FROM alpine ---> 187f426e38b1 Step 2/11 : ENV LANG C.UTF-8...

Reopened as requested on Discord.

Xiaomi and Yeelight annoying you is not good :-) I'm not sure what the best way would be to get the translated documentation in the project. Maybe a `doc_cn` folder...

I thinks it's easier to get it done through pull requests. Copying and pasting from here might end up in errors. Pull requests might sound difficult, but GitHub has a...

The latest ESPHome firmware is based on the ESP-IDF framework and not the Arduino framework. The reason for this is that it solves *a lot* of issues with getting the...

Ah, looking at the release notes of the latest stable ESPHome, I see that [a PR for adding MQTT to ESP-IDF builds](https://github.com/esphome/esphome/pull/2930) has been merged. So this might allow the...

I flashed my dev lamp with MQTT enabled, and what I see is that Home Assistant does not seem to understand the most important feature of the lamp: the actual...

When inspecting the MQTT traffic, I see the following auto-discovery info: ```json { "schema": "json", "clrm": true, "supported_color_modes": [ "color_temp", "rgb" ], "brightness": true, "effect": true, "fx_list": [ "Slow Random",...

I noticed quite a few of these messages during the build. This might possibly be related to the issue: ``` In file included from src/esphome/components/mqtt/mqtt_client.cpp:1: src/esphome/components/mqtt/mqtt_client.h:280:3: warning: missing initializer for...

That is to be expected I think. The light settings and light mode sensor are the elements that ought to be available throught mqtt autodiscovery. What functionality would you expect...