[Solved] LSC Led strip vs mqtt with tasmota

Configuration
,
1

I bought this ledstrip and I’ve been trying all night to add it to HA with mqtt, but I’m not getting it to work and could use some help.

The ledstrip is flashed with Tasmota and the Tasmota webpage is visible/accessible and I’ve configured the ledstrip for mqtt. The tasmota info page looks like this:

LSC-RGBW-Strip Module
Ledstrip_Zolder
Program Version	    7.0.0.3(tasmota)
Build Date & Time	2019-11-06T23:07:19
Core/SDK Version	STAGE/2.2.2-dev(38a443e)
Uptime	            0T01:09:44
Flash write Count	92 at 0xF8000
Boot Count	        37
Restart Reason	    Software/System restart
Friendly Name 1	    Ledstrip_Zolder
 
AP1 SSId (RSSI)	    XXXXXX (98%)
Hostname	        Ledstrip_zolder
IP Address	        192.168.1.243
Gateway	            192.168.1.1
Subnet Mask	        255.255.255.0
DNS Server	        213.46.228.196
MAC Address	        XX:XX:XX:XX:XX:XX
 
MQTT Host	        192.168.1.239
MQTT Port	        1883
MQTT User	        mosquitto
MQTT Client	        DVES_60C468
MQTT Topic	        Ledstrip_Zolder
MQTT Group Topic    Light/Ledstrip_Zolder/cmnd/
MQTT Full Topic     Light/Ledstrip_Zolder/cmnd/
MQTT Fallback Topic cmnd/DVES_60C468_fb/
 
Emulation	        Disabled
mDNS Discovery      Disabled
 
ESP Chip Id         6341736
Flash Chip Id       0x1540C8
Flash Size          2048kB
Program Flash Size 	1024kB
Program Size        446kB
Free Program Space	556kB
Free Memory	        30kB

In Home Assistant I’ve setup the Mosquitto Addon (following the instructions on the addon page)
I’ve added a mqtt user (‘mosquitto’) and in the mqtt logs I see the ledstrip connecting:

1578187143: New client connected from 192.168.1.243 as DVES_60C468 (p2, c1, k30, u'mosquitto').

I’ve also added the Broker in ‘Configuration, Integrations -> mqtt’ by adding the ip address, port, user & pw. This now shows in the integrations list as: MQTT:192.168.1.239 (But says the integration has no devices.)

In my configuration.yaml I’ve added this:

mqtt:
  broker: 192.168.1.239

(is it correct that if this is missing the mqtt option is not in the developter tools?)

For the light itself I used this:

light:
  - platform: mqtt
    name: "Ledstrip_Zolder"
    command_topic: "cmnd/Ledstrip_Zolder/POWER"
    state_topic: "stat/Ledstrip_Zolder/RESULT"
    state_value_template: "{{ value_json.POWER }}"
    availability_topic: "tele/Ledstrip_Zolder/LWT"
    brightness_command_topic: "cmnd/Ledstrip_Zolder/Dimmer"
    brightness_state_topic: "stat/Ledstrip_Zolder/RESULT"
    brightness_value_template: "{{value_json.Dimmer}}"
    brightness_scale: 100
    on_command_type: "brightness"
    rgb_command_topic: "cmnd/Ledstrip_Zolder/Color"
    rgb_state_topic: "stat/Ledstrip_Zolder/RESULT"
    rgb_value_template: "{{value_json.Color.split(',')[0:3]|join(',')}}"
    effect_command_topic: "cmnd/Ledstrip_Zolder/Scheme"
    effect_state_topic: "stat/Ledstrip_Zolder/RESULT"
    effect_value_template: "{{value_json.Scheme}}"
    effect_list:
      - 0
      - 1
      - 2
      - 3
      - 4
    payload_on: "ON"
    payload_off: "OFF"
    payload_available: "Online"
    payload_not_available: "Offline"
    qos: 1
    retain: false

In the Developer tools under States I can see the ledstrip (light.ledstrip.zolder), but the state is always ‘unavailable’ and I cannot control it. And I can’t figure out what is going wrong, simply because I have no knowledge of where to look…any help would be much appreciated :slight_smile:

2

That is normal. If you configured the led strip manual it will not show in integrations or entities.

Why not use auto-discovery ? In the Tasmota console, just enter setoption19 1

1 Like
3

Cause I didnt know that was a thing…
Thanks for the pointer in the right direction, I have it working now!

4

thx… great