diff --git a/source/_posts/2016-07-23-internet-of-things-data-exploration-with-jupyter-notebooks.markdown b/source/_posts/2016-07-23-internet-of-things-data-exploration-with-jupyter-notebooks.markdown index 3dcb993f816..9475ab7e1b5 100644 --- a/source/_posts/2016-07-23-internet-of-things-data-exploration-with-jupyter-notebooks.markdown +++ b/source/_posts/2016-07-23-internet-of-things-data-exploration-with-jupyter-notebooks.markdown @@ -30,7 +30,7 @@ _TL; DR: Use [this Jupyter Notebook][nb-prev] to visualize of your data_ [Pandas]: http://pandas.pydata.org/ [matplotlib]: http://matplotlib.org/ [Jupyter notebook]: https://jupyter.org/ -[nb-prev]: http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/DataExploration-1/DataExploration-1.ipynb +[nb-prev]: https://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/other/DataExploration-1/DataExploration-1.ipynb diff --git a/source/_posts/2016-08-19-github-style-calendar-heatmap-of-device-data.markdown b/source/_posts/2016-08-19-github-style-calendar-heatmap-of-device-data.markdown index c71aa88d6ca..90f3d202f0f 100644 --- a/source/_posts/2016-08-19-github-style-calendar-heatmap-of-device-data.markdown +++ b/source/_posts/2016-08-19-github-style-calendar-heatmap-of-device-data.markdown @@ -10,7 +10,7 @@ og_image: /images/blog/2016-08-data-exploration/heatmap.png --- -Thanks to [Anton Kireyeu](https://github.com/kireyeu) we are able to present another awesome [Jupyter notebook]. I guess that you all know the graph which Github is using to visualize your commits per day over a time-line. It's a so-called [heatmap]. If there are more commits, it's getting hotter. The latest [notebook][nb-prev] is capable to do the same thing for your devices. To be more precise, for the hours your devices are home. +Thanks to [Anton Kireyeu](https://github.com/kireyeu) we are able to present another awesome [Jupyter notebook]. I guess that you all know the graph which Github is using to visualize your commits per day over a time-line. It's a so-called [heatmap]. If there are more commits, it's getting hotter. The latest [notebook][nb-prev] is capable to do the same thing for your devices. To be more precise, for the hours your devices are home.

@@ -19,5 +19,4 @@ Heatmap [heatmap]: https://en.wikipedia.org/wiki/Heat_map [Jupyter notebook]: https://jupyter.org/ -[nb-prev]: http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/DataExploration-2/DataExploration-2.ipynb - +[nb-prev]: https://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/other/DataExploration-2/DataExploration-2.ipynb diff --git a/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown b/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown index dca1a3fb87a..c7079ba0997 100644 --- a/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown +++ b/source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown @@ -10,11 +10,11 @@ categories: Release-Notes Yes, after only nine days comes 0.30. Don't worry, we will try to keep our usual release cycle and not start to release every day. -We guess that you already know: The [Raspberry Pi image][pi-image] is available now. For Hassbian, [@Landrash] has combined the most essential parts for a Home Assistant setup in an easy-to-use image for the Raspberry Pi device family. Hassbian is quite young, thus we are looking forward to receive [feedback][hassbian-forum], [issue report][hassbian-forum], and [suggestions][hassbian-forum] to improve it. +We guess that you already know: The [Raspberry Pi image][pi-image] is available now. For Hassbian, [@Landrash] has combined the most essential parts for a Home Assistant setup in an easy-to-use image for the Raspberry Pi device family. Hassbian is quite young, thus we are looking forward to receive [feedback][hassbian-forum], [issue report][hassbian-forum], and [suggestions][hassbian-forum] to improve it. A large amount of resources of the development are still focusing on the effort to move Home Assistant further to asynchronous programming. It's a labor-intensive task, comes with segmentation faults, and unstable instances when certain combinations of sensors are used. The benefit will be more speed in the near future. -To reduce the run-time of your tests, [@balloob] did a lot of tweaking. For now the RFXtrx tests are excluded which cut the needed time for running on your Pull Request in half. +To reduce the run-time of your tests, [@balloob] did a lot of tweaking. For now the RFXtrx tests are excluded which cut the needed time for running on your Pull Request in half. ### Documentation @@ -75,7 +75,7 @@ sensor - Sensor: [Forecast][darksky] update interval is now configurable ([@KlaasH]) - Core: Failed login attempts are reported as persistent notifications ([@fabaff]) - Climate: Temperature convert now available in the Climate object ([@pvizeli]) -- Notify: Update to accept a list ([@robbiet480]) +- Notify: Update to accept a list ([@robbiet480]) - Device tracker: Support for tracking of your [Volvo] ([@molobrakos]) - Switch: Flux improvements ([@jawilson]) - InfluxDB: Time-out for connections ([@simonszu]) @@ -92,7 +92,7 @@ sensor - Sensor: Support for [Västtrafik][vasttrafik] public transport ([@persandstrom]) - Notify: Pushetta no longer sends message on start up ([@Danielhiversen]) - Sensor: [Forecast.io][forecast] sensor was replaced by [Dark Sky][darksky] ([@fabaff]) -- Device Tracker: The `known_device.yaml` file is now validated ([@kellerza]) +- Device Tracker: The `known_device.yaml` file is now validated ([@kellerza]) - Minor features and bug fixes by [@tchellomello], [@pavoni], [@fabaff], [@pvizeli], [@lwis], [@turbokongen], [@Danielhiversen], [@persandstrom], [@balloob], [@robbiet480], [@sam-io], [@bbangert], and you if you are missing here. ### Release 0.30.1 - October 8 @@ -116,9 +116,9 @@ sensor - All deprecated condition options from `automation` have been removed (deprecated since May and have printed warnings to your console): - `use_trigger_values` is gone. You have to copy your triggers to conditions and adjust for the correct config. - `condition_type` is gone. Use `condition: or` instead. - - To specify the type of a condition, use `condition:` instead of `platform:`. + - To specify the type of a condition, use `condition:` instead of `platform:`. - The [Forecast.io][forecast] was renamed to [Dark Sky][darksky]. Replace your `- platform: forecast` with `- platform: darksky`. -- The [aREST][arest] configuration between the [sensor][arest-sensor] and the [switch][arest-switch] platform was aligned. +- The [aREST][arest] configuration between the [sensor][arest-sensor] and the [switch][arest-switch] platform was aligned. ### If you need help... ...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you the former communication channels. Thanks. @@ -168,7 +168,7 @@ sensor [hassbian-forum]: https://community.home-assistant.io/c/installation/hassbian [mention-bot]: https://github.com/mention-bot [mysensors-cover]: /integrations/cover.mysensors/ -[notebook]: http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/database-statistics.ipynb +[notebook]: https://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/other/database-statistics.ipynb [pi-image]: /blog/2016/10/01/we-have-raspberry-image-now/ [pwrctrl-switch]: /integrations/anel_pwrctrl [rest-sensor]: /integrations/rest @@ -178,4 +178,3 @@ sensor [trend-sensor]: /integrations/trend [vasttrafik]: /integrations/vasttrafik [Volvo]: /integrations/volvooncall -