Hello, I just flashed my Heltec v3 with 2.2.24.e6a2c06 Beta.
I’ve noticed some issues with using MQTT and Wifi.
It will not connect my local MQTT broker when using Wifi. Sometimes a message will be published stat/{ID}/offline, but that’s it.
However, when I disable Wifi and connect to it with Bluetooth, enable “proxy to client” it works just fine.
I have a TBEAM on the same network & broker, using the same version of Meshtastic and it works just fine.
I just flashed another Heltec v3 node with the same firmware, and same issue persists. I can confirm that MQTT is working fine with a TBEAM using either of the credentials I used for both Heltecs with the same firmware version.
I’m using a Heltec lora V3 on wifi with MQTT and no problems. The wifi signal is fairly weak compared to a phone or laptop though. I’m on 2.3.1 but the previous versions work too…
I just updated to 2.3.2.63df972 Beta and same issue.
I pulled the logs from it:
INFO | 00:55:22 103 Attempting to connect directly to MQTT server 192.168.1.100, port: 1883, username: mesht_XXXX, password: XXXXXX
DEBUG | 00:55:22 103 [WifiConnect] Updating NTP time from 0.pool.ntp.org
INFO | 00:55:25 105 [WifiConnect] MQTT connected
INFO | 00:55:25 105 [WifiConnect] published online=1
DEBUG | 00:55:25 106 [WifiConnect] NTP Request Success - Setting RTCQualityNTP if needed
DEBUG | 00:55:25 106 [WifiConnect] Upgrading time to quality 3
DEBUG | 00:56:58 106 [WifiConnect] Read RTC time as 1712537818
DEBUG | 00:57:04 112 [Power] Battery: usbPower=0, isCharging=0, batMv=3957, batPct=76
DEBUG | 00:57:24 132 [Power] Battery: usbPower=0, isCharging=0, batMv=3989, batPct=79
[133335][D][WiFiClient.cpp:546] connected(): Disconnected: RES: 0, ERR: 128
INFO | 00:57:25 133 [mqtt] Using non-TLS-encrypted session
INFO | 00:57:25 133 [mqtt] Attempting to connect directly to MQTT server 192.168.1.100, port: 1883, username: mesht_XXXX, password: XXXXXX
[136350][I][WiFiClient.cpp:253] connect(): select returned due to timeout 3000 ms for fd 52
ERROR | 00:57:28 136 [mqtt] Failed to contact MQTT server directly (1/5)...
DEBUG | 00:57:44 152 [Power] Battery: usbPower=0, isCharging=0, batMv=4013, batPct=83
INFO | 00:57:58 166 [mqtt] Using non-TLS-encrypted session
INFO | 00:57:58 166 [mqtt] Attempting to connect directly to MQTT server 192.168.1.100, port: 1883, username: mesht_XXXX, password: XXXXXX
ERROR | 00:58:13 181 [mqtt] Failed to contact MQTT server directly (2/5)...
DEBUG | 00:58:13 181 [Power] Battery: usbPower=0, isCharging=0, batMv=4040, batPct=88
[181407][I][WiFiClient.cpp:549] connected(): Unexpected: RES: 0, ERR: 119
Seems like Wifi is disconnecting for some reason? Not sure what Err 119 or 128 is. I don’t think anything else is having Wifi issues. I run a few Tasmota sensors and that. I have a Lillygo T-Echo and it seems to run fine, but none of the 3 Heltecs are.
with ver 2.3.4 i can connect for less of an hour than stop to talk on wifi.
After the wifi is configured i can connect to the heltec by ip acquired via dhcp but after about 1 hour became unreacheble
Same issue here except with a tbeam - device states reconnecting to wifi after some time but never reconnects. Firmware 2.3.4, connected to official MQTT server.
Have a very stable network and have several IoT devices connected to the same network without an issue, so this is odd.