Broadlink is using different product ids on their sold devices. Many recently sold devices are not supported out-of-the-box with the master branch of python-broadlink.
Although the support of the new device ids was introduced in the new_product_ids branch, many projects use the master branch of python-broadlink as a dependency (famously home-assistant), thus preventing the new devices to work.
Proposed change
I propose integration of the new_product_ids branch into the master branch. This will add the support of the new devices in environments where it isn't easy to use new_product_ids branch, e.g. existing docker images.
Type of change
[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New device
[ ] New product id (the device is already supported with a different id)
[x] New feature (which adds functionality to an existing device)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code ~addition of tests
Context
Broadlink is using different product ids on their sold devices. Many recently sold devices are not supported out-of-the-box with the master branch of
python-broadlink.Although the support of the new device ids was introduced in the
new_product_idsbranch, many projects use the master branch ofpython-broadlinkas a dependency (famously home-assistant), thus preventing the new devices to work.Proposed change
I propose integration of the
new_product_idsbranch into the master branch. This will add the support of the new devices in environments where it isn't easy to usenew_product_idsbranch, e.g. existing docker images.Type of change
Checklist