You have devices that are not compatible with Gladys and do not use an open protocol like Zigbee or Matter? No panic.
I created a Matterbridge plugin factory powered by an AI, which automatically develops plugins for your devices. No development skills required.
Prerequisites: Matterbridge must be installed and configured. If this is not yet the case, first follow this tutorial in the documentation.
How it works?
You open a GitHub ticket to describe your device, the AI develops the plugin overnight, and you just have to test it. If something goes wrong, you leave a comment and the AI iterates.
Links: if you know of similar plugins on other projects (Home Assistant, Homebridge…), add the links. The more context you provide, the more relevant the result will be on the first try.
Features: describe what you want to control. Examples: temperature, on/off, humidity, brightness…
Additional context: optional field, but useful if your device has peculiarities.
Tip: if you don’t know what to put in the links, specify it in the description and ask the AI to search itself. But the more precise you are, the better the result will be.
Step 2: Install and Test the Plugin
The factory runs every morning and processes one plugin per pass. Once yours is developed, the AI will reply directly on the ticket with a download link:
I think the plugin factory is working pretty well, but we’re not moving fast enough: the main issue today is that we lack requests! It’s a shame because every minute the factory isn’t running, I keep paying Claude and the server for nothing.
Another point: starting June 15th, Claude will restrict the use of programmatic subscriptions. What I’m currently doing with the factory will therefore become much more complicated. I’ll either have to find a way around these limitations or switch to token-based billing, which is likely to be very expensive.
To speed things up, I asked the AI to identify the most important integrations based on:
forum requests;
the most popular integrations in other ecosystems.
I then automatically generated 29 integration specifications that will be developed in the coming days, trying to make the most of the remaining generation windows with my Pro subscription.
In short, we have 5 days left to make the most of it!!
It might be an integration for Gladys, but I don’t think it will be in Matterbridge, which is really for devices that can have corresponding Matter clusters
To download the plugin, click on the link! If you test the plugin, follow the tutorial at the top of this post, and if you have feedback, you can leave it directly in the GitHub ticket; the AI will make any necessary fixes
cozytouch plug-in, but it actually does everything (with feedback for Somfy IO)
It’s certain that when I see a plug-in called Overkiz, I think it must do everything, so I’ll test it.
However, we’re going to have redundancies everywhere with all these plug-ins, it’s going to be a bit of a mess on the matterbridge side (but not at Gladys).
On the maintenance side, how is it going to work?
I know we’ve already talked about it, but there will need to be a check (daily, hourly?) to see if the sources of a third-party project like Overkiz make updates and then the factory will decide to prepare an update.
I don’t know if it’s feasible in the process though.
And on my side, I haven’t had time to prepare anything for a new MELCloud Home plug-in that integrates the new APIs and the old ones
And that would be really useful to me because the Melcloud Home app is really …. terrible.
When testing Tasmota, I first tried Matterbridge. Not too complicated, but couldn’t the Matterbridge pairing code go directly into the Gladys Matter integration? I really struggled to understand how it worked, and since we’re in Gladys, it would be one less weird step…
With my water heater, I can’t use Overkiz because my version is recent and directly connected to the Wi-Fi box to access the internet. I don’t have a Cozytouch hub.
There is a version with and without a hub. New Atlantic devices will no longer have a hub in the future.
I think that if an integration breaks, for now the user can go back to the discussion and indicate that it’s broken so that Claude can fix it
In fact, just like we would if it was a developer maintaining the integration!
Not sure if Matterbridge’s APIs allow that ^^
After that, it shouldn’t be too magical either, because the user needs to understand how one communicates with the other.
We have great tutorials on the subject in the documentation, for example the Somfy integration explains step by step how to pair Matterbridge with Gladys:
I’m not necessarily in agreement with your point of view, especially if we want Gladys to be as easy to use as possible for the average user.
Providing information that indicates the container has been created, that pairing in the Matter integration has been done by Gladys, and that it is now possible to install and configure the matterbridge plugins to find devices in Gladys in the Matter integration, would really remove a beautiful thorn in the side for those who don’t have much computer knowledge.
As for the matterbridge plugins, it’s like for a smartphone app: you have to configure and enter your login/password, which is less confusing for a beginner.
Well, that’s my very personal opinion, I start from the principle that most things should be simple to get people to adopt a product/service.
Issues · GladysAssistant/matterbridge-ai-plugin-factory · GitHub
It’s a shame because every minute the factory isn’t running, I keep paying Claude and the server for nothing. 
