p.kaczmarek2 wrote: The autoexec.bat posted earlier also contains 0.01W resolution setup;
setChannelType 3 Power_div100
So,
@hwti, can you elaborate on what you mean here?
hwti wrote:
The device shows the energy values with 0.01Wh resolution, but only 1Wh is reported.
I suppose the only way to get the full resolution would be to modify the CH573F firmware (not sure if possible).
Are you saying that the values from the screen display are not sent to OBK?
I wrote about the energy values (in Wh), not the power.
For example, the screen displays 0.07309kWh, and OpenBK reads 73 for channels 6/9.
But since Tuya doesn't display these two additional digits either, the MCU firmware probably never reports them (unless it's behind an unknown setting).
maximesharp wrote: the pairing screen disappears once the device is connected to the Wi-Fi network.
Even with "MQTT State: not configured," like in your first post?
It seems by default OpenBK waits for the MQTT connection to be established to report the Wi-Fi state 4 (i.e., "connected to the cloud").
Maybe the MCU remembers if a Tuya pairing has been done and has a different behavior.