We’re currently in active discussions with Broadlink to support their IR hubs within the Haptique ecosystem, and things are looking positive so far.
Broadlink devices are widely available, affordable, and come with extensive IR code libraries, making them a popular choice for smart home users. As we consider prioritizing this integration, we’d love to hear your thoughts:
• How critical is Broadlink support for your setup?
• Would native Haptique control of Broadlink hubs improve your setup or experience?
Your feedback will help us gauge the demand and shape our development roadmap.
This would certainly help with the weak IR from the remote itself as I currently use Broadlink IR hubs with Home Assistant and they work very well together. Even better, also allow access to the (Broadlink) remote codes learned within HA so no need to repeat the learning process.
Personally, I think it’s much more important to prioritize and focus on making the Haptique® IR Extender, originally advertised on Kickstarter and Indiegogo, finally available and fully usable with the RS90 — rather than investing more time and energy into integrating additional third-party IR systems like Broadlink.
There are already several reliable and well-established IR solutions that can be used with the RS90 today — either directly via existing integrations or through Custom URL Device commands:
Homey Pro (via Cantata integration and Flow control)
IRTrans (via HTTP commands / local API)
SwitchBot Hub Mini (via HTTP API and scene control)
Global Caché Flex (with REST/HTTP interface – also previously mentioned on the roadmap)
I’d also like to remind you that more than a year ago, Tuya support was explicitly promoted on Kickstarter, and Global Caché was listed as part of the official roadmap.
To date — despite the RS90 hardware being released — neither has been implemented.
Rather than constantly opening new development fronts and asking the community to vote on what to add next, I believe it would be far more productive to deliver on the integrations that were already promised and publicly advertised, like Tuya — which, notably, can also be used for IR transmission.
Instead of shifting the responsibility for IR control to external platforms, I would strongly encourage Cantata to focus on completing its own native IR solution. The Haptique® IR Extender was not just a wishlist item — it was a key advertised feature of the campaign, and many backers are still waiting for it to materialize.
All I can tell you is Tuya is not possible on RS90 so we removed this Roadmap from the official website and Kickstarter. Did something changed? Yes a lot. Tuya is such a closed system and it doesn’t allow us to use their devices in our sequences. Recently Homey also posted that Tuya stopped their integration after making it live.
I would appreciate if we stay on the topic.
Our Extenders will take more time so it is better we cover more IR hubs which users are already having. RM mini from broadlink costs $10 compare to other hubs you mentioned.
Broadlink has their own library. You can use it only if you connect it with their cloud. Using with HA is like using it as an I/O but you don’t get to use their library.
Not currently, as far as I can see. Using the RS90 HA integration and searching for the devices I have learned the IR codes for comes up with a blank. (I did look at this to see if it would solve my IR issues)
This is where/how I am learning (and then sending) the codes using the Broadlink IR Hub.)
If I could call the ‘remote.send.command’ with the right parameters then that might be a good solution to the problem, at least for those using HA/Broadlink. (Which, admittedly, may be a small number but at least provides another option…)
This would also allow users to learn their own commands independently and not therefore be restricted by the provided library, similar to other remotes allow - Sofabaton, for example.
@ccsfounder As an owner of a rm4c mini I would love to have the integration.
I also have the device conected to alexa, so I would love that the state of the device was shared between the controls (so that if I turn the tv on with alexa and then want to activate a scene with the RS90 it doesn’t send the on command again).
I know this may not be possible with the rm4c mini as it is just a blaster, but maybe later with a full integration with a home assistant server it could be possible, with the server controlling the states and the interfaces (like alexa or the rs90) just sending the commands.
Anyways, I’m getting out of topic, love the work done so far and hope it continues to improve.