diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml index c34d9a26072..0df08aad5fd 100644 --- a/.github/workflows/test.yml +++ b/.github/workflows/test.yml @@ -10,7 +10,7 @@ jobs: - name: Check out files from GitHub uses: actions/checkout@v2.4.0 - name: Setting up Node.js - uses: actions/setup-node@v2.5.1 + uses: actions/setup-node@v3.0.0 with: node-version: 16.x cache: "npm" @@ -27,7 +27,7 @@ jobs: - name: Check out files from GitHub uses: actions/checkout@v2.4.0 - name: Setting up Node.js - uses: actions/setup-node@v2.5.1 + uses: actions/setup-node@v3.0.0 with: node-version: 16.x cache: "npm" diff --git a/Gemfile.lock b/Gemfile.lock index e0eaf25d779..03b8cba6bad 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -48,7 +48,7 @@ GEM jekyll-commonmark (1.4.0) commonmarker (~> 0.22) jekyll-paginate (1.1.0) - jekyll-sass-converter (2.1.0) + jekyll-sass-converter (2.2.0) sassc (> 2.0.1, < 3.0) jekyll-sitemap (1.4.0) jekyll (>= 3.7, < 5.0) diff --git a/source/_integrations/denonavr.markdown b/source/_integrations/denonavr.markdown index be07e8c5d7d..1c39c056c2f 100644 --- a/source/_integrations/denonavr.markdown +++ b/source/_integrations/denonavr.markdown @@ -26,6 +26,7 @@ Known supported devices: - Denon AVR-X1400H - Denon AVR-X1500H - Denon AVR-X1600H +- Denon AVR-X1700H - Denon AVR-X2000 - Denon AVR-X2100W - Denon AVR-X2200W @@ -74,6 +75,7 @@ Known supported devices: - Marantz NR1506 - Marantz NR1602 - Marantz NR1604 +- Marantz NR1606 - Marantz NR1607 - Marantz NR1710 - Other Denon AVR receivers (untested) diff --git a/source/_integrations/derivative.markdown b/source/_integrations/derivative.markdown index e8032a79aa7..d2517e51305 100644 --- a/source/_integrations/derivative.markdown +++ b/source/_integrations/derivative.markdown @@ -60,7 +60,7 @@ unit: required: false type: string time_window: - description: The time window in which to calculate the derivative. This is useful for sensor that output discrete values. By default the derivative is calculated between two consecutive updates. + description: The time window in which to calculate the derivative. Derivatives in this window will be averaged with a Simple Moving Average algorithm weighted by time. This is for instance useful for a sensor that outputs discrete values, or to filter out short duration noise. By default the derivative is calculated between two consecutive updates without any smoothing. default: 0 required: false type: time diff --git a/source/_integrations/generic.markdown b/source/_integrations/generic.markdown index 3770e0e7718..a0d827a4ebd 100644 --- a/source/_integrations/generic.markdown +++ b/source/_integrations/generic.markdown @@ -95,9 +95,10 @@ In this section, you find some real-life examples of how to use this camera plat camera: - platform: generic name: Weather - still_image_url: https://www.yr.no/place/Norway/Oslo/Oslo/Oslo/meteogram.svg + still_image_url: https://www.yr.no/en/content/1-72837/meteogram.svg content_type: "image/svg+xml" ``` +Instructions on how to locate the SVG for your location is available at [developer.yr.no](https://developer.yr.no/doc/guides/deprecating-old-widgets/) ### Local image diff --git a/source/_integrations/google.markdown b/source/_integrations/google.markdown index 0593a44ee85..8a329d108be 100644 --- a/source/_integrations/google.markdown +++ b/source/_integrations/google.markdown @@ -216,7 +216,7 @@ You either use `start_date_time` and `end_date_time`, or `start_date` and `end_d ## Using calendar in automations -A calendar can be used as an external scheduler for special events or reoccurring events instead of hardcoding them in automations. +A calendar can be used as an external scheduler for special events or reoccurring events instead of hardcoding them in automations. The calendar entry must have a duration greater than 1 minute. Events that are 0 minutes long will not trigger the automation. Trigger as soon as an event starts: @@ -242,3 +242,5 @@ For example, the actions following this condition will only be executed for even ``` {% endraw %} + + diff --git a/source/_integrations/google_travel_time.markdown b/source/_integrations/google_travel_time.markdown index 5de5a9f913f..8b4f39a8e59 100644 --- a/source/_integrations/google_travel_time.markdown +++ b/source/_integrations/google_travel_time.markdown @@ -25,6 +25,10 @@ A quota can be set against the API to avoid exceeding the free credit amount. Se {% include integrations/config_flow.md %} +Notes: + +- Origin and Destination can be the address or the GPS coordinates of the location (GPS coordinates have to be separated by a comma). You can also enter an entity ID that provides this information in its state, an entity ID with latitude and longitude attributes, or zone friendly name (case sensitive). + ## Manual Polling Using automatic polling can lead to calls that exceed your API limit, especially when you are tracking multiple travel times using the same API key. To use more granular polling, disable automated polling in your config entry's System Options. To manually trigger a polling request, call the [`homeassistant.update_entity` service](/integrations/homeassistant/#service-homeassistantupdate_entity) as needed, either manually or via automations. diff --git a/source/_integrations/motion_blinds.markdown b/source/_integrations/motion_blinds.markdown index d4561199468..9fa57defcb1 100644 --- a/source/_integrations/motion_blinds.markdown +++ b/source/_integrations/motion_blinds.markdown @@ -29,6 +29,7 @@ Additionally the following brands have been reported to also work with this inte ## Retrieving the API Key +### Motion Blinds app The Motion Blinds API uses a 16 character key that can be retrieved from the official "Motion Blinds" app for [IOS](https://apps.apple.com/us/app/motion-blinds/id1437234324) or [Android](https://play.google.com/store/apps/details?id=com.coulisse.motion). @@ -41,7 +42,14 @@ Please note that "-" characters need to be included in the key when providing it

