mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 00:55:52 +03:00
[GH-ISSUE #1107] Defining WifiManager causes MQTT connection to fail #948
Labels
No labels
📶 WiFi
🕸️ HTTP
Branch
DEV Help Wanted
Discussion
Documentation
ESP32
Example
Good First Issue
Hotfix
In Progress
Incomplete
Needs Feeback
Priority
QA
Question
Task
Upstream/Dependancy
bug
duplicate
enhancement
invalid
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/WiFiManager#948
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @coolcoastcat on GitHub (Aug 14, 2020).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1107
Hardware
WiFimanager Branch/Release:
Esp8266/Esp32:
Hardware: ESP-12e, esp01, esp25
ESP Core Version: 2.4.0, staging
Description
I have a working example in which I can connect to Google's IoT API with the Google Cloud IoT Core JWT library, v1.1.10, which uses the Arduino MQTT library, v2.4.7. I'm trying to weld this code into my project which leverages the WifiManager for AP configuration and simply instantiating the WifiManager with the following line of code causes the connection to MQTT to fail:
The error returned by the MQTT library, when the WifiManager is instantiated, is:
LWMQTT_NETWORK_FAILED_CONNECTwhich is cryptic and has no relevant hits in a google search.Settings in IDE
The project is built from command line using
pio run --target upload --target monitorRelevant Additional libraries:
#include "WiFiClientSecureBearSSL.h"
#include <CloudIoTCore.h>
#include "esp8266_mqtt.h"
Debug Messages
The WifiManager is the first call in the setup loop and no matter what delay is injected in the setup loop at the start, the only debug seen is:
Not clear why simply instantiating the WifiManager object would cause a collision in the ESP8266Wifi Wifi object and prevent a successful MQTT connection.
@coolcoastcat commented on GitHub (Aug 14, 2020):
This turned out to not be a WifiManager issue.