ha-inlite

commit 0f2e85aa7ac4e4ce208e21a6d5f3cc5e76c742cd
parent a8f57db392763ca79fc6aa286129c6b2f66ceb3f
Author: Bennet Brünings <bennet@bbruenings.com>
Date: Thu, 19 Mar 2026 15:50:38 +0100

Fix manifest key ordering for hassfest validation

Keys must be: domain, name, then alphabetical order.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

diff --git a/custom_components/inlite/manifest.json b/custom_components/inlite/manifest.json
index 494c6a1012d21342a8df17eca84f229d05623d00..d8d87c4a970463042a381b92fed09e3ca19b283a 100644
--- a/custom_components/inlite/manifest.json
+++ b/custom_components/inlite/manifest.json
@@ -1,6 +1,12 @@
 {
     "domain": "inlite",
     "name": "in-lite Outdoor Lighting",
+    "bluetooth": [
+        {
+            "local_name": "inlitebt",
+            "connectable": true
+        }
+    ],
     "codeowners": ["@bbruenings"],
     "config_flow": true,
     "dependencies": ["bluetooth"],
@@ -8,12 +14,6 @@     "documentation": "https://github.com/bbruenings/ha-inlite",
     "integration_type": "device",
     "iot_class": "local_polling",
     "issue_tracker": "https://github.com/bbruenings/ha-inlite/issues",
-    "bluetooth": [
-        {
-            "local_name": "inlitebt",
-            "connectable": true
-        }
-    ],
     "requirements": [
         "pycryptodomex>=3.20.0"
     ],