Yeelight Bedside Lights now Unavailable

[davidpadbury]

The problem

I have two yeelight bedside lights (model bslamp2). They were previously working with home assistant but now are shown as being in state unavailable and are no longer controllable.

I also have a yeelight bulb that continues to work fine so the problem seems specific to the bedside lamps.

The lamps remain controllable in the yeelight application and I've verified that the IP addresses are correct.

Environment

• Home Assistant Core release with the issue: 0.110.1
• Last working Home Assistant Core release (if known): unsure - within the last few
• Operating environment (Home Assistant/Supervised/Docker/venv): Home Assistant (hassio)
• Integration causing this issue: yeelight
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/yeelight

Problem-relevant configuration.yaml

Configured using the manual configuration (have tried with and without the model specification):

yeelight:
  devices:
    192.168.3.32:
      name: Porch
    192.168.3.193:
      name: Bedside Lamp 1
      model: bslamp2
    192.168.3.167:
      name: Bedside Lamp 2
      model: bslamp2

I have configured discovery to ignore yeelight.

Traceback/Error logs

Additional information

[probot-home-assistant[bot]]

yeelight documentation yeelight source _{^{(message by IssueLinks)}}

[probot-home-assistant[bot]]

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

[abelmatser]

I have the feeling my Yeelights became more stable after assigning a static IP to them, maybe worth a try. Before, when this happened (every month or so) a quick power unplug (or ultimately, a reset) made them available to me again

[davidpadbury]

@abelmatser yep, your "quick power unplug" suggestion did the trick immediately. I didn't think to do before as they were responding to pings and the yeelight app so assumed the device was fine and was a problem with the integration :facepalm:

Thanks!