Arduino Library 2.17.0

alvarolb · August 24, 2021, 7:28am

Hi, can you please verify the issue is still there?

I saw a problem with the us-east server in the cluster. I cannot test it directly, as based on my location the server resolves to eu-central.

George_Santiago · August 24, 2021, 2:09pm

Still with the same problem.
[_SOCKET] Connecting to iot.thinger.io:25202…
[_SOCKET] Using secure TLS/SSL connection: yes
[_SOCKET] Error while connecting!
[_SOCKET] Connecting to iot.thinger.io:25202…
[_SOCKET] Using secure TLS/SSL connection: yes
[_SOCKET] Error while connecting!

   Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/espressif8266/nodemcuv2.html
PLATFORM: Espressif 8266 (3.2.0) > NodeMCU 1.0 (ESP-12E Module)
HARDWARE: ESP8266 80MHz, 80KB RAM, 4MB Flash
PACKAGES:
 - framework-arduinoespressif8266 3.30002.0 (3.0.2)
 - tool-esptool 1.413.0 (4.13)
 - tool-esptoolpy 1.30000.201119 (3.0.0)
 - tool-mklittlefs 1.203.210628 (2.3)
 - tool-mkspiffs 1.200.0 (2.0)
 - toolchain-xtensa 2.100300.210717 (10.3.0)
LDF: Library Dependency Finder -> http://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Found 39 compatible libraries
Scanning dependencies...
Dependency Graph
|-- <thinger.io> 2.18.0
|   |-- <ESP8266WiFi> 1.0
|   |-- <DNSServer> 1.1.1
|   |   |-- <ESP8266WiFi> 1.0
|   |-- <ESP8266WebServer> 1.0
|   |   |-- <ESP8266WiFi> 1.0
|-- <DNSServer> 1.1.1
|   |-- <ESP8266WiFi> 1.0
|-- <ESP8266WebServer> 1.0
|   |-- <ESP8266WiFi> 1.0
Building in release mode

George_Santiago · August 26, 2021, 5:43pm

I did the test again today after verifying that the Thinger.io platform has updated to version 3.3.3. Even so, it still has an error.

alvarolb · August 26, 2021, 5:57pm

Hi, it has been fixed in the library but not released yet. You can try it taking the source from github in the develop branch.

github.com

thinger-io/Arduino-Library/blob/develop/src/ThingerESP8266.h

// The MIT License (MIT)
//
// Copyright (c) 2017 THINK BIG LABS SL
// Author: alvarolb@gmail.com (Alvaro Luis Bustamante)
//
// Permission is hereby granted, free of charge, to any person obtaining a copy
// of this software and associated documentation files (the "Software"), to deal
// in the Software without restriction, including without limitation the rights
// to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
// copies of the Software, and to permit persons to whom the Software is
// furnished to do so, subject to the following conditions:
//
// The above copyright notice and this permission notice shall be included in
// all copies or substantial portions of the Software.
//
// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
// IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
// FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
// AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,

This file has been truncated. show original

George_Santiago · August 26, 2021, 7:30pm

I did initial tests with the 2.2 library under development:
Some feedbacks:

ESP8266 successfully connected to Thinger.io;
OTA update worked correctly on ESP8266. After the update, the ESP8266 automatically reset and started the new Firmware.

NOTE: I will run tests with ESP8266 with WebConfig/WiFiManager to see if everything is ok. And I will try to perform OTA updates to check the device behavior.

General and library questions 2.2:

I use a JSON file to store the device credentials (USERNAME, DEVICE_ID, DEVICE_CREDENTIAL). Can I OTA the JSON file too? Or do I have to use the file “arduino_secrets.h” to be able to update this information via OTA, if necessary?
After updating a device via OTA, where can I store the information about the current Firmware version of the device? Would it be possible to inform the Firmware version in the Thinger.io extension of the VS Code?
I believe this information would be important to prevent the developer from updating via OTA a device that already has the Firmware updated.
What would the example of updating over the air with ThingerWebConfig look like?

