Dmitry

I described the problem in the correspondent issue. The device with firmware "4.1.8_9999" stops recognizing parameter "battery" in "get_value" command and returns "result":"ok" in the response instead of values if...

The device does not recognized request for battery value any more. I sent `get_value["battery"] ` to device and received `{"id":11974,"result":"ok","exe_time":32}` from it. After that I sent `get_value["temperature"]` to device and...

I'm totally agree with you. It might look like a riddle without the comment.

Done

I found a suitable solution: I defined custom refresh command for "battery". It should work for both old firmware (the battery information would be requested as before) and it does...

> It seems you can add permissions to the workflow, I got the build to work again once I added the following to the job: I tried to add write...

>Strange that an official Mi Home mobile app still gets this data from a device. The old way of getting this information locally was broken. I think the device still...

The solution still work, but causes warnings in logs like that: ``` [16:14:40][W][component:214]: Component took a long time for an operation (0.08 s). [16:14:40][W][component:215]: Components should block for at most...

I managed to make it to use second i2c bus for ESP32. I updated the library version to ""robtillaart/[email protected]" and modified the code for it: ``` #include "esphome.h" #include "AGS02MA.h"...