Yeelight bulb compatibility

Feature requests
,
1

Possibility to control yeelight bulbs (color/white)

2

I’m ready to take over the continuation of [v4] Dev service Yeelight - #10 par Pti_Nico if something is missing for this service

3 Likes
3

There is already a PR that is rather in the final phase:

I’m waiting for NickDub’s response to my last message, @Exilon62 I invite you to subscribe to the PR notifications, if you see that it is not progressing, you can organize with him to help?

1 Like
4

@Pti_Nico I’m leaving a message here in addition to the message I sent you on GitHub.

Maybe we should have a call to look at these Discovery issues, it might be simpler?

5

Absolutely, because on my end, I don’t have the problem.

6

Will you be at the developer call tonight? We can talk about it tonight!

7

Hello,

I’m here to provide feedback on the service.

On my end, no issues, I fixed the issue that @pierre-gilles had (indeed if you pound the page there is an error, a bit of a stretch as an approach because it will never happen but I think it’s « fixed Â».

I added an additional model :slight_smile:

I’ll let you know when I’ve pushed the image to @Pti_Nico’s.

8

Pull request that fixes the issue and adds my device! :slight_smile:

1 Like
9

Hi @damalgos,

I’ve added some comments about your PR.
Otherwise, well done for adding the model :wink:

10

Oh yes, idiot, what I did :smiley:

But why do you want me to rebase?

11

We can’t start from that principle, everything that « will never happen Â» will happen with the end user, we know that, it’s like that in software development.

And in this case, it was a really critical bug (a crash), so clearly something that should never happen to the end user, otherwise their feedback on Gladys will be « it crashes, poor software stability Â».

12

I know, but I didn’t see how a user could end up in this situation :smiley: I had to force it and open the page 20 times by doing a lot of right clicks ^^ I was just saying that casually ahah It’s a critical bug but with very little chance of happening. Indeed, it is important to fix it.

13

There were conflicts because your branch is not up to date.

14

@damalgos, I made a few last modifications regarding device creation (management by features and not by model).
Let me know if everything is OK for you


15

Hello,

So I did my tests, no problem for me. To know that my bulb is a bulb that manages colors. I thought we managed that in gladys, right?

And I can only manage on/off, it sees the luminosity feature but it’s not present in the dashboard.

Thanks :slight_smile:

16

I have implemented color and temperature management, but it seems that it is not working from the dashboard, as with brightness, in Gladys


17

The color is functional on the Dashboard :slight_smile: but your service needs to handle the color in the same way as Gladys (check out the Philips Hue service for example)

18

I was referring to the temperature

The color works well, indeed :wink:

1 Like
19

For information, I tested the PR this morning, and I still have the same issue. The discover feature is a bit of a mess:

Screenshot 2021-03-01 at 12.29.38
Screenshot 2021-03-01 at 12.29.382316×966 517 KB

I’m not doing anything crazy, I’m just browsing the UI. Are you able to reproduce this kind of error?

20

Indeed, on my end, the same problem occurs, although it might also be because I’m using WSL2 for testing


I’m not sure how WSL2 works. Is it due to network isolation, meaning the search is performed on the local network (of WSL2) and not on the WIFI / WAN network?

image
image832×257 14.6 KB