Skip to content
This repository has been archived by the owner on Dec 29, 2024. It is now read-only.

Docker container will not start if wf_host is populated with something other than 0.0.0.0 #248

Open
codemannh opened this issue Feb 6, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@codemannh
Copy link

Home Assistant Version?

2024.1.6

Add-On or Self Hosted?

Self managed Container

Weatherflow2MQTT version?

3.2.2

What happened?

I've been using Weatherflow2mqtt into HomeAssistant for well over a year. I have been segmenting my network and moved my HomeAssistant host to a new VLAN. Currently just to get everything working I am allowing all traffic between the 2 subnets. There has been no change to the Weatherflow hub. I added the hub address into the docker-compose based on the documentation and the docker container will just continually restart and not run. If I change the entry in docker-compose back to 0.0.0.0 the container starts, but can't get to the weather info from the hub as it is on a different network.
Is there a need for quotes or is there some other issue I need to address to get the container to start and get weather data?

Relevant log output

No response

@codemannh codemannh added the bug Something isn't working label Feb 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant