* Add Hass.io on generic Linux server as installation method
Also renamed Hass.io to Hass.io on HassOS because Hass.io can be installed in different ways.
* Remove information about HassOS for Hass.io install
* Move Hass.io generic Linux server install to alternative install methods
This makes more clear that: 1) https may be needed rather than http, 2) data is not needed for a webhook trigger to function, and 3) "curl" is a good way to test it. Hoping to save other people some of the time I spent figuring out how to get it to work.
The current structure leads to confusion, which parts apply to Hass.io, or Hassbian, or ... As discussed in the architecture issue, I've moved all the platform specific parts to the end, even for those that require no actions.
I've also:
* moved the details for how to find the appropriate device path, and highlighting the likely default paths
* linked to a useful site that'll generate the content for the key, for those not using Linux
* stripped out the duplication of statements about the first run
* reordered the Hass.io section to put the GUI actions first, with a "you can also use the command line" rather than the other way around
* added details of how to pass the stick through on Docker
* put in a Community install section for other Linux, and Mac. Removed RancherOS
* expanded the wall of text note explaining the `ls` output so that you can actually follow it
* Added docs for command line auth provider
Regards home-assistant/home-assistant#19985
* Added reference to a compatible script for LDAP authentication
* Added note about stderr with command_line auth provider
* Added note about stripping usernames
* Note that usernames are stripped with command_line auth provider
The `for:` piece can be confusing for folks, providing the examples as human readable time, and mentioning that days and milliseconds are also supported.
* Big bad install index rewrite
Following on from [this](https://github.com/home-assistant/architecture/issues/126#issuecomment-457819615) here is the first pass.
I've:
* Restructured the layout, simplifying the intro slightly, and moving more of the relevant things to know up there
* Removed redundant information
* Used slightly emotive _tier_ language, deliberately
* Put in a line and put the community provided guides underneath it
Feedback appreciated if this doesn't hit the mark
* Removed tier wording
* Manual -> Virtualenv
* Tweaks
Removed the out of context block about the sun, under the time pattern. It doesn't appear to fit anywhere, and appeared in the RC merge.
Added warning about `00` and so on
* Add encoding parameter to mqtt automation #20292
This is needed to trigger on received images/other byte payloads via mqtt because otherwise the decode fails. See also
#16004
* Update trigger.markdown
clarify
* Update trigger markdown to expand twilight discussion and sunrise timing
These changes expand on the sun angle for addition darkness by including detail on the three twilight definitions. A brief discussion has also been added to the time trigger section to explain why many automations that are relative to sunrise often fail. Since sunrise is a different day than any time before midnight, using timestamps is a reasonable option.
* Minor changes
* ✏️ Tweaks
* Split interval triggers from time trigger
* Default smaller interval units to zero
* Rename interval to schedule
* Rename schedule trigger to time_pattern
