Hi @SmsAlert I know nothing at all about uPython, but I have looked at the Blynk communication protocol in some detail.
I think you’re making the assumption that the Bklynk server sends a 200 (C8) back to the hardware after each virtual write, and that the uPython library is losing this somehow, but as far as I can tell this isn’t the case.
As you’ve discovered, some commands do return a 200 acknowledgement, but not virtual writes.
If you use C++ and add the #define BLYNK_DEBUG command you get quite a comprehensive output of the communication between the device and the server.
The meaning of these commands and responses are discussed to a certain extent in this topic…
That topic was based on Blynk Legacy, the Blynk IoT protocol definitions have changed slightly since, and are documented here:
I think the only way you’re going to get the acknowledgement you need is to call a sync_virtual immediately after your virtual_write and compare the two values.
Pete.