Saltar al contenido principal

MQTT connect failure

Comentarios

12 comentarios

  • Tim Beaulieu

    Hi @Dewy,

    To start with it might be worth upgrading to firmware 14.3 to see if that fixes the issues that you're running into. If that doesn't work can you grab a backup.tar file of the device from eBuddy with the support files included and send those over to me?

    -Tim

     

     

    0
  • Dewy

    Hi Tim,

    I've updated the firmware version, but I still got the MQTT failure.

    Can you find anything in the support files?

    MOVED TO STAFF NOTE (182 KB) This text will be hidden

    0
  • tedsch

    Anything in the real time logs? They would show the step by step of the mqtt connection since the logging is turned on.

    0
  • Dewy

    @Tim_hms,
    Do you have feedback for mee? Our client is out of operation.

     

     

    0
  • Dewy

    Hi Ted,
    The realtime logs show the following steps when I re-run the basic-id script:

    I can't really find anything that I can related the MQTT issue with. Do you have any advice?

    0
  • tedsch

    Can you check the basics?

    When does the CA.crt expire and is it still on the device?

    Is the device still setup on the IOT Hub?

    0
  • Dewy

    Hi @Tim_hms,

    The eWON is sending the MQTT message again and is working as it should be.
    In the end we found out that there were no more security certificates and bas file in the usr folder of the eWON Flexy 205. After putting back those files the eWON was working properly again.

    That brings me to the next question, is it possible that after a power loss the eWON somehow deletes these files from the devices?

     

     

    0
  • Dewy

    The CA.crt files where indeed not anymore in the usr file of the ewon. How they got removed from the device is still unclear to me.

    0
  • Tim Beaulieu

    Hi @Dewy,

    Sorry for the delay, it's been pretty busy the last few days with meetings and calls. The Ewon should not be deleting any files on its own, but if this happens again please let me know and I'll report this to the dev team.

    Are you doing any deleting in your scripting sections by any chance?

    -Tim

     

     

    0
  • Dewy

    We delete the "+ timezone_offset%" on line 159 of the script. But this doesnt have anything to do with this issue i think?

    0
  • Tim Beaulieu

    That shouldn't be an issue if you're not deleting files

    0
  • Tim Beaulieu

    Hi @Dewy,

    I'm going to close this ticket out for now, but if it happens again you can still comment on this ticket. Please let me know if you run into the same issue again.

    -Tim

     

     

    0

Iniciar sesión para dejar un comentario.