-At this time emulated_hue doesn’t appear to be working for new Google Home users.
+
+Be aware that emulated_hue doesn’t work for new Google Home users. If you’re a new user of Google Home, use the Google Assistant component.
The emulated_hue component provides a virtual Philips Hue bridge, written entirely in software, that allows services that work with the Hue API to interact with Home Assistant
entities. The driving use case behind this functionality is to allow Home Assistant to work with an Amazon Echo or Google Home with no set up cost outside of configuration changes.
diff --git a/components/hue/index.html b/components/hue/index.html
index fb1c95810b..b5325363bc 100644
--- a/components/hue/index.html
+++ b/components/hue/index.html
@@ -90,7 +90,7 @@
discovery component to discover Hue bridges.emulated_hue component.emulated_hue component.pip3 install websocket-client must be executed, turn on doesn’t work, turn off works fine)Currently tested but not working models:
Pilight is a modular and open source solution to communicate with 433 MHz devices and runs on various small form factor computers. A lot of common protocols are already available.
-This pilight hub connects to the pilight-daemon via a socket connection to receive and send codes. Thus Home Assistant does not have to run on the computer in charge of the RF communication.
+Pilight is a modular and open source solution to communicate with 433 MHz devices and runs on various small form factor computers. A lot of common protocols are already available.
+This pilight hub connects to the pilight-daemon via a socket connection to receive and send codes. Thus Home Assistant does not have to run on the computer in charge of the RF communication.
The received and supported RF codes are put on the event bus of Home Assistant and are therefore directly usable by other components (e.g. automation). Additionally a send service is provided to send RF codes.
To integrate pilight into Home Assistant, add the following section to your configuration.yaml file:
# Example configuration.yaml entry
@@ -87,11 +87,11 @@
Configuration variables:
- host (Required): The IP address of the computer running the pilight-daemon, e.g. 192.168.1.32.
- - port (Required): The network port to connect to. The usual port is 5000.
+ - port (Required): The network port to connect to. The usual port is 5000.
- send_delay (Optional): You can define a send delay as a fraction of seconds if you experience transmission problems when you try to switch multiple switches at once. This can happen when you use a pilight USB Nano as hardware and switches a whole group of multiple switches on or off. Tested values are between 0.3 and 0.8 seconds depending on the hardware.
- whitelist (Optional): You can define a whitelist to prevent that too many unwanted RF codes (e.g. the neighbours weather station) are put on your HA event bus. All defined subsections have to be matched. A subsection is matched if one of the items are true.
-In this example only received RF codes using a daycom or Intertechno protocol are put on the event bus and only when the device id is 42. For more possible settings please look at the receiver section of the pilight API.
+In this example only received RF codes using a daycom or Intertechno protocol are put on the event bus and only when the device id is 42. For more possible settings please look at the receiver section of the pilight API.
A full configuration sample could look like the sample below:
# Example configuration.yaml entry
pilight:
@@ -108,11 +108,11 @@
Troubleshooting
- - A list of tested RF transceiver hardware is available here. This might be useful before buying.
+ - A list of tested RF transceiver hardware is available here. This might be useful before buying.
- Sending commands is simple when the protocol is known by pilight, but receiving commands can be rather difficult. It can happen that the code is not correctly recognized due to different timings in the sending hardware or the RF receiver. If this happens follow these steps:
- - Install pilight from source (do not worry that is very easy) and only activate the protocols you are expecting in the pop up menu. This reduces false positives.
+ - Install pilight from source (do not worry that is very easy) and only activate the protocols you are expecting in the pop up menu. This reduces false positives.
- Check the real timings of your device + RF receiver by running
pilight-debug. Remember the pulslen parameter.
- Go to the
libs/pilight/protocols/433.92 subfolder of the pilight source code and open the .c file of your protocol. Search for MIN_PULSE_LENGTH, MAX_PULSE_LENGTH and AVG_PULSE_LENGTH. Change the pulse lengths to match your measured one. Recompile and install pilight by re-running $ sudo ./setup.sh.
diff --git a/components/sensor.command_line/index.html b/components/sensor.command_line/index.html
index 8f24af10d4..836e325f7d 100644
--- a/components/sensor.command_line/index.html
+++ b/components/sensor.command_line/index.html
@@ -171,7 +171,6 @@
- platform: command_line
name: Brightness
command: "python3 /path/to/script/arest-value.py"
- unit_of_measurement: "°C"
command:If you’re interested in logging in to Home Assistant while away, you’ll have to make your instance remotely accessible.
+If you’re interested in logging in to Home Assistant while away, you’ll have to make your instance remotely accessible. Remember to follow the securing checklist before doing this.
The most common approach is to set up port forwarding from your router to port 8123 on the computer that is hosting Home Assistant. General instructions on how to do this can be found by searching <router model> port forwarding instructions.
A problem with making a port accessible is that some Internet Service Providers only offer dynamic IPs. This can cause you to lose access to Home Assistant while away. You can solve this by using a free Dynamic DNS service like DuckDNS.
Remember: Just putting a port up is not secure. You should definitely consider encrypting your traffic if you are accessing your Home Assistant installation remotely. For details please check the set up encryption using Let’s Encrypt blog post, or this detailed guide to using Let’s Encrypt with HA.
diff --git a/docs/installation/virtualenv/index.html b/docs/installation/virtualenv/index.html index de9f429111..d0226cc6d5 100644 --- a/docs/installation/virtualenv/index.html +++ b/docs/installation/virtualenv/index.html @@ -135,7 +135,7 @@-Looking for more advanced guides? Check our Rasbian guide or the [other installation guides](/docs/installation/]. +Looking for more advanced guides? Check our Rasbian guide or the other installation guides.
diff --git a/sitemap.xml b/sitemap.xml index b9cc99c61b..5cf50065ed 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -3826,7 +3826,7 @@