@camstack/addon-provider-reolink 1.2.223 → 1.2.224

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
@@ -7,6 +7,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [1.2.224] - 2026-11-04
11
+
12
+ ### Changed
13
+
14
+ - Reolink starts again after the update: its integration migrations are offered in order, so the move of the connection settings runs
15
+
10
16
  ## [1.2.223] - 2026-11-04
11
17
 
12
18
  ### Changed
package/dist/addon.js CHANGED
@@ -221495,17 +221495,17 @@ var REOLINK_MIGRATIONS = [{
221495
221495
  plan: planDropWebhookIntakeSettings
221496
221496
  }];
221497
221497
  /**
221498
- * Every persisted camera that names no integration is claimed to the addon's default one. The
221499
- * integration a hub migration created is never the default, so it is not eligible. The integration
221500
- * settings themselves stay where they are until this addon's own wave moves them.
221498
+ * The integration wave (D1007) in declaration order, which must follow `seq`: the device claim
221499
+ * shipped first (seq 3) and the rows move follows it (seq 4). The engine refuses the whole
221500
+ * catalogue when a seq does not increase, and the addon then does not start.
221501
221501
  */
221502
- var REOLINK_CLAIM_MIGRATION = claimDevicesMigration({
221502
+ var REOLINK_INTEGRATION_MIGRATIONS = [claimDevicesMigration({
221503
221503
  addonId: "provider-reolink",
221504
221504
  date: "2026-11-04",
221505
221505
  seq: 3,
221506
221506
  dependsOn: [],
221507
221507
  eligible: (integration) => integration.info[MIGRATED_FROM_HUB_KEY] === void 0
221508
- });
221508
+ }), REOLINK_ROWS_TO_RECORD_MIGRATION];
221509
221509
  //#endregion
221510
221510
  //#region src/reolink-adoption-provider.ts
221511
221511
  var DEVICES_FILTER = {
@@ -222647,11 +222647,7 @@ var ReolinkProviderAddon = class extends BaseDeviceProvider {
222647
222647
  registryEvidenceOf
222648
222648
  });
222649
222649
  this.instances = instances;
222650
- await this.runMigrations([
222651
- ...defineAddonMigrations(REOLINK_MIGRATIONS, this.migrationPorts()),
222652
- ...defineAddonMigrations([REOLINK_ROWS_TO_RECORD_MIGRATION], integrationPorts),
222653
- ...defineAddonMigrations([REOLINK_CLAIM_MIGRATION], integrationPorts)
222654
- ]);
222650
+ await this.runMigrations([...defineAddonMigrations(REOLINK_MIGRATIONS, this.migrationPorts()), ...defineAddonMigrations(REOLINK_INTEGRATION_MIGRATIONS, integrationPorts)]);
222655
222651
  this.wireEmailBridge();
222656
222652
  const wireSleepPushResolvers = (event, via) => {
222657
222653
  const data = event.data;
package/dist/addon.mjs CHANGED
@@ -221487,17 +221487,17 @@ var REOLINK_MIGRATIONS = [{
221487
221487
  plan: planDropWebhookIntakeSettings
221488
221488
  }];
221489
221489
  /**
221490
- * Every persisted camera that names no integration is claimed to the addon's default one. The
221491
- * integration a hub migration created is never the default, so it is not eligible. The integration
221492
- * settings themselves stay where they are until this addon's own wave moves them.
221490
+ * The integration wave (D1007) in declaration order, which must follow `seq`: the device claim
221491
+ * shipped first (seq 3) and the rows move follows it (seq 4). The engine refuses the whole
221492
+ * catalogue when a seq does not increase, and the addon then does not start.
221493
221493
  */
221494
- var REOLINK_CLAIM_MIGRATION = claimDevicesMigration({
221494
+ var REOLINK_INTEGRATION_MIGRATIONS = [claimDevicesMigration({
221495
221495
  addonId: "provider-reolink",
221496
221496
  date: "2026-11-04",
221497
221497
  seq: 3,
221498
221498
  dependsOn: [],
221499
221499
  eligible: (integration) => integration.info[MIGRATED_FROM_HUB_KEY] === void 0
221500
- });
221500
+ }), REOLINK_ROWS_TO_RECORD_MIGRATION];
221501
221501
  //#endregion
221502
221502
  //#region src/reolink-adoption-provider.ts
221503
221503
  var DEVICES_FILTER = {
@@ -222639,11 +222639,7 @@ var ReolinkProviderAddon = class extends BaseDeviceProvider {
222639
222639
  registryEvidenceOf
222640
222640
  });
222641
222641
  this.instances = instances;
222642
- await this.runMigrations([
222643
- ...defineAddonMigrations(REOLINK_MIGRATIONS, this.migrationPorts()),
222644
- ...defineAddonMigrations([REOLINK_ROWS_TO_RECORD_MIGRATION], integrationPorts),
222645
- ...defineAddonMigrations([REOLINK_CLAIM_MIGRATION], integrationPorts)
222646
- ]);
222642
+ await this.runMigrations([...defineAddonMigrations(REOLINK_MIGRATIONS, this.migrationPorts()), ...defineAddonMigrations(REOLINK_INTEGRATION_MIGRATIONS, integrationPorts)]);
222647
222643
  this.wireEmailBridge();
222648
222644
  const wireSleepPushResolvers = (event, via) => {
222649
222645
  const data = event.data;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camstack/addon-provider-reolink",
3
- "version": "1.2.223",
3
+ "version": "1.2.224",
4
4
  "description": "Reolink camera device provider addon for CamStack — native Baichuan protocol",
5
5
  "keywords": [
6
6
  "camstack",