From 6c632c959cf9f51bca209550bda6c6795e2faf1a Mon Sep 17 00:00:00 2001
From: Paulus Schoutsen <balloob@gmail.com>
Date: Mon, 27 Aug 2018 16:08:12 +0200
Subject: [PATCH] Update config_entries_config_flow_handler.md

---
 docs/config_entries_config_flow_handler.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/config_entries_config_flow_handler.md b/docs/config_entries_config_flow_handler.md
index 852a53f1..43fa0bb5 100644
--- a/docs/config_entries_config_flow_handler.md
+++ b/docs/config_entries_config_flow_handler.md
@@ -25,7 +25,8 @@ You might want to initialize a config flow programmatically. For example, if we
 
 ```python
 await hass.config_entries.flow.async_init(
-    'hue', source=data_entry_flow.SOURCE_DISCOVERY, data=discovery_info)
+    'hue', data=discovery_info,
+    context={'source': config_entries.SOURCE_DISCOVERY})
 ```
 
 The config flow handler will need to add a step to support the given source. The step should follow the same return values as a normal step.