homebridge-roborock-vacuum 2.2.6 → 2.2.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,23 @@
1
1
  # Changelog
2
2
 
3
+ ## 2.2.8
4
+
5
+ - **New**: Project website in English, Traditional Chinese and Japanese: [tasict.github.io/homebridge-roborock-vacuum](https://tasict.github.io/homebridge-roborock-vacuum/). It is now the plugin's homepage in the Homebridge UI
6
+ - **New**: You can now support the plugin by buying me a boba (paid by card, no PayPal account needed) or with PayPal: from the bottom of the plugin settings, the donate link in the Homebridge UI, the README or GitHub's Sponsor button
7
+ - **Change (packaging)**: The npm package no longer contains a development test script, a leftover client ID file or the protocol sniffing helper; it now holds only what the plugin needs to run
8
+ - **Docs**: README rewritten around the current feature set — supported models (with corrected names such as Qrevo Curv), requirements matching the supported Homebridge and Node.js versions, the sign-in flow, and a reference of every config option. The header image is now the plugin's own icon
9
+ - **Change (config UI)**: The settings page describes what it is for, and has a small support footer below the settings
10
+
11
+ ## 2.2.7
12
+
13
+ - **Fix (connectivity)**: The plugin no longer fails to start when the Roborock cloud is unreachable. Startup used to abandon everything after the home-data request timed out (`AxiosError: timeout of 20000ms exceeded`, `ECONNRESET`), so no accessories were registered and every command was refused with "Adapter not inited" — even though the vacuum was reachable on the LAN the whole time. The home data (device list and local keys) is now cached on disk, and when the cloud fetch fails the plugin starts in **local-only mode** from that cache: it still runs LAN discovery, connects to each vacuum over the local protocol, publishes the accessories, and accepts start/stop/dock commands. Cloud-only features (scenes, push updates, fresh online flags) resume by themselves once the cloud answers again, without a Homebridge restart. One successful online start is needed to seed the cache; with no cache the plugin stays idle as before, now with a message that says why
14
+ - **Fix (connectivity)**: A vacuum the plugin is locally connected to is treated as online even when the cached cloud status says otherwise, so commands and polling are not blocked by a stale offline flag during a cloud outage
15
+ - **Fix (connectivity)**: Local-only mode no longer depends on UDP discovery finding the vacuums. Each device's last known LAN address is cached next to the device list, so vacuums on another VLAN (or when port 58866 is taken by another integration on the same host) are still dialed directly while the cloud is down
16
+ - **Fix (connectivity)**: Local-only mode also works without a cloud session. When the login itself fails while the cloud is down (or the cached session was cleared), the plugin still starts from the cache and logs in again on the periodic refresh once the cloud answers. Only network-level login failures are retried; a rejected login or a pending two-factor prompt is left to the Config UI
17
+ - **Fix (connectivity)**: A degraded cloud no longer costs you the session. The cached session is cleared only when the login API explicitly rejects it with an API error code. An empty or malformed answer, and a `401` from the device API that the login API does not confirm, are treated as transient and retried
18
+ - **Fix (connectivity)**: The cached device list is tagged with the account it was fetched for and ignored after switching accounts, so a local-only start never controls another account's vacuums
19
+ - **Fix (logging)**: During an outage the periodic home-data refresh logs its failure once at error level and then at debug level until the cloud answers again, instead of an error every interval. The signed device API now times out after 20 s instead of hanging on a black-holed connection
20
+
3
21
  ## 2.2.6
4
22
 
5
23
  - **New Feature**: The Roborock region is now detected automatically from the account email when no endpoint is configured — the config UI's Region selector gains an "Auto detect (recommended)" option and new installs no longer need to know which server their account lives on. An explicitly chosen region keeps working exactly as before, and if detection fails the plugin falls back to the previous US default with a hint to pin the region manually. Two-factor login also benefits: it now sends the account's real registered country from the detection response instead of guessing it from the endpoint host (which mapped every EU account to Germany)
@@ -45,7 +63,7 @@ Maintenance release — no functional changes to device control. Reworks the fou
45
63
 
46
64
  ## 2.2.0
47
65
 
48
- Connectivity and device-support release, porting recent fixes from the python-roborock and ioBroker.roborock upstream projects (see `UpstreamReview-2026-07.md`).
66
+ Connectivity and device-support release, porting recent fixes from the python-roborock and ioBroker.roborock upstream projects.
49
67
 
50
68
  - **New Feature**: Docks introduced since 2025 (Qrevo Curv, Saros 10, Qrevo S5V, Saros 20, and other new dock type codes 10–40) now get their dust-collection, mop-wash, and drying features — including the dock mop-wash switch. Unknown future dock types default to full-featured instead of featureless
51
69
  - **New Feature**: Room names now resolve for vacuums shared from another Roborock account (fetched via the device-share rooms API), so Matter room cleaning and the current-room publisher work on shared devices
package/README.md CHANGED
@@ -1,82 +1,88 @@
1
- # homebridge-roborock-vacuum
1
+ <p align="center">
2
+ <img src="https://raw.githubusercontent.com/tasict/homebridge-roborock-vacuum/master/branding/icon.png" width="96" height="96" alt="">
3
+ </p>
2
4
 
3
- ![Roborock Vacuum in Home App](https://is1-ssl.mzstatic.com/image/thumb/Purple211/v4/40/21/71/40217177-c879-f670-bd01-c93acfabc31e/AppIcon-0-0-1x_U007emarketing-0-8-0-85-220.png/460x0w.webp)
5
+ # Homebridge Roborock Vacuum
4
6
 
5
- A Homebridge plugin to integrate your Roborock vacuum cleaner with Apple HomeKit, allowing you to control it via the Home app and Siri.
7
+ **Website: [tasict.github.io/homebridge-roborock-vacuum](https://tasict.github.io/homebridge-roborock-vacuum/)** (English, 繁體中文, 日本語)
6
8
 
7
- ## Introduction
9
+ [![npm version](https://img.shields.io/npm/v/homebridge-roborock-vacuum?color=%23cb3837&label=npm)](https://www.npmjs.com/package/homebridge-roborock-vacuum)
10
+ [![npm downloads](https://img.shields.io/npm/dm/homebridge-roborock-vacuum)](https://www.npmjs.com/package/homebridge-roborock-vacuum)
11
+ [![License: MIT](https://img.shields.io/badge/license-MIT-blue)](LICENSE)
8
12
 
9
- `homebridge-roborock-vacuum` brings your Roborock vacuum cleaner into Apple HomeKit. Using your Roborock app account credentials, this plugin automatically detects your vacuum, enabling you to control it directly from the Home app on your iPhone, iPad, or Mac, or with Siri voice commands.
13
+ `homebridge-roborock-vacuum` is a [Homebridge](https://homebridge.io) plugin that brings Roborock robot vacuums into Apple Home, over HomeKit or Matter. Sign in with your Roborock app account and the plugin finds your vacuums by itself; you can then start and stop them from the Home app, with Siri or from automations. Commands go to the vacuum over your home network, so it stays controllable when the Roborock cloud is down.
14
+
15
+ Free and open source. If it saves you a few chores, you can [buy me a boba](https://tasict.bobaboba.me) (by card, no PayPal account needed) or [tip with PayPal](https://paypal.me/tasict).
10
16
 
11
17
  This plugin is inspired by and adapted from the [ioBroker.roborock](https://github.com/copystring/ioBroker.roborock) project by copystring.
12
18
 
13
19
  ## Features
14
20
 
15
- - **Automatic Device Detection**: No need to manually find or enter your vacuum's device ID.
16
- - **Start/Stop Cleaning**: Begin or end cleaning sessions.
17
- - **Device Exclusion**: Skip selected Roborock device IDs so shared or remote vacuums stay out of HomeKit.
18
-
19
- ## The supported robots are:
20
-
21
- Roborock S4
22
- Roborock S4 Max
23
- Roborock S5 Max
24
- Roborock S6
25
- Roborock S6 Pure
26
- Roborock S6 MaxV
27
- Roborock S7
28
- Roborock S7 MaxV (Ultra)
29
- Roborock Q5+
30
- Roborock Q7
31
- Roborock Q7 Max
32
- Roborock S7 Pro Ultra
33
- Roborock S7 Max Ultra
34
- Roborock S8
35
- Roborock S8 Pro Ultra
36
- Roborock Q Revo
37
- Roborock Q8 Max
38
- Roborock Q5 Pro
39
- Roborock Q Revo Pro
40
- Roborock Qrevo S
41
- Roborock Qrevo Curve
42
- Roborock Saros 10
43
- Roborock (roborock.vacuum.a95)
44
- Roborock (roborock.vacuum.a159)
45
- Roborock (roborock.vacuum.ss07)
21
+ - **Automatic device discovery** — no device IDs or IP addresses to look up. The Roborock region is detected from your account.
22
+ - **Start, stop and send home** — over HomeKit the vacuum is a fan-style accessory: turn it on to start cleaning, off to stop and return to the dock.
23
+ - **Battery, charging and status** — battery level, charging state, low-battery warning, and a fault/offline flag when the vacuum reports an error or loses its connection.
24
+ - **Roborock scenes as switches** — every enabled scene from the Roborock app that uses the vacuum can be run from Apple Home.
25
+ - **Dock mop-wash switch** on docks that wash the mop. See [Dock mop-wash switch](#dock-mop-wash-switch).
26
+ - **Consumables** (HomeKit) — remaining life of the filter, main brush and side brush, with a change reminder at 5% or less.
27
+ - **Matter (Beta)** — publish a vacuum as a native Matter robot vacuum, with room cleaning and clean modes. See [Matter support (Beta)](#matter-support-beta).
28
+ - **Works through cloud outages** — local control over the LAN, and a local-only start when the Roborock cloud is unreachable. See [Cloud outages and local-only mode](#cloud-outages-and-local-only-mode).
29
+ - **Current room → MQTT** (optional) — publish the room being cleaned to your MQTT broker. See [Current Room → MQTT](#current-room--mqtt-optional-telemetry).
30
+ - **Per-device choice** — publish each vacuum over HomeKit or Matter, or skip it (for example a vacuum shared from another home).
46
31
 
47
- ## Requirements
32
+ ## Supported vacuums
48
33
 
49
- Before installing, ensure you have:
34
+ The plugin works with vacuums that are on your **Roborock app** account. These models are known to work:
50
35
 
51
- - A Roborock vacuum cleaner compatible with the Roborock app.
52
- - A Roborock app account (email and password).
53
- - [Homebridge](https://github.com/homebridge/homebridge) installed on a server (e.g., Raspberry Pi).
54
- - Node.js and npm installed on your Homebridge server.
36
+ S4, S4 Max, S5 Max, S6, S6 Pure, S6 MaxV, S7, S7 MaxV (Ultra), S7 Pro Ultra, S7 Max Ultra, S8, S8 Pro Ultra, Q5+, Q5 Pro, Q7, Q7 Max, Q8 Max, Qrevo, Qrevo Pro, Qrevo S, Qrevo Curv, Saros 10, and the models `roborock.vacuum.a95`, `roborock.vacuum.a159` and `roborock.vacuum.ss07`.
55
37
 
56
- ## Installation
38
+ Most other vacuums in the Roborock app work as well; which extras (dock mop wash, consumables, clean modes) appear depends on what the model reports. A vacuum that is set up only in the Xiaomi Home app is not on your Roborock account, so the plugin cannot see it.
57
39
 
58
- Follow these steps to install the plugin:
40
+ ## Requirements
59
41
 
60
- 1. **Install Homebridge** (if not already installed):
42
+ - A Roborock vacuum added to the Roborock app, and the email address of that Roborock account.
43
+ - [Homebridge](https://homebridge.io) 1.6 or later, on Node.js 18.20, 20.15, 22 or 24.
44
+ - For Matter: Homebridge 2.x with Matter enabled on the bridge the plugin runs on.
61
45
 
62
- - Refer to the official [Homebridge installation guide](https://github.com/homebridge/homebridge#installation).
46
+ ## Installation
63
47
 
64
- 2. **Install the Plugin**:
65
- - Open a terminal and run:
66
- ```bash
67
- npm install -g homebridge-roborock-vacuum
68
- ```
48
+ In the Homebridge UI, open **Plugins**, search for **Roborock Vacuum** and install `homebridge-roborock-vacuum`.
49
+
50
+ Without the UI, install it next to Homebridge:
51
+
52
+ ```bash
53
+ npm install -g homebridge-roborock-vacuum
54
+ ```
69
55
 
70
56
  ## Configuration
71
57
 
72
- Use the Homebridge UI settings page to sign in and configure the plugin. Click **Load devices** to list the vacuums on your account, then choose a protocol for each one:
58
+ Configure the plugin from its settings page in the Homebridge UI:
73
59
 
74
- - **HomeKit (HAP)** — the default. The vacuum is bridged to Apple Home as a fan-style accessory, as in previous versions.
75
- - **Matter (Beta)** — the vacuum is published over Matter as a robotic vacuum cleaner, so it gets the native vacuum icon and controls in Apple Home (and works with Google Home, Alexa and SmartThings). This is an experimental feature — read the [Matter support (Beta)](#matter-support-beta) section below before enabling it.
76
- - **Skip** — the vacuum is excluded entirely. You can also enter device IDs manually in the list below; manual entries are always skipped.
60
+ 1. **Sign in.** Enter your Roborock app email. Either enter your password and press **Password Login**, or press **Send 2FA Email** and enter the code from the email with **Verify Code** (also the way to finish a login that asks for two-factor authentication). Leave **Region** on _Auto detect_ unless detection picks the wrong server. The settings page stores an encrypted session token; you do not need to sign in again after a restart.
61
+ 2. **Choose a protocol per vacuum.** Press **Load devices** to list the vacuums on your account and pick one for each:
62
+ - **HomeKit (HAP)** — the default. The vacuum is bridged to Apple Home as a fan-style accessory, as in previous versions.
63
+ - **Matter (Beta)** — the vacuum is published over Matter as a robotic vacuum cleaner, so it gets the native vacuum icon and controls in Apple Home (and works with Google Home, Alexa and SmartThings). This is an experimental feature — read the [Matter support (Beta)](#matter-support-beta) section below before enabling it.
64
+ - **Skip** — the vacuum is excluded entirely. You can also enter device IDs manually in the list below; manual entries are always skipped.
65
+ 3. **Restart Homebridge.**
77
66
 
78
67
  When Homebridge restarts, each device is (re)published according to its selection. A device that was cached under a different protocol (or is now skipped) is removed from the old bridge first. **Changing a device's protocol re-creates the accessory**, so it loses its room and automation assignments in your home app and must be re-organized there.
79
68
 
69
+ ### Options
70
+
71
+ The settings page writes these keys to the `RoborockVacuumPlatform` block in `config.json`:
72
+
73
+ | Key | Description |
74
+ | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
75
+ | `email` | Roborock app account email. Required. |
76
+ | `password` | Roborock account password, saved by **Password Login**. Not needed when you sign in with an email code. |
77
+ | `encryptedToken` | Encrypted session data, managed by the settings page. |
78
+ | `baseURL` | Roborock API endpoint. Leave empty to auto-detect; otherwise `https://usiot.roborock.com` (US), `https://euiot.roborock.com` (EU), `https://cniot.roborock.com` (CN) or `https://api.roborock.com` (Asia). |
79
+ | `language` | Language of the names the plugin gives to switches and sensors it adds (`en`, `de`, `es`, `fr`, `it`, `nl`, `pl`, `pt`, `ru`, `uk`, `zh-cn`, `zh-tw`). Default `en`. |
80
+ | `skipDevices` | Device IDs to leave out, as a list or a comma- or newline-separated string. |
81
+ | `matterDevices` | Device IDs to publish over Matter instead of HomeKit. Ignored without Homebridge 2 and Matter. |
82
+ | `matterSceneDevices` | Matter device IDs whose Roborock scenes become Matter buttons. When omitted, every Matter device gets them. |
83
+ | `currentRoomMqtt` | Optional current-room telemetry, see [Current Room → MQTT](#current-room--mqtt-optional-telemetry). |
84
+ | `debugMode` | Write debug messages to the Homebridge log. Default `false`. |
85
+
80
86
  ### Matter support (Beta)
81
87
 
82
88
  > ⚠️ **This is an experimental, lab-grade beta feature.** Matter support for robotic vacuums is still very new on the controller side. In particular, **Apple Home's compatibility is currently poor and not very stable**: the bridge is uncertified (Apple shows an "Uncertified Accessory" warning), the accessory appears as a generic **"Matter Accessory"** during pairing and must be named manually, room selection needs iOS 18.4 or later, and accessories can occasionally show "Not responding" or lose features after iOS updates. If you want the most reliable day-to-day experience, stay on **HomeKit (HAP)**. Choose Matter only if you want the native vacuum UI and room cleaning, and can live with rough edges.
@@ -115,6 +121,33 @@ Pairing is one-time per node — switching a device between HAP and Matter later
115
121
  - Scene buttons require the **separate bridge pairing** (step 5) and appear as plain on/off switches in the controller.
116
122
  - Multi-floor maps are not exposed (rooms come from the currently active map), and zone cleaning, consumables and dock controls other than the mop-wash switch are not available over Matter yet.
117
123
 
124
+ ## Cloud outages and local-only mode
125
+
126
+ Roborock's cloud is required to log in and to read your device list, but it is
127
+ not required to _control_ a vacuum: once the plugin knows a device's local key,
128
+ it talks to the robot directly over your LAN.
129
+
130
+ The plugin caches the device list, the local keys and each vacuum's last known
131
+ LAN address on disk (owner-readable only) after every successful cloud
132
+ refresh. If the Roborock cloud is unreachable when Homebridge starts, the
133
+ plugin falls back to that cache and starts in **local-only mode**:
134
+
135
+ - your vacuums still appear in HomeKit, and start/stop/dock commands work over the LAN;
136
+ - vacuums are found by UDP discovery, or dialed at their cached address when
137
+ discovery finds nothing (another VLAN, or port 58866 in use);
138
+ - cloud-only features are unavailable until the cloud returns — scenes, push
139
+ status updates, and the cloud online flag;
140
+ - the plugin keeps retrying in the background, so cloud features come back on
141
+ their own without a Homebridge restart. If the login itself failed during
142
+ the outage, the plugin logs in again by itself once the cloud answers (a
143
+ pending two-factor prompt still needs the Config UI).
144
+
145
+ The log says which mode you are in (`Starting adapter finished in local-only
146
+ mode (cloud unreachable).`). Two caveats: the plugin needs **one successful
147
+ online start** to create the cache, so a brand-new install cannot start offline,
148
+ and a vacuum that is shared from another Roborock account can only be controlled
149
+ through the cloud.
150
+
118
151
  ## Dock mop-wash switch
119
152
 
120
153
  On vacuums whose dock can wash the mop (G10, S7 Pro/MaxV Ultra, S7 Max Ultra, S8 Pro Ultra, Q Revo family, …) the plugin adds a switch that starts and stops a dock mop wash:
@@ -164,3 +197,14 @@ A retained JSON message is published whenever the room changes:
164
197
  - Room names are resolved from the robot's saved map; name your rooms in the Roborock app for them to appear.
165
198
 
166
199
  > Validated on a Roborock Qrevo (`roborock.vacuum.a185`). On models that don't populate `cleaning_info`, the payload degrades gracefully to `segment_id: -1` / `room: null`.
200
+
201
+ ## Support
202
+
203
+ If this plugin is useful to you, I'd love it if you bought me a boba:
204
+
205
+ - **[Buy me a boba](https://tasict.bobaboba.me)**: pay by card, no PayPal account needed
206
+ - **[Tip with PayPal](https://paypal.me/tasict)**
207
+
208
+ ## Trademarks
209
+
210
+ Roborock is a trademark of Beijing Roborock Technology Co., Ltd. Apple Home and HomeKit are trademarks of Apple Inc. Matter is a trademark of the Connectivity Standards Alliance. This plugin is unofficial and is not affiliated with, endorsed by, or sponsored by any of them.
@@ -17,13 +17,13 @@
17
17
  "title": "Email",
18
18
  "type": "string",
19
19
  "format": "email",
20
- "description": "Roborock account email"
20
+ "description": "Email of your Roborock app account"
21
21
  },
22
22
  "password": {
23
23
  "title": "Password",
24
24
  "type": "string",
25
25
  "placeholder": "Password",
26
- "description": "Roborock account password"
26
+ "description": "Roborock account password (not needed when signing in with an email code)"
27
27
  },
28
28
  "encryptedToken": {
29
29
  "title": "Encrypted Token",
@@ -34,7 +34,7 @@
34
34
  "skipDevices": {
35
35
  "title": "Skipped Device IDs",
36
36
  "type": "string",
37
- "description": "Roborock device IDs to exclude from HomeKit."
37
+ "description": "Roborock device IDs to leave out of Apple Home (neither HomeKit nor Matter)."
38
38
  },
39
39
  "matterDevices": {
40
40
  "title": "Matter Device IDs",
Binary file
@@ -1,10 +1,11 @@
1
- <link rel="stylesheet" href="styles.css?v=2.1.1" />
1
+ <link rel="stylesheet" href="styles.css?v=2.2.8" />
2
2
 
3
3
  <main class="rr-container">
4
4
  <header>
5
5
  <h1>Roborock Vacuum</h1>
6
6
  <p class="subtitle">
7
- Manage login and two-factor authentication for your Roborock account.
7
+ Sign in to your Roborock account and choose how each vacuum appears in
8
+ Apple Home.
8
9
  </p>
9
10
  </header>
10
11
 
@@ -202,8 +203,41 @@
202
203
  </div>
203
204
  </div>
204
205
  </section>
206
+
207
+ <footer class="rr-support">
208
+ <p class="rr-support-text">
209
+ This plugin is free and open source. If it saves you a few chores, you can
210
+ buy me a boba or send a tip with PayPal.
211
+ </p>
212
+ <div class="rr-support-links">
213
+ <a
214
+ class="rr-tip"
215
+ href="https://tasict.bobaboba.me"
216
+ target="_blank"
217
+ rel="noopener noreferrer"
218
+ ><img src="boba.png" alt="" width="20" height="20" />Buy me a boba</a
219
+ >
220
+ <a
221
+ class="rr-tip"
222
+ href="https://paypal.me/tasict"
223
+ target="_blank"
224
+ rel="noopener noreferrer"
225
+ >Tip with PayPal</a
226
+ >
227
+ <a
228
+ class="rr-tip"
229
+ href="https://tasict.github.io/homebridge-roborock-vacuum/"
230
+ target="_blank"
231
+ rel="noopener noreferrer"
232
+ >Plugin website</a
233
+ >
234
+ </div>
235
+ <p class="rr-support-note">
236
+ Boba is paid by card. No PayPal account needed.
237
+ </p>
238
+ </footer>
205
239
  </main>
206
240
 
207
241
  <div id="toast-container" class="rr-toast-container"></div>
208
242
 
209
- <script src="index.js?v=2.1.1"></script>
243
+ <script src="index.js?v=2.2.8"></script>
@@ -303,3 +303,55 @@ body.dark-mode .rr-toast {
303
303
  opacity: 1;
304
304
  }
305
305
  }
306
+
307
+ /* Support: a quiet footer below the settings, never in the way of a task. */
308
+ .rr-support {
309
+ margin-top: 4px;
310
+ padding-top: 14px;
311
+ border-top: 1px solid var(--rr-border);
312
+ font-size: 0.8rem;
313
+ }
314
+ .rr-support-text {
315
+ margin: 0 0 8px;
316
+ color: var(--rr-muted);
317
+ line-height: 1.5;
318
+ }
319
+ .rr-support-links {
320
+ display: flex;
321
+ flex-wrap: wrap;
322
+ gap: 8px;
323
+ }
324
+ .rr-tip {
325
+ display: inline-flex;
326
+ align-items: center;
327
+ gap: 6px;
328
+ min-height: 30px;
329
+ padding: 3px 12px;
330
+ border: 1px solid var(--rr-border);
331
+ border-radius: 8px;
332
+ color: inherit;
333
+ font-weight: 600;
334
+ text-decoration: none;
335
+ white-space: nowrap;
336
+ }
337
+ .rr-tip:hover,
338
+ .rr-tip:focus {
339
+ color: inherit;
340
+ text-decoration: none;
341
+ border-color: var(--rr-muted);
342
+ }
343
+ .rr-tip:focus-visible {
344
+ outline: 2px solid #0d6efd;
345
+ outline-offset: 2px;
346
+ }
347
+ .rr-tip img {
348
+ width: 20px;
349
+ height: 20px;
350
+ margin-left: -5px;
351
+ border-radius: 5px;
352
+ }
353
+ .rr-support-note {
354
+ margin: 8px 0 0;
355
+ color: var(--rr-muted);
356
+ font-size: 0.75rem;
357
+ }
package/package.json CHANGED
@@ -1,17 +1,20 @@
1
1
  {
2
2
  "name": "homebridge-roborock-vacuum",
3
- "version": "2.2.6",
4
- "description": "Roborock Vacuum Cleaner - plugin for Homebridge.",
3
+ "displayName": "Homebridge Roborock Vacuum",
4
+ "version": "2.2.8",
5
+ "description": "Homebridge plugin that brings Roborock robot vacuums to Apple Home over HomeKit or Matter, with local control on your network.",
5
6
  "license": "MIT",
6
7
  "keywords": [
8
+ "homebridge",
7
9
  "homebridge-plugin",
8
- "vacuum cleaner",
9
- "roborock app",
10
+ "homekit",
11
+ "matter",
12
+ "roborock",
10
13
  "roborock vacuum",
14
+ "robot vacuum",
15
+ "vacuum cleaner",
11
16
  "supports-hap",
12
- "support-matter",
13
- "roborock",
14
- "homekit"
17
+ "supports-matter"
15
18
  ],
16
19
  "repository": {
17
20
  "type": "git",
@@ -20,14 +23,28 @@
20
23
  "bugs": {
21
24
  "url": "https://github.com/tasict/homebridge-roborock-vacuum/issues"
22
25
  },
23
- "homepage": "https://github.com/tasict/homebridge-roborock-vacuum",
26
+ "homepage": "https://tasict.github.io/homebridge-roborock-vacuum/",
27
+ "funding": [
28
+ {
29
+ "type": "individual",
30
+ "url": "https://tasict.bobaboba.me"
31
+ },
32
+ {
33
+ "type": "paypal",
34
+ "url": "https://paypal.me/tasict"
35
+ }
36
+ ],
24
37
  "main": "dist/index.js",
25
38
  "files": [
26
39
  "CHANGELOG.md",
27
40
  "config.schema.json",
28
41
  "dist",
42
+ "!dist/**/*.test.*",
29
43
  "homebridge-ui",
30
- "roborockLib"
44
+ "roborockLib",
45
+ "!roborockLib/data",
46
+ "!roborockLib/lib/sniffing",
47
+ "!roborockLib/test.js"
31
48
  ],
32
49
  "engines": {
33
50
  "homebridge": "^1.6.0 || ^2.0.0-beta.0",
@@ -141,6 +141,9 @@ class vacuum {
141
141
  // another account can never be local.
142
142
  if (attribute == "ip" && !this.adapter.isSharedDevice(duid)) {
143
143
  this.adapter.localDevices[duid] = networkInfo[attribute];
144
+ if (typeof this.adapter.persistLocalDevices === "function") {
145
+ this.adapter.persistLocalDevices();
146
+ }
144
147
  }
145
148
  this.adapter.setStateAsync(
146
149
  `Devices.${duid}.networkInfo.${attribute}`,