@@ -152,0 +208,4 @@
+		return UplinkCase(
+			kind=Uplink(radio["uplink"]),
+			connection=connection if isinstance(connection, str) else None,
+			drops_uplink=bool(radio.get("drops_uplink")),

@@ -241,0 +301,4 @@
+	async def _async_update_data(self) -> Offered:
+		"""Ask what is cached and what installing it would cost."""
+		return Offered(
+			versions=await self._asked(self.client.async_offered_versions, {}),

@@ -1513,0 +1634,4 @@
+	assert uplink_shown(hass) == ("ethernet", False)
+
+
+async def test_the_pi_on_wifi_says_an_install_costs_the_connection(

@@ -189,0 +243,4 @@
+			return None
+		return {"update_drops_uplink": case.drops_uplink, "connection": case.connection}
+
+	async def async_added_to_hass(self) -> None:

@@ -117,6 +117,19 @@ the van's uplink could not reach, and an image offered but not fetched whole
 are each reported as themselves. The last two especially, because either one
 otherwise looks exactly like nothing new having been published.
 
+Beside the button is an uplink sensor, because an install can cost the very

@@ -189,0 +252,4 @@
+		# Nothing else would ask on a bus nothing announces on, and that is the
+		# van most likely to be updated. Asked for outright rather than
+		# requested: the debounced request would spend its immediate turn here
+		# and hold back the one an update entity makes as its node arrives.

@@ -351,0 +427,4 @@
+			asking.close()
+			return None
+		try:
+			return waiting.result(REPORT_TIMEOUT.total_seconds())

@@ -120,0 +123,4 @@
+traffic while that stands: `ethernet`, `wireless` or `none`. Whether it costs
+anything is `update_drops_uplink` beside it rather than the state, because only
+an uplink on the radio the access point wants has to come down — a wire, a
+second radio, and nothing at all all cost nothing. When one does come down,

@@ -109,6 +110,47 @@ class CheckOutcome:
 	failed: tuple[str, ...]
 
 
+class Uplink(StrEnum):

@@ -189,0 +256,4 @@
+		# Scheduled rather than awaited, because setting the entry up must not
+		# wait on the updater — a Pi restart brings both containers up at once,
+		# and one still starting has ten seconds to answer.
+		self.hass.async_create_task(

@@ -351,0 +428,4 @@
+			return None
+		try:
+			return waiting.result(REPORT_TIMEOUT.total_seconds())
+		except RadioError, TimeoutError, CancelledError: