Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Featuremap attribute in cluster init state has effect on features partially #1209

Open
Apollon77 opened this issue Sep 17, 2024 · 0 comments
Assignees

Comments

@Apollon77
Copy link
Collaborator

When someone does this

const endpoint = new Endpoint(
    ExtendedColorLightDevice.with(BridgedDeviceBasicInformationServer),
{
    id: `COL-1}`,
    bridgedDeviceBasicInformation: {
        nodeLabel: nodename, // Main end user name for the device
        productName: nodename,
        productLabel: nodename,
        serialNumber: `node-matter-${uniqueId}-1}`,
        reachable: true,
    },
    colorControl: {
        coupleColorTempToLevelMinMireds: 0x00FA,
        startUpColorTemperatureMireds: 0x00FA,
        featureMap: {
            hueSaturation: true,
            enhancedHue: false,
            colorLoop: false,
            xy: true,
            colorTemperature: true
        },
        colorMode: 0,
        enhancedColorMode: 0
    }
},
);

This seems to have an effect like the featureMap global attribute seems to be set like provided, but the real features and also typing do not know certain features (e.g. in this case hue should not be enabled).

We need to make sure providing "global attribute names" here do not have an effect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Planned
Development

No branches or pull requests

2 participants