@camstack/types 1.2.241 → 1.2.242

package/dist/device/container-primary-child.d.ts

@@ -90,10 +90,4 @@ export interface ContainerChildRef {
  * they are deliberately absent and fall through to type priority.
  */
 export declare const CONTAINER_CHILD_ROLE_PRIORITY: readonly string[];
-/**
- * The child a container stands for: the operator's pick when it still exists,
- * else the highest-priority type. `null` for a childless container — a caller
- * must decide what an empty container means for it, rather than being handed a
- * child that is not there.
- */
 export declare function resolveContainerPrimaryChild(children: readonly ContainerChildRef[], overrideEntityId: string | null | undefined, containerName?: string): ContainerChildRef | null;

package/dist/index.js

@@ -42717,12 +42717,39 @@ function rank(type) {
 * must decide what an empty container means for it, rather than being handed a
 * child that is not there.
 */
+/**
+* Two names for the same thing, compared the way an integration writes them.
+*
+* An exact case-insensitive match was not enough, and the failure was total
+* rather than marginal. An ESPHome shutter arrives as a container named
+* `Tapparella-Cucina` whose children include the COVER, named `Tapparella
+* cucina`, and a device-presence entity carrying the slug verbatim,
+* `tapparella-cucina`. The slug matched the container exactly and the cover
+* did not, so the namesake tie-break handed the container to a connectivity
+* indicator — and the viewer's accessory panel, which correctly shows only
+* children with an actuating control, then rendered NOTHING. The operator saw
+* no shutters at all on cucina, studio and both veranda cameras (2026-09-22).
+*
+* `Markise` was the control case that proved the mechanism: there the cover
+* really is called exactly like its container, so it won and appeared.
+*
+* Separators are therefore normalised — `-`, `_` and whitespace are the same
+* character for this comparison, and runs of them collapse. The two candidates
+* then tie on the namesake and the decision falls through to `rank(type)`,
+* where `cover` is eighth and a `presence` entity is not listed at all. The
+* criterion keeps doing its job for a container whose child IS the namesake;
+* it stops being decided by which integration used a hyphen.
+*/
+function sameName(childName, containerName) {
+	const flatten = (v) => v.toLowerCase().replace(/[-_\s]+/g, " ").trim();
+	return flatten(childName) === flatten(containerName);
+}
 function resolveContainerPrimaryChild(children, overrideEntityId, containerName) {
 	if (overrideEntityId !== void 0 && overrideEntityId !== null) {
 		const picked = children.find((c) => c.stableId === overrideEntityId) ?? children.find((c) => c.entityId !== void 0 && c.entityId === overrideEntityId);
 		if (picked !== void 0) return picked;
 	}
-	const namesake = (c) => containerName !== void 0 && containerName.length > 0 && c.name !== void 0 && c.name.toLowerCase() === containerName.toLowerCase() ? 0 : 1;
+	const namesake = (c) => containerName !== void 0 && containerName.length > 0 && c.name !== void 0 && sameName(c.name, containerName) ? 0 : 1;
 	return [...children].toSorted((a, b) => roleRank(a.role) - roleRank(b.role) || namesake(a) - namesake(b) || rank(a.type) - rank(b.type))[0] ?? null;
 }
 //#endregion

package/dist/index.mjs

@@ -42716,12 +42716,39 @@ function rank(type) {
 * must decide what an empty container means for it, rather than being handed a
 * child that is not there.
 */
+/**
+* Two names for the same thing, compared the way an integration writes them.
+*
+* An exact case-insensitive match was not enough, and the failure was total
+* rather than marginal. An ESPHome shutter arrives as a container named
+* `Tapparella-Cucina` whose children include the COVER, named `Tapparella
+* cucina`, and a device-presence entity carrying the slug verbatim,
+* `tapparella-cucina`. The slug matched the container exactly and the cover
+* did not, so the namesake tie-break handed the container to a connectivity
+* indicator — and the viewer's accessory panel, which correctly shows only
+* children with an actuating control, then rendered NOTHING. The operator saw
+* no shutters at all on cucina, studio and both veranda cameras (2026-09-22).
+*
+* `Markise` was the control case that proved the mechanism: there the cover
+* really is called exactly like its container, so it won and appeared.
+*
+* Separators are therefore normalised — `-`, `_` and whitespace are the same
+* character for this comparison, and runs of them collapse. The two candidates
+* then tie on the namesake and the decision falls through to `rank(type)`,
+* where `cover` is eighth and a `presence` entity is not listed at all. The
+* criterion keeps doing its job for a container whose child IS the namesake;
+* it stops being decided by which integration used a hyphen.
+*/
+function sameName(childName, containerName) {
+	const flatten = (v) => v.toLowerCase().replace(/[-_\s]+/g, " ").trim();
+	return flatten(childName) === flatten(containerName);
+}
 function resolveContainerPrimaryChild(children, overrideEntityId, containerName) {
 	if (overrideEntityId !== void 0 && overrideEntityId !== null) {
 		const picked = children.find((c) => c.stableId === overrideEntityId) ?? children.find((c) => c.entityId !== void 0 && c.entityId === overrideEntityId);
 		if (picked !== void 0) return picked;
 	}
-	const namesake = (c) => containerName !== void 0 && containerName.length > 0 && c.name !== void 0 && c.name.toLowerCase() === containerName.toLowerCase() ? 0 : 1;
+	const namesake = (c) => containerName !== void 0 && containerName.length > 0 && c.name !== void 0 && sameName(c.name, containerName) ? 0 : 1;
 	return [...children].toSorted((a, b) => roleRank(a.role) - roleRank(b.role) || namesake(a) - namesake(b) || rank(a.type) - rank(b.type))[0] ?? null;
 }
 //#endregion

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/types",
-  "version": "1.2.241",
+  "version": "1.2.242",
   "description": "Shared types, interfaces, and model catalogs for the CamStack detection ecosystem",
   "keywords": [
     "camstack",