hacs integration

.github/workflows/validate.yaml

@@ -0,0 +1,17 @@
+name: Validate
+
+on:
+  push:
+  pull_request:
+  schedule:
+    - cron: "0 0 * * *"
+
+jobs:
+  validate:
+    runs-on: "ubuntu-latest"
+    steps:
+      - uses: "actions/checkout@v2"
+      - name: HACS validation
+        uses: "hacs/action@main"
+        with:
+          category: "integration"

README.md

@@ -4,8 +4,8 @@
 
 Ideas are welcome ! Don't hesitate to create issue to suggest something, it will be really appreciated.
 
-##Installations
-- If you are using HACS, please see https://hacs.xyz/docs/faq/custom_repositories/
+## Installations
+- Through HACS !
 - Otherwise, download the zip from the latest release and copy `multimatic` folder and put it inside your `custom_components` folder.
 
 You can configure it through the UI using integration.
@@ -102,6 +102,12 @@ You can do some find and replace (e.g. `climate.vaillant_bathroom`-> `climate.ba
 ### [1.6.0](https://github.com/thomasgermain/vaillant-component/releases/tag/1.6.0)
 - Supporting HACS (only by custom repository right now). Please be sure to install at least version 1.6.0). See https://hacs.xyz/docs/faq/custom_repositories/ for installations.
 
+### [1.6.1](https://github.com/thomasgermain/vaillant-component/releases/tag/1.6.1)
+- Logos (will be available after next HA release)
+- Version alignment between releases and manifest
+- Integration into the HACS default repositories 
+- Special thanks to [@vit-](https://github.com/vit-)
+
 ## Provided entities
 - 1 water_heater entity, if any water heater: `water_heater.<water heater id>`, basically `water_heater.control_dhw`
 - 1 climate entity per zone (expect if the zone is controlled by room) `climate.<zone id>`

custom_components/multimatic/manifest.json

@@ -14,5 +14,6 @@
   "codeowners": [
     "@thomasgermain"
   ],
-    "version": "1.5.0"
+  "version": "1.6.1",
+  "iot_class": "cloud_polling"
 }