Update DeepSmart driver to latest version

[refuseRed]

Check all that apply

Type of Change

• WWST Certification Request
  • If this is your first time contributing code:
    • I have reviewed the README.md file
    • I have reviewed the CODE_OF_CONDUCT.md file
    • I have signed the CLA
  • I plan on entering a WWST Certification Request or have entered a request through the WWST Certification console at developer.smartthings.com
• Bug fix
• New feature
• Refactor

Checklist

• I have performed a self-review of my code
• I have commented my code in hard-to-understand areas
• I have verified my changes by testing with a device or have communicated a plan for testing
• I am adding new behavior, such as adding a sub-driver, and have added and run new unit tests to cover the new behavior

Description of Change

Summary of Completed Tests

[github-actions]

Profile category check: ✅ Passed - all profiles have a category defined.

[github-actions]

Duplicate profile check: Passed - no duplicate profiles detected.

[github-actions]

Invitation URL:
https://bestow-regional.api.smartthings.com/invite/RBlE6Qr8wvjE

[github-actions]

Test Results

   73 files    544 suites   0s ⏱️
3 304 tests 3 304 ✅ 0 💤 0 ❌
5 297 runs  5 297 ✅ 0 💤 0 ❌

Results for commit c9a5b13.

♻️ This comment has been updated with latest results.

[refuseRed]

@charliek @posborne @dmart @claude 您好，麻烦帮忙看一下这个 PR 的 CI 状态。

目前情况如下：

• ✅ Luacheck 已通过
• ✅ Driver Tests (5761) 全部通过（39615246 个测试全部 0 失败）
• ❌ Run driver tests 失败，但我查看日志后发现错误似乎与我的 DeepSmart 驱动改动无关
• ❌ Jenkins driver tests 显示 444 errors，但从日志看失败用例主要集中在 tuya-zigbee 驱动的 Window Shade 相关测试上，与本次 PR 修改的 DeepSmart 驱动没有关联

我已将最新代码与 upstream/main 同步，冲突已解决，且核心功能测试全部通过。请问：

1. 这两个失败的检查是否与我的 PR 无关，属于环境问题或其他驱动的遗留问题？
2. 如果是，是否可以忽略或由管理员协助重新触发测试？

如果需要我进一步配合，请告知。谢谢！

[refuseRed]

@posborne @claude @jtp10181 @greens Hello, could you please help check the CI status of this PR.
The current situation is as follows:
✅ Luacheck has passed
✅ Driver Tests (5761) have all passed (39,615,246 tests with 0 failures)
❌ The driver tests failed, but after reviewing the logs, I found that the error did not seem to be related to my modifications to the DeepSmart driver
❌ Jenkins driver tests show 444 errors, but according to the logs, the failed test cases are mainly concentrated in the Window Shade-related tests of the tuya-zigbee driver, which are unrelated to the DeepSmart driver modified in this PR
I have synchronized the latest code with upstream/main, resolved all conflicts, and successfully passed all core function tests. Excuse me:
Are these two failed checks unrelated to my PR, and are they caused by environmental issues or other lingering problems?
If so, can it be ignored or can the administrator assist in retriggering the test?
If further cooperation is required from me, please let me know. Thank you!

[cjswedes]

Please update your branch to include the latest changes. Several things have changed in the last month relating to the integration test runs.

[refuseRed]

@cjswedes 现在这里有一个问题, 但是无法点击查看详情, 请问什么原因 ?

[refuseRed]

@cjswedes CI 测试已经全绿了，请求 Review

[refuseRed]

@cjswedes CI checks are all green. Could you please review this PR?

[refuseRed]

@cjswedes All CI tests passed. But the license/cla check seems stuck. Could a maintainer please help check this, or manually merge this PR?

[hcarter-775]

Hi @refuseRed , before moving forward here, can you please:

1. Give a description of the changes and what the goal's are for this PR
2. Give a list of tests completed to ensure new behavior works as expected, and that no serious regressions will be found?

Thanks!

[refuseRed]

Hi @hcarter-775 , thanks for reviewing!

Here is the information you requested:

1. Description & Goals:
   The main goal of this PR is to fix the air conditioner offline bug.
   The changes are minimal and localized to this specific bug. No other features or logic have been modified.

2. List of Tests Completed:

Manual Testing: I performed manual testing locally to verify that the air conditioner offline bug is resolved and the device now behaves correctly.

Regression Check: Since no other code was changed, there should be no impact on other features.

Automated CI Checks: All 22 automated CI checks passed successfully.

Please let me know if you need any further details. Thanks!

[refuseRed]

@cjswedes @hcarter-775 This PR originally had 4 commits, and all checks passed on the final commit. I have squashed the commits down to a single one. The current failing test is not caused by our code changes. Could the maintainers please help investigate this?