Merge branch 'current' into next

This commit is contained in:
Franck Nijhof 2020-08-05 15:20:17 +02:00
commit 760bdc3d11
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
4 changed files with 91 additions and 41 deletions

View File

@ -6,42 +6,42 @@
"appID": "UTQFCBPQRF.io.robbie.HomeAssistant.dev",
"paths": [
"/ios/*",
"/nfc/*"
"/tag/*"
]
},
{
"appID": "UTQFCBPQRF.io.robbie.HomeAssistant.beta",
"paths": [
"/ios/*",
"/nfc/*"
"/tag/*"
]
},
{
"appID": "UTQFCBPQRF.io.robbie.HomeAssistant",
"paths": [
"/ios/*",
"/nfc/*"
"/tag/*"
]
},
{
"appID": "QMQYCKL255.io.robbie.HomeAssistant.dev",
"paths": [
"/ios/*",
"/nfc/*"
"/tag/*"
]
},
{
"appID": "QMQYCKL255.io.robbie.HomeAssistant.beta",
"paths": [
"/ios/*",
"/nfc/*"
"/tag/*"
]
},
{
"appID": "QMQYCKL255.io.robbie.HomeAssistant",
"paths": [
"/ios/*",
"/nfc/*"
"/tag/*"
]
}
]

View File

