LAN stack gives out its LAN address: dev-lan sets FRONTEND_HOST to the published port on the host's default-route address, so the Panels dialog links a screen somewhere it can reach instead of app.localhost

docs/interface/dashboards.md

@@ -409,8 +409,8 @@ access.
 
 The openpanel firmware, kept in its own repository, draws dashboards as native
 widgets on an ESP32-P4 wall panel (Waveshare ESP32-P4-WIFI6-Touch-LCD-7B,
-1024×600). Once its config page points it at this instance, it shows the
-pairing code itself; enter it as in step 4. It reads the same published
+1024×600). Once its config page points it at this instance (the dialog's link
+works too, the device keeps only its address), it shows the pairing code itself; enter it as in step 4. It reads the same published
 dashboards and live values and draws every widget type with two exceptions,
 both shown as a placeholder: a website tile that embeds a page (image tiles
 work), and a chart of runs, which a panel credential may not read. Media tiles
@@ -446,7 +446,8 @@ by the nodes that produce it.
 !!! note "If the local link is wrong"
 
     Pairing links use `FRONTEND_HOST`. Set it to the app address reachable
-    from the screen's network.
+    from the screen's network. `make dev-lan` sets it to the published port on
+    the host's LAN address.
 
 ### A screen somewhere you cannot reach