Issue with Limitless Led Lights

[ryanlaux]

I have four bulbs setup, and two are involved in a few scenes. Everything works and executes fine, but after about 5 minutes of the server running on a raspberry pi, the bulbs involved in the scenes stop responding to home assistant. They work fine using their own iOS app. Interestingly, the bulbs I do not yet have in a scene continue to work.

It's also worth noting that the bulbs that continue working are 6w and the troubled bulbs are 9w. Any suggestions?

[happyleavesaoc]

Can you paste your scene config here, and your light config? What version bridge are you running?

[ryanlaux]

When I first boot or restart home assistant everything seems to work fine, I can trigger the scenes and turn on and off all the added light bulbs. I have four bulbs and put them each on their own group for individual control. After about 10-15 minutes the 2 bulbs within the scenes simply stop responding to requests, either by means of the scene trigger or the switch for each bulb. Like I mentioned earlier, the two additional bulbs not in scenes still work fine.

In debugging I tried making the "TV Left/Right" lights on the same group number as the other lights in the light platform config, and after the scene lights stop responding to their own named switches, strangely they'll respond to the TV Left/Right switches (since they are now pointing to the same bulbs).

I believe I have version 4 of the bridge ( I have night mode capability ) but almost certain I don't have version 5. Running on raspberry pi 1 B2.

homeassistant:
  # Name of the location where Home Assistant is running
  name: Home
  # Location required to calculate the time the sun rises and sets
  latitude: 40.266412
  longitude: -74.781919
  # C for Celcius, F for Fahrenheit
  temperature_unit: F
  # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  time_zone: America/New_York

http:

# Discover some devices automatically
discovery:

# Enables the frontend
frontend:

# Track the sun
sun:

# Show links to resources in log and frontend
introduction:

# View all events in a logbook
logbook:

# Allows you to issue voice commands from the frontend
conversation:

# Enables support for tracking state changes over time.
history:

# Checks for available updates
updater:

#device_tracker:
#  platform: icloud
#  username: 
#  password: 
#  # If new discovered devices are tracked by default (default: yes)
#  track_new_devices: yes
#  # Seconds between each scan for new devices (default: 12)
#  interval_seconds: 12
#  # Seconds to wait till marking someone as not home after not being seen
#  # (default: 180)
#  consider_home: 180

light:
  platform: limitlessled
  bridges:
    - host: 192.168.0.03
      version: 5
      port: 8899
      groups:
      - number: 1
        type: rgbw
        name: TV Left
      - number: 2
        type: rgbw
        name: TV Right
      - number: 3
        type: rgbw
        name: Ryan
      - number: 4
        type: rgbw
        name: Chris

scene:
  - name: Livingroom normal
    entities:
        light.ryan:
            state: on
            transition: 2
            brightness: 255
            rgb_color: [255, 255, 255]  
        light.chris:
            state: on
            transition: 2
            brightness: 255
            rgb_color: [255, 255, 255]  
  - name: Livingroom dim
    entities:
        light.ryan:
            state: on
            transition: 2
            brightness: 20
            rgb_color: [255, 255, 255]  
        light.chris:
            state: on
            transition: 2
            brightness: 20
            rgb_color: [255, 255, 255]  
  - name: Reading
    entities:
        light.ryan:
            state: on
            transition: 2
            brightness: 204
            rgb_color: [255, 38, 0]
        light.chris:
            state: on
            transition: 2
            brightness: 204
            rgb_color: [255, 38, 0]   

automation:
- alias: livingroom_dim

  trigger:
    platform: event
    event_type: 'livingroom_dim'

  action:
    service: scene.turn_on
    entity_id: scene.livingroom_dim

[ryanlaux]

Not sure why github is bolding parts of my config but the meat of it starts at the light platform

[happyleavesaoc]

I edited your response (only) to format the config.

Can you try your scenes, but without the transition?

[ryanlaux]

I'll give that a shot. Just delete the line entirely?

[happyleavesaoc]

Yes. Also check your logs for messages from limitlessled.pipeline. You should always see a message that says "Starting a new pipeline on group X" followed by the specific settings you chose, followed by "Finished pipeline on group X", for each state change.

[ryanlaux]

So far so good! I guess these bulbs don't like transitions forced on them

[happyleavesaoc]

Transitions work in my scenes, so I wonder what the difference is. Anyway, there is probably some bug in the limitlessled module. The transitions functionality is fairly complicated since its implemented entirely in the module.

[ryanlaux]

Yeah not sure what would cause the issue. When it works it's great but then just locks up. Seems to be working for over 10 hours now though so I'm happy with it. My biggest goal is getting them controlled by Amazon echo

On Thursday, February 11, 2016, happyleavesaoc notifications@github.com wrote:

Transitions work in my scenes, so I wonder what the difference is. Anyway, there is probably some bug in the limitlessled module. The transitions functionality is fairly complicated since its implemented entirely in the module.

— Reply to this email directly or view it on GitHub https://github.com/balloob/home-assistant/issues/1193#issuecomment-183050097 .

[robbiet480]

Closing in favor of #1459.