I’ve received the ESPs and I’ve flashed one with ESP Easy R120. v2.0 would not connect to my wireless access point.
The ESP is on my local network, accessible via the web interface. I’ve entered my mqtt broker credentials.
A few questions:
- The ESP may be subscribing with the client ID: “ESPClient0” and not “diffuser”. At least this is what my MQTT broker’s (mosca) log suggests.
`logs/mosca.log:11811:{“pid”:14,“hostname”:“mosca”,“name”:“mosca”,“level”:20,“time”:1524614051222,“msg”:“pingreq”,“client”:“ESPClient0”,“v”:1}
logs/mosca.log:11812:{“pid”:14,“hostname”:“mosca”,“name”:“mosca”,“level”:20,“time”:1524614051222,“msg”:“setting keepalive timeout”,“timeout”:22500,“client”:“ESPClient0”,“v”:1}
I’m not terribly worried about this but it’s not what I expected.
- How do I map ESPEasy’s GPIO layout to the ESPs? The ESP8266 has labels like D[0-8], but the ESPEasy suggests labels like GPIO-[0-16], but with a few entries greyed-out. Does D0 map to GPIO-0? I cannot understand the greyed-out GPIOs in the input.
This post suggests that I should be able to set the ‘First GPIO: GPIO-5 (D1)’ but I don’t seem to have that setting. I wonder if it’s a ESPEasy v2 feature vs. R120 that I am using (see above wireless AP problem).
- Can I create a log entry or some LED-blinks on the ESP upon receiving the MQTT event? I’d like to confirm that I’m receiving events properly before cutting any wires on the diffuser.