Bump yeelight to 0.5.4

[shenxn]

Proposed change

The bug is introduced in #39542. yeelight version 0.5.3 renames transitions.randomloop to transitions.random_loop which causes AttributeError.
The author of the yeelight library uploads multiple files of version 0.5.3 with different code that causes AttributeError. Bump yeelight to 0.5.4 to fix this problem.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

• This PR fixes or closes issue: fixes Yeelight integration broken in 0.116.1 #41507
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[probot-home-assistant]

Hey there @rytilahti, @zewelor, mind taking a look at this pull request as its been labeled with an integration (yeelight) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[bdraco]

It looks like its this commit

https://gitlab.com/stavros/python-yeelight/-/commit/78632f8e8f652df67010524fb4bbd7ea6990da85

[bdraco]

(venv) root@ha-dev:~/home-assistant# grep random venv/lib/python3.8/site-packages/yeelight/transitions.py 
import random
def random_loop(duration=750, brightness=100, count=9):

Its definitely now random_loop

It seems the CI is using an old package?

[shenxn]

@bdraco Yes seems that the CI is using an old package, and that might be the reason that #39542 passed all checks.

[bessarabov]

Maybe we should also change file requirements_all.txt to bump the version to 0.5.4 ?

I think that there is problem with 0.5.3 — #41507 (comment)

[bessarabov]

After thinking about this problem a bit I think that we definitely should change the version in requirements_all.txt to 0.5.4

I'm not sure what the author of yeelight will do. If he re-re-upload 0.5.3 with the same code as before Home Assistant yeelight integration will break again.

[bieniu]

I also think we should bump yeelight library to version 0.5.4.

[bieniu]

I tested this change locally and everything works as it should.

[bieniu]

IMO, this PR should be tagged 0.116.2.

[slydiman]

Most of problems are fixed in 0.116.2, but something is still broken.
I got the following error: Cannot determine device type for [IP], [name]. Falling back to white only
This yeelight object is completely missing.
The device model is yeelink.light.lamp3
Probably few other yeelight models are broken too.

[MartinHjelmare]

Please open an issue. Thanks!