-Note that it has been reported that the official Bloc Blinds app doesn't seem to hand out the API key on Android, it does seem to provide the API key on the iOS version of the official Bloc Blinds app. +### Brel Home app + +In the Brel Home app on iOS go to the `me` page (home screen 4th tab), on the bottom of this page multi-tap on the “version x.x.x(xxxx)” gray info and a pop-up with the key will be shown. +In the Brel Home app on Android go to the `me` page (home screen 4th tab), tap 5 times on the right side of the photo place and a pop-up with the key will be shown. + +### Bloc Blinds app + +The official Bloc Blinds app doesn't seem to hand out the API key on Android, it does seem to provide the API key on the iOS version of the official Bloc Blinds app. ## Top Down Bottom Up (TDBU) blinds diff --git a/source/_integrations/rfxtrx.markdown b/source/_integrations/rfxtrx.markdown index 80d989f2600..28e114c5521 100644 --- a/source/_integrations/rfxtrx.markdown +++ b/source/_integrations/rfxtrx.markdown @@ -58,10 +58,27 @@ Not all protocols as advertised are enabled on the initial setup of your transce You can host your device on another computer by setting up ser2net and example configuration for ser2net looks like this and then using host/port in your Home Assistant configuration. +Configuration example for ser2net older than 4.x.x (check with command `ser2net -v`): + ```text 50000:raw:0:/dev/ttyUSB0:38400 8DATABITS NONE 1STOPBIT ``` +Configuration example for ser2net 4.x.x: + +```yaml +# Example /etc/ser2net.yaml for proxying USB/serial connections +connection: &rfxtrx + accepter: tcp,5000 + enable: on + options: + kickolduser: true + telnet-brk-on-sync: true + connector: serialdev, + /dev/ttyUSB0, + 38400n81,local +``` + ## Settings options To configure options for RFXtrx integration go to **Configuration** >> **Devices & Services** and press **Options** on the RFXtrx card. diff --git a/source/_integrations/waze_travel_time.markdown b/source/_integrations/waze_travel_time.markdown index c686a21a6be..f89bbb9c148 100644 --- a/source/_integrations/waze_travel_time.markdown +++ b/source/_integrations/waze_travel_time.markdown @@ -20,7 +20,7 @@ The `waze_travel_time` sensor provides travel time from the [Waze](https://www.w Notes: - If a unit system is not specified, the integration will use the unit system configured on your Home Assistant instance. -- Origin and Destination can be the address or the GPS coordinates of the location (GPS coordinates has to be separated by a comma). You can also enter an entity id which provides this information in its state, an entity id with latitude and longitude attributes, or zone friendly name. +- Origin and Destination can be the address or the GPS coordinates of the location (GPS coordinates has to be separated by a comma). You can also enter an entity id which provides this information in its state, an entity id with latitude and longitude attributes, or zone friendly name (case sensitive). - The string inputs for `Substring *` allow you to force the integration to use a particular route or avoid a particular route in its time travel calculation. These inputs are case insensitive matched against the description of the route. - When using the `Avoid Toll Roads?`, `Avoid Subscription Roads?` and `Avoid Ferries?` options be aware that Waze will sometimes still route you over toll roads or ferries if a valid vignette/subscription is assumed. Default behavior is that Waze will route you over roads having subscription options, so best is to set both `Avoid Toll Roads?` and `Avoid Subscription Roads?` or `Avoid Ferries?` if needed and experiment to ensure the desired outcome. diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index d1eb40b954d..c078930ceb0 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -456,8 +456,8 @@ Using a Philips Hue Dimmer Switch or Lutron Connected Bulb Remote is probably th 1. Turn on your Hue bulb/light you want to reset. (It is important that the bulb has just been turned). 2. Hold the Philips Hue Dimmer Switch near your bulb (closer than 10 centimeters / 4 inches). -3. Press and hold the (I)/(ON) and (O)/(OFF) buttons on the Philips Hue Dimmer Switch for about 10 seconds continuously until your bulb starts to blink. On the newer switches hold the I/O and Scene Switch buttons. -4. Your bulb should stop blinking and eventually turn on again. At the same time, a green light on the top left of your remote indicates that your bulb has been successfully reset to factory default settings. +3. Press and hold the (I)/(ON) and (O)/(OFF) buttons on the Philips Hue Dimmer Switch. The bulb should start blinking in 10-20 seconds. The bulb will blink, then turn off, then turn on. You can now release the dimmer buttons. +4. Your bulb is now factor resey and ready for pairing. A green light on the top left of the dimmer remote indicates that your bulb has been successfully reset to factory default settings. Note: If you are not unable to reset the bulb, remove it from the Hue Bridge and retry the procedure. diff --git a/source/_lovelace/statistics-graph.markdown b/source/_lovelace/statistics-graph.markdown index 5b6d226eaff..95dcb8511ff 100644 --- a/source/_lovelace/statistics-graph.markdown +++ b/source/_lovelace/statistics-graph.markdown @@ -43,7 +43,7 @@ chart_type: type: string stat_types: required: false - description: The statistics types to render. `min`, `max`, `mean`, `sum` + description: The statistics types to render. `min`, `max`, `mean`, `sum`, `state` type: list title: required: false