You essentially have two (or more) devices sharing the same Blynk auth token. You have the physical device (e.g., ESP8266 nodeMCU) and a “virtual device” corresponding to each instance of the web client. Beware … the Blynk project / app depicts a physical device as online if: the physical device is connected; or one or more of the virtual devices (web clients) is connected. Your physical device may appear to be connected when, in fact, it’s not.
I tested the web client with an auth token assigned through dynamic provisioning. As expected, the web client can’t differentiate statically- and dynamically-provisioned auth tokens. The web client works fine.
I have a Labeled Value widget with a Refresh Interval of one second. At times, the BLYNK_READ corresponding to the virtual pin assigned to the widget is no longer invoked (on the physical device) once the web client connects. Once the web client disconnects, the BLYNK_READ automatically resumes. I assume the BLYNK_READ is being redirected to the web client (and into the bit bucket). At times, the physical device and web client can co-exist with the BLYNK_READ being invoked on the physical device. This seems to relate to the state of the Blynk project / app at the time the web client connects. In one state, the BLYNK_READ continues with respect to the physical device. In the other state, the BLYNK_READ is redirected to the virtual device (web client). Just an uneducated guess on my part.
In addition to the Number Input and Image widgets (and likely others), the Text Input and Device Tiles widgets are not yet supported. Avin is maintaining the list of supported widgets on GitHub.
Is there any way the web client could dynamically discover the devices / auth tokens associated with a user’s account or Blynk project / app?
This is an outstanding effort on Avin’s part and offers tremendous potential.