Why do you want to link Redmond and Xiaomi?
Redmond’s smart kettles and Xiaomi’s ecosystem are two popular solutions for home automation, but sharing them often raises questions. Users are faced with the problem of how to make devices from different brands work in the same control system?
The main challenge is that Redmond uses its own communication protocol, and Xiaomi Mi Home works via Zigbee or Wi-Fi. However, there are workarounds, from official adapters to third-party solutions like Home Assistant. We will look at all the relevant methods, including step-by-step instructions with illustrations of processes.
It's important to understand that not all Redmond kettles support integration. M170S Compatible with Xiaomi via the cloud API, RMK-M250 It's going to require additional hardware, and then we're going to figure out which devices we can connect to, and what we're going to need to do that.
Model Compatibility: Which Redmond Dummies Work With Xiaomi?
Before buying adapters or setting up a system, check if your kettle model supports integration.Redmond produces several lines of smart kettles, but only a fraction of them can interact with the Xiaomi ecosystem:
- 🔌 SkyKettle M170S/M172S — Supports Wi-Fi and Cloud Management through API Redmond, you can connect to Mi Home through IFTTT or Home Assistant.
- 🔌 RMK-M250/M252 — Requires Redmond Gateway for integration, and can connect to Xiaomi via Home Assistant with a Redmond Cloud plugin.
- ❌ RMK-170/175 — Outdated models without cloud services. Integration is impossible.
- ⚠️ SkyKettle G200S — It only works with Google Home and Alice, and Xiaomi will need an intermediate server.
If your model is not listed, check its specifications on Redmond’s official website or documentation, and note whether you have Wi-Fi or Zigbee protocol support, which are key conditions for integration.
Connection methods: from simple to complex
There are three main ways to integrate Redmond teapot into Xiaomi ecosystem, depending on your device model, availability of additional equipment and level of technical skills:
- Through the cloud. API + IFTTT — Suitable for Wi-Fi models (e.g. SkyKettle) M170S). No need to purchase additional devices, but depends on the stability of the Internet connection.
- Through the Redmond Gateway, you need to purchase the brand's original gateway, allowing you to manage the kettle locally, without cloud services.
- With Home Assistant, it's a universal solution for power users, requiring server configuration, but providing maximum flexibility.
Let’s consider each method in more detail, indicating the pros and cons.
| Connection method | Equipment required | Pluses | Cons |
|---|---|---|---|
| Cloudy API + IFTTT | Just a kettle with Wi-Fi. | No additional cost, quick setup | Internet addiction, team delays |
| Redmond Gateway Gateway | Teapot + lock (~3 000 ₽) | Local management, stable operation | Additional costs, limited compatibility |
| Home Assistant | The server (Raspberry Pi) + teapot | Maximum flexibility and support for all models | Complicated configuration requires technical knowledge |
💡
If your kettle supports Wi-Fi, start with the method IFTTT — This is the easiest way to check the functionality of the integration before buying additional equipment.
Step-by-step: Connecting through IFTTT
This method is suitable for SkyKettle models M170S/M172S and other cloud-enabled kettles API Redmond, you're gonna need it:
- 📱 Smartphone with Mi Home app installed.
- 🌐 Service account IFTTT (ifttt.com).
- 🔌 Redmond teapot connected to Wi-Fi.
Follow the instructions:
- Create an applet in IFTTT: Go to the site. IFTTT and log in. Press Create. → If This: Search for Redmond and select Redmond Cloud. Select a trigger, such as Kettle turned on).
- Set up the action for Xiaomi: Click Then That and find the Xiaomi Mi Home service. Select an action like Turn on a smart plug. Link the action to a specific device in Mi Home (like the smart socket that the kettle is connected to).
Save and test the applet
- Press Continue. → Finish.
- Turn on the kettle manually - check if the action worked in Mi Home.
☑️ Preparation for setup IFTTT
Limitations of the method:
- Delay of execution of commands up to 5-10 seconds (depends on the servers) IFTTT).
- Not all kettle functions are available (e.g. setting the exact temperature).
- When the Internet is shut down, management will become impossible.
How to speed up the work of IFTTT?
Connection via Redmond Gateway
If you need local management without depending on cloud services, purchase the original Redmond Gateway. RG-R450S). It allows you to connect Redmond devices with other smart home systems, including Xiaomi.
To adjust, follow the algorithm:
- Connect the gateway to the router: Put the gateway into the socket next to the router. Wait for the indicator on the case to flash blue (pairing mode).
- Add the gateway to the Ready for Sky app: Download the Ready for Sky app (official website). Register or log in. Click Add Device → Gateway and follow instructions.
- Connect the kettle to the gateway: In the Ready for Sky app, click Add Device → Choose a model of a kettle. Hold the button on the kettle for 5 seconds until the Wi-Fi indicator flashes.
Integrate the gateway with Xiaomi
- In Home Assistant or Node-RED, set up the Redmond Gateway plugin.
- Use it. MQTT-broker for transferring commands between the gateway and Mi Home.
⚠️ Note: The Redmond Gateway does not support direct connection to Mi Home without middleware.
Critical detail: gateway RG-R450S It only works with 2019 Redmond devices and newer ones. Check the serial number of the kettle on the manufacturer's website.
Advanced configuration via Home Assistant
For power users, the best option is Home Assistant, which allows you to combine devices from different brands, including Redmond and Xiaomi, into a single ecosystem.
- 🖥️ Server (e.g. Raspberry Pi 4 with Home Assistant installed) OS).
- 🔌 Redmond teapot with Wi-Fi support or Redmond Gateway.
- 📡 Xiaomi Mi Gateway (if you use Xiaomi devices on Zigbee).
Instructions for setting:
- Install the Redmond component: # Add to configuration.yaml redmond: username: your email@mail.ru password: your password scan_interval: 30 Reboot the Home Assistant.
- Set up integration with Xiaomi: # Add to Configuration.yaml xiaomi_aqara: gateways: - key: yours_Mi_Home_key The key can be obtained in the Mi Home application (Device About section). → Public access).
- Create automation: Go to Settings → Automation. Add a trigger (e.g., the teapot turned on). Select an action (e.g., Turn on Xiaomi smart lamp).
Advantages of the method:
- Local management without depending on clouds.
- Support for all functions of the kettle (temperature, timer, lock).
- The ability to create complex scenarios (for example, “if the kettle boils, turn on music and tell through Xiaomi Speaker”).
⚠️ Warning: When setting up Home Assistant, disable two-factor authentication in your Xiaomi account – it can block access to your home assistant. API. Use a complex password instead of 2FA.
Solving common problems
When integrating Redmond kettle and Xiaomi gateway, users often encounter common mistakes.
| Problem. | Possible cause | Decision |
|---|---|---|
| The teapot is not on the Ready for Sky app | Outdated device firmware | Update the teapot software through the official Redmond app |
| Teams from Mi Home not being followed | Wrong setup IFTTT or Home Assistant | Check the server logs, recreate the applet in IFTTT |
| Redmond Gateway does not connect to Wi-Fi | Incompatible Wi-Fi standard (e.g. 5 GHz) | Switch router to 2.4 GHz mode or use guest network |
| Home Assistant can't see the kettle | Incorrect credentials in configuration.yaml | Check your email and password and enable debugging (logger: default: debug) |
If none of these methods worked, try the following:
- Reset the kettle to factory settings (hold the power button for 10 seconds).
- Update the Xiaomi Mi Gateway to the latest version.
- Contact Redmond with error logs (use the Export Logs feature in Home Assistant).
💡
90% of connectivity problems are solved by resetting devices and checking network settings. Start with basic steps before you delve into the complex diagnostics.