Welcome to EnviroDIY, a community for do-it-yourself environmental science and monitoring. EnviroDIY is part of WikiWatershed, an initiative of Stroud Water Research Center designed to help people advance knowledge and stewardship of fresh water.
New to EnviroDIY? Start here

Reply To: DigiXBeeWifi class mqtt codeflow example

Home Forums Mayfly Data Logger DigiXBeeWifi class mqtt codeflow example Reply To: DigiXBeeWifi class mqtt codeflow example

#19624
Sabin
Participant

    Thank you for your response.
    I used TinyGSM directly and got into this problem. I was deploying broker locally,, the code on the inside check for dns lookup.. Currently I commented this code out and tinygsm works.
    https://github.com/issues/created?issue=vshymanskyy%7CTinyGSM%7C854

    This is what my full code looks without tinygsm:

    This is how I am implementing tinygsm

    Tinygsm implementation will result in flaky broker connection like this:
    1773954855: New client connected from 144.39.141.49:49164 as ArduinoTempSensor (p4, c1, k15). 1773954865: Client ArduinoTempSensor [144.39.141.49:49164] disconnected: connection closed by client. 1773954865: New connection from 144.39.141.49:49165 on port 1883. 1773954865: Protocol error from 144.39.141.49:49165: First packet not CONNECT (30). 1773954865: Client 144.39.141.49 [144.39.141.49:49165] disconnected: protocol error.