From a405c03c31605acc976e20dfd45f88dc60041ace Mon Sep 17 00:00:00 2001 From: Edward Brown Date: Sat, 2 Sep 2023 13:21:04 +0100 Subject: [PATCH] Fix README links --- README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 32f5a89..c64968a 100644 --- a/README.md +++ b/README.md @@ -54,7 +54,8 @@ Blueprints, Helpers and Templates (on the Home Assistant side). You can see how much work creating such guides involves by seeing how it was [heroically undertaken by Blakadder](https://blakadder.com/proscenic-in-home-assistant/), as -compared with the [full `haco`-based equivalent](/configs/proscenic_t21.py). +compared with +the [full `haco`-based equivalent](https://github.com/fmtr/haco/blob/release/haco/configs/proscenic_t21.py). With `haco`, on the other hand, the thorny parts of the initial setup are abstracted away and your final configuration can often be shared via a single script. Below is a list of some of the tasks that `haco` @@ -165,7 +166,8 @@ Whichever type you use, assigning them to a device is done as we saw above. ### Built-In Modules `haco` ships with a small number of built-in configurations. These can be found in -the [configs directory](tree/release/haco/configs) in this repo. But in the likely event that your device hasn't already +the [configs directory](https://github.com/fmtr/haco/blob/release/haco/configs) in this repo. But in the likely event +that your device hasn't already been added, you'll need to define your own. :information_source: The aim is to expand the number of built-in configurations over time. So if you define your own (