* added dismiss topic for service
This file change will be linked to a PR which enhances the `persistent notification` with a "dismiss" service
* Changed the description as requested
Hope you find this version more acceptable. Maybe you can suggest a more suiting description?
* Doc for nad7050 component
Initial commit.
* removed volume_step
* Revert "removed volume_step"
This reverts commit 3594e7b94a7da2c3d16060f3d831cd79bd45abc4.
* reader volume_step
* simplified example
* renamed component
* Made description more generic.
* more stuff
* Set release version
* Update sensor.fritzbox_callmonitor.markdown
Added a configuration example for callmonitor push notifications
* Update sensor.fritzbox_callmonitor.markdown
Added raw/endraw as suggested by @fabaff. Elaborated notification text a bit more.
* If the used influxdb is configured to use authentication the user needs read/write permissions on the database. Mention this in the doc.
* The influxdb documentation has a */latest* link. Use this instead of a fixed version number.
The docs previously suggested a "generalized" service name for updating flux manually, when the name is actually determined by the name of the switch in the config.
* updating docs to show how to use position attribute in template
Conflicts:
source/_components/cover.mqtt.markdown
* updating docs
Conflicts:
source/_components/cover.mqtt.markdown
The "state" used to be an alias for "to" but this was deprecated to make the
meaning more clear.
This commit updates the examples to no longer use the deprecated name.
* Update light.markdown
I had a hard time setting up attributes to entities until I research for some other user's examples and saw they were using "data:". I feel like this should be mentioned or at least exposed with an example. I saw being used in 2 different ways:
```yaml
action:
service: light.turn_on
data:
entity_id: light.kitchen_lights
brightness: 200
```
```yaml
action:
- service: light.turn_on
entity_id: light.kitchen_lights
data:
brightness: 200
```
I'm not sure which one is the best/correct way but tried with both and they work
* Fix typos
I had to explicitly set `listen_port: 80` for Google Home to work properly. It was defaulting to port 8300 without that declaration.
Also the docs should be more explicit in the Troubleshooting section because the URLs you need to confirm for Google Home are actually
- http://<HA IP Address>:80/description.xml
- http://<HA IP Address>:80/api/pi/lights
