SUPERNIGHT WiFi Wireless LED Smart Controller

Anyone know what I’m doing wrong? I can’t seem to get this to work. It doesn’t turn on at 5pm. The time is correct on the Raspberry Pi. I can turn on and off the light in HA.
I’m using this:
SUPERNIGHT WiFi Wireless LED Smart Controller

Got it working…
Scenes.yaml:

- name: LED_Red_10
  entities:
     group.LED_group:
         state: 'on'
         color_name: 'Red'
         brightness: 10

How does the configuration of the led strip look like? are you able to control it from HA?

configuration.yaml:

light:
  - platform: flux_led
    devices:
      xxx.xxx.xxx.xxx:          #network ip address
        name: Kitchen_Ceiling_LED
        mode: "rgb"

counter:
  accent_color_num:
    initial: 0
    step: 1

group:    
  Kitchen_Lighting_Above_Cabinet:
    name: Kitchen Lighting Above Cabinet
    entities:
      - counter.accent_color_num
      - light.Kitchen_Ceiling_LED

script:
  color_scenes:
    sequence:
      - service: counter.increment
        entity_id: counter.accent_color_num
      - service: scene.turn_on
        data_template:
          entity_id: >
            scene.color_{{ states.counter.accent_color_num.state }}    

automation:
  - alias: LEDs on
    trigger:
      platform: time
      minutes: '/7'
      seconds: '/30'
    condition:
      - condition: time
        after: '17:00'
        before: '23:00'
    action:
      - service: script.color_scenes

  - alias: LEDs off
    trigger:
      platform: time
      at: '16:55:00'
      at: '23:01:00'
    action:
      - service: light.turn_off
        entity_id:
          - light.Kitchen_Ceiling_LED
      - service: counter.reset
        entity_id: counter.accent_color_num

scene: !include scenes.yaml

scenes.yaml

- name: LED_off
  entities:
     group.LED_group:
         state: 'off'

- name: color_1
  entities:
     light.Kitchen_Ceiling_LED:
         state: 'on'
         rgb_color: [255,248,224]
         brightness: 200

- name: color_2
  entities:
     light.Kitchen_Ceiling_LED:
         state: 'on'
         rgb_color: [255,245,209]
         brightness: 200

- name: color_3
  entities:
     light.Kitchen_Ceiling_LED:
         state: 'on'
         rgb_color: [255,241,193]
         brightness: 200
################################################
#Note:  I really have 48 scenes, I just listed the first 3 and the last 3.
################################################
- name: color_46
  entities:
     light.Kitchen_Ceiling_LED:
         state: 'on'
         rgb_color: [34,12,46]
         brightness: 200

- name: color_47
  entities:
     light.Kitchen_Ceiling_LED:
         state: 'on'
         rgb_color: [22,8,30]
         brightness: 200

- name: color_48
  entities:
     light.Kitchen_Ceiling_LED:
         state: 'on'
         rgb_color: [11,4,15]
         brightness: 200
1 Like

I have that same device and I swear that is the only thing in my 5:00 turn on scene that won’t turn on. Works if I manually use it in home assistant though. My main issue with that device is every time the power at the house flicks off for something, the device has to be set back up again using the Magic Home app or else it won’t work in Home Assistant. I even assigned it a static IP. It basically forgets its wifi settings.

I am trying to make one of the SuperNight SMD 2835 kits work with HA. Alexa controls the device fine as does my phone. But the light component returns the following errors:

Running the latest Hass.io on an RPI 2.

2018-07-24 23:15:44 WARNING (SyncWorker_10) [homeassistant.components.light.flux_led] Failed to connect to bulb 192.168.1.171, teststrip
2018-07-24 23:15:44 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=light.teststrip, old_state=None, new_state=<state light.teststrip=unavailable; friendly_name=teststrip, supported_features=21 @ 2018-07-24T23:15:44.944005-05:00>>

Here is my base config for the strip:

  - platform: flux_led
    devices:
      192.168.1.171:
        name: teststrip
        mode: "rgb"

I can ping it at the DHCP static assigned address and it goes away when I power it off. It shows up in my router as and ESP device.

Ideas?