diff --git a/source/_components/sensor.enphase_envoy.markdown b/source/_components/sensor.enphase_envoy.markdown
index ec6d8002162..13c1b5924b3 100644
--- a/source/_components/sensor.enphase_envoy.markdown
+++ b/source/_components/sensor.enphase_envoy.markdown
@@ -13,7 +13,7 @@ ha_release: 0.76
 ha_iot_class: "Local Polling"
 ---
 
-A sensor platform for the [Enphase Envoy](https://enphase.com/en-us/products-and-services/envoy) solar energy monitor.
+A sensor platform for the [Enphase Envoy](https://enphase.com/en-us/products-and-services/envoy) solar energy gateway. Works with older models that only have production metrics (ie. Envoy-C) and newer models that offer both production and consumption metrics (ie. Envoy-S). 
 
 ### {% linkable_title Configuration %}
 
@@ -26,24 +26,24 @@ sensor:
 ```
 
 ```yaml
-# Example configuration.yaml entry
+# Example configuration.yaml entry, limiting the metrics to production only
 sensor:
   - platform: enphase_envoy
     ip_address: LOCAL_IP_FOR_ENVOY
     monitored_conditions:
       - production
-      - consumption
+      - daily_production
+      - seven_days_production
       - lifetime_production
-      - lifetime_consumption
 ```
 
 {% configuration %}
 ip_address:
-  description: The local IP Address of your Envoy. Leave blank to search for it, but this may not always be reliable.
+  description: The local IP address of your Envoy. Leave blank to use the default host name 'envoy', but this may not always be reliable. You should be able to just browse to this IP address.
   required: false
   type: string
 monitored_conditions:
-  description: The list of conditions to monitor.
+  description: The list of conditions to monitor. If you have an Envoy that doesn't support consumption metrics (ie. Envoy-C), it's best only configure the production metrics.
   required: false
   type: list
   keys: