Hello,
I bought 2 RM4 mini units to control the TV/Dyson in the living room and the heat pump in the master bedroom.
However, I saw that only the TV appeared in the list of devices:
Hi 
Your Dyson is already controllable via Matter, right?
Which brand is your heat pump?
Regarding the Broadlink integration, it was originally developed by @AlexTrovato, who has been a bit less available since he became a dad.
If we want this integration to keep evolving, someone would need to take the lead on development.
If anyone reading this would like to contribute, feel free to jump in 
yes and also via IR. For now I have more features via the remote control than via Matter, which hasn’t implemented all the functions (speed +/-, auto/manual mode, timer, oscillation angle).
haha, it’s Innova, an unknown Italian brand
It’s a standalone heat pump with a single indoor unit and one external intake and one outlet, controllable via IR.
I used to control it via Jeedom + Orvibo AllOne and I want to switch to Gladys + Broadlink RM4 mini (well the RM4 is already in place now).
I tested with the Broadlink app and it works very well, now all that’s left is to switch to Gladys ^^
yes I had seen the posts about Broadlink.
I tried assigning the different IR signals to a TV device (and it’s OK via the test buttons in the integration) but on the dashboard you can do nothing except on/off 
and that’s where the problem lies.
I’m not a dev (right, I already said that? 
) but I’d be interested in looking into it.
Do you think that with AI assistance it could work?
I remember your livecoding on Matter and the AI did some very strange things…
Anyway, I can help but not do 100% of the development.
Not at all 
I have a lot of dev work planned on the core, and on the integration side I dedicate all my availability to Matter, which for me is the future.
The ideal would be for Broadlink to adapt to Matter; this kind of proprietary API, to me, is not the future at all…
I see several possibilities for you!
In the long run, I’m really betting that 100% of products will be Matter, so products with a non-standard, proprietary API — I really don’t believe in them and I’m not investing in them personally 
[quote=« pierre-gilles, post:4, topic:9685 »]
[
Oops sorry 
No, not planned either!
There had been a start of development by the same developer who did the Broadlink integration a few years ago, but it didn’t come to fruition:
Hi @pierre-gilles
I saw in another thread that you talk about a remote control for music:
Is there a way to control the features of a Broadlink device with Gladys’ native functions in remote control mode?
I’m a bit lost about what can be done with what you show:
EDIT :
yes, I really don’t understand how it works 
Basically, if you write an external tool (or use Node-RED), yes, it’s possible to use these native functions with a Broadlink
@mutmut Would you like us to look at this together to set it up at your place?
With Node-RED + node-red-contrib-broadlink-control (node) - Node-RED, it should be fairly easy to set up
Otherwise, if you want, it could be coded with AI + Matterbridge, I think, but it requires a bit more skill and willingness.
Hi @pierre-gilles, it would be my pleasure because I’d like to automate turning on my devices with one click depending on their state, and also be able to have a good portion of the individual functions of my different remote controls on a single dashboard page.
I’m not super comfortable with Node-RED but I watched some tutorials about it and I can tinker.
On the other hand, does that mean the learning would happen via Node-RED and no longer via Gladys, is that right?
If so, and in my case where I want to use my RM4mini for the devices, Gladys’s Broadlink integration would no longer be useful to me (if I followed the reasoning correctly).
Well, it’s not the desire that’s missing here
As I said, I tinker.
I have a few questions about this dev:
In both cases, how do we control via the dashboard?
Ok, we could make scenes but I can’t see myself creating a scene for each function/button of my remotes. For a sequence of functions, scenes are fine.
There should be a remote control, a remote control widget more precisely, where we’d put the buttons we need (play, vol+, source, P-, oscillation, etc.), and if that’s not in a future dev, I struggle to see how I could manage my devices without an overcomplicated mess 
Exactly Everything is explained in the Node-RED module documentation: node-red-contrib-broadlink-control (node) - Node-RED
Yes! The Gladys Matter integration must already handle this type of devices.
For now the Matter integration supports these functions: Intégrer des appareils Matter dans Gladys Assistant | Gladys Assistant
Matterbridge!
If you use the MQTT + Node-RED integration, you will have a device directly usable on the dashboard, no need to create scenes. Same for Matter.
In my opinion, the Node-RED route is the right one in your case, coding a Matterbridge plugin with AI would probably be a bit complicated for you I think
Don’t hesitate if you have any questions while configuring all that!
[quote=« pierre-gilles, post:11, topic:9685 »]
[quote=« mutmut, post:10, topic:9685 »]
Who should the learning go through:
Hi @mutmut, we crossed paths — I just opened a similar request without seeing your topic, so I’m centralizing here all the Broadlink needs as I see them:
These leads had already been identified at the time of the service development (points 1, 3, and 4 were in a GitHub backlog, never finalized). With the arrival of external integrations, there may be a great project here for a motivated developer from the community; the widget (point 2) is part of Gladys’ core.
Analyzed and consolidated with the help of Claude (AI) — reviewed and validated by me.
Given your precise points, I’ll go change the category of this post to Feature Request and close the ones you opened if you’re okay with that.
Correction, it would be better to close this one and add your points to your request.
Do your best then but let’s avoid duplicates indeed.
Feature request via external integration:
