I agree that we can clearly improve the existing integration
We’ll have to see if the Matterbridge API allows it, otherwise we’ll have to scrape the Matterbridge container logs to find the code
guim31
June 11, 2026, 8:04pm
22
I just tested the Reolink integration since I have 3 cameras from this brand.
I’m having trouble understanding what has been developed. I end up with a lot of features whose purpose I don’t understand.
But I don’t really know what to write on Github to help the team.
I thought the Reolink integration would eventually allow me to view a camera stream, and maybe even change some settings. But if I’m mistaken, I’m off track ^^
Matterbridge implements Matter clusters: in practice, it mainly translates between the features exposed by Reolink and the features standardized by Matter.
Regarding the video stream, this is a very recent feature of Matter (introduced with Matter 1.5). To my knowledge, no consumer camera actually implements it yet today. Gladys is not yet compatible with this part of the standard, and for Matterbridge I’m not sure either (to be verified).
So, it doesn’t surprise me that there is no video stream exposed via Matter.
For camera settings, it’s the same principle: for them to be reported in Matter, there must be a corresponding Matter cluster. If the standard does not provide this feature, or if it is not implemented in Matterbridge, it cannot be exposed.
That said, I already find the result very nice! Being able to retrieve a motion sensor from a Reolink camera via Matter is practical!!
guim31
June 12, 2026, 6:52am
24
Ok, I understand the logic behind all this.
However, what is quite disturbing and not intuitive at all, is that I have 3 switches whose function I have no idea about, but also that regarding motion detection: it is disabled on my camera (since I use Frigate for that) and incidentally I could only add one camera… and I have 3 « motion sensors »
Maybe look in the plugin’s .tar.gz file, maybe there’s a README with explanations of what the plugin does
guim31
June 12, 2026, 7:04am
26
I looked at the readme but it only seems to contain instructions on how the plugin is created
Leave a comment at the factory asking to add information to the README on how the plugin works and that explains each feature!
If it works well, we can add this to the prompt as a standard.
guim31
June 12, 2026, 9:19am
31
Well… the factory has decided it’s not listening to me ^^ I don’t have anything more in the readme.
Yet when I go snooping on GitHub, I can see the changes:
Is this issue related?
✅ Result: The README documentation has been written. However, I'm blocked from completing the build/test: `npm install` requires your approval (it's repeatedly returning "haven't granted it yet"), and without it `tsc` isn't available to build.
That said, this allows me to read that logically, if you add 1 camera, you should have 1 channel. But I added 1 camera and I end up with multiple channels.
I’ll try to point that out to the factory
There might be 2 READMEs, the main thing is that you see the content on GitHub
guim31
June 12, 2026, 1:46pm
33
I added a response on GitHub… by adding screenshots, and I don’t even know if the AI used knows how to use them ^^
We’ll see what happens
All plugins have been developed, except for « Sensibo » which never worked. I need to check why.
Feel free to test them and provide feedback directly on the issue
mutmut
June 15, 2026, 9:42am
35
It’s D-day, have you seen the restrictions it implies?
No plugins generated/edited today so far, so I don’t know
From what I’ve read, there will apparently be a different quota for programmatic uses of Claude Code. We’ll see if this breaks the plugin factory model or if it remains sufficient!
For now, I’m spending €25.59/month on the plugin factory (€3.99/month for Hetzner server + €21.60 for Claude Code)
I remind you that there are 28 plugins waiting for testers:
Overkiz (Somfy TaHoma local API)
HomeWizard
KNX
TP-Link Tapo / Kasa
Philips Hue
WLED
Tasmota
ESPHome
SwitchBot
Tado
Netatmo
Enphase Envoy
iRobot Roomba
Freebox (Player & Freebox OS)
Withings
WiZ (Philips WiZ)
Lutron Caséta
Google Nest
Ring
Reolink
Ecobee
Govee BLE
LIFX
August / Yale Smart Lock
VeSync (Levoit, Etekcity, Cosori)
Belkin Wemo
Viessmann ViCare
AVM FRITZ!Box
I left a comment for Withings
Unfortunately, I can’t test the other integrations because I don’t own those products.
Oh, the change isn’t happening after all
guim31
June 16, 2026, 7:26am
39
It’s definitely been eventful at Anthropic between this and Fable/Mythos ^^
New « Ajax Systems » plugin:
ouvert 09:05AM - 19 Jun 26 UTC
ready-for-testing
plugin-request
ai-factory
## Device/Service Name
Ajax Systems (alarmes et domotique sécurité : Hub, détec… teurs, sirènes, relais, prises)
## Existing Integrations & Documentation
### npm (Node.js)
Pas de client Ajax dédié sur npm. Stack recommandée pour porter le protocole gRPC de l'app mobile :
- **@grpc/grpc-js** — client gRPC Node.js : https://www.npmjs.com/package/@grpc/grpc-js
- **@grpc/proto-loader** — chargement des `.proto` : https://www.npmjs.com/package/@grpc/proto-loader
Référence d'implémentation à porter en TypeScript : **Aegis for Ajax** (Python, protocole app mobile, stream temps réel).
### Autres références
- **Aegis for Ajax** (gRPC, compte utilisateur, sans clé Enterprise) : https://github.com/bvis/aegis-hass
- **Ajax Security co-branded** (variante gRPC, apps white-label ADT/G4S/Protegim…) : https://github.com/bvis/ajax-cobranded-hass
- **Ajax Systems — API officielle** (User API / PRO API, clé sur demande) : https://ajax.systems/api-request/ — https://github.com/exabird/ha-ajax-systems
- **Home Assistant SIA** (écoute locale du hub, **sans** armement/désarmement) : https://www.home-assistant.io/integrations/sia/
- Serveur gRPC cloud Ajax : `mobile-gw.prod.ajax.systems:443`
- Documentation produits : https://ajax.systems/
**Hubs supportés :** Hub, Hub 2, Hub 2 Plus, Hub 2 4G, Hub Hybrid, Hub Mega, etc.
**Apps co-brandées :** chaque app envoie un **application label** au cloud (ex. `Ajax` pour l'app officielle, ou labels ADT, G4S, Protegim…). Obligatoire pour l'authentification gRPC.
## Device Capabilities
**Centrale d'alarme :**
- États : désarmé, armé total (away), mode nuit, groupes / espaces
- Armement / désarmement (avec code PIN si configuré)
- Force arm (ignorer capteurs ouverts) — option avancée
**Capteurs (selon modèle) :**
- Porte / fenêtre (DoorProtect, DoorProtect Plus…)
- Mouvement (MotionProtect, MotionCam, CombiProtect…)
- Fumée / CO / chaleur (FireProtect)
- Inondation (LeaksProtect)
- Bris de vitre (GlassProtect)
- Vibrations, anti-masquage, sabotage (tamper), contacts externes
**Actionneurs :**
- Relais, WallSwitch, prises connectées (Socket) — on/off multi-canaux
- Variateurs (dimmer) — luminosité
**Sirènes :**
- HomeSiren, StreetSiren — déclenchement (si exposé par l'API)
**Hub / connectivité :**
- État réseau : Ethernet, Wi-Fi, GSM/4G
- Alimentation secteur / batterie hub
- Niveau batterie et signal des périphériques
**Caméras (optionnel, hors MVP) :**
- MotionCam Photo on Demand (capture photo, pas de flux vidéo Matter)
## Additional Context
**Objectif Gladys :** exposer l'alarme Ajax et ses capteurs en Matter pour pilotage depuis Gladys (armement, états capteurs, automatisations).
### Modes de connexion
| Mode | Description | Arm/disarm |
|------|-------------|------------|
| **gRPC cloud** (app mobile) | Email + mot de passe + app label — recommandé pour utilisateurs | Oui |
| **API officielle Ajax** | Clé User API ou PRO API (`https://api.ajax.systems/api`) | Oui |
| **Protocole SIA** | Hub envoie les événements vers Gladys/Matterbridge (IP locale) | Non (écoute seule) |
**Recommandation MVP :** gRPC cloud (comme Aegis) — pas de clé Enterprise, compte utilisateur standard.
### Authentification (gRPC)
1. Email + mot de passe du compte Ajax (ou app co-brandée)
2. **Application label** de l'app (ex. `Ajax` pour l'app officielle)
3. 2FA TOTP si activé sur le compte
4. Connexion stream persistante sur `mobile-gw.prod.ajax.systems:443`
5. Commandes arm/disarm via requêtes gRPC on-demand
```typescript
// Stack cible — pas de SDK npm Ajax existant ; porter la logique depuis aegis-hass
import * as grpc from '@grpc/grpc-js';
import * as protoLoader from '@grpc/proto-loader';
// Auth → liste hubs/espaces → subscribe stream capteurs → commandes arm/disarm
```
**⚠️** Protocole non officiel (reverse-engineered). Stocker refresh token / session de façon persistante.
### Mapping Matter
| Ajax | Matter |
|------|--------|
| Alarm panel (arm/disarm/night) | IAS / Security system (best effort) |
| Door / window sensor | Contact Sensor |
| Motion sensor | Occupancy Sensor |
| Smoke / CO | Smoke CO Alarm |
| Water leak | Water Leak Detector |
| Glass break / tamper | Boolean State |
| Relay / socket / WallSwitch | On/Off Plug-in Unit |
| Dimmer | Dimmable Light |
| Battery level | Power Source |
| Temperature | Temperature Measurement |
| Hub power (mains/battery) | Power Source / Boolean State |
**Pas de flux vidéo Matter** pour MotionCam.
### Priorité MVP
1. Auth (email/password + app label + 2FA UI)
2. État centrale + arm away / disarm / night mode
3. Capteurs porte + mouvement (états temps réel via stream)
4. Niveau batterie des périphériques
5. Relais / prises on/off (si présents sur l'installation)
### Limitations
- Pas d'API publique documentée sans demande de clé (route gRPC = protocole app mobile)
- **Cloud obligatoire** en mode gRPC — pas d'API locale type Developer Mode
- Protocole peut changer sans préavis (comme Ring / August)
- App label requis pour les apps co-brandées (ADT, G4S, etc.)
- SIA permet du local mais sans contrôle de l'alarme
- Sécurité critique — tester soigneusement arm/disarm et codes PIN
## Confirmations
- [x] I have provided links to existing integrations in other projects
- [x] I have verified the API documentation is accessible
- [x] I understand this is an automated AI process and results may vary
- [x] I am willing to test the generated plugin and provide feedback
Requested by someone on X here , developed in 15 minutes by AI