Hostname Resolution Error

F1zzyD commented 2 weeks ago

Govee Device SKU

N/A

Govee2MQTT Version

Latest

Describe the issue

I am running govee2mqtt in a docker alongside hass core and mosquitto. Mosquitto and hass boot up fine and so does govee2mqtt... except after the 10 second delay it throws a huge block of text and the error "Hostname resolution error: Try again". I've spent three hours double checking everything and my credentials are correct, but govee2mqtt refuses to work. However, I am able to get MQTT installed through the Hass UI and it sees mosquitto at 127.0.0.1:1883

I'm attaching the log from govee2mqtt, the compose.yml, and the mosquitto.conf for reference.

Startup Diagnostics

log.txt

Additional Logs

No response

Home Assistant Logs

N/A

Anything else?

compose.txt mosquitto.txt

wez commented 2 weeks ago

Since network_mode=host, I don't think docker's DNS magic is applicable and you should probably set MQTT_BROKER=127.0.0.1

F1zzyD commented 2 weeks ago

I just changed MQTT_BROKER to 127.0.0.1 and I'm still getting "Hostname resolution error: Try again". That didn't seem to do anything.

HASS Core accepts MQTT being set to 127.0.0.1 and I see the Govee integration pop up, but it refuses to make any sort of connection.

From: Wez Furlong @.> Sent: Wednesday, June 12, 2024 8:53:06 AM To: wez/govee2mqtt @.> Cc: F1zzyD @.>; Author @.> Subject: Re: [wez/govee2mqtt] Hostname Resolution Error (Issue #217)

Since network_mode=host, I don't think docker's DNS magic is applicable and you should probably set MQTT_BROKER=127.0.0.1

— Reply to this email directly, view it on GitHubhttps://github.com/wez/govee2mqtt/issues/217#issuecomment-2163069991, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AWWKU4Q7SCEODDJPJGLOYVTZHBHEFAVCNFSM6AAAAABJF3MGVCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRTGA3DSOJZGE. You are receiving this because you authored the thread.Message ID: @.***>

F1zzyD commented 2 weeks ago

I did some more tinkering and now I have more errors than I did before. I went back and redid everything outlined in the main guide for docker and I'm finding several inconsistencies/conflicting instructions:

Step 5 has me make the default network as mqtt5-network, however when moving forward with 5.1 we delete this and change it to caddy-mqtt. Which is it?
I have my own domain through Cloudfare. Do I need to follow step 5.1? If so...
The step for DNS Setup does not tell us were to put the code mqtt.domain.com A <public-IP-address-for-MQTT-instance>. Where am I supposed to put this?
When running with docker compose up, I get this warning in the logs: {"level":"warn","ts":1718217729.2704155,"msg":"Caddyfile input is not formatted; run 'caddy fmt --overwrite' to fix inconsistencies","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":2}. This is from when I copied and pasted the code included in "Content of configuration file called 'Caddyfile'. I also tried using my domain and switching to https:// like the logs told me to do with no success.

I've included the full log from caddy here and my updated compose.yml. I am still getting "Hostname resolution error: Try again" from govee2mqtt as well.

compose.txt log.txt

wez commented 2 weeks ago

Troubleshooting your caddy, cloudflare and docker installation is out of scope for me; sorry, but you'll need to continue on your own.

wez / govee2mqtt