@apocaliss92/nodelink-js 0.6.3 → 0.6.4

package/dist/index.d.cts

@@ -11719,7 +11719,28 @@ type AutoDetectResult = {
     api: ReolinkBaichuanApi;
 };
 /**
- * Normalize UID string (trim and return undefined if empty).
+ * Normalize UID string (trim, force uppercase, return undefined if empty).
+ *
+ * Uppercase is non-negotiable for two reasons:
+ *
+ * 1. Reolink's cloud API (`apis.reolink.com/v2/devices/{uid}/server-binding`)
+ *    is case-sensitive: a lowercase UID returns HTTP 400
+ *    `invalid_parameters` and we lose the per-UID zone hint, falling back
+ *    to the full 24-hostname sweep. Verified empirically against a known
+ *    good UID — uppercase returns 200 + zone allocation, lowercase
+ *    returns 400 + `invalid_parameters`.
+ *
+ * 2. The BCUDP discovery protocol embeds `<uid>...</uid>` in the C2D_C
+ *    packet. Cameras compare it against their own self-UID (which they
+ *    store uppercase). A lowercase mismatch is silently dropped — the
+ *    cam appears "asleep" from `sent=N replies=0` even though it's
+ *    awake and on the LAN. BaichuanClient already uppercases for the
+ *    XOR/AES nonce derivation; normalizing here makes the whole
+ *    pipeline consistent.
+ *
+ * Users in Scrypted / config files sometimes paste UIDs in lowercase
+ * (it works visually with Reolink's own UI, which normalizes
+ * internally) — we shouldn't punish them for that.
  */
 declare function normalizeUid(uid?: string): string | undefined;
 /**

package/dist/index.d.ts

@@ -6723,7 +6723,28 @@ export declare function normalizeDayNightMode(input: string): string;
 export declare function normalizeOpenClose(input: string): string;
 
 /**
- * Normalize UID string (trim and return undefined if empty).
+ * Normalize UID string (trim, force uppercase, return undefined if empty).
+ *
+ * Uppercase is non-negotiable for two reasons:
+ *
+ * 1. Reolink's cloud API (`apis.reolink.com/v2/devices/{uid}/server-binding`)
+ *    is case-sensitive: a lowercase UID returns HTTP 400
+ *    `invalid_parameters` and we lose the per-UID zone hint, falling back
+ *    to the full 24-hostname sweep. Verified empirically against a known
+ *    good UID — uppercase returns 200 + zone allocation, lowercase
+ *    returns 400 + `invalid_parameters`.
+ *
+ * 2. The BCUDP discovery protocol embeds `<uid>...</uid>` in the C2D_C
+ *    packet. Cameras compare it against their own self-UID (which they
+ *    store uppercase). A lowercase mismatch is silently dropped — the
+ *    cam appears "asleep" from `sent=N replies=0` even though it's
+ *    awake and on the LAN. BaichuanClient already uppercases for the
+ *    XOR/AES nonce derivation; normalizing here makes the whole
+ *    pipeline consistent.
+ *
+ * Users in Scrypted / config files sometimes paste UIDs in lowercase
+ * (it works visually with Reolink's own UI, which normalizes
+ * internally) — we shouldn't punish them for that.
  */
 export declare function normalizeUid(uid?: string): string | undefined;
 

package/dist/index.js

@@ -72,7 +72,7 @@ import {
   setGlobalLogger,
   tcpReachabilityProbe,
   xmlIndicatesFloodlight
-} from "./chunk-Q4AXRV2G.js";
+} from "./chunk-UL34MR4L.js";
 import {
   ReolinkCgiApi,
   ReolinkHttpClient,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@apocaliss92/nodelink-js",
-  "version": "0.6.3",
+  "version": "0.6.4",
   "description": "TypeScript library implementing Reolink Baichuan protocol (control + streaming) with CGI and RTSP helpers. Full TypeScript support with comprehensive type definitions.",
   "license": "MIT",
   "author": "",