diff --git a/.gitmodules b/.gitmodules index e590545c1cb..23f4fc92120 100644 --- a/.gitmodules +++ b/.gitmodules @@ -1,4 +1,4 @@ [submodule "_deploy"] path = _deploy - url = https://github.com/balloob/home-assistant.git - branch = gh-pages + url = https://github.com/home-assistant/home-assistant.git + branch = gh-pages diff --git a/README.markdown b/README.markdown index 3dc2d536518..4f5f2528c9c 100644 --- a/README.markdown +++ b/README.markdown @@ -1,10 +1,10 @@ # Home Assistant website -This is the source for the [Home-Assistant.io website](https://home-assistant.io) for the [Home Assistant project](https://github.com/balloob/home-assistant) +This is the source for the [Home-Assistant.io website](https://home-assistant.io) for the [Home Assistant project](https://github.com/home-assistant/home-assistant) ## Setup -Setting up to contribute to documentation and the process for submitting pull requests is [explained here](https://home-assistant.io/developers/website/). +Setting up to contribute to documentation and the process for submitting pull requests is [explained here](https://home-assistant.io/developers/website/). ## Create a new blog post diff --git a/source/_components/configurator.markdown b/source/_components/configurator.markdown index 44c594c9edb..3d9661d50bd 100644 --- a/source/_components/configurator.markdown +++ b/source/_components/configurator.markdown @@ -21,6 +21,6 @@ The configurator component allows components to request information from the use - Input fields can be defined with a description, and optional type - It will trigger a callback when the button is pressed -The Hue component in [the demo](/demo) and Plex are implemented using the configurator. See [the source of the demo component](https://github.com/balloob/home-assistant/blob/master/homeassistant/components/demo.py#L132) for a simple example. +The Hue component in [the demo](/demo) and Plex are implemented using the configurator. See [the source of the demo component](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/demo.py#L132) for a simple example. -See [the source](https://github.com/balloob/home-assistant/blob/master/homeassistant/components/configurator.py#L39) for more details on how to use the configurator component. +See [the source](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/configurator.py#L39) for more details on how to use the configurator component. diff --git a/source/_components/light.markdown b/source/_components/light.markdown index 56f078f65e3..c544d7d9af0 100644 --- a/source/_components/light.markdown +++ b/source/_components/light.markdown @@ -11,7 +11,7 @@ footer: true This component allows you to track and control various light bulbs. -It has [4 built-in light profiles](https://github.com/balloob/home-assistant/blob/master/homeassistant/components/light/light_profiles.csv) which you're able to extend by putting a `light_profiles.csv` file in your config dir. +It has [4 built-in light profiles](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/light/light_profiles.csv) which you're able to extend by putting a `light_profiles.csv` file in your config dir. Preferred way to setup the Philips Hue platform is through the [the discovery component]({{site_root}}/components/discovery/). For the Wink light platform enable [the wink component]({{site_root}}/components/wink/). diff --git a/source/_components/media_player.panasonic_viera.markdown b/source/_components/media_player.panasonic_viera.markdown index 6902988957f..744869cc2eb 100644 --- a/source/_components/media_player.panasonic_viera.markdown +++ b/source/_components/media_player.panasonic_viera.markdown @@ -18,7 +18,7 @@ Currently known supported models: - TX-P42STW50 -If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/balloob/home-assistant.io). +If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io). To add a TV to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/media_player.samsungtv.markdown b/source/_components/media_player.samsungtv.markdown index bcd63bcda47..273e96b6948 100644 --- a/source/_components/media_player.samsungtv.markdown +++ b/source/_components/media_player.samsungtv.markdown @@ -40,5 +40,5 @@ Currently known supported models: - ES6800 - F6500 -If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/balloob/home-assistant.io). +If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io). The two letters at the beginning of the model number represent the region, UE is Europe, UN is North America and UA is Asia & Australia. The two numbers following that represent the screen size. If you add your model remember to remove these before adding them to the list. diff --git a/source/_includes/custom/footer.html b/source/_includes/custom/footer.html index efc3c3c40a6..7123ee56fc6 100644 --- a/source/_includes/custom/footer.html +++ b/source/_includes/custom/footer.html @@ -1,6 +1,6 @@
- +
Website powered by Jekyll and the Oscalite theme.
diff --git a/source/_includes/edit_github.html b/source/_includes/edit_github.html index be883cf42a2..51600423fc3 100644 --- a/source/_includes/edit_github.html +++ b/source/_includes/edit_github.html @@ -1,3 +1,3 @@ {% if page.hide_github_edit != true %} -
Edit this page on GitHub
+
Edit this page on GitHub
{% endif %} \ No newline at end of file diff --git a/source/_posts/2015-02-24-streaming-updates.markdown b/source/_posts/2015-02-24-streaming-updates.markdown index 9353563a929..a6b2c071185 100644 --- a/source/_posts/2015-02-24-streaming-updates.markdown +++ b/source/_posts/2015-02-24-streaming-updates.markdown @@ -18,7 +18,7 @@ A new toggle has been added ot the sidebar to turn streaming updates on and off. -Streaming updates has been implemented using the HTML5 `EventSource` tag. Implementation is pretty straight forward as all the reconnection logic will be handled by the event source tag. The [server-side code](https://github.com/balloob/home-assistant/blob/master/homeassistant/components/api.py#L90) is 50 lines and the [client-side code](https://github.com/balloob/home-assistant-js/blob/master/src/actions/stream.js) is 80 lines of code. +Streaming updates has been implemented using the HTML5 `EventSource` tag. Implementation is pretty straight forward as all the reconnection logic will be handled by the event source tag. The [server-side code](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/api.py#L90) is 50 lines and the [client-side code](https://github.com/home-assistant/home-assistant-js/blob/master/src/actions/stream.js) is 80 lines of code. All events that happen on the server will now also be sent to the browser. This turns any browser running the UI into a fully functioning [slave instance](https://home-assistant.io/developers/architecture/#multiple-connected-instances) of Home Assistant. This opens up new possibilities for Home Assistant components that live completely client-side. diff --git a/source/_posts/2015-02-28-home-assistant-migrating-to-yaml.markdown b/source/_posts/2015-02-28-home-assistant-migrating-to-yaml.markdown index 0f216bba728..255f17db9e3 100644 --- a/source/_posts/2015-02-28-home-assistant-migrating-to-yaml.markdown +++ b/source/_posts/2015-02-28-home-assistant-migrating-to-yaml.markdown @@ -13,6 +13,6 @@ Home Assistant is now using [YAML](http://yaml.org/) for it's configuration file The new file is named configuration.yaml and if it can't be found in your config directory, Home Assistant will instead try to find the old configuration file, home-assistant.conf. -The home-assistant.conf.example has been replaced with an updated [configuration.yaml.example](https://github.com/balloob/home-assistant/blob/dev/config/configuration.yaml.example). +The home-assistant.conf.example has been replaced with an updated [configuration.yaml.example](https://github.com/home-assistant/home-assistant/blob/dev/config/configuration.yaml.example). Users of Home Assistant should migrate as the old configuration format is deprecated. diff --git a/source/_posts/2015-05-09-utc-time-zone-awareness.markdown b/source/_posts/2015-05-09-utc-time-zone-awareness.markdown index 0e5ebc7a771..f668fd693f3 100644 --- a/source/_posts/2015-05-09-utc-time-zone-awareness.markdown +++ b/source/_posts/2015-05-09-utc-time-zone-awareness.markdown @@ -12,7 +12,7 @@ categories: Release-Notes I have recently merged code to refactor Home Assistant to use only UTC times internally. A much needed refactor. I've added some extra test coverage to time sensitive parts to ensure stability. The code has been live in the dev branch for the last 9 days and will be soon released to the master branch. -From now on all internal communication will be done in UTC: time changed events, datetime attributes of states, etc. To get the current time in UTC you can call `homeassistant.util.dt.utcnow()`. This is a timezone aware UTC datetime object. [`homeassistant.util.dt`](https://github.com/balloob/home-assistant/blob/dev/homeassistant/util/dt.py) is a new util package with date helpers. +From now on all internal communication will be done in UTC: time changed events, datetime attributes of states, etc. To get the current time in UTC you can call `homeassistant.util.dt.utcnow()`. This is a timezone aware UTC datetime object. [`homeassistant.util.dt`](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/util/dt.py) is a new util package with date helpers. There is also such a thing as local time. Local time is based on the time zone that you have setup in your `configuration.yaml`. Local times should only be used for user facing information: logs, frontend and automation settings in `configuration.yaml`. diff --git a/source/_posts/2015-05-14-release-notes.markdown b/source/_posts/2015-05-14-release-notes.markdown index 180e76ba281..1b16ae2fa74 100644 --- a/source/_posts/2015-05-14-release-notes.markdown +++ b/source/_posts/2015-05-14-release-notes.markdown @@ -17,7 +17,7 @@ This release includes a significant startup boost for the frontend and a fix for I would like to give a big shout out to our newest contributor [fabaff](https://github.com/fabaff) for taking the time to improve the documentation.

-To update to the latest version, run scripts/update. Please report any issues on GitHub. +To update to the latest version, run scripts/update. Please report any issues on GitHub.

diff --git a/source/_posts/2015-06-10-release-notes.markdown b/source/_posts/2015-06-10-release-notes.markdown index 71c61162cf5..551a199f485 100644 --- a/source/_posts/2015-06-10-release-notes.markdown +++ b/source/_posts/2015-06-10-release-notes.markdown @@ -21,7 +21,7 @@ A big improvement has been brought this release by wind-rider. He took the time

-To update to the latest version, run scripts/update. Please report any issues on GitHub. +To update to the latest version, run scripts/update. Please report any issues on GitHub.

diff --git a/source/_posts/2015-07-11-ip-cameras-arduino-kodi-efergy-support.markdown b/source/_posts/2015-07-11-ip-cameras-arduino-kodi-efergy-support.markdown index 50a598d67ba..b192d9b9bbd 100644 --- a/source/_posts/2015-07-11-ip-cameras-arduino-kodi-efergy-support.markdown +++ b/source/_posts/2015-07-11-ip-cameras-arduino-kodi-efergy-support.markdown @@ -30,7 +30,7 @@ camera: ```

-To update to the latest version, run scripts/update. Please report any issues on GitHub. +To update to the latest version, run scripts/update. Please report any issues on GitHub.

diff --git a/source/_posts/2015-08-09-mqtt-raspberry-pi-squeezebox-asuswrt-support.markdown b/source/_posts/2015-08-09-mqtt-raspberry-pi-squeezebox-asuswrt-support.markdown index 65220a86734..719e9981444 100644 --- a/source/_posts/2015-08-09-mqtt-raspberry-pi-squeezebox-asuswrt-support.markdown +++ b/source/_posts/2015-08-09-mqtt-raspberry-pi-squeezebox-asuswrt-support.markdown @@ -10,12 +10,12 @@ comments: true categories: Release-Notes --- -It's time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to [@balloob](https://github.com/balloob). If you're a developer, make sure you read up on [the deprecation notices](https://github.com/balloob/home-assistant/pull/251). [@fabaff](https://github.com/fabaff) did another great round of documentating all the various components. +It's time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to [@balloob](https://github.com/balloob). If you're a developer, make sure you read up on [the deprecation notices](https://github.com/home-assistant/home-assistant/pull/251). [@fabaff](https://github.com/fabaff) did another great round of documentating all the various components. __MQTT Support__ The big new addition in this release is the support for the MQTT protocol by [@fabaff](https://github.com/fabaff) with some help from [@balloob](https://github.com/balloob). It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics ([see the example][mqtt-example]) and also support for the automation component [has been added][mqtt-automation]. For more information, see [the MQTT component page][mqtt-component]. -[mqtt-example]: https://github.com/balloob/home-assistant/blob/dev/config/custom_components/mqtt_example.py +[mqtt-example]: https://github.com/home-assistant/home-assistant/blob/dev/config/custom_components/mqtt_example.py [mqtt-automation]: /components/automation/#mqtt-based-automation [mqtt-component]: /components/mqtt/ diff --git a/source/_posts/2015-09-18-monitoring-with-glances-and-home-assistant.markdown b/source/_posts/2015-09-18-monitoring-with-glances-and-home-assistant.markdown index a5f79670f6d..9e6b903c4c6 100644 --- a/source/_posts/2015-09-18-monitoring-with-glances-and-home-assistant.markdown +++ b/source/_posts/2015-09-18-monitoring-with-glances-and-home-assistant.markdown @@ -11,7 +11,7 @@ og_image: /images/supported_brands/glances.png --- -Inspried by a [feature requests](https://github.com/balloob/home-assistant/issues/310) I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the [systemmonitor](/components/sensor.systemmonitor/) sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present. +Inspried by a [feature requests](https://github.com/home-assistant/home-assistant/issues/310) I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the [systemmonitor](/components/sensor.systemmonitor/) sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present. @@ -75,4 +75,4 @@ If there are no error in the log file then you should see your new sensors. The Glances sensors

-[Glances](https://github.com/nicolargo/glances) has a couple of optional dependencies which are extenting the range of provided information. This means that it would be possible to get details about the RAID system, HDD temperature, IP addresses, sensors, etc., please create a [Pull request](https://github.com/balloob/home-assistant/pulls) with your additions or a [Feature request](https://github.com/balloob/home-assistant/issues/new) if you want see more details in your Home Assistant frontend. +[Glances](https://github.com/nicolargo/glances) has a couple of optional dependencies which are extenting the range of provided information. This means that it would be possible to get details about the RAID system, HDD temperature, IP addresses, sensors, etc., please create a [Pull request](https://github.com/home-assistant/home-assistant/pulls) with your additions or a [Feature request](https://github.com/home-assistant/home-assistant/issues/new) if you want see more details in your Home Assistant frontend. diff --git a/source/_posts/2015-09-19-alarm-sonos-and-itunes-support.markdown b/source/_posts/2015-09-19-alarm-sonos-and-itunes-support.markdown index 4bb71289457..94e2d8fae5d 100644 --- a/source/_posts/2015-09-19-alarm-sonos-and-itunes-support.markdown +++ b/source/_posts/2015-09-19-alarm-sonos-and-itunes-support.markdown @@ -12,7 +12,7 @@ categories: Release-Notes It's like someone opened a can of rock solid developers and emptied it above our [chat channel](https://gitter.im/balloob/home-assistant) because it exploded with great conversations and solid contributions. Featured in release 0.7.3: Sonos, iTunes, Alarm component and Automation upgrade. -See [GitHub](https://github.com/balloob/home-assistant/releases/tag/0.7.3) for more detailed release notes. +See [GitHub](https://github.com/home-assistant/home-assistant/releases/tag/0.7.3) for more detailed release notes. _Migration note: the `scheduler` component has been removed in favor of the `automation` component._ diff --git a/source/_posts/2016-01-17-extended-support-for-diy-solutions.markdown b/source/_posts/2016-01-17-extended-support-for-diy-solutions.markdown index a439256b957..3699f1bc5eb 100644 --- a/source/_posts/2016-01-17-extended-support-for-diy-solutions.markdown +++ b/source/_posts/2016-01-17-extended-support-for-diy-solutions.markdown @@ -12,8 +12,8 @@ categories: Release-Notes First release of 2016 and we are on 🔥! The [main repository][github-ha] has passed 2500 ⭐ on GitHub (2596 ⭐ as of now). This release also has a [record number][release-pr] of 20 contributors all working on improving and extending Home Assistant. With the continued growth, I am very excited to see what 2016 will bring us 🤘. -[github-ha]: https://github.com/balloob/home-assistant/ -[release-pr]: https://github.com/balloob/home-assistant/pull/883#partial-users-participants +[github-ha]: https://github.com/home-assistant/home-assistant/ +[release-pr]: https://github.com/home-assistant/home-assistant/pull/883#partial-users-participants diff --git a/source/_posts/2016-04-07-static-website.markdown b/source/_posts/2016-04-07-static-website.markdown index 5ec90e23a82..9e81ef881fe 100644 --- a/source/_posts/2016-04-07-static-website.markdown +++ b/source/_posts/2016-04-07-static-website.markdown @@ -21,7 +21,7 @@ But there is more you can do! You can not only host images for customization the -In the past the buzz word "Smart mirror" was used a couple of times in our [chatroom](https://gitter.im/balloob/home-assistant) and even made it into the [issue tracker](https://github.com/balloob/home-assistant/issues/1392). The existing solutions ([Smart mirror](http://docs.smart-mirror.io/), [MagicMirror](http://michaelteeuw.nl/tagged/magicmirror), and [HomeMirror](https://github.com/HannahMitt/HomeMirror)) seems to be overkill if you already have Home Assistant running somewhere in your house or apartment. Why not simple display a web page served by Home Assistant on the tablet? No app and no Raspberry Pi running in the background. +In the past the buzz word "Smart mirror" was used a couple of times in our [chatroom](https://gitter.im/balloob/home-assistant) and even made it into the [issue tracker](https://github.com/home-assistant/home-assistant/issues/1392). The existing solutions ([Smart mirror](http://docs.smart-mirror.io/), [MagicMirror](http://michaelteeuw.nl/tagged/magicmirror), and [HomeMirror](https://github.com/HannahMitt/HomeMirror)) seems to be overkill if you already have Home Assistant running somewhere in your house or apartment. Why not simple display a web page served by Home Assistant on the tablet? No app and no Raspberry Pi running in the background. There are plenty of ways to achieve this...[RESTful API](/developers/rest_api/), [Python API](/developers/python_api/), or one of the [history components](/components/#history). If it is to be a web page I'm using the [MQTT Eventstream component](/components/mqtt_eventstream/) and [mqttws31.js](http://git.eclipse.org/c/paho/org.eclipse.paho.mqtt.javascript.git/tree/src). diff --git a/source/cookbook/index.markdown b/source/cookbook/index.markdown index 61990b01be9..033156e1ce5 100644 --- a/source/cookbook/index.markdown +++ b/source/cookbook/index.markdown @@ -17,7 +17,7 @@ This is a community curated list of different ways to use Home Assistant. Most o [sec-automation]: /components/#automation [organization]: /components/#organization -New recipes can be added via the [home-assistant.io repository](https://github.com/balloob/home-assistant.io/tree/master/source/_cookbook). +New recipes can be added via the [home-assistant.io repository](https://github.com/home-assistant/home-assistant.io/tree/master/source/_cookbook). {% assign cookbook = site.cookbook | sort: 'title' %} {% assign categories = cookbook | map: 'ha_category' | uniq | sort %} diff --git a/source/developers/add_new_platform.markdown b/source/developers/add_new_platform.markdown index ffe7dafdd38..439fdadfa60 100644 --- a/source/developers/add_new_platform.markdown +++ b/source/developers/add_new_platform.markdown @@ -11,7 +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 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. +For example, the built-in `switch` component consists of various platform in [`homeassistant/components/switch/`](https://github.com/home-assistant/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. @@ -30,7 +30,7 @@ DEPENDENCIES = ['mqtt'] -Entities are Home Assistant's representation of lights, switches, sensors, etc. and are derived from the [Entity Abstract Class](https://github.com/balloob/home-assistant/blob/master/homeassistant/helpers/entity.py). This abstract class contains logic for integrating most standard features into your entities, such as visibility, entity IDs, updates, and many more. +Entities are Home Assistant's representation of lights, switches, sensors, etc. and are derived from the [Entity Abstract Class](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/helpers/entity.py). This abstract class contains logic for integrating most standard features into your entities, such as visibility, entity IDs, updates, and many more. This example is for adding support for the imaginary Awesome Lights. @@ -105,7 +105,7 @@ Home Assistant has a discovery service running in the background to discover new ### {% linkable_title Add discovery instructions %} -Device discovery for Home Assistant has been extracted into an external library called [NetDisco](https://github.com/balloob/netdisco). This library is integrated using [the `discovery` component](https://github.com/balloob/home-assistant/blob/dev/homeassistant/components/discovery.py) and scans the network in intervals for uPnP and zeroconf/mDNS services. +Device discovery for Home Assistant has been extracted into an external library called [NetDisco](https://github.com/balloob/netdisco). This library is integrated using [the `discovery` component](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/discovery.py) and scans the network in intervals for uPnP and zeroconf/mDNS services. To have your device be discovered, you will have to extend the NetDisco library to be able to find your device. This is done by adding a new discoverable. [See the repository for examples of existing discoverables.](https://github.com/balloob/netdisco/tree/master/netdisco/discoverables) @@ -129,7 +129,7 @@ def setup(hass, config): ### {% linkable_title Auto-loading your component upon discovery %} -The Discovery component is capable of setting up your components before firing the `SERVICE_DISCOVERD` event. To do this you will have to update the [`SERVICE_HANDLERS`](https://github.com/balloob/home-assistant/blob/dev/homeassistant/components/discovery.py#L29) constant in [the `discovery` component](https://github.com/balloob/home-assistant/blob/dev/homeassistant/components/discovery.py). +The Discovery component is capable of setting up your components before firing the `SERVICE_DISCOVERD` event. To do this you will have to update the [`SERVICE_HANDLERS`](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/discovery.py#L29) constant in [the `discovery` component](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/discovery.py).

This option is currently limited to built-in components. diff --git a/source/developers/architecture.markdown b/source/developers/architecture.markdown index e457e5d8e9e..7da43611436 100644 --- a/source/developers/architecture.markdown +++ b/source/developers/architecture.markdown @@ -75,7 +75,7 @@ For example the [`device_sun_light_trigger` component](/components/device_sun_li Turn on the lights ``` -An extended example of a home automation component can be found [here](https://github.com/balloob/home-assistant/blob/master/config/custom_components/example.py). +An extended example of a home automation component can be found [here](https://github.com/home-assistant/home-assistant/blob/master/config/custom_components/example.py). ### {% linkable_title The full picture %} diff --git a/source/developers/creating_components.markdown b/source/developers/creating_components.markdown index db00d1fb8b1..7dc8478925a 100644 --- a/source/developers/creating_components.markdown +++ b/source/developers/creating_components.markdown @@ -9,9 +9,9 @@ sharing: true footer: true --- -Home Assistant offers [built-in components]({{site_root}}/components/) but it is easy to build your own. If you are the kind of person that likes to learn from code rather then guide then head over to the [`config/custom_components`](https://github.com/balloob/home-assistant/tree/master/config/custom_components) folder in the repository for two example components. Or visit the [Custom Python Component Examples]({{site_root}}/cookbook/#custom-python-component-examples). +Home Assistant offers [built-in components]({{site_root}}/components/) but it is easy to build your own. If you are the kind of person that likes to learn from code rather then guide then head over to the [`config/custom_components`](https://github.com/home-assistant/home-assistant/tree/master/config/custom_components) folder in the repository for two example components. Or visit the [Custom Python Component Examples]({{site_root}}/cookbook/#custom-python-component-examples). -The first is [hello_world.py](https://github.com/balloob/home-assistant/blob/master/config/custom_components/hello_world.py) (this is similar to the [Basic State Setting Example](https://home-assistant.io/cookbook/python_component_basic_state/)), which is the classic "Hello World" example for Home Assistant. The second one is [example.py](https://github.com/balloob/home-assistant/blob/master/config/custom_components/example.py) which showcases various ways you can tap into Home Assistant to be notified when certain events occur. +The first is [hello_world.py](https://github.com/home-assistant/home-assistant/blob/master/config/custom_components/hello_world.py) (this is similar to the [Basic State Setting Example](https://home-assistant.io/cookbook/python_component_basic_state/)), which is the classic "Hello World" example for Home Assistant. The second one is [example.py](https://github.com/home-assistant/home-assistant/blob/master/config/custom_components/example.py) which showcases various ways you can tap into Home Assistant to be notified when certain events occur. If you want to load these components in Home Assistant, add the following lines to your `configuration.yaml` file: @@ -59,10 +59,10 @@ The Home Assistant instance contains three objects to help you interact with the | Object | Description | | ------ | ----------- | -| `hass.config` | This is the core configuration of Home Assistant exposing location, temperature preferences and config directory path. [Details](https://github.com/balloob/home-assistant/blob/dev/homeassistant/core.py#L687) -| `hass.states` | This is the StateMachine. It allows you to set states and track when they are changed. [See available methods](https://github.com/balloob/home-assistant/blob/dev/homeassistant/core.py#L434). | -| `hass.bus` | This is the EventBus. It allows you to trigger and listen for events.
[See available methods](https://github.com/balloob/home-assistant/blob/dev/homeassistant/core.py#L229). | -| `hass.services` | This is the ServiceRegistry. It allows you to register services.
[See available methods](https://github.com/balloob/home-assistant/blob/dev/homeassistant/core.py#L568). | +| `hass.config` | This is the core configuration of Home Assistant exposing location, temperature preferences and config directory path. [Details](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/core.py#L687) +| `hass.states` | This is the StateMachine. It allows you to set states and track when they are changed. [See available methods](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/core.py#L434). | +| `hass.bus` | This is the EventBus. It allows you to trigger and listen for events.
[See available methods](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/core.py#L229). | +| `hass.services` | This is the ServiceRegistry. It allows you to register services.
[See available methods](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/core.py#L568). | ### {% linkable_title `config`: User given configuration. %} @@ -79,4 +79,4 @@ Then in the setup method of your component you will be able to refer to `config[ ## {% linkable_title Responding to events %} -Home Assistant has different ways of responding to events that occur in Home Assistant. These have been organized in [helper methods](https://github.com/balloob/home-assistant/blob/dev/homeassistant/helpers/event.py). Examples are `track_state_change`, `track_point_in_time`, `track_time_change`. +Home Assistant has different ways of responding to events that occur in Home Assistant. These have been organized in [helper methods](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/helpers/event.py). Examples are `track_state_change`, `track_point_in_time`, `track_time_change`. diff --git a/source/developers/credits.markdown b/source/developers/credits.markdown index 8ef5cde5a83..c6ecb4585ee 100644 --- a/source/developers/credits.markdown +++ b/source/developers/credits.markdown @@ -127,4 +127,4 @@ This page contains a list of people who have contributed in one way or another t - [wind-rider](https://github.com/wind-rider) - [Zac Mrowicki](https://github.com/zmrow) -This page is irregularly updated. As a base we use the Github [contributors overview](https://github.com/balloob/home-assistant/graphs/contributors) of the Home Assistant git repository and the [overview](https://github.com/balloob/home-assistant.io/graphs/contributors) for [home-assistant.io](https://home-assistant.io). If you think that you are missing, please let us know or add yourself. +This page is irregularly updated. As a base we use the Github [contributors overview](https://github.com/home-assistant/home-assistant/graphs/contributors) of the Home Assistant git repository and the [overview](https://github.com/home-assistant/home-assistant.io/graphs/contributors) for [home-assistant.io](https://home-assistant.io). If you think that you are missing, please let us know or add yourself. diff --git a/source/developers/frontend.markdown b/source/developers/frontend.markdown index 983935b339f..4bf7589a117 100644 --- a/source/developers/frontend.markdown +++ b/source/developers/frontend.markdown @@ -12,9 +12,9 @@ footer: true Home Assistant uses [Polymer](https://www.polymer-project.org/) for the UI and [NuclearJS](http://optimizely.github.io/nuclear-js/) for maintaing the app state. * Polymer allows building encapsulated custom HTML elements. - [Home-Assistant-Polymer source code on GitHub.](https://github.com/balloob/home-assistant-polymer) + [Home-Assistant-Polymer source code on GitHub.](https://github.com/home-assistant/home-assistant-polymer) * NuclearJS is a reactive flux built with ImmutableJS data structures. - [Home-Assistant-JS source code on GitHub.](https://github.com/balloob/home-assistant-js) + [Home-Assistant-JS source code on GitHub.](https://github.com/home-assistant/home-assistant-js)

Do not use development mode in production. Home Assistant uses aggressive caching to improve the mobile experience. This is disabled during development so that you do not have to restart the server in between changes. @@ -76,20 +76,20 @@ The main interface of Home Assistant is a list of the current entities and their ![Cards in the frontend](/images/frontend/frontend-cards1.png) -The different card types can be found [here](https://github.com/balloob/home-assistant-polymer/tree/master/src/state-summary). +The different card types can be found [here](https://github.com/home-assistant/home-assistant-polymer/tree/master/src/state-summary). Sensors, when not [grouped](/components/group/), are shown as so-called badges on top of the state cards. ![Badges in the frontend](/images/frontend/frontend-badges.png) -The different badges are located in the file [`/src/components/entity/ha-state-label-badge.js`](https://github.com/balloob/home-assistant-polymer/blob/master/src/components/entity/ha-state-label-badge.js). +The different badges are located in the file [`/src/components/entity/ha-state-label-badge.js`](https://github.com/home-assistant/home-assistant-polymer/blob/master/src/components/entity/ha-state-label-badge.js). Adding a custom card type can be done with a few simple steps. For this example we will add a new state card for the domain `camera`: - 1. Add `'camera'` to the array `DOMAINS_WITH_CARD` in the file [/util/state-card-type.js](https://github.com/balloob/home-assistant-polymer/blob/master/src/util/state-card-type.js#L3-L4). - 2. Create the files `state-card-camera.html` and `state-card-camera.js` in the folder [/state-summary/](https://github.com/balloob/home-assistant-polymer/tree/master/src/state-summary). - 3. Add `require('./state-card-camera')` to [state-card-content.js](https://github.com/balloob/home-assistant-polymer/blob/master/src/state-summary/state-card-content.js). - 4. Add `` to [state-card-content.html](https://github.com/balloob/home-assistant-polymer/blob/master/src/state-summary/state-card-content.html). + 1. Add `'camera'` to the array `DOMAINS_WITH_CARD` in the file [/util/state-card-type.js](https://github.com/home-assistant/home-assistant-polymer/blob/master/src/util/state-card-type.js#L3-L4). + 2. Create the files `state-card-camera.html` and `state-card-camera.js` in the folder [/state-summary/](https://github.com/home-assistant/home-assistant-polymer/tree/master/src/state-summary). + 3. Add `require('./state-card-camera')` to [state-card-content.js](https://github.com/home-assistant/home-assistant-polymer/blob/master/src/state-summary/state-card-content.js). + 4. Add `` to [state-card-content.html](https://github.com/home-assistant/home-assistant-polymer/blob/master/src/state-summary/state-card-content.html). # {% linkable_title More info screens for custom types %} @@ -102,7 +102,7 @@ Whenever the user taps or clicks on one of the cards, a more info dialog will sh The instructions to add a more info dialog are very similar to adding a new card type. This example will add a new more info component for the domain `camera`: - 1. Add `'camera'` to the array `DOMAINS_WITH_MORE_INFO` in the file [util/state-more-info-type.js](https://github.com/balloob/home-assistant-polymer/blob/master/src/util/state-more-info-type.js#L1). - 2. Create the files `more-info-camera.html` and `more-info-camera.js` in the folder [/more-infos](https://github.com/balloob/home-assistant-polymer/tree/master/src/more-infos). - 3. Add `require('./more-info-camera')` to [more-info-content.js](https://github.com/balloob/home-assistant-polymer/blob/master/src/more-infos/more-info-content.js) - 4. Add `` to [more-info-content.html](https://github.com/balloob/home-assistant-polymer/blob/master/src/more-infos/more-info-content.html) + 1. Add `'camera'` to the array `DOMAINS_WITH_MORE_INFO` in the file [util/state-more-info-type.js](https://github.com/home-assistant/home-assistant-polymer/blob/master/src/util/state-more-info-type.js#L1). + 2. Create the files `more-info-camera.html` and `more-info-camera.js` in the folder [/more-infos](https://github.com/home-assistant/home-assistant-polymer/tree/master/src/more-infos). + 3. Add `require('./more-info-camera')` to [more-info-content.js](https://github.com/home-assistant/home-assistant-polymer/blob/master/src/more-infos/more-info-content.js) + 4. Add `` to [more-info-content.html](https://github.com/home-assistant/home-assistant-polymer/blob/master/src/more-infos/more-info-content.html) diff --git a/source/developers/index.markdown b/source/developers/index.markdown index 926accf982e..d1cc8003612 100644 --- a/source/developers/index.markdown +++ b/source/developers/index.markdown @@ -13,21 +13,21 @@ Home Assistant is built from the ground up to be easily-extensible by other deve Home Assistant is open-source and MIT licensed. The source can be found here: - - [home-assistant](https://github.com/balloob/home-assistant) - Python server backend - - [home-assistant-js](https://github.com/balloob/home-assistant-js) - JavaScript backend powering the client - - [home-assistant-polymer](https://github.com/balloob/home-assistant-polymer) - Polymer UI + - [home-assistant](https://github.com/home-assistant/home-assistant) - Python server backend + - [home-assistant-js](https://github.com/home-assistant/home-assistant-js) - JavaScript backend powering the client + - [home-assistant-polymer](https://github.com/home-assistant/home-assistant-polymer) - Polymer UI ### {% linkable_title Starting development %} You will need to set up a development environment if you want to start developing a new feature or component for Home Assistant. Please follow these steps to get setup. -Visit the [the Home Assistant repository](https://github.com/balloob/home-assistant) first and click fork in the top right. +Visit the [the Home Assistant repository](https://github.com/home-assistant/home-assistant) first and click fork in the top right. We suggest that you setup a [virtual environment](https://docs.python.org/3.4/library/venv.html) aka `venv` before running the setup script. ```bash $ git clone https://github.com/YOUR_GIT_USERNAME/home-assistant.git $ cd home-assistant -$ git remote add upstream https://github.com/balloob/home-assistant.git +$ git remote add upstream https://github.com/home-assistant/home-assistant.git $ script/setup ``` diff --git a/source/developers/python_api.markdown b/source/developers/python_api.markdown index 06395eb10f5..f40aec0aa17 100644 --- a/source/developers/python_api.markdown +++ b/source/developers/python_api.markdown @@ -9,7 +9,7 @@ sharing: true footer: true --- -In the package [`homeassistant.remote`](https://github.com/balloob/home-assistant/blob/master/homeassistant/remote.py) a Python API on top of the [HTTP API](/developers/api/) can be found. +In the package [`homeassistant.remote`](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/remote.py) a Python API on top of the [HTTP API](/developers/api/) can be found. This page is not a full documentation it's more a collection of some example. A simple way to get all current entities is to visit the "Set State" page in the "Developer Tools". For the examples below just choose one from the available entries. Here the sensor `sensor.office_temperature` and the switch `switch.livingroom_pin_2` are used. @@ -151,4 +151,4 @@ data = {"title":"Test", "message":"A simple test message from HA."} remote.call_service(api, domain, 'jabber', data) ``` -For more details please check the source of [homeassistant.remote](https://github.com/balloob/home-assistant/blob/master/homeassistant/remote.py). +For more details please check the source of [homeassistant.remote](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/remote.py). diff --git a/source/developers/website.markdown b/source/developers/website.markdown index 3a5bead0605..d1fcbe2ce9b 100644 --- a/source/developers/website.markdown +++ b/source/developers/website.markdown @@ -24,7 +24,7 @@ To test your changes locally, you need to install the **Ruby** dependencies (gem Then you can work on the documentation: -- Fork home-assistant.io [git repository](https://github.com/balloob/home-assistant.io). +- Fork home-assistant.io [git repository](https://github.com/home-assistant/home-assistant.io). - Create/edit/update a page in the directory `source/_components/` for your platform/component. - Test your changes to home-assistant.io locally: run ``rake preview`` and navigate to [http://127.0.0.1:4000](http://127.0.0.1:4000) - Create a Pull Request (PR) against the **next** branch of home-assistant.io if your documentation is for a new feature, platform, or component. diff --git a/source/getting-started/configuration.markdown b/source/getting-started/configuration.markdown index 35e597ae540..bf3e2f64382 100644 --- a/source/getting-started/configuration.markdown +++ b/source/getting-started/configuration.markdown @@ -11,7 +11,7 @@ footer: true Home Assistant will create a configuration folder when it is run for the first time. The location of the folder differs between operating systems: on OS X and Linux it's `~/.homeassistant` and on Windows it's `%APPDATA%/.homeassistant`. If you want to use a different folder for configuration, run `hass --config path/to/config`. -Inside your configuration folder is the file `configuration.yaml`. This is the main file that contains which components will be loaded and what their configuration is. This file contains YAML code, which is explained briefly below. [An example configuration file is located here](https://github.com/balloob/home-assistant/blob/master/config/configuration.yaml.example). +Inside your configuration folder is the file `configuration.yaml`. This is the main file that contains which components will be loaded and what their configuration is. This file contains YAML code, which is explained briefly below. [An example configuration file is located here](https://github.com/home-assistant/home-assistant/blob/master/config/configuration.yaml.example). When launched for the first time, Home Assistant will write a default configuration file enabling the web interface and device discovery. It can take up to a minute for your devices to be discovered and show up in the user interface. diff --git a/source/getting-started/index.markdown b/source/getting-started/index.markdown index b161bf6d241..352d0a21bcb 100644 --- a/source/getting-started/index.markdown +++ b/source/getting-started/index.markdown @@ -297,7 +297,7 @@ In addition to this site, check out these sources for additional help: - [Forum](https://community.home-assistant.io) for Home Assistant discussions and questions. - [Gitter Chat Room](https://gitter.im/balloob/home-assistant) for real-time chat about Home Assistant. - - [GitHub Page](https://github.com/balloob/home-assistant/issues) for issue reporting. + - [GitHub Page](https://github.com/home-assistant/home-assistant/issues) for issue reporting. ### {% linkable_title What's next %} diff --git a/source/getting-started/troubleshooting-configuration.markdown b/source/getting-started/troubleshooting-configuration.markdown index f21209385c5..55e69fb2b92 100644 --- a/source/getting-started/troubleshooting-configuration.markdown +++ b/source/getting-started/troubleshooting-configuration.markdown @@ -40,17 +40,17 @@ sensor 2: Another common problem is that a required configuration setting is missing. If this is the case, the component will report this to `home-assistant.log`. You can have a look at [the component page](/components/) for instructions on how to setup the components. -If you find any errors or want to expand the documentation, please [let us know](https://github.com/balloob/home-assistant.io/issues). +If you find any errors or want to expand the documentation, please [let us know](https://github.com/home-assistant/home-assistant.io/issues). #### {% linkable_title Problems with dependencies %} Almost all components have external dependencies to communicate with your devices and services. Sometimes Home Assistant is unable to install the necessary dependencies. If this is the case, it should show up in `home-assistant.log`. -The first step is trying to restart Home Assistant and see if the problem persists. If it does, look at the log to see what the error is. If you can't figure it out, please [report it](https://github.com/balloob/home-assistant/issues) so we can investigate what is going on. +The first step is trying to restart Home Assistant and see if the problem persists. If it does, look at the log to see what the error is. If you can't figure it out, please [report it](https://github.com/home-assistant/home-assistant/issues) so we can investigate what is going on. #### {% linkable_title Problems with components %} -It can happen that some components either do not work right away or stop working after Home Assistant has been running for a while. If this happens to you, please [report it](https://github.com/balloob/home-assistant/issues) so that we can have a look. +It can happen that some components either do not work right away or stop working after Home Assistant has been running for a while. If this happens to you, please [report it](https://github.com/home-assistant/home-assistant/issues) so that we can have a look. #### {% linkable_title Multiple files %} diff --git a/source/help/index.markdown b/source/help/index.markdown index c89f7e6d824..57b31e80dd3 100644 --- a/source/help/index.markdown +++ b/source/help/index.markdown @@ -22,8 +22,8 @@ There are various ways to get in touch with the Home Assistant community. It doe Have you found an issue in your Home Assistant installation? Please report it. Reporting it makes it easy to track and ensures that it gets fixed. -- [Issue tracker Home Assistant](https://github.com/balloob/home-assistant/issues) -- [Issue tracker home-assistant.io](https://github.com/balloob/home-assistant.io/issues) (Website and documentation) +- [Issue tracker Home Assistant](https://github.com/home-assistant/home-assistant/issues) +- [Issue tracker home-assistant.io](https://github.com/home-assistant/home-assistant.io/issues) (Website and documentation) - [Feature requests Home Assistant](https://community.home-assistant.io/c/feature-requests) ### {% linkable_title Roadmap %} diff --git a/source/help/trivia.markdown b/source/help/trivia.markdown index 69751b83855..74d886db6cd 100644 --- a/source/help/trivia.markdown +++ b/source/help/trivia.markdown @@ -37,13 +37,13 @@ This sections just contains some random numbers of the Home Assistant eco-system | [Forum posts](https://community.home-assistant.io/) | 352 | | [Forum topics](https://community.home-assistant.io/) | 83 | | [Forum members](https://community.home-assistant.io/) | 92 | -| [Github stars](https://github.com/balloob/home-assistant/stargazers) | 2519 | -| [Github forks](https://github.com/balloob/home-assistant/network) | 374 | +| [Github stars](https://github.com/home-assistant/home-assistant/stargazers) | 2519 | +| [Github forks](https://github.com/home-assistant/home-assistant/network) | 374 | | Page views [ha.io](https://home-assistant.io) | 190'271| ### {% linkable_title Commit per year %} -The numbers below only covers the [main git repository](https://github.com/balloob/home-assistant/) and doesn't take the helpers ([home-assistant.io](https://github.com/balloob/home-assistant.io), [home-assistant-polymer](https://github.com/balloob/home-assistant-polymer), and [home-assistant-js](https://github.com/balloob/home-assistant-js)) into account. +The numbers below only covers the [main git repository](https://github.com/home-assistant/home-assistant/) and doesn't take the helpers ([home-assistant.io](https://github.com/home-assistant/home-assistant.io), [home-assistant-polymer](https://github.com/home-assistant/home-assistant-polymer), and [home-assistant-js](https://github.com/home-assistant/home-assistant-js)) into account. ```bash 2013: 147 @@ -52,7 +52,7 @@ The numbers below only covers the [main git repository](https://github.com/ballo 2016: 1439 (so far) ``` -More details and statistics can be found on [Github](https://github.com/balloob/home-assistant/graphs/contributors). +More details and statistics can be found on [Github](https://github.com/home-assistant/home-assistant/graphs/contributors). [RocketGraph](https://rocketgraph.com) reports shows commit stats for the last 90 days and a neat visual calendar for the current calendar year.