Tracking external integrations

Hi everyone!

At the current pace (well done @prohand, @guim31, and @lmilcent :grinning_face_with_smiling_eyes:), we’re starting to lose track of who’s doing what: we’ve already had a KNX duplicate, and as @GBoulvin mentioned earlier, the list is no longer really up to date.

So I created a 100% automatic tracking page, updated every 6 hours (and on demand):

:backhand_index_pointing_right: Suivi des intégrations Gladys

For each of the 1,190 ideas on @pierre-gilles’s list, it shows:

  • whether it is published in the store, in progress on GitHub, or available;
  • the corresponding Gladys integration, with its cover, author, and link to the repository;
  • the duplicates (multiple repositories for the same idea).

A second tab lists all the Gladys integrations identified (store + in-progress repositories), with their equivalent in the list. There’s a search, filters by status, priority, and category, and an xlsx/CSV export.

No one has to keep anything up to date: the page automatically reads the store, GitHub, and the list. It identifies published and in-progress repositories (created from the template), and it automatically links a Gladys integration to the list idea with the same name.

Where we stand today: 152 ideas out of 1,190 taken or done, 95 P1 out of 115, and 12 duplicates among Gladys integrations (KNX, tado°, Viessmann, Livebox, EcoFlow, Xiaomi Home, Plex, Mealie…).

For this to work, just one habit to adopt: when you take an integration, create the repository on the first day, from the template integration-template-js, with a name like gladys-…. It then appears as « in progress » at the next update, and others see that it’s taken. No form to fill out, no list to update.

:warning: Only create the topic gladys-assistant-integration upon publication: before that, the store would list an empty integration. If you don’t start from the template, the topic gladys-integration-wip has the same effect without affecting the store.

It’s beautiful, thank you

Thanks @Will_71 :ok_hand:

That’s great, thank you so much!

Before, I asked Claude to check before and after creating the modules on the forum, but that wasn’t enough for KNX. With this project, that should prevent that!

After I checked and according to the names, Claude couldn’t make the connection, it’s not perfect yet but it’s already a good base.

And especially since I wanted to launch it tonight but I had no idea what to take, even though there’s still quite a bit left.

I really like this project. The only « issue » is the update frequency, right?
Because at the rate we’re going (even if it’s bound to slow down), 6 hours seems rather long as a launch window.. Or maybe I misunderstood ^^

My bad! I hadn’t seen the button to manually refresh!!

You’re right, I should have taken that parameter and told Claude you were going too fast. After the delay, I can shorten it, but I just left the default value Claude gave me.

Exactly, you can try if it works!

Claude tells me that a 15-minute refresh is possible without risking GitHub API quotas

It’s really well done and it was necessary! Now we can see where we’re going…

Thanks!

Does this take archived repositories into account?

I archived my KNX repo because it was a duplicate and not as good. However, I see other duplicates from other developers who haven’t officially published their modules (no tags, for example).

Not as good, we don’t know, we haven’t had user feedback.
For archives, it will be more counted in duplicates but marked as archived.

For others, it also looks at the name gladys-…
image

I will enforce only looking at the topic because a gladys-… repository is not necessarily an integration

Edit: Claude tells me he looks at the name and then if the gladys-assistant-integration.json file is present.
So for those without the topic, they may not have understood how to add it

Small update to the tracker page following your feedback :backhand_index_pointing_right: Suivi des intégrations Gladys

Update every 15 minutes instead of 6 hours, to keep up with @guim31 :grinning_face_with_smiling_eyes: And a ↻ Refresh button at the top of the page to trigger an update immediately (you need rights on the repository, ask me if needed). There is also a button at the bottom right to go back to the top of the page.

New, more accurate statuses:

  • Published: in the store. It still counts, even without a recent commit.
  • In progress: repository outside the store with a commit in the last 30 days.
  • Outside store, inactive: repository outside the store without a commit for more than 30 days. The integration still counts for its idea, unless it’s a copy of the template never filled out: in that case, the idea becomes free again.
  • Archived: repository archived or deleted on GitHub. It no longer counts, even if the store still lists it (this is the case for @lmilcent’s KNX, archived today: the KNX duplicate has disappeared).

A repository without a topic is only retained if it contains the gladys-assistant-integration.json manifest: a name in gladys-… is not enough.

23 more matches between the list and Gladys integrations with different names (Torrent ↔ qBittorrent / Transmission, Usenet ↔ SABnzbd / NZBGet, Public IP ↔ Cloudflare / Duck DNS, Belgian Mobility ↔ De Lijn…). A partial match no longer counts as a duplicate: Le Vélo complements TBM, it does not duplicate it.

Result: 172 ideas out of 1,190 taken or done, including 97 P1 out of 115, and 11 remaining duplicates: EcoFlow, Heatzy, Livebox, Wake on LAN, Plex, Saunier Duval, tado°, Tuya, Xiaomi Home, Mealie and Viessmann.

Same old habit: create the repository from the template from day one, and only post the gladys-assistant-integration topic when publishing. A match is missing or incorrect? Let me know here.

For my « duplicates », these are users who have never published with the tag or written on the forum.

  • EcoFlow
  • Livebox
  • tado°

For example, with EcoFlow, we can now see that the project hasn’t moved at VV69004 and isn’t published on the store.