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

CCT5010-0001 was sold under the name 550B1012 in Denmark #8569

Merged
merged 2 commits into from
Jan 6, 2025

Conversation

poizan42
Copy link
Contributor

@poizan42 poizan42 commented Jan 6, 2025

Adding as white label model for lack of a better place. It was sold as a fully first-party product, albeit with additional "Lauritz Knudsen by Schneider Electric" branding.

Originally made as a PR to zigbee2mqtt.io: zigbee2mqtt.io#3351:

Not sure exactly how we usually document multiple model numbers for the same hardware when it's not quite a white label situation. It was sold with both Schneider Electric and "LK" (Lauritz Knudsen) branding on the device (see https://www.lk.dk/produkter/550B1012/wiser-tradlos-lysdaemper-for-indbygning-puck)

They exists as two different products in Schneider Electric's catalog

* https://www.se.com/dk/da/product/CCT5010-0001/connected-dimmer-wiser-micro-module/

* https://www.se.com/dk/da/product/550B1012/wiser-tr%C3%A5dl%C3%B8s-lysd%C3%A6mper-for-indbygning-puck/
  • but their "dimmer guide" makes it clear that they are in fact the same product with two different SKUs (or CRs whatever that means):

image

Adding as white label model for lack of a better place. It was sold as a fully first-party product, albeit with additional "Lauritz Knudsen by Schneider Electric" branding.
@poizan42
Copy link
Contributor Author

poizan42 commented Jan 6, 2025

Actually there is precedence for adding multiple model numbers from the same vendor directly to model:

model: 'CCT5011-0001/CCT5011-0002/MEG5011-0001',

@poizan42
Copy link
Contributor Author

poizan42 commented Jan 6, 2025

Ugh, would it be possible to make the CI scripts actually print what prettier is unhappy about? I'm not really into the whole node ecosystem, but I couldn't see anything obvious from the documentation. Maybe it could call prettier with --write and print out the unified diff between working copy and PR branch?

I will try to set up a node development environment when I have the time to figure out what the problem is, but it feels like a bit of high barrier to just update some documentation :/

@Koenkk Koenkk merged commit bec15f2 into Koenkk:master Jan 6, 2025
2 checks passed
@Koenkk
Copy link
Owner

Koenkk commented Jan 6, 2025

Thanks!

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

Successfully merging this pull request may close these issues.

2 participants