Light logger for the hallway, Wemos D1 mini with an LDR on A0. I wanted smooth values so the loop reads A0 as fast as it can and keeps a running average, then publishes every 10 s to Hermetry with PubSubClient.
WiFi keeps dropping. client.state() shows -3 (connection lost) a few times an hour, sometimes -2 on reconnect. When I comment out the analogRead loop it stays connected all day. Is the ADC somehow fighting the WiFi?
Try adding delay(1) in the loop?
Pretty much, yes. Hit this with a soil sensor last spring.
On the ESP8266 the ADC and the radio share bits of the RF hardware, and calling analogRead() thousands of times a second starves the WiFi stack. It’s a known issue on that core. delay(1) helps a bit because it yields, but you’re still hammering the ADC.
An LDR in a hallway doesn’t change in milliseconds. Read every 100 ms, average ten readings, done:
unsigned long t = 0; uint32_t acc = 0; uint8_t n = 0;
void loop() {
client.loop();
if (millis() - t >= 100) {
t = millis(); acc += analogRead(A0);
if (++n == 10) { lux_raw = acc / 10; acc = 0; n = 0; }
}
}And if you ever want every sample in Hermetry, don’t publish each one. Collect a minute of them and send one message with an array of {ts, values} records, a message costs the same against the quota whether it holds one reading or fifty.
Down to one read every 100 ms and it has been connected for two days straight. Michael, delay(1) alone made it drop less, but it still dropped.
- Debes estar registrado para responder a este debate.
Únete a la conversación
Inicia sesión para preguntar y responder, dar me gusta a las publicaciones útiles y marcar la respuesta que resolvió tu problema. Cada aportación suma puntos y niveles.