Issues / Info on Esp32 card embedded

[DM5861]

Hello,

Recently, I purchased a pellet stove and it has a motherboard on which is plugged an ESP32 wifi module which communicates with an Android application installed on the phone either directly or by the operator box in wifi in both cases.
For 2 or 3 weeks, the installation of the app has ended with an error and not knowing this module, I would like to learn more about the ESP32 in particular.
I noticed after a few measurements with the "Wifi scanner" app that
1) The transmission power is lower than the other Wlan for the same distance.
2) The flow is very unstable (see graph) and confirmed by the pings sent to the address 192.168.4.1 is this normal or not?
3) How can the operator box (192.168.1.1) on the Lan 192.168.1.0/24 reach the address of the ESP32 (192.168.4.1) and then modify it to 192.168.1.38 in its dhcp range, as I mentioned above have noticed for several months?

[ESP_Sprite]

I'm afraid that there might be very little we can tell you about that... Espressif makes the chip, but whoever designed the pellet stove or the WiFi module for it is responsible for the software running on it. We create a SDK to use the chip, but that effectively only provides functionality on which a manufacturer can build a program/user experience.

[DM5861]

Thank you for your reply.
But, for my first two observations, the pings were raised at a distance of 10 cm from the esp32 and 5/10 were lost.
Is it a correct result or not to join the esp32 module? In this test condition, we override the manufacturer's software.

[ESP_Sprite]

Thank you for your reply.
But, for my first two observations, the pings were raised at a distance of 10 cm from the esp32 and 5/10 were lost.
Is it a correct result or not to join the esp32 module? In this test condition, we override the manufacturer's software.

However, unless you're actually re-flashing the ESP32, you're not overwriting the manufacturers software *that is running on the ESP32 itself*. Hence there's very little we can do for you. I'd suggest you ask the manufacturer; given the fact that they sold this to you, they should be responsible for fixing this.