I copied the example code to a file, and ran it. It pulled the version, but bailed turning on the WLED module.
using WLED 0.13.0-b5, python 3.10.0

import asyncio

from wled import WLED


async def main():
    """Show example on controlling your WLED device."""
    async with WLED("10.0.0.47") as led:
        device = await led.update()
        print(device.info.version)

        # Turn strip on, full brightness
        await led.light(on=True, brightness=255)


if __name__ == "__main__":
    asyncio.run(main())

PS C:\Users\nicko\OneDrive\Documents\Repos\nellson\nellson> python .\wled-test.py
0.13.0-b5
Traceback (most recent call last):
  File "C:\Users\nicko\OneDrive\Documents\Repos\nellson\nellson\wled-test.py", line 17, in <module>
    asyncio.run(main())
  File "C:\Users\nicko\AppData\Local\Programs\Python\Python310\lib\asyncio\runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "C:\Users\nicko\AppData\Local\Programs\Python\Python310\lib\asyncio\base_events.py", line 641, in run_until_complete
    return future.result()
  File "C:\Users\nicko\OneDrive\Documents\Repos\nellson\nellson\wled-test.py", line 13, in main
    await led.light(on=True, brightness=255)
AttributeError: 'WLED' object has no attribute 'light'
Exception ignored in: <function _ProactorBasePipeTransport.__del__ at 0x00000214AF0672E0>
Traceback (most recent call last):
  File "C:\Users\nicko\AppData\Local\Programs\Python\Python310\lib\asyncio\proactor_events.py", line 116, in __del__
    self.close()
  File "C:\Users\nicko\AppData\Local\Programs\Python\Python310\lib\asyncio\proactor_events.py", line 108, in close
    self._loop.call_soon(self._call_connection_lost, None)
  File "C:\Users\nicko\AppData\Local\Programs\Python\Python310\lib\asyncio\base_events.py", line 745, in call_soon
    self._check_closed()
  File "C:\Users\nicko\AppData\Local\Programs\Python\Python310\lib\asyncio\base_events.py", line 510, in _check_closed
    raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed
PS C:\Users\nicko\OneDrive\Documents\Repos\nellson\nellson>

With popular strip chips like FW1906 hitting the market with RGBCCT leds support and with WLED properly supporting CCT channel from version 0.15 we really need CCT support in python-wled as well.

This would allow adding those kind of strip to home assistant as well, because as for now it's not possible to add them (if cct strip is detected the config flow is being stopped) Aircoookie/WLED#3298 (comment) and home-assistant/core#101029 (comment)

This was already asked here: #977

Moreover, a PULL request was already made (I was going to implement basically the same before checking for existing PRs): #1137

It was closed by bot for stale, but please consider merging it to allow me opening a PR to home assistant adding support for CCT strips, thank you.

Frenck, could You add support control of brightness and power per segment implemented in WLED 0.10.0?
Thank you for your work!!

While troubleshooting an issue, I've stumbled upon this erroneous check:

https://github.com/frenck/python-wled/blob/e427bd63eb960ab66d379fd070780ed476215d16/src/wled/models.py#L713C13-L713C50

If the key is not in the dict (k not in data), accessing that non-existent key (and data[k]) will throw an KeyError exception.
I assume it should be like

if any(
    k not in data or data[k] is None
    for k in ("effects", "palettes", "info", "state")
):

cheers!

Problem/Motivation

Related to: home-assistant/core#93475
Every time the state gets updated, the update sensor in HA goes unavailable. It looks like this is caused by this library as every time this

Expected behavior

After the versions have been fetched, cache and re-use them (unless the full_update parameter is set to True).

Actual behavior

Version gets fetched again.

Steps to reproduce

• Use the WLED integration in HomeAssistant and toggle a the light switch
• Watch how the firmware update sensor goes to Unkown

Since yesterday my internet connection isn’t working anymore because failure from the ISP side.
That sucks but HA works locally too for, right?

Well actually I noticed all my WLED interfaces don’t work anymore through the Home Assistant integration.

The error message the integration gives is :Invalid response from API: Timeout occurred while communicating with GitHub for WLED version

The WLED instances are reachable through the local network to their IP addresses and the WLED app with the instances is working fine. When I click on a device in the HA integration I can also click the button ‘Go to device’ which points me to the actual device on my local network.

