-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
getaddrinfo ENOTFOUND f e80 #556
Comments
The plugin is attempting to contact a homebridge instance running on a host named ‘fe80’ and can’t find it. If you ask Alexa to discover devices it will update the device cache and it should resolve. also does your docker instances allow mdns ( port 5353 ) communication? |
I have no host called fe80 😬 I already check the hostnames etc… Were are the settings for mdns? |
There are no settings within the plugin for MDNS. Any MDNS setting for port 5353 would be within your docker config. I googled the name 'fe80' and it is related to IPV6, are you running an IPV4 or IPV6 environment ? Can you enable debug in the plugin config, and share the log from when the plugin starts up ? I should include alot of messages about Homebridge instance discovery. |
IPv6 is activated in my Fritzbox. Should I disable it? Here is my log after a restart: |
Removed incorrect log file |
That log did not contain any Alexa plugin debug messages, can you enable the debug option in the Alexa plugin config and share the log again ? You could try disabling ipv6 on the fritzbox as a test. If you do this, please restart the Alexa plugin as it cache's the instance details on startup, and refreshes every 15 minutes. |
Now with the alexa debug: [12/4/2022, 9:49:41 AM] [My FRITZ!Box] < getTemperature 15
[TuyaDiscovery] Discovery started on port 6666. |
IPv6 was deactivated in my Fritzbox. |
Tks for that log Am seeing these errors
Am thinking the usage if ipv6 in your setup is causing this. As a quick workaround could you disable ipv6 in your setup, while I do more testing with ipv6 to determine the root cause of this. |
You would disable it at the operating system level of the operating system hosting homebridge, and not the router. |
Homebridge runs in docker over portainer. I have a have problem: Few minutes ago this error message appears:
[12/2/2022, 8:39:11 AM] [Alexa] Power ontroller TurnOff BA: 4F: 96:40:34:E8 un defined Error: getaddrinfo ENOTFOUND f e80 at GetAddrInfoReqwrap.onlookup [as
oncomplete] (node:dns: 107:26) {
errno: -3008, code:
'ENOTFOUND'
syscall:
'getaddrinfo'
hostname:
'fe80
attempts: 5
It happens only, when I start a command over Alexa. Sometimes it works, sometimes not.
Every device will not work for few minutes and Alexa says: XXX is not reachable.
Please help me!
Latest version of Homebridge and the plug-in are installed. Node is up-to-date.
The text was updated successfully, but these errors were encountered: