Repository: uilibs/uiprotect

Issue:
Unable to control UP Floodlight if Floodlight turned in by Protect
### Describe the bug

see Title and https://github.com/home-assistant/core/issues/133872

### To Reproduce

see https://github.com/home-assistant/core/issues/133872

### Additional context

_No response_

### Version

latest

### Platform

HA

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct.

### No Duplicate

- [X] I have checked existing issues to avoid duplicates.

Discussion:
coderabbitai[bot]: <!-- This is an auto-generated comment: summarize by coderabbit.ai -->
<!-- This is an auto-generated comment: review in progress by coderabbit.ai -->

> [!NOTE]
> Currently processing new changes in this PR. This may take a few minutes, please wait...
> 
> <details>
> <summary>📥 Commits</summary>
> 
> Reviewing files that changed from the base of the PR and between 468dcab06e302e3505b082c191758c6b062f84c4 and db37b9bfa7be8c4657ad30793567322ac06af1d2.
> 
> </details>
> 
> <details>
> <summary>📒 Files selected for processing (2)</summary>
> 
> * `src/uiprotect/api.py` (1 hunks)
> * `tests/test_api.py` (1 hunks)
> 
> </details>
> 
> ```ascii
>  ____________________________________________
> < This is what it sounds like when bugs cry. >
>  --------------------------------------------
>   \
>    \   \
>         \ /\
>         ( )
>       .( o ).
> ```

<!-- end of auto-generated comment: review in progress by coderabbit.ai -->

<!-- usage_tips_start -->

> [!TIP]
> <details>
> <summary>You can disable poems in the walkthrough.</summary>
> 
> Disable the `reviews.poem` setting in your project's settings in CodeRabbit to disable the poems in the walkthrough.
> 
> </details>

<!-- usage_tips_end -->
<!-- tips_start -->

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

<details>
<summary>❤️ Share</summary>

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai)
- [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai)
- [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai)
- [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

</details>

<details>
<summary>🪧 Tips</summary>

### Chat

There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai):

- Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  - `I pushed a fix in commit <commit_id>, please review it.`
  - `Generate unit testing code for this file.`
  - `Open a follow-up GitHub issue for this discussion.`
- Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples:
  - `@coderabbitai generate unit testing code for this file.`
  -	`@coderabbitai modularize this function.`
- PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.`
  - `@coderabbitai read src/utils.ts and generate unit testing code.`
  - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.`
  - `@coderabbitai help me debug CodeRabbit configuration file.`

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

### CodeRabbit Commands (Invoked using PR comments)

- `@coderabbitai pause` to pause the reviews on a PR.
- `@coderabbitai resume` to resume the paused reviews.
- `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
- `@coderabbitai full review` to do a full review from scratch and review all the files again.
- `@coderabbitai summary` to regenerate the summary of the PR.
- `@coderabbitai generate docstrings` to [generate docstrings](https://docs.coderabbit.ai/finishing-touches/docstrings) for this PR. ([Beta](https://docs.coderabbit.ai/early-access#beta))
- `@coderabbitai resolve` resolve all the CodeRabbit review comments.
- `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository.
- `@coderabbitai help` to get help.

### Other keywords and placeholders

- Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed.
- Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description.
- Add `@coderabbitai` anywhere in the PR title to generate the title automatically.

### CodeRabbit Configuration File (`.coderabbit.yaml`)

- You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository.
- Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information.
- If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json`

### Documentation and Community

- Visit our [Documentation](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit.
- Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback.
- Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

</details>

<!-- tips_end -->
codecov[bot]: ## [Codecov](https://app.codecov.io/gh/uilibs/uiprotect/pull/347?dropdown=coverage&src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=uilibs) Report
All modified and coverable lines are covered by tests :white_check_mark:

| [Files with missing lines](https://app.codecov.io/gh/uilibs/uiprotect/pull/347?dropdown=coverage&src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=uilibs) | Coverage Δ | |
|---|---|---|
| [src/uiprotect/api.py](https://app.codecov.io/gh/uilibs/uiprotect/pull/347?src=pr&el=tree&filepath=src%2Fuiprotect%2Fapi.py&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=uilibs#diff-c3JjL3VpcHJvdGVjdC9hcGkucHk=) | `56.92% <100.00%> (+0.10%)` | :arrow_up: |


Patch:
diff --git a/src/uiprotect/api.py b/src/uiprotect/api.py
index a63fb19..21334a3 100644
--- a/src/uiprotect/api.py
+++ b/src/uiprotect/api.py
@@ -1835,6 +1835,16 @@ class ProtectApiClient(BaseApiClient):
         """Plays chime tones on a chime"""
         await self.api_request(f"chimes/{device_id}/play-buzzer", method="post")
 
+    async def set_light_is_led_force_on(
+        self, device_id: str, is_led_force_on: bool
+    ) -> None:
+        """Sets isLedForceOn for light."""  # workaround because forceOn doesnt work via websocket
+        await self.api_request(
+            f"lights/{device_id}",
+            method="patch",
+            json={"lightOnSettings": {"isLedForceOn": is_led_force_on}},
+        )
+
     async def clear_tamper_sensor(self, device_id: str) -> None:
         """Clears tamper status for sensor"""
         await self.api_request(f"sensors/{device_id}/clear-tamper-flag", method="post")


Test patch:
diff --git a/tests/test_api.py b/tests/test_api.py
index f872f87..71cb5ba 100644
--- a/tests/test_api.py
+++ b/tests/test_api.py
@@ -1065,3 +1065,48 @@ async def test_play_speaker_with_all_parameters(protect_client: ProtectApiClient
             "ringtoneId": ringtone_id,
         },
     )
+
+
+@pytest.mark.asyncio()
+async def test_set_light_is_led_force_on(protect_client: ProtectApiClient):
+    """Test set_light_is_led_force_on with valid parameters."""
+    device_id = "test_light_id"
+    is_led_force_on = True
+    protect_client.api_request = AsyncMock()
+
+    await protect_client.set_light_is_led_force_on(device_id, is_led_force_on)
+
+    protect_client.api_request.assert_called_with(
+        f"lights/{device_id}",
+        method="patch",
+        json={"lightOnSettings": {"isLedForceOn": is_led_force_on}},
+    )
+
+
+@pytest.mark.asyncio()
+async def test_set_light_is_led_force_on_false(protect_client: ProtectApiClient):
+    """Test set_light_is_led_force_on with is_led_force_on set to False."""
+    device_id = "test_light_id"
+    is_led_force_on = False
+    protect_client.api_request = AsyncMock()
+
+    await protect_client.set_light_is_led_force_on(device_id, is_led_force_on)
+
+    protect_client.api_request.assert_called_with(
+        f"lights/{device_id}",
+        method="patch",
+        json={"lightOnSettings": {"isLedForceOn": is_led_force_on}},
+    )
+
+
+@pytest.mark.asyncio()
+async def test_set_light_is_led_force_on_invalid_device_id(
+    protect_client: ProtectApiClient,
+):
+    """Test set_light_is_led_force_on with invalid device ID."""
+    device_id = "invalid_id"
+    is_led_force_on = True
+    protect_client.api_request = AsyncMock(side_effect=BadRequest)
+
+    with pytest.raises(BadRequest):
+        await protect_client.set_light_is_led_force_on(device_id, is_led_force_on)