Lights now show lightning bolt for on/off instead of button/slider

[amelchio]

@DavidFW1960

Ok so begs the question why it changed to a lightning bolt from a toggle.

Turn on the light with MiLight app. With the toggle, now you cannot turn the light off. You must first change the toggle to on.

Pressing the toggle twice is annoying and it fails if you cannot observe the physical light that you are working with.

[DavidFW1960 (David)]

@amelchio

Pressing the toggle twice is annoying and it fails if you cannot observe the physical light that you are working with.

Ah ok I understand. I never use the app anyway except for testing.

[amelchio]

@DavidFW1960

Just one other thing, I just set the kelvin in the Mi-Light app and it’s a little warmer than the 3100 in HA - it’s ok - just cooler than the app.

We should make it perfect before merging my change. Can you find the new HA value matching MiLight 3100K and also test if the extremes are off (2700K and 6500K)? Thanks!

[DavidFW1960 (David)]

OK!

I am using the .py file you gave me above.

If I set 2700 or 6500 in the app (the extremes) then I see the same as if I set 2000 or 6500 in Home Assistant so the extremes are right.

If I set 3100 in the app, this is the equivalent of 2950 in Home Assistant.

[amelchio]

Thanks, I think I fixed it now.

Can you once again copy this file (it is updated) to config/custom_components/light/limitlessled.py, restart and test 3100K?

[DavidFW1960 (David)]

@amelchio

Thanks, I think I fixed it now.

I think you did as well! I can’t see a difference between the app and Home Assistant now. Well done. I looked in the .py file and don’t really see what you did… I know your original calculation was right so I dunno what you did? Do you need me to test any other temperatures as confirmation over the range?

[amelchio]

Very well . I don’t think further tests are needed but do speak up if you notice anything strange …

I changed the conversion to work on Kelvin rather than Mired (which is what HA uses internally).

[DavidFW1960 (David)]

Ah. How bizzare!

Thanks again. So much better now and understanding more about how all this works too. Great work!

When will this be rolled out generally? (I presume it won’t make next 0.65)

[amelchio]

Now that it is tested it should make it into 0.65.

[DavidFW1960 (David)]

I’ll watch the release notes and then delete the .py file. Thanks again.

[myle (StePhan McKillen (Other kiwi Here))]

The reason for the lighing bolt is

it needs a “state_topic:”

I made mine the same as the

command_topic:

and the you get the switch back

[DavidFW1960 (David)]

@DavidFW1960

homeassistant:
  customize_domain:
    light:
      assumed_state: false

I used this as recommended by the Dev.