How to alias device configs? #2779
Replies: 3 comments 3 replies
-
seems like templating is the way to do this. I see no references to |
Beta Was this translation helpful? Give feedback.
-
It the device finger print is identical (manufacturer, productType and productID) we can't distinguish them so they go in one file and both model numbers are added to the file. If they are distinguishable we generally put them in different files unless there is a good reason not to, like different model numbers for different frequencies (X-US and X-EU). I'm not aware of any based solely on color but I'd be fine combining those. To do that you'd just add the fingerprint to the file and expand the label "14295 / 14296". |
Beta Was this translation helpful? Give feedback.
-
The SKU change was mainly a marketing ploy for most of their active products. The switches are a little slimmer, the leads are pre-stripped for “simple-wire” and the heat-sync flanges were removed. The core functionality (and programming) was not touched. There should not be separate files added, the productIDs should be added as additional to the existing. |
Beta Was this translation helpful? Give feedback.
-
It's common for two devices to be identical other than ID and branding. For example,
SKU 14296 = https://byjasco.com/ge-z-wave-plus-wall-smart-dimmer-light-almond-toggle-500s
is identical to
SKU 14295 = https://byjasco.com/ge-enbrighten-z-wave-plus-smart-dimmer-with-quickfittm-and-simplewiretm-toggle-white
other than product SKU, color, and slightly different branding ("GE Enbrighten" vs "Enbrighten")
14296 did not have an entry in zwavealliance or in zwavejs config, so I submitted #2778. But I basically just copied and pasted the json from packages/config/config/devices/0x0063/14295_46204_zw3011.json
Is there a better way? I haven't dig into the templating system yet, but perhaps I should be using that?
Beta Was this translation helpful? Give feedback.
All reactions