* Added troubleshooting info
The `INVALID_CLIENT: Invalid redirect URI` error can occur when the URL, for example, contains a port number. This can happen if the port number is set in the Base_URL attribute of the HTTP integration.
* Convert text to note box
* ✏️ Tweak
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
* Update synology.markdown
It is also possible to run Hass.io in a VM on Synology using the VDI image.
* Update source/_docs/installation/synology.markdown
Co-Authored-By: Klaas Schoute <klaas_schoute@hotmail.com>
Co-authored-by: Klaas Schoute <klaas_schoute@hotmail.com>
certbot-auto appears to no longer be the preferred method to install certs, certbot is now the recommended method (https://github.com/certbot/certbot/issues/6933#issuecomment-481243457)
I've also added an additional chmod that I had to add to allow Home Assistant to read the cert files, as otherwise I got the error:
Invalid config for [http]: file not readable for dictionary value @ data['http']['ssl_key'].
* Update streamlabswater.markdown
I didn't know about the API costs when I purchased the device, so this warning may help others make a more informed decision if they want to buy this product based on it's HA integration like I did.
* Moved warning from description to a note box
Wasn't sure if a note box, or a warning box was appropriate, so just used a normal note box. I also added a link to their subscription page instead of specifically listing the prices. That way if the prices change the docs don't need updated.
* Update streamlabswater.markdown
Fixed broken URL from previous edit
* ✏️ Tweak
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
* added note about name variable
I though that name is just for frontend and spent some time finding out where my sensor had gone when I had changed its name.
Hope it will save others' time.
Actually, I don't think this component's approach is great - would be much more intuitive to have name as a key of a dictionary (as with template sensors, for example) and a friendly_name for UI.
Unfortunately, there are many of similar components - perhaps they are older than current template sensor's implementation?
* links -> relative
* ✏️ Tweak
Co-authored-by: Klaas Schoute <klaas_schoute@hotmail.com>
* Add documentation for new opnsense component
This commit adds documentation for the opnsense device tracker which is
being added in home-assistant/home-assistant#26834.
* Update source/_components/opnsense.markdown
Co-Authored-By: Klaas Schoute <klaas_schoute@hotmail.com>
* Fixes from review comments
* More updates from code review
The previous updates in dc933232ab654d79a27cc0a16f8ca13b16196d46 around
the defaults were applied a bit too mechanically and the same problem
existed elsewhere in the configuration section. This commit also updates
those to fix the same issue there.
* ✏️ Tweaks
* Move documentation to new integrations location
* Remove LAN default for tracker_interfaces
Part of the review changes made to the PR adding this component was to
not set a default value for the tracker_interfaces to ["LAN"]. This
commit just updates the configuration section of the docs to reflect
this change.
* Update opnsense.markdown
Co-authored-by: Klaas Schoute <klaas_schoute@hotmail.com>
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
