You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/guides/faq.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -534,13 +534,13 @@ services:
534
534
> in the [ESPHome Device Builder](/guides/getting_started_hassio#installing-esphome-device-builder). In order for this feature to work, you
535
535
> must either use Docker's [host](https://docs.docker.com/network/drivers/host/) networking mode or create [macvlan](https://docs.docker.com/engine/network/drivers/macvlan/)/[ipvlan](https://docs.docker.com/engine/network/drivers/ipvlan/) networks.
536
536
>
537
-
> The [host networking driver]() only works on Linux hosts; it is
537
+
> The host networking driver only works on Linux hosts; it is
538
538
> available on Docker Desktop version 4.29 and later.
539
539
>
540
540
> When working with multiple network interfaces, you can specify which interface the dashboard should bind to by setting the environment
541
541
> variable `DASHBOARD_LISTENING_NETWORK_INTERFACE`. This is particularly useful when using a reverse proxy: the dashboard can be exposed
542
-
> through the reverse proxy on one network while managing devices on another.
543
-
>
542
+
> through the reverse proxy on one network while device management take place on another one.
543
+
>
544
544
> If you cannot use docker any of those networking based solutions, you have to use an alternate method as described below.
545
545
>
546
546
> Note that mDNS might not work if your Home Assistant server and your ESPHome nodes are on different subnets
0 commit comments