fix(clg-collection): route flow actions to actual member devices

Pairing stored Homey's UUID in config.devices[].id while resolveMemberEntries
looked it up against the local device's getData().id. The two id spaces never
matched, so every fan-out silently failed and pause/resume/turn-on/apply were
no-ops on members. Pair now stores data.id; lookup also accepts the legacy
UUID via device.id so existing Collections work without re-pairing.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: Tiwas

no.tiwas.booleantoolbox/drivers/circadian-light-group-collection/device.js

@@ -24,17 +24,21 @@ class CircadianLightGroupCollectionDevice extends CircadianLightGroupDevice {
   }
 
   resolveMemberEntries() {
-    const byId = new Map();
+    const byDataId = new Map();
+    const byHomeyId = new Map();
     this.getAvailableCircadianGroups().forEach(device => {
       const dataId = device.getData?.().id;
-      if (dataId) byId.set(dataId, device);
+      if (dataId) byDataId.set(dataId, device);
+      // device.id is the Homey-wide UUID exposed on local device instances
+      const homeyId = device.id;
+      if (homeyId) byHomeyId.set(homeyId, device);
     });
 
     return this.getMemberItems().map(item => ({
       id: item.id,
       name: item.name || item.id,
       item,
-      memberDevice: byId.get(item.id) || null,
+      memberDevice: byDataId.get(item.id) || byHomeyId.get(item.id) || null,
     }));
   }
 

no.tiwas.booleantoolbox/drivers/circadian-light-group-collection/driver.js

@@ -121,8 +121,10 @@ class CircadianLightGroupCollectionDriver extends CircadianLightGroupDriver {
         };
       }
 
+      const dataId = homeyDevice.data?.id || homeyDevice.id;
       candidates.push({
-        id: homeyDevice.id,
+        id: dataId,
+        homeyDeviceId: homeyDevice.id,
         name: homeyDevice.name,
         zoneName: allZones[homeyDevice.zone] ? allZones[homeyDevice.zone].name : 'Unknown',
         capabilities: supportedCapabilities,