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

API: Host not found (authoritative)


10der

Question

Hi!

 

Please login or register to see this code.

the issue  is directly linked to a losing HC2 internet (not local.net)

 

hey FIBARO, would there any chance to resolve host name>

Please login or register to see this code.

 

IMHO the problem was that the constructor for query has the address_configured flag set by default which won't return an address

if the loopback device is the only device with an address. By just settings flags to 0 or anything other than address_configured the problem is fixed.

 

please check your source code!

 

since the client cannot resolve the host (presumably because you cannot reach a resolver or DNS server because you're not connected to the network) then you're supposed to catch the exception and deal with it accordingly.

This looks like a Boost.Asio issue, which I think will only come up if you have a DNS server set up in your environment, but your network is down and thus the resolver cannot be reached.

PS: 

Please login or register to see this link.

Edited by 10der
Link to comment
Share on other sites

2 answers to this question

Recommended Posts

  • 0
3 hours ago, 10der said:

This looks like a Boost.Asio issue

 

not necessary, it might be something else as well, or both, or even more :\

 

 

  • Thanks 1
Link to comment
Share on other sites

  • 0

I am getting this in scenes that are not making any API calls at all.  And the frequency is increasing day by day.

 

As an example in a motion_based scene, the trigger from a motion sensor runs the scene, which checks its status and I get this fault.  Its not every day in that scene.  But when it happens, it fails on multiple devices in a window of a few minutes.  And then it starts to work again.

Please login or register to see this attachment.

Link to comment
Share on other sites

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...