diff --git a/source/_integrations/mqtt.markdown b/source/_integrations/mqtt.markdown
index 2292a2ed6c7..e25a0f14dae 100644
--- a/source/_integrations/mqtt.markdown
+++ b/source/_integrations/mqtt.markdown
@@ -138,6 +138,7 @@ MQTT Devices and entities can be set up through [MQTT -discovery](#mqtt-discover
 - [Siren](/integrations/siren.mqtt/)
 - [Switch](/integrations/switch.mqtt/)
 - [Text](/integrations/text.mqtt/)
+- [Valve](/integrations/valve.mqtt/)
 
 To add an MQTT device via a Subentry, follow these steps:
 
diff --git a/source/_integrations/valve.mqtt.markdown b/source/_integrations/valve.mqtt.markdown
index 0926cd4d467..03a7a801736 100644
--- a/source/_integrations/valve.mqtt.markdown
+++ b/source/_integrations/valve.mqtt.markdown
@@ -18,7 +18,7 @@ A valve entity can be have the following states: `open`, `opening`, `closed` or
 
 If a `state_topic` is configured, the entity's state will be updated only after an MQTT message is received on `state_topic` matching `state_open`, `state_opening`, `state_closed` or `state_closing`. Commands configured through `payload_open`, `payload_closed`, and `payload_stop` will be published to `command_topic` to control the valve.
 
-To use an MQTT valve in your installation, add the following to your {% term "`configuration.yaml`" %} file.
+To use an MQTT valve in your installation, [add an MQTT device as a subentry](/integrations/mqtt/#configuration), or add the following to your {% term "`configuration.yaml`" %} file.
 {% include integrations/restart_ha_after_config_inclusion.md %}
 
 ```yaml