Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


  • 0

Errorcode 2 is what??? when Net.FTcpSocket is used


Question

Posted

I stil have continuing problems with this errorcode = 2, LUA code is like this:


Please login or register to see this code.

And result is an email everytime I get into problemes with transmitting, and it is frequent:

Please login or register to see this code.

Translated: "Trial x was unsucessfull to transmit "SIIRADIO", returncode = 2"

 

It would be great if someone could give any clues to WHY this is happening and WHAT errorcode = 2 is...

6 answers to this question

Recommended Posts

  • 0
  • Inquirer
  • Posted

    Not funny, just changed to latest beta fw 4.056, and stil the same errorcode. No difference what so ever and not a single word from Fibaro??????

    • 0
    Posted

    It is generic code that means socket had problems with making connection to desired address, no specific reason given.

    • 0
  • Inquirer
  • Posted

    Okay, thanks for the answeer. I think there might be a challenge then when two (or more) sockets try to use the same target IP... It feeks like I can not have more than one open IP socket against one IP adress....?

    • 0
    Posted

    To honest I have not tried that before. Let us know how it went and what was the solution.

    • 0
  • Inquirer
  • Posted

    I am on latest BETA (4.063) and I still have this exact same crappy behavior. I think Fibaro has missed something in the implementation since I have never had this before Fibaro HC2 - I just have it with HC2.

     

    I'm about ready to give up on FW4 - let's wait for FW5 and a couple of more years of "user beta testing".

    • 0
    Posted

    Did you already tried to set a higher timeout?

     

    tcpSocket:setReadTimeout(50) this is really short....

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Answer this question...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×
    ×
    • Create New...