@apocaliss92/nodelink-js 0.4.34-beta.0 → 0.4.35

package/dist/{chunk-ZRDPJAXB.js → chunk-N6TCSER3.js}

@@ -8274,7 +8274,19 @@ function computeDeviceCapabilities(params) {
     // lightType >= 2 indicates controllable white LED / floodlight (1 = IR only).
     // ledCtrl > 1 is a secondary signal that rescues firmwares like the Duo 3
     // WiFi which under-report lightType (=1) despite having a real spotlight.
-    hasFloodlight: Number.isFinite(lightType) ? lightType >= 2 || hasFloodlightFromLedCtrl : hasFloodlightFromAbilities || hasFloodlightFromLedCtrl,
+    //
+    // Doorbell exception: the Reolink desktop app's native SDK exposes
+    // three SEPARATE ability flags — `supportFloodLight`, `supportDoorbellLight`
+    // (with KeepOff/KeepOn sub-flags) and `supportIndicatorLight`. Doorbell-class
+    // devices route the ring / button-area LED through `supportDoorbellLight`,
+    // which is NOT a controllable white-light floodlight. We don't have a
+    // documented bit-level mapping for ledCtrl, so we use the narrowest
+    // rule that matches Reolink's own taxonomy: when the firmware is
+    // categorical with lightType=0 AND the device identifies itself as a
+    // doorbell (doorbellVersion > 0), trust lightType=0 and ignore the
+    // ledCtrl bitmask. Verified against UID 9527000ICL1T1MDS (lightType=0,
+    // ledCtrl=3073, doorbellVersion=31, no spotlight hardware).
+    hasFloodlight: Number.isFinite(lightType) ? lightType >= 2 || hasFloodlightFromLedCtrl && !(isDoorbellFromSupport && lightType === 0) : hasFloodlightFromAbilities || hasFloodlightFromLedCtrl,
     hasPir: hasPirFromAbilities || hasPirFromSupport,
     isDoorbell,
     hasAutotracking: ptzDisabledBySupport ? false : hasAutotrackingFromSupport || hasAutotrackingFromAbilities,
@@ -24126,6 +24138,17 @@ async function discoverReolinkDevices(options = {}) {
 }
 
 // src/reolink/autodetect.ts
+var ALL_UDP_DISCOVERY_METHODS = [
+  "local-direct",
+  "local-broadcast",
+  "remote",
+  "relay",
+  "map"
+];
+function selectViableUdpMethods(hasUid, methods = ALL_UDP_DISCOVERY_METHODS) {
+  if (hasUid) return [...methods];
+  return methods.filter((m) => m === "local-direct");
+}
 function normalizeUid(uid) {
   const v = uid?.trim();
   return v ? v : void 0;
@@ -24617,7 +24640,7 @@ async function autoDetectDeviceType(inputs) {
       }
       if (!normalizedUid) {
         logger?.log?.(
-          `[AutoDetect] UID discovery failed; will try local-direct without UID first.`
+          `[AutoDetect] UID discovery failed; only local-direct can run without a UID. If the camera is sleeping or on a different subnet, supply its UID to enable BCUDP P2P fallback (remote/relay/map) which can wake it via Reolink's servers.`
         );
       }
     }
@@ -24670,8 +24693,7 @@ async function autoDetectDeviceType(inputs) {
           api: udpApi
         };
       };
-      const methodsToTry = ["local-direct", "local-broadcast", "remote", "relay", "map"];
-      const viableMethods = normalizedUid ? methodsToTry : methodsToTry.filter((m) => m === "local-direct" || m === "local-broadcast");
+      const viableMethods = selectViableUdpMethods(Boolean(normalizedUid));
       return await runUdpMethodsParallel(
         viableMethods,
         async (m, isAborted) => {
@@ -24777,9 +24799,11 @@ export {
   discoverViaTcpPortScan,
   discoverViaOnvif,
   discoverReolinkDevices,
+  ALL_UDP_DISCOVERY_METHODS,
+  selectViableUdpMethods,
   normalizeUid,
   maskUid,
   isTcpFailureThatShouldFallbackToUdp,
   autoDetectDeviceType
 };
-//# sourceMappingURL=chunk-ZRDPJAXB.js.map
+//# sourceMappingURL=chunk-N6TCSER3.js.map