From 68a35bb6418b714e3ac031b12479ec4f9a9928fd Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Mon, 1 Feb 2016 23:25:44 +0100 Subject: [PATCH] Minor update --- source/developers/add_new_platform.markdown | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/source/developers/add_new_platform.markdown b/source/developers/add_new_platform.markdown index d1d3c540046..91f5b6b49aa 100644 --- a/source/developers/add_new_platform.markdown +++ b/source/developers/add_new_platform.markdown @@ -11,13 +11,7 @@ footer: true Components that interact with devices are structured in core- and platform logic. This allows the same logic to be used for different platforms. -For example, the built-in `switch` component consists of the following files in [`homeassistant/components/switch/`](https://github.com/balloob/home-assistant/tree/master/homeassistant/components/switch): - -| File | Description | -| ---- | ----------- | -| \_\_init\_\_.py | Contains the Switch core logic.| -| wemo.py | WeMo platform logic. Included if in config `platform=wemo`. | -| tellstick.py | Tellstick platform logic. Included if in config `platform=tellstick`. | +For example, the built-in `switch` component consists of various platform in [`homeassistant/components/switch/`](https://github.com/balloob/home-assistant/tree/master/homeassistant/components/switch). The file `\_\_init\_\_.py` contains the core logic of all platform and the `vendor_name.py` files only the relevant platform code. If you are planning to add support for a new type of device to an existing component, you can get away with only writing platform logic. Have a look at how the component works with other platforms and create a similar file for the platform that you would like to add.