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
MQT connected but Tasmota not sending all sensor data (MQT/RSL) #3009
Comments
I would check first why mqtt is not working reliable. Nothing from client side should be able to. |
Hi @Jason2866 , thanks for you comment.
I've tested two different ESP's, both do the same thing also - as soon as a Switch is introduced to the module, the temperature data gets tagged with RSL. The switch then sends the MQT message, which is recieved by the broker. (I have also put a MQTT monitor - MQTT.fx - in line with this, and verified). |
Free Memory is low. Compile a version with features disabled and try again. |
Thanks @Jason2866 , I've fully removed the Arduino IDE and reinstall a portable nightly version with core 2.3.0, and this has indeed fixed the issue. I think I initially made the mistake of using the Wemos D1 mini board rather than the generic ESP8266 in the upload config. Such a minor mistake, such annoying consequences! The 5 second status updates from the log above was due to SonWeb interface, which I've fixed also. Many thanks, I'll mark as closed |
I do apologise in advance if this is a user error but I've spent a good number of days trying to fix this without much luck.
I have a WemosD1 mini as a Generic module with a BMP180 (D3 GPIO0 - I2C SDA & D4 GPIO2 I2C SCL) )and a PIR sensor (D7 GPIO13 - Switch1) attached. MQTT broker is Mosquito running on Home Assistant - this is connecting fine apparently.
My BMP180 sensor is being recognised and data is displayed on the UI, and MQT transmits are occurring in the console. As soon as I enable the Switch1 module and the device reboots, my temperature telemetry gets tagged with "RSL" (which I'm led to believe is normally if the MQTT broker is offline?) instead of MQT. The broker is still connected though, as the Switch1 activations (PIR sensor) transmit with no issues.
This can be replicated by removing the Switch1 modeule, which results in the MQT tag in front of the temperature sensor data returning.
12:55:56 MQT: stat/roofspace/RESULT = {"POWER":"ON"}
12:55:56 MQT: stat/roofspace/POWER = ON
12:56:12 RSL: tele/roofspace/STATE = {"Time":"2018-06-17T12:56:12","Uptime":"0T14:01:04","Vcc":2.703,"Wifi":{"AP":1,"SSId":"AP","RSSI":50,"APMac":"APMAC"}}
12:56:12 RSL: tele/roofspace/SENSOR = {"Time":"2018-06-17T12:56:12","Switch1":"ON","BMP180":{"Temperature":18.4,"Pressure":1012.2},"TempUnit":"C"}
-Without 'Switch1' enabled
13:06:08 RSL: tele/roofspace/STATE = {"Time":"2018-06-17T13:06:08","Uptime":"0T00:00:16","Vcc":2.702,"Wifi":{"AP":1,"SSId":"XXXX","RSSI":50,"APMac":"10:XXXF"}}
13:06:08 MQT: tele/roofspace/SENSOR = {"Time":"2018-06-17T13:06:08","BMP180":{"Temperature":18.6,"Pressure":1012.0},"TempUnit":"C"}
I've found similar bug reports, and have tried using Tasmota 5.12 as well as the 2.30 ESP libraries (Initially I was using 6.0.0.a and 2.41 lib). As of now I'm out of ideas...?
Many thanks.
The text was updated successfully, but these errors were encountered: