Replies: 1 comment
-
Seriously, posting your email and password in your YAML config is not wise. And you're giving away your API key... wow. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Help:
wyze-bridge
in Docker w/ Tailscale getsIOTC_ER_TIMEOUT
on macOSGoal:
I'm trying to run
docker-wyze-bridge
to get my Wyze cameras into HomeKit. My setup involves running the bridge in a Docker container on a Mac, with a sidecar Tailscale container for remote access.My Environment:
The Problem:
After a lot of troubleshooting, I have a stable setup where:
tailscale
container starts, gets a permanent IP address, and successfully accepts the route to my home LAN (192.168.1.0/24
).wyze-bridge
container starts, successfully logs into my Wyze account, and fetches the correct list of my cameras.However, when
wyze-bridge
tries to connect to the cameras at their local IP addresses (e.g.,192.168.1.155
), the connection fails with the error:[-13] IOTC_ER_TIMEOUT
. This results in "preview not available" in the web UI.Final
docker-compose.yml
Configuration:This is the final configuration file we landed on, which solves the Tailscale persistence issues.
Troubleshooting Steps Taken:
I've confirmed the following:
✅ Wyze Credentials: The email, password, and API keys are correct, as proven by the fact that wyze-bridge successfully fetches the camera list from the Wyze API.
✅ Tailscale Persistence: The container now keeps the same IP address (100.98.139.85) after restarts (docker-compose down && up).
✅ Subnet Routing (Host): The native Tailscale client on my Mac is running and successfully advertising the 192.168.1.0/24 route.
✅ Subnet Routing (Container): The Docker container is successfully accepting the route (confirmed in the logs).
✅ macOS Firewall: The firewall on my Mac is completely disabled.
✅ Router Firewall: The Verizon router's firewall is set to "Low Security" (the lowest setting), and "AP/Client Isolation" is disabled. DNS Rebind protection is also disabled.
✅ Camera Status: The cameras are online and viewable in the native Wyze mobile app.
Even with all of this correctly configured, the connection from the container to the camera's local IP still times out. This seems to be a very specific networking issue between Docker for Mac, Tailscale's network_mode, and the local LAN.
Beta Was this translation helpful? Give feedback.
All reactions