profile
viewpoint

Arduino-and-RaspberryPi/ESPWebUpdateHttpServer 4

OTA (Over the Air) update of ESP8266 firmware using its (AP)access-point over the HTTP.

last-stand/java-algorithms-usage 3

Use of different encryption, hashing and compression algorithm in Java.

last-stand/invoice-generator-react 1

Consumes https://github.com/last-stand/invoice-generator and generates invoice.

Arduino-and-RaspberryPi/RaspberryPowerControlServer 0

RaspberryPowerControlServer in python to control relay.

Dollyg/TicTacToe 0

Multi-Player Cmd-Line Game Tic-Tac-Toe implemented in Java.

Future-Focus-Tech/FaceRecognitionClient 0

FaceRecognition client using tracking.js

last-stand/Air-Hunter 0

Air Hunter is a simple JavaScript based game.

last-stand/AngularJS 0

Angular JS Examples by Last-Stand

issue commenthome-assistant/home-assistant.io

Missing information why to use the Raspberry Pi Docker image.

Isn't that clear from the naming?

Those images are specifically made to have maximum compatibility and capabilities for these devices.

See for example https://github.com/home-assistant/core/blob/dev/machine/raspberrypi4

MrDiba

comment created time in 26 minutes

issue openedhome-assistant/home-assistant.io

Missing information why to use the Raspberry Pi Docker image.

The problem

When reading the documentation on how to install Home Assistant Core in Docker (link) It is not clear to me why I should use the Raspberry Pi variant over the 'default' one.

I would like to see some introduction to the RPi image as the Docker Hub has no information on the image as well.

What is different between the images and why should I use the RPi image on a Pi as the other image works as well?

created time in 3 hours

PR opened home-assistant/home-assistant.io

Add custom services to dyson documentation

Proposed change

<!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue in the additional information section. -->

  • Add custom services to dyson documentation.
  • Add the missing dyson_speed attribute.
  • Change IOT class of dyson to local push. It uses cloud service once at setup to retrieve credentials and then communicate with devices using local MQTT.

Type of change

<!-- What types of changes does your PR introduce to our documentation/website? Put an x in the boxes that apply. You can also fill these out after creating the PR. -->

  • [ ] Spelling, grammar or other readability improvements (current branch).
  • [ ] Adjusted missing or incorrect information in the current documentation (current branch).
  • [ ] Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • [x] Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • [ ] Removed stale or deprecated documentation.

Additional information

<!-- Details are important, and help maintainers processing your PR. Please be sure to fill out additional details, if applicable. -->

  • Link to parent pull request in the codebase: home-assistant/core#45331
  • Link to parent pull request in the Brands repository:
  • This PR fixes or closes issue:

Checklist

<!-- Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. -->

  • [x] This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • [x] The documentation follows the Home Assistant documentation standards.
+59 -0

0 comment

1 changed file

pr created time in 4 hours

Pull request review commenthome-assistant/home-assistant.io

Added Daikin Madoka integration

