No longer able to set dimmer brightness without triggering the light to turn on
### Is there an existing issue for this?

- [X] I have searched the existing issues

### What happened?

Starting with version 7.1 it is not possible to set a dimmer brightness level without triggering the switch to turn on. In version 7.0.1 and previous, one could set the brightness level and the switch would not change state. This is useful for setting all your dimmers to say 5% at night, so that if you do turn it on you won't be blinded, but also ensuring that you don't turn on all your dimmer in your house when doing so. This can't be done with the stock Apple Home app, but can be done using "Controller for Home" app on iOS, where the brightness and power toggle are exposed as 2 seperate and independent functions.

### What, if anything, has recently changed?

All versions after 7.0.1 have this issue. Version 7.1 introduced duplicate switches for all devices which limited functionality. Latest version of plugin fixed the duplicate switches issue, but the "dimming independant of power state" issue still remains.

### Version

8.0.2

### Node Version

20.10.0

### Homebridge Version

4.55.1

### Which OS/Platform?

Linux

### Relevant log output

```shell
Log shows light turning on when brightness is changed as opposed to previously where a dimmer level change did not also trigger light to turn on.
```


### Configuration

```json
"name": "TPLink",
            "addCustomCharacteristics": false,
            "deviceTypes": [
                "plug",
                "bulb"
            ],
            "timeout": 20,
            "devicesUseDiscoveryPort": false,
            "_bridge": {
                "username": "XX:XX:XX:XX:XX:XX",
                "port": XXXXX
            },
            "platform": "TplinkSmarthome"
```