Thanks for the attention and for the library update!

George_Santiago · August 27, 2021, 7:34pm

Also regarding the 2.2 library under development:

I understand how important it is to update the codes of “ThingerTinyGSM.h” and “ThingerWebConfig.h” to accept OTA firmware upgrade and new functionality, as I believe these are very important approaches for commercial products. Companies use a lot of GSM chip in devices and the possibility for the user to indicate the SSID and password of the router to connect products to the internet.

NOTE: In our commercial products, we use “ThingerTinyGSM.h” and “ThingerWebConfig.h” .

Thank you (@alvarolb ) for the excellent work you are doing

alvarolb · August 30, 2021, 12:51pm

Hi @George_Santiago,

The TinyGSM and ThingerWebConfig, should support OTA. Did you tried something like:

#define THINGER_SERIAL_DEBUG

// Requires WifiManager from Library Manager or https://github.com/tzapu/WiFiManager
#include <ThingerWebConfig.h>
#include <ThingerESP8266OTA.h>

ThingerWebConfig thing;
ThingerESP8266OTA ota(thing);

void setup() {
  // open serial for debugging
  Serial.begin(115200);

  pinMode(LED_BUILTIN, OUTPUT);

  // digital pin control example (i.e. turning on/off a light, a relay, configuring a parameter, etc)
  thing["led"] << digitalPin(LED_BUILTIN);

  // resource output example (i.e. reading a sensor value)
  thing["millis"] >> outputValue(millis());

  /*
    Steps for getting the ESP8266 WebConfig working:
    1. Connect to Thinger-Device WiFi with your computer or phone, using thinger.io as WiFi password
    2. Wait for the configuration window, or navigate to http://192.168.4.1 if it does not appear
    3. Configure the wifi where the ESP8266 will be connected, and your thinger.io device credentials
    4. Your device should be now connected to the platform.
    More details at http://docs.thinger.io/arduino/
  */
}

void loop() {
  thing.handle();
}

We will be improving OTA support in the next months. This is a first step where we can evaluate the functionality and performance. Later we will include OTA updates for a fleet of devices, so we will have to integrate other mechanishm for handling firmware version.

M.E · September 6, 2021, 5:51pm

Hello,
I’m trying to connect my MKR1010 through this library but it doesn’t work. I don’t get any errors, but there is no connection in the device list in the platform. I don’t know what the problem is. I got the code from the library example(see below)
SSL certificate and firmware update are done.
would be very nice if you share your idea. Thanks

ega · September 6, 2021, 7:52pm

Hi,

Write at the very first line #define _DEBUG_ and paste the serial console here, as a code please (select all what you want to show as code and press the "</> " button at the toolbar), not a print screen, to make easy for us to read it.

Regards,

M.E · September 6, 2021, 8:17pm

Hi ega,
thank you for your feedback and tip. What I unfortunately overlooked are the messages in Serial Console. As I can see, the device cannot connect to the Internet. This is strange to me because I connected my Raspberry Pi to the Thniger.io via the same internet.
Unbenannt

Do you have any idea why is it like this?

bests

ega · September 6, 2021, 8:37pm

Hi,

The issue is the at the wifi connection, check the parameters and try again, and read carefully my previous answer before posting again.

Regards,

Edwin_Lima · April 4, 2023, 8:21am

It continues with the same problem, I have the idea that some modification in the libraries started with this problem, everything was going well with the connection, until I tried to migrate to ESP32 and from then on I made several changes but I already tried everything but still continue offline.

ega · April 4, 2023, 3:23pm

Hi,

I recommend you to add the #define _DEBUG_ line before thinger’s library is declared and watch the serial console output to see what is happening, I use the esp32 and it works flawlessly with the 2.25.2 library.

Hope this helps