+---+title: Daikin Madoka AC+description: Instructions on how to integrate Daikin BRC1H thermostat (madoka) devices with Home Assistant.+ha_category:+  - Climate+  - Sensor+ha_release: 2021.1.4+ha_iot_class: Local Polling+ha_config_flow: true+ha_codeowners:+  - '@mduran80'+ha_domain: daikin_madoka+---++The `Daikin Madoka AC` integration provides support for the Daikin BRC1H thermostats in Home Assistant.++The BRC1H (and its variants) is a thermostat with Bluetooth LE support controlled by mobile apps on Android and iOS.++There is currently support for the following device types within Home Assistant:++- [Climate](#climate)+- [Sensor](#sensor)++## Requirements++- This integration has only been tested on Linux+- Bluetooth adapter+- DBUS support on the system where Home Assistant runs. If run within Docker or custom installation, make sure it is available to your containers by checking that it has access to the dbus(`/var/run/dbus/system_bus_socket` must be present and the container must be run in privileged mode). ++<div class='note'>++* The BRC1H thermostat has requirements:+    * Only one Bluetooth client can be connected at a time. When the thermostat is connected, it is not listed on a Bluetooth devices scan. Therefore, it is required to disconnect and forget any previous connection from the device screen.+    * The Bluetooth pairing requires authorization code and human intervention. The thermostat has to be paired with the system on which the integration is going to be run. For instance, in Linux these steps must be followed:+    * **Remove any previous Bluetooth connections from the thermostat menu.**+    * On the host to be paired, run the following commands in a terminal:+    1. Type `bluetoothctl`+    2. Type `agent off`+    3. Type `agent KeyboardDisplay`+    4. Type `remove <BRC1H_MAC_ADDRESS>`. This step helps to remove unsuccessful previous pairings and makes the device visible.+    5. Type `scan on` and wait until your thermostat Bluetooth MAC address is listed+    6. Type `scan off`+    7. Type `pair <BRC1H_MAC_ADDRESS>`+    8. Type 'yes' when prompted and accept the connection on the thermostat screen. These two actions must be relatively close in time or the thermostat will cancel the operation. The thermostat will be paired with the host.+    ++A dedicated Bluetooth adapter is desirable. If you run Home Assistant in a virtual machine, it makes it easiser for the device to be used. In VMWare, make sure to remove the checkbox "Share Bluetooth devices with guests" so the device is fully available to the virtual machine.++</div>

Added new section, it definitely improved readability

mduran80

comment created time in 6 hours

Pull request review commenthome-assistant/home-assistant.io

Added Daikin Madoka integration

+---+title: Daikin Madoka AC+description: Instructions on how to integrate Daikin BRC1H thermostat (madoka) devices with Home Assistant.+ha_category:+  - Climate+  - Sensor+ha_release: 2021.1.4+ha_iot_class: Local Polling+ha_config_flow: true+ha_codeowners:+  - '@mduran80'+ha_domain: daikin_madoka+---++The `Daikin Madoka AC` integration provides support for the Daikin BRC1H thermostats in Home Assistant.++The BRC1H (and its variants) is a thermostat with Bluetooth LE support controlled by mobile apps on Android and iOS.++There is currently support for the following device types within Home Assistant:++- [Climate](#climate)+- [Sensor](#sensor)++## Requirements++- This integration has only been tested on Linux+- Bluetooth adapter+- DBUS support on the system where Home Assistant runs. If run within Docker or custom installation, make sure it is available to your containers by checking that it has access to the dbus(`/var/run/dbus/system_bus_socket` must be present and the container must be run in privileged mode). ++<div class='note'>++* The BRC1H thermostat has requirements:+    * Only one Bluetooth client can be connected at a time. When the thermostat is connected, it is not listed on a Bluetooth devices scan. Therefore, it is required to disconnect and forget any previous connection from the device screen.+    * The Bluetooth pairing requires authorization code and human intervention. The thermostat has to be paired with the system on which the integration is going to be run. For instance, in Linux these steps must be followed:+    * **Remove any previous Bluetooth connections from the thermostat menu.**+    * On the host to be paired, run the following commands in a terminal:+    1. Type `bluetoothctl`+    2. Type `agent off`+    3. Type `agent KeyboardDisplay`+    4. Type `remove <BRC1H_MAC_ADDRESS>`. This step helps to remove unsuccessful previous pairings and makes the device visible.+    5. Type `scan on` and wait until your thermostat Bluetooth MAC address is listed+    6. Type `scan off`+    7. Type `pair <BRC1H_MAC_ADDRESS>`+    8. Type 'yes' when prompted and accept the connection on the thermostat screen. These two actions must be relatively close in time or the thermostat will cancel the operation. The thermostat will be paired with the host.+    ++A dedicated Bluetooth adapter is desirable. If you run Home Assistant in a virtual machine, it makes it easiser for the device to be used. In VMWare, make sure to remove the checkbox "Share Bluetooth devices with guests" so the device is fully available to the virtual machine.++</div>

I used the note because I think it should be highlighted. If the user does not follow the procedure, the integration will not work. I will reduce the note to just the procedure

mduran80

comment created time in 6 hours

Pull request review commenthome-assistant/home-assistant.io

Added Daikin Madoka integration

+---+title: Daikin Madoka AC+description: Instructions on how to integrate Daikin BRC1H thermostat (madoka) devices with Home Assistant.+ha_category:+  - Climate+  - Sensor+ha_release: 2021.1.4+ha_iot_class: Local Polling+ha_config_flow: true+ha_codeowners:+  - '@mduran80'+ha_domain: daikin_madoka+---++The `Daikin Madoka AC` integration provides support for the Daikin BRC1H thermostats in Home Assistant.++The BRC1H (and its variants) is a thermostat with Bluetooth LE support controlled by mobile apps on Android and iOS.++There is currently support for the following device types within Home Assistant:++- [Climate](#climate)+- [Sensor](#sensor)

I think you can remove this because we have TOC now in the sidebar

mduran80

comment created time in 6 hours

Pull request review commenthome-assistant/home-assistant.io

Added Daikin Madoka integration

+---+title: Daikin Madoka AC+description: Instructions on how to integrate Daikin BRC1H thermostat (madoka) devices with Home Assistant.+ha_category:+  - Climate+  - Sensor+ha_release: 2021.1.4+ha_iot_class: Local Polling+ha_config_flow: true+ha_codeowners:+  - '@mduran80'+ha_domain: daikin_madoka+---++The `Daikin Madoka AC` integration provides support for the Daikin BRC1H thermostats in Home Assistant.++The BRC1H (and its variants) is a thermostat with Bluetooth LE support controlled by mobile apps on Android and iOS.++There is currently support for the following device types within Home Assistant:++- [Climate](#climate)+- [Sensor](#sensor)++## Requirements++- This integration has only been tested on Linux+- Bluetooth adapter+- DBUS support on the system where Home Assistant runs. If run within Docker or custom installation, make sure it is available to your containers by checking that it has access to the dbus(`/var/run/dbus/system_bus_socket` must be present and the container must be run in privileged mode). ++<div class='note'>++* The BRC1H thermostat has requirements:+    * Only one Bluetooth client can be connected at a time. When the thermostat is connected, it is not listed on a Bluetooth devices scan. Therefore, it is required to disconnect and forget any previous connection from the device screen.+    * The Bluetooth pairing requires authorization code and human intervention. The thermostat has to be paired with the system on which the integration is going to be run. For instance, in Linux these steps must be followed:+    * **Remove any previous Bluetooth connections from the thermostat menu.**+    * On the host to be paired, run the following commands in a terminal:+    1. Type `bluetoothctl`+    2. Type `agent off`+    3. Type `agent KeyboardDisplay`+    4. Type `remove <BRC1H_MAC_ADDRESS>`. This step helps to remove unsuccessful previous pairings and makes the device visible.+    5. Type `scan on` and wait until your thermostat Bluetooth MAC address is listed+    6. Type `scan off`+    7. Type `pair <BRC1H_MAC_ADDRESS>`+    8. Type 'yes' when prompted and accept the connection on the thermostat screen. These two actions must be relatively close in time or the thermostat will cancel the operation. The thermostat will be paired with the host.+    ++A dedicated Bluetooth adapter is desirable. If you run Home Assistant in a virtual machine, it makes it easiser for the device to be used. In VMWare, make sure to remove the checkbox "Share Bluetooth devices with guests" so the device is fully available to the virtual machine.++</div>++## Configuration++The Daikin integration can be configured via the Home Assistant user interface (menu Configuration > Integrations) The following fields are available:++- List of devices to be integrated. Specify a comma-separated list of MAC addresses +- Adapter: Name of the Bluetooth adapter to be used for the connections+- Discovery timeout: Scan for Bluetooth devices for the specified interval+- Force device disconnection: It improves the detection of the Bluetooth LE services offered by the device++## Climate++The `daikin madoka` climate platform integrates Daikin air conditioning systems into Home Assistant, enabling control of setting the following parameters:++- [**set_hvac_mode**](/integrations/climate/#service-climateset_hvac_mode) (`off`, `heat`, `cool`, `heat_cool`, or `fan_only`)+- [**target temperature**](/integrations/climate#service-climateset_temperature)+- [**turn on/off**](/integrations/climate#service-climateturn_on)+- [**fan mode**](/integrations/climate#service-climateset_fan_mode) (speed)+- [**swing mode**](/integrations/climate#service-climateset_swing_mode)++Current indoor temperature is displayed.++## Sensor++The `daikin_madoka` sensor platform integrates Daikin air conditioning systems into Home Assistant, enabling displaying the following parameters:++- Indor temperature
- Indoor temperature
mduran80

comment created time in 6 hours

Pull request review commenthome-assistant/home-assistant.io

Added Daikin Madoka integration

+---+title: Daikin Madoka AC+description: Instructions on how to integrate Daikin BRC1H thermostat (madoka) devices with Home Assistant.+ha_category:+  - Climate+  - Sensor+ha_release: 2021.1.4
ha_release: 2021.2

Version number without patch number 😉

mduran80

comment created time in 6 hours

Pull request review commenthome-assistant/home-assistant.io

Added Daikin Madoka integration

+---+title: Daikin Madoka AC+description: Instructions on how to integrate Daikin BRC1H thermostat (madoka) devices with Home Assistant.+ha_category:+  - Climate+  - Sensor+ha_release: 2021.1.4+ha_iot_class: Local Polling+ha_config_flow: true+ha_codeowners:+  - '@mduran80'+ha_domain: daikin_madoka+---++The `Daikin Madoka AC` integration provides support for the Daikin BRC1H thermostats in Home Assistant.++The BRC1H (and its variants) is a thermostat with Bluetooth LE support controlled by mobile apps on Android and iOS.++There is currently support for the following device types within Home Assistant:++- [Climate](#climate)+- [Sensor](#sensor)++## Requirements++- This integration has only been tested on Linux+- Bluetooth adapter+- DBUS support on the system where Home Assistant runs. If run within Docker or custom installation, make sure it is available to your containers by checking that it has access to the dbus(`/var/run/dbus/system_bus_socket` must be present and the container must be run in privileged mode). ++<div class='note'>++* The BRC1H thermostat has requirements:+    * Only one Bluetooth client can be connected at a time. When the thermostat is connected, it is not listed on a Bluetooth devices scan. Therefore, it is required to disconnect and forget any previous connection from the device screen.+    * The Bluetooth pairing requires authorization code and human intervention. The thermostat has to be paired with the system on which the integration is going to be run. For instance, in Linux these steps must be followed:+    * **Remove any previous Bluetooth connections from the thermostat menu.**+    * On the host to be paired, run the following commands in a terminal:+    1. Type `bluetoothctl`+    2. Type `agent off`+    3. Type `agent KeyboardDisplay`+    4. Type `remove <BRC1H_MAC_ADDRESS>`. This step helps to remove unsuccessful previous pairings and makes the device visible.+    5. Type `scan on` and wait until your thermostat Bluetooth MAC address is listed+    6. Type `scan off`+    7. Type `pair <BRC1H_MAC_ADDRESS>`+    8. Type 'yes' when prompted and accept the connection on the thermostat screen. These two actions must be relatively close in time or the thermostat will cancel the operation. The thermostat will be paired with the host.+    ++A dedicated Bluetooth adapter is desirable. If you run Home Assistant in a virtual machine, it makes it easiser for the device to be used. In VMWare, make sure to remove the checkbox "Share Bluetooth devices with guests" so the device is fully available to the virtual machine.++</div>

This seems too big to put in a note

mduran80

comment created time in 6 hours

Pull request review commenthome-assistant/home-assistant.io

Added Daikin Madoka integration

+---+title: Daikin Madoka AC+description: Instructions on how to integrate Daikin BRC1H thermostat (madoka) devices with Home Assistant.+ha_category:+  - Climate+  - Sensor+ha_release: 2021.1.4+ha_iot_class: Local Polling+ha_config_flow: true+ha_codeowners:+  - '@mduran80'+ha_domain: daikin_madoka+---++The `Daikin Madoka AC` integration provides support for the Daikin BRC1H thermostats in Home Assistant.++The BRC1H (and its variants) is a thermostat with Bluetooth LE support controlled by mobile apps on Android and iOS.++There is currently support for the following device types within Home Assistant:++- [Climate](#climate)+- [Sensor](#sensor)++## Requirements++- This integration has only been tested on Linux+- Bluetooth adapter+- DBUS support on the system where Home Assistant runs. If run within Docker or custom installation, make sure it is available to your containers by checking that it has access to the dbus(`/var/run/dbus/system_bus_socket` must be present and the container must be run in privileged mode). ++<div class='note'>++* The BRC1H thermostat has requirements:+    * Only one Bluetooth client can be connected at a time. When the thermostat is connected, it is not listed on a Bluetooth devices scan. Therefore, it is required to disconnect and forget any previous connection from the device screen.+    * The Bluetooth pairing requires authorization code and human intervention. The thermostat has to be paired with the system on which the integration is going to be run. For instance, in Linux these steps must be followed:+    * **Remove any previous Bluetooth connections from the thermostat menu.**+    * On the host to be paired, run the following commands in a terminal:+    1. Type `bluetoothctl`+    2. Type `agent off`+    3. Type `agent KeyboardDisplay`+    4. Type `remove <BRC1H_MAC_ADDRESS>`. This step helps to remove unsuccessful previous pairings and makes the device visible.+    5. Type `scan on` and wait until your thermostat Bluetooth MAC address is listed+    6. Type `scan off`+    7. Type `pair <BRC1H_MAC_ADDRESS>`+    8. Type 'yes' when prompted and accept the connection on the thermostat screen. These two actions must be relatively close in time or the thermostat will cancel the operation. The thermostat will be paired with the host.+    ++A dedicated Bluetooth adapter is desirable. If you run Home Assistant in a virtual machine, it makes it easiser for the device to be used. In VMWare, make sure to remove the checkbox "Share Bluetooth devices with guests" so the device is fully available to the virtual machine.++</div>++## Configuration++The Daikin integration can be configured via the Home Assistant user interface (menu Configuration > Integrations) The following fields are available:
The `Daikin Madoka AC` integration can be configured via the Home Assistant user interface, menu **Configuration** -> **Integrations**. The following fields are available:
mduran80

comment created time in 6 hours

issue closedhome-assistant/home-assistant.io

Missing configuration alternative for ZHA

The problem

<!-- There are undocumented configurations parameters in regards to configuring ZHA. -->

There are multiple configurations parameters that can be see in regards to the ZHA integration with zigpy.

See here: https://github.com/zigpy/zigpy/issues/154

zha:
  zigpy_config:
    database_path: /path/to/your/zigbee.db

    device:
      path: /dev/serial/by-id/yourPort
      #baudrate: 12345         # Most radios have a default for this
      #flow_control: software  # Optional for some radios


    #################################################
    # Everything past this point is set by default. #
    #  You probably don't need to change anything.  #
    #################################################


    # OTA config. Nothing is enabled by default
    ota:
      ikea_provider: false                       # Auto update Trådfri devices
      ledvance_provider: false                   # Auto update LEDVANCE devices
      #otau_directory: /path/to/your/ota/folder  # Utilize .ota files to update everything else

    # Default network settings
    network:
      channel: 15             # What channel the radio should try to use.
      channels: [15, 20, 25]  # Channel mask
      extended_pan_id: null   # Will be set to a random value if not provided
      key: null
      key_sequence_number: 0  # Used by some radios to indicate that the key has been updated
      pan_id: null            # Will be set to a random value if not provided
      tc_address: null
      tc_link_key: [0x5A, 0x69, 0x67, 0x42, 0x65, 0x65, 0x41, 0x6C, 0x6C, 0x69, 0x61, 0x6E, 0x63, 0x65, 0x30, 0x39]
      update_id: 0            # Used by some radios to indicate that the network config has been updated

    # Used by zigpy-znp
    znp_config:
      tx_power: 0  # Max is +19
      sync_request_timeout: 5
      auto_reconnect_retry_delay: 5
    
    # Used by bellows
    source_routing: false
    ezsp_config: {}  # Tons and tons of options
                     # See https://github.com/zigpy/bellows/blob/dev/bellows/config/ezsp.py

It would have been nice to update the documentaion regarding the possibility of channel change,

closed time in 6 hours

prilly-dev

issue commenthome-assistant/home-assistant.io

Missing configuration alternative for ZHA

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved. If this issue is still relevant, please let us know by leaving a comment 👍 This issue has now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

prilly-dev

comment created time in 6 hours

pull request commenthome-assistant/home-assistant.io

Added Daikin Madoka integration

I think I found it. It was an actual "change base" by editing the PR and changing the target branch, right?

mduran80

comment created time in 7 hours

PR opened home-assistant/home-assistant.io

Bump ruby2_keywords from 0.0.2 to 0.0.4

Bumps ruby2_keywords from 0.0.2 to 0.0.4. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/ruby/ruby2_keywords/commit/31766f4327e6e4555543b44fc6a5dc252c8ff6d9"><code>31766f4</code></a> bump up to 0.0.4</li> <li><a href="https://github.com/ruby/ruby2_keywords/commit/8bf4b5b4169545ef5be46dec8cd6502d902a3e4a"><code>8bf4b5b</code></a> Added bump target</li> <li><a href="https://github.com/ruby/ruby2_keywords/commit/fba8eb45d6b2db2d0f829b0d20300e7d19268146"><code>fba8eb4</code></a> Build package</li> <li><a href="https://github.com/ruby/ruby2_keywords/commit/403ff84d12c9fe1f34397b3a164b0b2f73a560d1"><code>403ff84</code></a> Set SOURCE_DATE_EPOCH to make builds reproducible</li> <li><a href="https://github.com/ruby/ruby2_keywords/commit/956156ba793330928280c5301b093300a1a9f792"><code>956156b</code></a> Add Ruby 2.5 to the CI matrix</li> <li><a href="https://github.com/ruby/ruby2_keywords/commit/d6d1775d793bcaf206af700120b0b4bd2dc3842d"><code>d6d1775</code></a> Fix Ruby 2.5 incopatibility</li> <li><a href="https://github.com/ruby/ruby2_keywords/commit/396cc7991604632bc686e3c363504db42337cca3"><code>396cc79</code></a> Added tests</li> <li><a href="https://github.com/ruby/ruby2_keywords/commit/aa06490df9efa905ef17c143e96edee547c4ffad"><code>aa06490</code></a> Fixed RDoc location</li> <li><a href="https://github.com/ruby/ruby2_keywords/commit/9603fec096b257d382776c09ab1f5fe88d289307"><code>9603fec</code></a> Make README.md the main page</li> <li><a href="https://github.com/ruby/ruby2_keywords/commit/5093cd212b44d1fbd8ef1c6b3f2bfa8f3427de16"><code>5093cd2</code></a> Added least documents</li> <li>Additional commits viewable in <a href="https://github.com/ruby/ruby2_keywords/compare/v0.0.2...v0.0.4">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

+1 -1

0 comment

1 changed file

pr created time in 10 hours

PR opened home-assistant/home-assistant.io

Bump textlint-rule-terminology from 2.1.4 to 2.1.5

Bumps textlint-rule-terminology from 2.1.4 to 2.1.5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/sapegin/textlint-rule-terminology/releases">textlint-rule-terminology's releases</a>.</em></p> <blockquote> <h2>v2.1.5</h2> <h2><a href="https://github.com/sapegin/textlint-rule-terminology/compare/v2.1.4...v2.1.5">2.1.5</a> (2021-01-19)</h2> <h3>Bug Fixes</h3> <ul> <li>Support excluding terms declared as arrays (<a href="https://github-redirect.dependabot.com/sapegin/textlint-rule-terminology/issues/29">#29</a>) (<a href="https://github.com/sapegin/textlint-rule-terminology/commit/18ddf4a196b7642845f3c5aed76665ebe0350788">18ddf4a</a>), closes <a href="https://github-redirect.dependabot.com/sapegin/textlint-rule-terminology/issues/24">#24</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/sapegin/textlint-rule-terminology/commit/18ddf4a196b7642845f3c5aed76665ebe0350788"><code>18ddf4a</code></a> fix: Support excluding terms declared as arrays (<a href="https://github-redirect.dependabot.com/sapegin/textlint-rule-terminology/issues/29">#29</a>)</li> <li><a href="https://github.com/sapegin/textlint-rule-terminology/commit/c3f366a2c153f9260544861e84cc0006864263d8"><code>c3f366a</code></a> Chore(deps): Bump yargs-parser from 13.1.1 to 13.1.2 (<a href="https://github-redirect.dependabot.com/sapegin/textlint-rule-terminology/issues/27">#27</a>)</li> <li><a href="https://github.com/sapegin/textlint-rule-terminology/commit/11868b327a162d51fc24538af06f58e0052fe253"><code>11868b3</code></a> Chore(deps): Bump lodash from 4.17.15 to 4.17.19 (<a href="https://github-redirect.dependabot.com/sapegin/textlint-rule-terminology/issues/26">#26</a>)</li> <li>See full diff in <a href="https://github.com/sapegin/textlint-rule-terminology/compare/v2.1.4...v2.1.5">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

+17 -17

0 comment

2 changed files

pr created time in 10 hours

pull request commenthome-assistant/home-assistant.io

Updated to use condition attributes released in 0.115.

Hi @dannytsang,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

dannytsang

comment created time in 19 hours

PR opened home-assistant/home-assistant.io

Updated to use condition attributes released in 0.115.

Proposed change

Updated documentation to use condition attributes released in 0.115.

Type of change

<!-- What types of changes does your PR introduce to our documentation/website? Put an x in the boxes that apply. You can also fill these out after creating the PR. -->

  • [ ] Spelling, grammar or other readability improvements (current branch).
  • [ ] Adjusted missing or incorrect information in the current documentation (current branch).
  • [ ] Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • [ ] Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • [ ] Removed stale or deprecated documentation.

Additional information

<!-- Details are important, and help maintainers processing your PR. Please be sure to fill out additional details, if applicable. -->

  • Link to parent pull request in the codebase:
  • Link to parent pull request in the Brands repository:
  • This PR fixes or closes issue:

Checklist

<!-- Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. -->

  • [ ] This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • [ ] The documentation follows the Home Assistant documentation standards.
+4 -2

0 comment

1 changed file

pr created time in 19 hours

pull request commenthome-assistant/home-assistant.io

Add troubleshooting to share scenes in google home

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. Thank you for your contributions.

scribblrsam

comment created time in 20 hours

pull request commenthome-assistant/home-assistant.io

Added Daikin Madoka integration

Yeah i can't see the PR updated. I don't have much experience with git so any help would be appreciated.

I rebased the four commits from my branch to mduran80:next using 'git rebase --onto next current patch-1' and pushed the changes. I can see them on my "next" branch (local and origin) but I don't understand how to push those to home-assistant.io:next. Any suggestion?

mduran80

comment created time in 20 hours

PR opened home-assistant/home-assistant.io

Add link from MQTT discovery to Scenes.mqtt.markdown

Proposed change

Minor docs fix, missing link to new(-ish) scene mqtt discovery docs.

Type of change

<!-- What types of changes does your PR introduce to our documentation/website? Put an x in the boxes that apply. You can also fill these out after creating the PR. -->

  • [ ] Spelling, grammar or other readability improvements (current branch).
  • [ ] Adjusted missing or incorrect information in the current documentation (current branch).
  • [ ] Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • [ ] Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • [ ] Removed stale or deprecated documentation.

Additional information

<!-- Details are important, and help maintainers processing your PR. Please be sure to fill out additional details, if applicable. -->

  • Link to parent pull request in the codebase:
  • Link to parent pull request in the Brands repository:
  • This PR fixes or closes issue:

Checklist

<!-- Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. -->

  • [ ] This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • [ ] The documentation follows the Home Assistant documentation standards.
+1 -0

0 comment

1 changed file

pr created time in 20 hours

PR opened home-assistant/home-assistant.io

Add MiHome devices token App for Windows and MACOS

Proposed change

Add Windows and MACOS App

Type of change

Dokumentation

+4 -0

0 comment

1 changed file

pr created time in 21 hours

pull request commenthome-assistant/home-assistant.io

Added Daikin Madoka integration

After rebase you push the changes from the patch-1 branch, your changes will then automatically appear in this pull request.

mduran80

comment created time in a day

PR closed home-assistant/home-assistant.io

Update volkszaehler Stale in-progress needs-rebase next

Proposed change

<!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue in the additional information section. --> Update Docu volkszaehler, only needed if code-owner acceppt pull request.

Type of change

<!-- What types of changes does your PR introduce to our documentation/website? Put an x in the boxes that apply. You can also fill these out after creating the PR. -->

  • [ ] Spelling, grammar or other readability improvements (current branch).
  • [ ] Adjusted missing or incorrect information in the current documentation (current branch).
  • [ ] Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • [X] Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • [ ] Removed stale or deprecated documentation.

Additional information

<!-- Details are important, and help maintainers processing your PR. Please be sure to fill out additional details, if applicable. -->

  • Link to parent pull request in the codebase:
  • Link to parent pull request in the Brands repository:
  • This PR fixes or closes issue:

Checklist

<!-- Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. -->

  • [ ] This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • [ ] The documentation follows the Home Assistant documentation standards.
+1887 -117

1 comment

54 changed files

bbr111

pr closed time in a day

pull request commenthome-assistant/home-assistant.io

Added Daikin Madoka integration

I just rebased the changes, I didn't notice the branch on the browser. Do I have to PR again?

mduran80

comment created time in a day

pull request commenthome-assistant/home-assistant.io

Added Daikin Madoka integration

Please rebase your branch to the next branch

mduran80

comment created time in a day

pull request commenthome-assistant/home-assistant.io

Update volkszaehler

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. Thank you for your contributions.

bbr111

comment created time in a day

pull request commenthome-assistant/home-assistant.io

Update raspberry-pi.markdown

Hi @geolemon,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

geolemon

comment created time in a day

more