From d220c19a36e8083b2123f4e9bdd38ecd31c19e03 Mon Sep 17 00:00:00 2001
From: Sam Reed <sam@reedyboy.net>
Date: Tue, 18 Oct 2022 17:05:06 +0100
Subject: [PATCH] emoncms.markdown: Fix initial example (#24609)

---
 source/_integrations/emoncms.markdown | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/source/_integrations/emoncms.markdown b/source/_integrations/emoncms.markdown
index 2883a7e4417..0de4be95c8d 100644
--- a/source/_integrations/emoncms.markdown
+++ b/source/_integrations/emoncms.markdown
@@ -20,10 +20,10 @@ To enable this sensor, add the following lines to your `configuration.yaml`, it
 ```yaml
 # Example configuration.yaml entry using cloud based Emoncms
 sensor:
-  platform: emoncms
-  api_key: API_KEY
-  url: https://emoncms.org
-  id: 1
+  - platform: emoncms
+    api_key: API_KEY
+    url: https://emoncms.org
+    id: 1
 ```
 
 As of Feb 2020, the integration will discover all sensors from Emoncms and will use the unit of measurement specified in the Feed from Emoncms, in preference to the one set in the configuration. Tested with [Emoncms](https://github.com/emoncms/emoncms) V10.1.13 - `unit` was added to the API around version V9.9.1.