An external broker is more stable, this is something I did not know as a beginner.
Especially because the embedded broker has a memory leak.
It would have saved me a bunch of time and WAF trust issues if I would have had this piece of knowledge.
Issue on memory leak: https://github.com/home-assistant/home-assistant/issues/11594
* add supporting info for 2nd gen august lock
2nd Gen August Lock needs to have the August Connect Module to be able to talk to home-assistant. If you have Doorbell then you don't need to have Connect. Just trying to help people troubleshoot in case they don't know whats going wrong.
* Update syntax
* Pushover: update webpage with clone URL
Hi, Pushover developer here.
I was notified that your app has a Pushover plugins, so I've listed it on our [apps page](https://pushover.net/apps) and enabled cloning for it. Instead of users having to upload an icon and fill in all the fields, users can be directed to https://pushover.net/apps/clone/home_assistant which pre-fills those fields and copies the icon.
I'm not sure if the `date` field in this markdown page needs to be bumped when it's updated, or if it's a creation date.
* Add some other minor changes
- Removed the "(Optional)" tag from the host-Parameter, because it is mandatory now
- Added another configuration example to clarify how to specify multiple configuration variables; the examples in the "multiple bridges..." section do show this already, but this section might be skipped by the majority of users owning only a single bridge.
Proposing changes to steps 8a and 8d. I looked back at previous versions and I don't think these steps were updated when the other steps it was originally referencing were moved/changed.
This text:
SQLite databases do not support native dates. That's why all the dates are saved in seconds since the UNIX epoch. Convert them manually using this site or in Python:
should have a link where it says "this text"
It now reads:
SQLite databases do not support native dates. That's why all the dates are saved in seconds since the UNIX epoch. Convert them manually using [this site](https://www.epochconverter.com/) or in Python:
* Fix ON/OFF being interpreted in binary_sensor.mqtt
YAML interprets `ON` and `OFF` to `true` and `false`. This causes the site to show that instead of the actual default payloads.
* Add header
* sensor.command_line: Round example CPU temperature value
multiply returns a float, which is inexact and sometimes gets rendered
with a lot of decimal places. Round additionally to get cleaner result.
* Move raw
