WLED Live View Proxy for Home Assistant

Share your Projects! Dashboards & Frontend
, , ,
1

Hello, Home Assistant community!

I’d like to share my small integration project called WLED Live View Proxy. It allows you to see a real-time preview of the current effect running on your WLED lights, similar to the built-in “peek” feature of WLED, directly within your Home Assistant dashboard.

image
image2005×750 169 KB

Why did I make this? I wanted a secure and convenient way to remotely preview my lights directly from Home Assistant without using iframes or exposing the WLED interface externally. So I built a secure websocket proxy and a simple-to-use Lovelace card.

The project is fully open-source and available via HACS:

to hear your suggestions and feedback! If you like the project, don’t forget to star it on GitHub!

16 Likes
2

:rocket: WLED Live View Proxy v0.2.1 — Now with JSON Command Support and Gradient Rotation!
Hi again, Home Assistant community!

I’m excited to share an update to my small project — WLED Live View Proxy. With version 0.2.1, it gets two major new features that make it even more powerful and flexible:

:sparkles: What’s New:

  • JSON API Command Service
    You can now send direct WLED JSON API commands (like setting segments, presets, or activating Nightlight mode) via a built-in service:
    wled_liveviewproxy.send_command — great for automations and scripts!
    :white_check_mark: Includes full state return if you add "v": true.
  • Gradient Rotation
    The Lovelace card now supports changing the direction of the gradient, in addition to brightness.

:wrench: Under the Hood:

  • Improved debug logging across all modules
  • Optimized WebSocket command handling and cleanup
  • Updated LitElement CDN with better styling compatibility

You can install the latest version via HACS or update from the repo:

:bulb: A sample dashboard configuration is available here:
:page_facing_up: docs/demo.yaml

Thanks to everyone who tried it out! I’d love to hear how you’re using it, and as always — suggestions and feedback are welcome :raised_hands:
:star: If you find the integration useful, give it a star on GitHub to support the project!

2 Likes
3

Can this be used with the Led controller A1-SLWF-03?
Do I need any other wled integration in HA than this one?

4

Hey @pepe59 :wave:

Yes, this integration should work perfectly with your A1-SLWF-03 LED controller — as long as it’s flashed with WLED firmware.
It communicates directly via the WLED JSON API, so hardware brand doesn’t matter — only that WLED is running.

:white_check_mark: No other WLED integration is required

This integration works independently and gives you live preview, WebSocket control, and advanced JSON commands.

:heavy_plus_sign: Optional: Use alongside the official WLED integration

You can also install the official WLED integration if you want:

  • Built-in entity support (segment brightness, effect dropdowns, etc)
  • UI-based controls for light entities

Both integrations work great together — no conflicts.

:package: GitHub + installation guide:
:link: github.com/danishru/wled_liveviewproxy

2 Likes
5

:wave: Hey everyone! Just a quick update:

:sparkles: v0.2.2 is out!
The wled-ws-card.js card now works fully offline — no more CDN or external imports required.
Perfect for offline setups and improved reliability in your dashboards.

:link: See full changelog

1 Like
6

In your demo.yaml wled_liveviewproxy/docs/demo.yaml at f56720c5157eac7be2f25f743057df9f999a63da · danishru/wled_liveviewproxy · GitHub you have 2 sensors:
wlvp_wled_bead
wlvp_wled_bulbs

After I installed your integration I just have 1 sensor and one light in the device. Is this because you have 2 segments or am I something missing?

7

Hi @eric1905 — good observation!

In the demo.yaml, the two sensors:

  • sensor.wlvp_wled_bead
  • sensor.wlvp_wled_bulbs

…correspond to two separate WLED devices. The integration creates one sensor per WLED instance you add.

So if you currently see only one sensor and one light entity, that means you’ve added just one WLED device — which is completely normal.

To add more, just go to Settings → Devices & Services → Add Integration → WLED Live View Proxy, and repeat the setup for each additional WLED IP.

8

Hi @danishru, I want to send a JSON API command to my WLED device through a button on my dashboard. Unfortunately, I wasn’t able to get it to work with a script. Can you provide an example how the wled_liveviewproxy.send_command is implemented ?

9

Hi Marcel, thanks for using the integration! :blush:
You can use the wled_liveviewproxy.send_command service to send JSON API commands via a button or script in Home Assistant.
A full example is available in the documentation here:

:point_right: JSON API Command Service — GitHub Docs

Here’s a basic example of a script you can call from your dashboard:

alias: test_on_wled
sequence:
  - service: wled_liveviewproxy.send_command
    data:
      targets:
        entity_id:
          - light.wlvp_wled_bulbs
      command:
        "on": true
        bri: 166
    response_variable: return_wled
mode: single
10

Just want to say thank you for this integration. This is so much easier/less complicated than my previous solution of using a reverse proxy and an iframe, which also stopped working with WLED 15.

1 Like
11

Localy, the direct access to the peek is more faster than via websocket (but can’t be seen from internet)

I’m using this kind of card:

  - type: conditional
    conditions:
      - condition: state
        entity: light.wled_studio
        state: "on"
    card:
      type: iframe
      url: http://wled-studio.local/liveview?ws
      aspect_ratio: 2%

Now the real interest is to use service. I have to redo some tests because last try (earlier version of the wled liveview), it was giving me some performances issue in HA core. The script was sending every second a json update to the wled based on the power injection to the grid. I will do a second trial :wink: