mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-23 09:17:06 +00:00
Merge branch 'current' into rc
This commit is contained in:
Franck Nijhof
commit
1ae35fa224
@ -23,7 +23,7 @@ ha_platforms:
|
||||
|
||||
The [EnOcean](https://en.wikipedia.org/wiki/EnOcean) standard is supported by many different vendors. There are switches and sensors of many different kinds, and typically they employ energy harvesting to get power such that no batteries are necessary.
|
||||
|
||||
The `enocean` integration adds support for some of these devices. You will need a controller like the [USB300](https://www.enocean.com/en/enocean_modules/usb-300-oem/) in order for it to work.
|
||||
The EnOcean integration adds support for some of these devices. You will need a controller like the [USB300](https://www.enocean.com/en/enocean_modules/usb-300-oem/) in order for it to work.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
@ -43,17 +43,13 @@ The following devices have been confirmed to work out of the box:
|
||||
- EnOcean STM-330 temperature sensor
|
||||
- Hoppe SecuSignal window handle from Somfy
|
||||
|
||||
If you own a device not listed here, please check whether your device can talk in one of the listed [EnOcean Equipment Profiles](https://www.enocean-alliance.org/what-is-enocean/specifications/) (EEP).
|
||||
If it does, it will most likely work.
|
||||
The available profiles are usually listed somewhere in the device manual.
|
||||
If you own a device not listed here, please check whether your device can talk in one of the listed [EnOcean Equipment Profiles](https://www.enocean-alliance.org/what-is-enocean/specifications/) (EEP). If it does, it will most likely work. The available profiles are usually listed somewhere in the device manual.
|
||||
|
||||
Support for tech-in messages is not implemented.
|
||||
|
||||
## Configuration
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
Despite the UI-based configuration of the hub, the entities are still configured using YAML see mext chapters).
|
||||
Despite the UI-based configuration of the hub, the entities are still configured using YAML see next chapters).
|
||||
|
||||
## Binary Sensor
|
||||
|
||||
|
||||
@ -65,7 +65,7 @@ vapid_prv_key:
|
||||
required: true
|
||||
type: string
|
||||
vapid_email:
|
||||
description: The e-mail account associated with your Firebase project, [see configuring the platform](#configuring-the-platform).
|
||||
description: The e-mail account of your Google account associated with your Firebase project, [see configuring the platform](#configuring-the-platform).
|
||||
required: true
|
||||
type: string
|
||||
gcm_api_key:
|
||||
@ -99,7 +99,7 @@ The `html5` platform can only function if all of the following requirements are
|
||||
6. Select the ['Cloud Messaging' tab](https://console.firebase.google.com/project/_/settings/cloudmessaging).
|
||||
7. Generate a new key pair under the Web configuration listing at the bottom of the page. To view the private key click the three dots to the right and 'Show private key'.
|
||||
8. Select the ['Service Accounts' tab](https://console.firebase.google.com/project/_/settings/serviceaccounts/adminsdk).
|
||||
9. Get the email address for the project under the text that says "Firebase service account".
|
||||
9. Get the email address for the project under the text that says "Firebase service account" for reference. This is not what you have to insert in `vapid_email`! You'll have to insert your Google account e-mail there.
|
||||
|
||||
### Setting up your browser
|
||||
|
||||
|
||||
@ -12,8 +12,6 @@ ha_platforms:
|
||||
|
||||
The MH-Z19 is a small non-dispersive infrared sensor that can measure CO2 level. High CO2 levels can lead to drowsiness, poor concentration, loss of attention or increased heart rate. The CO2 level outside is around 400ppm, but inside levels can reach between 1000 and 5000 ppm. High CO2 levels indicate that you should increase ventilation.
|
||||
|
||||
Check out the [Open Home Automation web site](https://www.open-homeautomation.com/2016/08/24/monitor-co2-levels-in-your-house/) for a quick guide how to connect the sensor to your PC or Raspberry Pi.
|
||||
|
||||
**Note:** the new version MH-Z19B requires the VIN to be connected to a 5V pin, rather than 3.3V.
|
||||
|
||||
## Configuration
|
||||
|
||||
@ -10,7 +10,7 @@ ha_platforms:
|
||||
- switch
|
||||
---
|
||||
|
||||
The `netio` switch platform allows you to control your [Netio](https://www.netio-products.com/en/overview/) Netio4, Netio4 All, and Netio 230B. These are smart outlets controllable through Ethernet and/or Wi-Fi that reports consumptions (Netio4all).
|
||||
The `netio` switch platform allows you to control your [Netio](https://www.netio-products.com/en/overview/) Netio4, Netio4 All, and Netio 230B. These are smart outlets controllable through Ethernet and/or Wi-Fi that reports consumptions (Netio4all). This integration requires Telnet to be enabled on the Netio device.
|
||||
|
||||
To use Netio devices in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -15,38 +15,28 @@ ha_platforms:
|
||||
- sensor
|
||||
---
|
||||
|
||||
The `speedtestdotnet` integration uses the [Speedtest.net](https://speedtest.net/) web service to measure network bandwidth performance.
|
||||
The Speedtest.net integration uses the [Speedtest.net](https://speedtest.net/) web service to measure network bandwidth performance.
|
||||
|
||||
By default, a speed test will be run every hour. The user can change the update frequency in the configuration by defining the `scan_interval` for a speed test to run.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
Most Speedtest.net servers require TCP port 8080 outbound to function. Without this port open you may experience significant delays or no results at all. See note on their [help page](https://www.speedtest.net/help).
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
By default, a speed test will be run every hour. You can update frequency in the integration configuration.
|
||||
|
||||
## Integration Sensors
|
||||
|
||||
The following sensors are added by the integration:
|
||||
|
||||
sensors:
|
||||
- Ping sensor: Reaction time in ms of your connection (how fast you get a response after you’ve sent out a request).
|
||||
- Download sensor: The download speed (Mbit/s).
|
||||
- Upload sensor: The upload speed (Mbit/s).
|
||||
|
||||
- Ping sensor: Reaction time in ms of your connection (how fast you get a response after you’ve sent out a request).
|
||||
- Download sensor: The download speed (Mbit/s).
|
||||
- Upload sensor: The upload speed (Mbit/s).
|
||||
|
||||
### Time period dictionary example
|
||||
|
||||
```yaml
|
||||
scan_interval:
|
||||
# At least one of these must be specified:
|
||||
days: 0
|
||||
hours: 0
|
||||
minutes: 3
|
||||
seconds: 30
|
||||
milliseconds: 0
|
||||
```
|
||||
|
||||
### Service
|
||||
|
||||
Once loaded, the `speedtestdotnet` integration will expose a service (`speedtestdotnet.speedtest`) that can be called to run a Speedtest.net speed test on demand. This service takes no parameters. This can be useful if you have enabled manual mode.
|
||||
Once loaded, the integration will expose a service (`speedtestdotnet.speedtest`) that can be called to run a Speedtest.net speed test on demand. This service takes no parameters. This can be useful when auto update has been disabled in the integration options.
|
||||
|
||||
```yaml
|
||||
action:
|
||||
@ -59,18 +49,6 @@ Please be aware of the potential [inconsistencies](https://github.com/sivel/spee
|
||||
## Examples
|
||||
|
||||
In this section you will find some real-life examples of how to use this component.
|
||||
|
||||
### Run periodically
|
||||
|
||||
Every half hour of every day:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
speedtestdotnet:
|
||||
scan_interval:
|
||||
minutes: 30
|
||||
```
|
||||
|
||||
### Using as a trigger in an automation
|
||||
|
||||
{% raw %}
|
||||
|
||||
@ -579,7 +579,8 @@ The integration will add as many useable entities for you as possible from the i
|
||||
|
||||
### I renamed my devices in Z-Wave JS 2 MQTT but those names are not visible in Home Assistant
|
||||
|
||||
Correct. Only a few devices actually support having their name stored in the hardware. In case your device supports it, you can rename it from the control panel and it will be stored on your device (and Home Assistant will prefer that name). Most devices don't support that feature. Zwavejs2mqtt changes are only available within the application and not stored/synced with the actual Z-Wave network and thus not populated to Home Assistant.
|
||||
The names are only loaded when the Z-Wave JS integration is started. For Home Assistant
|
||||
to pick up those new names, either reload the integration or restart Home Assistant.
|
||||
|
||||
## Troubleshooting Issues
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
#
|
||||
|
||||
# General use redirects
|
||||
/join-chat https://discord.gg/BzQNTqK
|
||||
/join-chat https://discord.gg/home-assistant
|
||||
/suggest-community-highlight https://docs.google.com/forms/d/e/1FAIpQLSd9VWPeVM0xg0swWL6kT3wkQUKt8vWsTL5WtPO95LAy-0cYZw/viewform
|
||||
/get-blueprints https://community.home-assistant.io/c/blueprints-exchange/53
|
||||
/latest-security-alert /blog/2021/01/23/security-disclosure2/
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user