@ -235,7 +235,9 @@ Here are the modes that are currently available:
- dry
- eco
### Troubleshooting the request_sync service
### Troubleshooting
#### 404 errors on request sync
Syncing may fail after a period of time, likely around 30 days, due to the fact that your Actions on Google app is technically in testing mode and has never been published. Eventually, it seems that the test expires. Control of devices will continue to work but syncing may not. If you say "Ok Google, sync my devices" and get the response "Unable to sync Home Assistant" (or whatever you named your project), this can usually be resolved by going back to your test app in the [Actions on Google console](https://console.actions.google.com/) and clicking `Simulator` under `TEST`. Regenerate the draft version Test App and try asking Google to sync your devices again. If regenerating the draft does not work, go back to the `Action` section and just hit the `enter` key for the URL to recreate the Preview.
@ -249,7 +251,19 @@ The `request_sync` service may fail with a 404 if the `project_id` of the HomeGr
4. Generate a new API key.
5. Again, create a new project in the [Actions on Google console](https://console.actions.google.com/). Described above. But at the step 'Build under the Actions SDK box' choose your newly created project. By this, they share the same `project_id`.
### Troubleshooting with NGINX
#### 403 errors on request sync
The `request_sync` service may fail with a 403 if the HomeGraph API is not enabled. Go to [Google API Console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview) and verify that HomeGraph API is enabled for your project.
#### 404 errors on report state
If you receive 404 errors linked to reporting state in your log, Home Assistant is reporting state for entities that were never synced to Google. Ask your Google Home to `Sync my devices` or run the service `google_assistant.request_sync`.
#### Error during linking: "Could not update the setting. Please check your connection"
Your fulfillment URL may be invalid or unreachable. Recheck the `Fulfillment URL` as specified in [Manual Setup](#manual-setup) and verify that it's publicly reachable.
#### NGINX
When using NGINX, ensure that your `proxy_pass` line *does not* have a trailing `/`, as this will result in errors. Your line should look like:
@ -258,3 +272,7 @@ When using NGINX, ensure that your `proxy_pass` line *does not* have a trailing
### Unlink and relink
If you're having trouble with *Account linking failed* after you unlinked your service, try clearing the browser history and cache.
### Failed linking - Could not update the setting. Please check your connection
If you're having trouble linking your account, with the error message `Could not update the setting. Please check your connection` after logging into your Home Assistant instance, try setting `expose_by_default: false` then exposing a single simple device (light or switch preferably). It is also worth checking if any home ad blocker is disabled if you are having issues.

View File

@ -3,6 +3,7 @@ title: Nextcloud
description: Instructions on how to integrate Nextcloud monitor api data into Home Assistant.
ha_category:
- Sensor
- Binary Sensor
ha_iot_class: Cloud Polling
ha_release: 0.108
ha_domain: nextcloud

View File

@ -51,8 +51,23 @@ theme:
## Elements
Elements are the active components (icons, badges, buttons, text, etc.) that overlay the image.
There are several different element types that can be added to a Picture Elements card:
- [State Badge](#state-badge)
- [State Icon](#state-icon)
- [State Label](#state-label)
- [Service Call Button](#service-call-button)
- [Icon](#icon-element)
- [Image](#image-element)
- [Conditional](#conditional-element)
- [Custom](#custom-elements)
### State Badge
This element creates a badge representing the state of an entity.
{% configuration %}
type:
required: true
@ -64,7 +79,7 @@ entity:
type: string
style:
required: true
description: Position and style the element using CSS.
description: '[Position and style the element](#how-to-use-the-style-object) using CSS.'
type: map
default: "position: absolute, transform: translate(-50%, -50%)"
title:
@ -85,7 +100,9 @@ double_tap_action:
type: map
{% endconfiguration %}
### Icon representing an entity state
### State Icon
This element represents an entity state using an icon.
{% configuration %}
type:
@ -158,12 +175,14 @@ double_tap_action:
type: map
style:
required: true
description: Position and style the element using CSS.
description: '[Position and style the element](#how-to-use-the-style-object) using CSS.'
type: string
default: "position: absolute, transform: translate(-50%, -50%)"
{% endconfiguration %}
### Label with state text
### State Label
This element represents an entity's state via text.
{% configuration %}
type:
@ -205,13 +224,15 @@ double_tap_action:
type: map
style:
required: true
description: Position and style the element using CSS.
description: '[Position and style the element](#how-to-use-the-style-object) using CSS.'
type: string
default: "position: absolute, transform: translate(-50%, -50%)"
{% endconfiguration %}
### Service Call Button
This entity creates a button (with arbitrary text) that can be used to call a service.
{% configuration %}
type:
required: true
@ -231,13 +252,15 @@ service_data:
type: map
style:
required: true
description: Position and style the element using CSS.
description: '[Position and style the element](#how-to-use-the-style-object) using CSS.'
type: string
default: "position: absolute, transform: translate(-50%, -50%)"
{% endconfiguration %}
### Icon Element
This element creates a static icon that is not linked to the state of an entity.
{% configuration %}
type:
required: true
@ -269,13 +292,15 @@ double_tap_action:
type: map
style:
required: true
description: Position and style the element using CSS.
description: '[Position and style the element](#how-to-use-the-style-object) using CSS.'
type: string
default: "position: absolute, transform: translate(-50%, -50%)"
{% endconfiguration %}
### Image Element
This creates an image element that overlays the background image.
{% configuration %}
type:
required: true
@ -333,7 +358,7 @@ aspect_ratio:
default: "50%"
style:
required: true
description: Position and style the element using CSS.
description: '[Position and style the element](#how-to-use-the-style-object) using CSS.'
type: string
default: "position: absolute, transform: translate(-50%, -50%)"
{% endconfiguration %}
@ -370,6 +395,25 @@ elements:
type: list
{% endconfiguration %}
### Custom Elements
The process for creating and referencing custom elements is the same as for custom cards.
Please see the [developer documentation](https://developers.home-assistant.io/docs/frontend/custom-ui/lovelace-custom-card.html)
for more information.
{% configuration %}
type:
required: true
description: 'Card name with `custom:` prefix (e.g., `custom:my-custom-card`)'
type: string
style:
required: true
description: '[Position and style the element](#how-to-use-the-style-object) using CSS.'
type: string
default: "position: absolute, transform: translate(-50%, -50%)"
{% endconfiguration %}
## Options For Exemptions
{% configuration badges %}
@ -379,27 +423,12 @@ user:
type: string
{% endconfiguration %}
### Custom Elements
## Notes on Element Attributes
{% configuration %}
type:
required: true
description: 'Card name with `custom:` prefix (e.g., `custom:my-custom-card`)'
type: string
style:
required: true
description: Position and style the element using CSS.
type: string
default: "position: absolute, transform: translate(-50%, -50%)"
{% endconfiguration %}
### How to use the style object
The process for creating and referencing custom elements is the same as for custom cards.
Please see the [developer documentation](https://developers.home-assistant.io/docs/frontend/custom-ui/lovelace-custom-card.html)
for more information.
## How to use the style object
Position and style your elements using [CSS](https://en.wikipedia.org/wiki/Cascading_Style_Sheets). More/other keys are also possible.
Position and style your elements using [CSS](https://developer.mozilla.org/en-US/docs/Web/CSS). More/other keys are also possible.
Note, the default style for most elements includes [translate](https://developer.mozilla.org/en-US/docs/Web/CSS/transform-function/translate)(-50%, -50%), which means that the coordinates you provide will set the position of the center of the element.
```yaml
style:
@ -410,7 +439,7 @@ style:
"--paper-item-icon-color": pink
```
## How to use state_image
### How to use state_image
Specify a different image to display based on the state of the entity.
@ -420,7 +449,7 @@ state_image:
"off": /local/living_room_off.jpg
```
## How to use state_filter
### How to use state_filter
Specify different [CSS filters](https://developer.mozilla.org/en-US/docs/Web/CSS/filter)
@ -430,7 +459,7 @@ state_filter:
"off": brightness(50%) hue-rotate(45deg)
```
## How to use click-and-hold
### How to use click-and-hold
If the option `hold_action` is specified, that action will be performed when the entity is clicked and held for half a second or more.
@ -445,7 +474,9 @@ hold_action:
brightness_pct: 100
```
## Example
## Examples
### Example of icons, labels and buttons
```yaml
type: picture-elements
@ -495,7 +526,7 @@ elements:
left: 10%
```
## Images Example
### Images Example
```yaml
type: picture-elements
@ -544,7 +575,7 @@ elements:
width: 5%
```
## Conditional Example
### Conditional Example
```yaml
type: picture-elements