I’ve deleted one of the lights and tried to re add is but then I get an error that it’s unable to connect, which is strange because I can actually ping the instance from both the HA cli and the server HA is running on. (Proxmox server)

Previously WLED devices did work without an internet connection. When we moved last November we didn’t had an internet connection for a couple of days but through the local network I would still be able to manage my WLED instances.

Nothing changed in my local network except that I don’t have a WAN connection at the moment.

I can’t find any specific WLED errors in the logs either so that ain’t much helpful.

I understand that some API call require an internet connection but I don’t see why the basic functionality of a WLED integration requires an internet connection. Is this a bug or did something change recently or am I overseeing something?

Problem/Motivation

WLED 0.13.0 added a new parameter in the API for changing the color temperature of the white color, for lights that support cold and warm whites. It's called "cct". See here https://kno.wled.ge/interfaces/json-api/
It will be nice to have a support for this.

Expected behavior

Providing this ability will allow us to control the temperature of the white color.

Actual behavior

I don't see any way to control the temperature of the white color.

Steps to reproduce

Check out the current API.

Proposed changes

In the segment method of the WLED class, add another "cct" argument. This argument should be translated to the "cct" parameter in the JSON that is sent to the WLED controller.

What needs to be done to add upgrade support for the new ESP32 board types, like ESP32-C3? With https://github.com/Aircoookie/WLED/releases/tag/v0.14.0, there's "-S2/-C3/-S3" (initial) support.

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/wled/helpers.py", line 28, in handler
    await func(self, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/components/wled/update.py", line 88, in async_install
    await self.coordinator.wled.upgrade(version=version)
  File "/usr/local/lib/python3.11/site-packages/wled/wled.py", line 661, in upgrade
    raise WLEDUpgradeError(msg)
wled.exceptions.WLEDUpgradeError: Upgrade is only supported on ESP01, ESP02, ESP32 and ESP8266 devices

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 226, in handle_call_service
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 2012, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2049, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 235, in handle_service
    return await service.entity_service_call(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 876, in entity_service_call
    response_data = await _handle_entity_call(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 948, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 157, in async_install
    await entity.async_install_with_progress(version, backup)
  File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 432, in async_install_with_progress
    await self.async_install(version, backup)
  File "/usr/src/homeassistant/homeassistant/components/wled/helpers.py", line 37, in handler
    raise HomeAssistantError("Invalid response from WLED API") from error
homeassistant.exceptions.HomeAssistantError: Invalid response from WLED API

As WLED 0.11.1 now supports a json attribute to determine if a white value is required, this could be used to determine if a white value should be sent. When the controller runs in rgbw mode with automatic white value calculation, the leds.wv flag is set to false.

To maintain backwards compatibility we can check for the existence the field, and if it does not exist assume it should be true. This should keep the current behavior for older WLED versions.

It looks like this should not be hard to implement, so I am willing to create a PR with this change if you are willing to accept it.

I am sorry, if this does not fit here, but I noticed the following.

In src/wled/wled.py there are two functions async def preset and async def playlist that both POST a request to /json/state with data={"ps": preset} or data={"ps": playlist}, respectively.

If I understand https://kno.wled.ge/interfaces/json-api/ correctly, the "ps" parameter should be used to set the preset, but since 0.11.0 "playlist" can be used to select a playlist. So I think, using data={"ps": playlist} in async def playlist is wrong, but should be something like data={"playlist": playlist}.

I have no idea what that implies about backwards compatibility.

I noticed that with homeassistant, when selecting a playlist through homeassistant's web UI the correct playlist is exececuted on the led strip, but at the same time, the hass UI displayed an error that $nameOfThePlaylist is not a valid preset option.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• ⬆️ Lock file maintenance

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• ⬆️ Update dependency ruff to v0.4.6
• ⬆️ Update dependency codespell to v2.3.0

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• ⬆️ Update codecov/codecov-action action to v4
• ⬆️ Update dependency pytest to v8

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

How do I set the device state?

I would like to use this library to control my WLED device, but cannot find documentation on usage.

Expected behavior

I would like to find the command (likely AWAIT) to set/command it to switch to {device.state.preset.name}, similar to how you have used:
await led.master(on=True, brightness=64)

Actual behavior

All I see in the example is how to read {device.state.preset.name}, please help! Thank you!