-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mqtt stops working when adding a second sensor #2342
Comments
This line seems to indicate things are working somewhat I would not use the RX TX lines for sensors unless it was all that was left. You have to turn off serial logging to get them to work properly. |
@Frogmore42 thanks for the input. Changed the pins from TX/RX to D4/D2 and the problem persists. EDIT: Checking web log, I found that the mqtt command is sent, but it is not logged on the server. |
The fact it states 16:31:05 RSL means the MQTT connection is gone. it should say 16:31:05 MQT. You're also using a non-tasmota supported memory model. Only 1M(no spiffs) is supported. |
@arendst thanks for the response, but according to the wiki the NodeMCU esp8266 is indeed supported. I don't really understand what do you mean by Only 1M(no spiffs) when it works without problem with the other two sensors. |
this is the part (memory model) that is not supported: There are different ways to set that depending on how you are building the image. NodeMCU is supported and generally works. But, do you have this on a breadboard? I discovered a couple of days ago that some of my NodeMCU devices behave very strangely when I have them on a breadboard. I had assumed that they were just defective, but I was curious so I removed it from the breadboard and used jumper wires to connect the 4 pins I actually needed on the breadboard. With this small change, it started working just fine. Previously, it would get hardware watchdogs and reboot and not be able to connect and get the watchdog again. If I reloaded the FW it would work fine for a little bit. My guess is that all the metal in the breadboard was causing problems with the 2.4GHz Wi-Fi signal. Now, I have several other Wemos D1 Minis and one or two other NodeMCUs that work fine on a breadboard. But, having the Wi-Fi antenna right next to the metal jumpers in a breadboard is a really bad idea according to many RF experts. |
@Frogmore42 thanks for the response. No the nodemcu is not on a breadboard, it works with both sensors when one of them is disabled. |
I have the same problem, did you fix it. |
It's not your hardware that is not supported. It's your compiled software memory model that is not supported. Learn how to set your IDE (or use provided platformIO ini file) for 1M (No SPIFFS) during initial serial upload. |
@arendst sorry to disturb you again, but I´ve reflashed with 1 MB no SPIFSS, rewired everything again to only one board and the problem is exactly the same. I attach you the status 0 response.
|
Check your power supply. Do not use esp/arduino 2.4.1. RSL means no mqtt connection. Get a solid mqtt connection first. Then log what messages you receive with logging level 3 when mqtt drops connection. This normally works fine so prepare for a local solution. |
@arendst Switched to a new power supply (5V 1A), switched to logging level 3 and hot plugged the last sensor when an stable mqtt connection was made. (marked in code with brackets)
|
Well, I experience the same problem and I narrowed it down to a message size problem.
|
Okay, this took hours of sleep, but now I solved it. A 128 characters are by far not enough!
So if you have the "RSL:" instead of "MQT:" check the version of your "PubSubClient-EspEasy". |
Make sure these boxes are checked before submitting your issue - Thank you!
status 0
ESP8266 with SI7021 works perfectly and sends to mqtt humidity and temperature values.
when I connect BH1750 Ambient Light Intensity sensor to tx/rx, tasmota web interface logs the three values (lux, temp and humidity) but no reports are sent to mqtt.
If I physically disconnect BH1750 and reset, the mqtt starts working again.
BH1750 connections:
![tasmota pin config](https://user-images.githubusercontent.com/12032199/38255857-2ff6fa9c-375d-11e8-9175-c4d7cdb6cbde.png)
VCC -> 3v3
GND -> GND
SCL -> RX
SDA -> TX
ADDR -> not connected
status 0 (unplugged BH1750):
status 0 (plugged BH1750):
The text was updated successfully, but these errors were encountered: