You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear,
Welcome to my thread and I hope you can help me with a question:
I'm developing an IoT project using the Ubidots platform, using the “esp32-mqtt-main” library together with “WIFIMANAGER-ESP32-master”. The whole project was going well until I decided to use the “Custom Parameters” feature available in the WiFiManager library in order to add the “TOKEN” variable through the access portal to facilitate the use of the Ubidots platform.
The problem arises when matching the TOKEN obtained through the WiFiManager access portal and the variable responsible for storing the TOKEN of the “esp32-mqtt-main” library, generating the error below:
Note that the value of UBIDOTS_TOKEN is correct, but the connection does not happen. I did a test by inserting the Token directly into the variable and it works perfectly, but making the entire implementation unfeasible, I need help.
Dear,
Welcome to my thread and I hope you can help me with a question:
I'm developing an IoT project using the Ubidots platform, using the “esp32-mqtt-main” library together with “WIFIMANAGER-ESP32-master”. The whole project was going well until I decided to use the “Custom Parameters” feature available in the WiFiManager library in order to add the “TOKEN” variable through the access portal to facilitate the use of the Ubidots platform.
The problem arises when matching the TOKEN obtained through the WiFiManager access portal and the variable responsible for storing the TOKEN of the “esp32-mqtt-main” library, generating the error below:
Note that the value of UBIDOTS_TOKEN is correct, but the connection does not happen. I did a test by inserting the Token directly into the variable and it works perfectly, but making the entire implementation unfeasible, I need help.
Higrometro_teste.zip
The text was updated successfully, but these errors were encountered: