mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-18 23:06:58 +00:00
🔗 Fixing multiple blog links (#10741)
* 🔗 Fix broken links * 🔗 Fix broken links * 🔗 Fix broken links * 🔗 Fix broken links * 🔗 Fix broken links * 🔗 Fix broken links * 🔗 Fix broken links * 🔗 Fix broken links * 🔗 Fix broken links * 🔗 Fix broken links * 🔗 Fix broken links
This commit is contained in:
Hmmbob
Franck Nijhof
parent
f802564975
commit
9c99aa1fa0
@ -11,6 +11,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/home-assistant/home-assistant/blob/dev/config/configuration.yaml.example).
|
||||
The home-assistant.conf.example has been replaced with an updated configuration.yaml.example.
|
||||
|
||||
Users of Home Assistant should migrate as the old configuration format is deprecated.
|
||||
|
||||
@ -36,7 +36,7 @@ Maker channel setup:
|
||||
|
||||
| Field | Value |
|
||||
| ----- | ----- |
|
||||
| URL | http://xxx.xxx.xxx.xxx:8123/api/services/switch/turn_off?api_password=xxxxxxxx
|
||||
| URL | `http://xxx.xxx.xxx.xxx:8123/api/services/switch/turn_off?api_password=xxxxxxxx`
|
||||
| METHOD | POST
|
||||
| CONTENT TYPE | application/json
|
||||
| BODY | { "entity_id": "switch.irrigation" }
|
||||
@ -73,7 +73,7 @@ Maker channel setup:
|
||||
|
||||
| Field | Value |
|
||||
| ----- | ----- |
|
||||
| URL | http://xxx.xxx.xxx.xxx:8123/api/services/light/turn_on?api_password=xxxxxxxx
|
||||
| URL | `http://xxx.xxx.xxx.xxx:8123/api/services/light/turn_on?api_password=xxxxxxxx`
|
||||
| METHOD | POST
|
||||
| CONTENT TYPE | application/json
|
||||
| BODY | { "entity_id": "light.kitchen" }
|
||||
@ -88,7 +88,7 @@ Maker channel setup:
|
||||
|
||||
| Field | Value |
|
||||
| ----- | ----- |
|
||||
| URL | http://xxx.xxx.xxx.xxx:8123/api/services/light/turn_on?api_password=xxxxxxxx
|
||||
| URL | `http://xxx.xxx.xxx.xxx:8123/api/services/light/turn_on?api_password=xxxxxxxx`
|
||||
| METHOD | POST
|
||||
| CONTENT TYPE | application/json
|
||||
| BODY | { "entity_id": "group.all_lights", "flash":"yes" }
|
||||
|
||||
@ -27,7 +27,7 @@ Launch the InfluxDB service.
|
||||
sudo systemctl start influxdb
|
||||
```
|
||||
|
||||
If everything went well, then the web interface of the database should be accessible at [http://localhost:8083/](http://localhost:8083/). Create a database `home_assistant` to use with Home Assistant either with the web interface or the commandline tool `influx`.
|
||||
If everything went well, then the web interface of the database should be accessible at `http://localhost:8083/`. Create a database `home_assistant` to use with Home Assistant either with the web interface or the commandline tool `influx`.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2015-12-influxdb/influxdb-frontend.png' />
|
||||
@ -88,7 +88,7 @@ sudo systemctl start grafana-server
|
||||
sudo systemctl status grafana-server
|
||||
```
|
||||
|
||||
Login with the username `admin` and the password `admin` at [http://localhost:3000/login](http://localhost:3000/login). Now follow the [InfluxDB setup instructions](http://docs.grafana.org/datasources/influxdb/).
|
||||
Login with the username `admin` and the password `admin` at `http://localhost:3000/login`. Now follow the [InfluxDB setup instructions](http://docs.grafana.org/datasources/influxdb/).
|
||||
|
||||
Now you can start to create dashboards and graphs. You have various options to get the data from the graph. The next image just shows a screenshot of the setting for a temperature sensor.
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ categories: How-To
|
||||
og_image: /images/blog/2016-04-display/ha-display.png
|
||||
---
|
||||
|
||||
The frontend of Home Assistant is served with the help of a local web server. If you have [customized](/getting-started/devices/#customizing-devices-and-services) your installation you already use this functionality. The content of your folder `www` in your Home Assistant configuration directory (`.homeassistant`) is available under `/local` (eg. [http://localhost:8123/local](https://localhost:8123/local/index.html) for an `index.html` file).
|
||||
The frontend of Home Assistant is served with the help of a local web server. If you have [customized](/getting-started/devices/#customizing-devices-and-services) your installation you already use this functionality. The content of your folder `www` in your Home Assistant configuration directory (`.homeassistant`) is available under `/local` (eg. `https://localhost:8123/local/index.html` for an `index.html` file).
|
||||
|
||||
But there is more you can do! You can not only host images for customization there but HTML files or even web applications including CSS and Javascript.
|
||||
|
||||
@ -19,11 +19,10 @@ But there is more you can do! You can not only host images for customization the
|
||||
|
||||
<!--more-->
|
||||
|
||||
In the past the buzz word "Smart mirror" was used a couple of times in our [chatroom](https://discord.gg/c5DvZ4e) 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.
|
||||
In the past the buzz word "Smart mirror" was used a couple of times in our [chatroom](https://discord.gg/c5DvZ4e) and even made it into the [issue tracker](https://github.com/home-assistant/home-assistant/issues/1392). The existing solutions ([Smart mirror](https://docs.smart-mirror.io/), [MagicMirror](https://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](/integrations/#history). If it is to be a web page I'm using the [MQTT Eventstream component](/integrations/mqtt_eventstream/) and [mqttws31.js](http://git.eclipse.org/c/paho/org.eclipse.paho.mqtt.javascript.git/tree/src).
|
||||
There are plenty of ways to achieve this...[RESTful API](/developers/rest_api/), [Python API](/developers/python_api/), or one of the [history components](/integrations/#history). If it is to be a web page I'm using the [MQTT Eventstream component](/integrations/mqtt_eventstream/) and [Eclipse Paho JavaScript Client](https://www.eclipse.org/paho/clients/js/).
|
||||
|
||||
The [HBMQTT](https://pypi.python.org/pypi/hbmqtt) broker provides websockets support for MQTT and mqttws31.js included in web page gives you access to the MQTT messages. It's a matter of minutes. OK, it took a little longer because I'm not a Javascript guy to create the software part that will show details about your environment. The source is available at [https://github.com/fabaff/home-assistant-display](https://github.com/fabaff/home-assistant-display) and the screenshot above shows the result. I guess that every person who is familiar with Javascript would be able to reduce the amount of code and to make it more flexible. Well, it's only a prototype and showcase to include an image in this blog post.
|
||||
The [HBMQTT](https://pypi.org/pypi/hbmqtt) broker provides websockets support for MQTT and mqttws31.js included in web page gives you access to the MQTT messages. It's a matter of minutes. OK, it took a little longer because I'm not a Javascript guy to create the software part that will show details about your environment. The source is available at [https://github.com/fabaff/home-assistant-display](https://github.com/fabaff/home-assistant-display) and the screenshot above shows the result. I guess that every person who is familiar with Javascript would be able to reduce the amount of code and to make it more flexible. Well, it's only a prototype and showcase to include an image in this blog post.
|
||||
|
||||
I hope that this little article could give you an idea of extending Home Assistant in an unconventional way.
|
||||
|
||||
|
||||
@ -10,14 +10,14 @@ categories: Website
|
||||
|
||||
One of the main complaints that we receive is something along the lines "I read that X is possible yet I am unable to find it on the website.". This post is to announce that we have taken the first steps to improve it by revamping the [getting started] and [developers] sections. It's still a work in progress but we now have a solid foundation to build on for the future 👍.
|
||||
|
||||
Our documentation has been going through various phases. Initially it was just the README in our GitHub repository. I discovered Jekyll and GitHub pages in December 2014 and created home-assistant.io. I more or less broke the README in 5 pages and [called it a website]. Back then we had a whopping [11 components](https://github.com/home-assistant/home-assistant.io/blob/86bb2df430ce267ab2123d51592d3f068ae509b5/source/integrations/index.markdown).
|
||||
Our documentation has been going through various phases. Initially it was just the README in our GitHub repository. I discovered Jekyll and GitHub pages in December 2014 and created home-assistant.io. I more or less broke the README in 5 pages and [called it a website]. Back then we had a whopping 11 components!
|
||||
|
||||
As Home Assistant grew, so did our documentation. [Fabian Affolter](https://github.com/fabaff) does an amazing job in making sure there is at least a documentation stub for each new feature that lands. And that's quite a feat given our [frequent releases](/blog/categories/release-notes/)! But despite all the efforts, the documentation outgrew our existing documentation organization.
|
||||
|
||||
Today it has been almost 1.5 years since we started the website. We now have [264 components and platforms] under our belt and have been honored with 1.5 million page views ✨. And hopefully we now also have documentation that our community deserves.
|
||||
|
||||
[getting started]: /getting-started/
|
||||
[developers]: /developers/
|
||||
[developers]: https://developers.home-assistant.io/
|
||||
[called it a website]: /blog/2014/12/18/website-launched/
|
||||
[264 components and platforms]: /integrations/
|
||||
|
||||
|
||||
@ -128,7 +128,7 @@ Of course you can use both fixed and mobile beacons at the same time. I want my
|
||||
### Buying Beacons
|
||||
This isn’t a buyer's guide, but I just wanted to mention the iBeacons I’ve been using. I think you should be able to use any iBeacon with HA and OwnTracks. You generally can’t buy beacons in your local electronics shop - so I just wanted to briefly mention the two suppliers I’ve used so far.
|
||||
|
||||
I’ve bought quite a few iBeacons from a company called [Blue Sense Networks](http://bluesensenetworks.com/). I work in the tech startup sector in the UK so I partly chose them because they are a local start-up who seemed worth supporting. The products, support and software all seem good. I use a number of their beacons - from a simple USB dongle, to a long range beacon. All their products have batteries that can be changed (or no batteries in the case of the externally powered USB device) - and you can configure all the parameters you’d want to using their software. I had one software issue, support got back to me at a weekend(!) - and the issue was resolved with a software release two days later.
|
||||
I’ve bought quite a few iBeacons from a company called Blue Sense Networks. I work in the tech startup sector in the UK so I partly chose them because they are a local start-up who seemed worth supporting. The products, support and software all seem good. I use a number of their beacons - from a simple USB dongle, to a long range beacon. All their products have batteries that can be changed (or no batteries in the case of the externally powered USB device) - and you can configure all the parameters you’d want to using their software. I had one software issue, support got back to me at a weekend(!) - and the issue was resolved with a software release two days later.
|
||||
|
||||
All the beacons seem fine - and the long range unit does work over a longer range than my other beacons.
|
||||
|
||||
|
||||
@ -9,13 +9,13 @@ og_image: /images/blog/2016-07-micropython/social.png
|
||||
---
|
||||
|
||||
<img src='/images/blog/2016-07-micropython/micropython.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 12px;' width='200' />
|
||||
The first release of Micropython for ESP8266 was delivered a couple of weeks ago. The [documentation](http://docs.micropython.org/en/latest/esp8266/esp8266_contents.html) covers a lot of ground. This post is providing only a little summary which should get you started.
|
||||
The first release of Micropython for ESP8266 was delivered a couple of weeks ago. The [documentation](http://docs.micropython.org/en/latest/) covers a lot of ground. This post is providing only a little summary which should get you started.
|
||||
|
||||
Until a couple of weeks ago, the pre-built MicroPython binary for the ESP8266 was only available to backers of the Kickstarter campaign. This has changed now and it is available to the public for [download](https://micropython.org/download/#esp8266).
|
||||
|
||||
<!--more-->
|
||||
|
||||
The easiest way is to use [esptool.py](https://github.com/themadinventor/esptool) for firmware handling tasks. First erase the flash:
|
||||
The easiest way is to use [esptool.py](https://github.com/espressif/esptool) for firmware handling tasks. First erase the flash:
|
||||
|
||||
```bash
|
||||
$ sudo python esptool.py --port /dev/ttyUSB0 erase_flash
|
||||
|
||||
@ -33,6 +33,6 @@ Keep in mind that you may have to pay the fee for customs handling and the impor
|
||||
|
||||
[LES]: https://www.thomas-krenn.com/en/products/low-energy-systems/les-v2.html
|
||||
[award]: https://www.thomas-krenn.com/de/tkmag/allgemein/zammad-home-assistant-und-freifunk-das-sind-die-gewinner-des-thomas-krenn-awards-2017/
|
||||
[forum]: https://community.home-assistant.io/c/contest-2017
|
||||
[forum]: https://community.home-assistant.io/t/hardware-contest-2017/42546
|
||||
[twitter]: https://twitter.com/home_assistant
|
||||
|
||||
|
||||
@ -69,7 +69,7 @@ sudo systemctl start install_homeassistant.service
|
||||
|
||||
Wait about 15-20 minutes and voilà you have your Home Assistant on your Raspberry Pi Zero W in 30 minutes.
|
||||
|
||||
To try it out, go to [http://hassbian:8123](http://hassbian:8123) or [http://hassbian.local:8123](http://hassbian.local:8123) if you're using Mac.
|
||||
To try it out, go to `http://hassbian:8123` or `http://hassbian.local:8123` if you're using Mac.
|
||||
|
||||
For further details about HASSbian, take a look at the [documentation](/docs/installation/hassbian/).
|
||||
|
||||
|
||||
@ -55,7 +55,7 @@ Last login: Fri Oct 27 17:50:09 2017
|
||||
[ha@home-assistant ~]$
|
||||
```
|
||||
|
||||
Now you are able to use your frontend on your local system: [http://localhost:8000](http://localhost:8000)
|
||||
Now you are able to use your frontend on your local system: `http://localhost:8000`
|
||||
|
||||
Things to keep in mind:
|
||||
|
||||
@ -63,5 +63,5 @@ Things to keep in mind:
|
||||
- You need to setup port forwarding on your router.
|
||||
- Don't allow `root` to use SSH. Set `PermitRootLogin no` on the remote system.
|
||||
- Your local port must be above 1024. Only `root` is allowed to forward privileged ports which are below 1024.
|
||||
- Use [SSH keys for authentication](https://docs-old.fedoraproject.org/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-configuration-keypairs.html) instead of passwords to avoid bruteforce attacks.
|
||||
- Use [SSH keys for authentication](http://docs.fedoraproject.org//en-US/Fedora/14/html/Deployment_Guide/s2-ssh-configuration-keypairs.html) instead of passwords to avoid bruteforce attacks.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user