Hi, I have a confusion to read a VPin. Before I start, I’ve looked some websites to get the idea behind this problem. The problem is really basic,
I’m using 2 ESP-01S modules to turn on/off relay according to DHT11.
I used the LED to display relay state on DHT11’s code which is “V5”.
When I try to write V5 it shows the correct value on LED widget, however it does not write to the relay.
I used the backup method, I defined a variable named testPin as V10. Then, I made V5 and V10 pins SET/RESET respectively according to the sensor. Their definitions are exactly the same. When I turn the relay ON/OFF with V10, it works successfully, but when I try with V5, the relay does not accept the values.
I guess LED Widget block to read value from another ESP01 module.
Edit: I did not use V10 on any widget. It just runs only on datastream.
The ESP-01 isn’t a great choice as ot only has two useable pins and is difficult to work with because of its form factor. Also, communication between two devices needs to be done via the Blynk server using Automations. Each ESP-01 needs to be a separate Blynk device with a unique auth token.
@mfatihtuz Please edit your post, using the pencil icon at the bottom, and add triple backticks at the beginning and end of your code so that it displays correctly.
Triple backticks look like this:
```
Copy and paste these if you can’t find the correct symbol on your keyboard.
Blynk expects each device to have its own Auth token, and to establish its own continuous connection to the Blynk server.
If you don’t do this then you a you can’t monitor whether each individual device is online, as Blynk reports “Online” when either one of the two devices are connected to the server.
I suspect that in future, if the Blynk server detects two devices sharing the same Auth token it will kill one (or both) of the connections. This is because the Blynk billing system is based on device count, and you’re misusing the system when you have one Blynk device with two physical devices connected to it.
In addition, your relay code is using V4, when I suspect it should be using V5 instead, but this will be irrelevant when you stop sharing a single Auth token across two devices.