Merge pull request #147 from Luligu/dev

Release 2.0.9

Author: Luligu

.npmignore

@@ -15,6 +15,8 @@ src
 tsconfig.json
 tsconfig.eslint.json
 tsconfig.tsbuildinfo
+tsconfig.jest.json
+tsconfig.production.json
 
 # vscode
 .vscode
@@ -170,7 +172,6 @@ rock-s0
 CODEOWNERS
 create-release.js
 src/net
-tsconfig.production.json
 jest
 matterstorage
 matterstorage.backup

CHANGELOG.md

@@ -12,22 +12,34 @@ You can also sponsor Tamer here https://buymeacoffee.com/6sjde6vkzl for his inva
 
 ### Breaking Changes
 
-New setups:
-
-- these components are blacklisted (with entityBlackList) by default: "Lux", "Illuminance", "Vibration", "Button". This allows to create simplified devices for the controllers that don't manage correctly composed devices (i.e. Alexa and SmartThings).
-- all switches are exposed like outlet (matter compliant).
-- shellyplusi4, shellyi4g3, shellyix3 and shellybutton1 are automatically added to inputMomentaryList when discovered.
-- expertMode is disabled (the config shows only username, password, whitelist and blackList).
-
 New device types:
 
 - shellyflood device type has been updated from contact sensor to water leak sensor.
 - shellysmoke device type has been updated from contact sensor to smoke sensor.
-- for all the rgb lights the device type has been updated from colorTemperatureLight to extendedColorLight. This solves SmartThings issues with color lights.
+- the device type for all the rgb lights has been updated from colorTemperatureLight to extendedColorLight. This solves SmartThings issues with color lights.
 
-If your controller has issues detecting the new device type, blacklist the flood and smoke devices, restart, remove the blacklist and restarat again. This will create a new endpoint on the controller.
+If your controller has issues detecting the new device type, blacklist these devices, restart, remove the blacklist and restart again. This will create a new endpoint on the controller.
 For shellyflood, if you have SmartThings, blacklist the Temperature entity for each flood device with deviceEntityBlackList to allow the controller to setup the correct driver.
 
+## [2.0.9] - 2025-04-30
+
+### Added
+
+### Changed
+
+- [package]: Added tsconfig.jest.json with "isolatedModules": true for ts-jest.
+- [package]: Updated package.
+- [package]: Updated dependencies.
+- [plugin]: Requires Matterbridge 3.0.0.
+
+### Fixed
+
+- [WallDisplay]: Fixed PowerSource component.
+
+<a href="https://www.buymeacoffee.com/luligugithub">
+  <img src="bmc-button.svg" alt="Buy me a coffee" width="80">
+</a>
+
 ## [2.0.8] - 2025-04-19
 
 ### Added

COMPONENTS.md

@@ -2,6 +2,13 @@
 
 All components for all devices are exposed to Matter, but it is possible to exclude certain components globally or on a per-device basis.
 
+New setups only:
+
+- these components are blacklisted (with entityBlackList) by default: "Lux", "Illuminance", "Vibration", "Button". This allows to create simplified devices for the controllers that don't manage correctly composed devices (i.e. Alexa and SmartThings).
+- all switches are exposed like outlet (matter compliant).
+- shellyplusi4, shellyi4g3, shellyix3 and shellybutton1 are automatically added to inputMomentaryList when discovered.
+- expertMode is disabled (the config shows only username, password, whitelist and blackList).
+
 ## Example 1: How to Blacklist a Component on a shellyplusrgbwpm Device
 
 Given the components of a shellyplusrgbwpm device (as shown in the logs from the console or frontend):

jest.config.js

@@ -22,6 +22,7 @@ export default {
       'ts-jest',
       {
         useESM: true,
+        tsconfig: 'tsconfig.jest.json',
       },
     ],
   },