Limitless LED Bridge in docker

Configuration
1

I’ve got a MiLight iBox 2 bridge which i can control fine from the android app, however i’m getting nowhere with HA sadly.

I’m running the homeassistant/home-assistant:latest docker on unraid,

Configuration:

light:
platform: limitlessled
bridges:
- host: 192.168.1.83
groups:
- number: 2
name: Fishtank

And in the logs I’m getting this error:

e[31m2018-02-12 14:00:01 ERROR (MainThread) [homeassistant.components.light] Error while setting up platform limitlesslede[0m

Traceback (most recent call last):
File “/usr/src/app/homeassistant/helpers/entity_platform.py”, line 84, in async_setup
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File “/usr/local/lib/python3.6/asyncio/tasks.py”, line 358, in wait_for
return fut.result()
File “/usr/local/lib/python3.6/asyncio/futures.py”, line 243, in result
raise self._exception
File “/usr/local/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/src/app/homeassistant/components/light/limitlessled.py”, line 119, in setup_platform
‘fade’: group_conf[CONF_FADE]
File “/usr/src/app/homeassistant/components/light/limitlessled.py”, line 177, in factory
return LimitlessLEDRGBWGroup(group, config)
File “/usr/src/app/homeassistant/components/light/limitlessled.py”, line 258, in init
self.group.white()
File “/usr/local/lib/python3.6/site-packages/limitlessled/group/rgbw.py”, line 56, in white
cmd = self.command_set.white()
AttributeError: ‘CommandSetRgbwV6’ object has no attribute 'white’e[0m
e[32m2018-02-12 14:00:01 INFO (MainThread) [homeassistant.core] Bus:Handling
<Event system_log_event[L]: timestamp=1518408001.9279697, level=ERROR, message=Error while setting up platform limitlessled, exception=Traceback (most recent call last):

File “/usr/src/app/homeassistant/helpers/entity_platform.py”, line 84, in async_setup
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File “/usr/local/lib/python3.6/asyncio/tasks.py”, line 358, in wait_for
return fut.result()
File “/usr/local/lib/python3.6/asyncio/futures.py”, line 243, in result
raise self._exception
File “/usr/local/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/src/app/homeassistant/components/light/limitlessled.py”, line 119, in setup_platform
‘fade’: group_conf[CONF_FADE]
File “/usr/src/app/homeassistant/components/light/limitlessled.py”, line 177, in factory
return LimitlessLEDRGBWGroup(group, config)
File “/usr/src/app/homeassistant/components/light/limitlessled.py”, line 258, in init
self.group.white()
File “/usr/local/lib/python3.6/site-packages/limitlessled/group/rgbw.py”, line 56, in white
cmd = self.command_set.white()
AttributeError: ‘CommandSetRgbwV6’ object has no attribute ‘white’
, source=components/light/limitlessled.py>e[0m

2

You’re missing the light type. Here is my config:

# LimitlessLED
- platform: limitlessled
  bridges:
    - host: x.x.x.x
      version: 6
      port: 5987
      groups:
      - number: 1
        type: rgbww
        name: Lounge
      - number: 2
        type: rgbww
        name: Dining
      - number: 3
        type: rgbww
        name: Office
      - number: 4
        type: rgbww
        name: Spots

I have my lights split off into a lights.yaml file but you can see what it needs to look like.
Your spacing might be off too but it’s hard to tell when you don’t format it correctly.

3

Thanks for your response. I’m sure I previously had the type in there, but it doesn’t seem to have made a difference. I’ve attached the updated config (hopefully formatted properly). I’m not really sure about the YAML syntax / spacing.

light:
  platform: limitlessled
  bridges:
    - host: 192.168.1.83
      groups:
      - number: 2
        type: rgbw
        name: Fishtank
4

I’ve had a bit more progress - i’ve tried some different options in the config, as per below, and now the controls appear properly in HA, but they don’t do anything at all with the lights.

Config:
    light:
      platform: limitlessled
      bridges:
        - host: 192.168.1.83
          version: 5
          port: 8899
          groups:
          - number: 2
            type: rgbw
            name: Fishtank

Log:
e[32m2018-02-13 09:44:12 INFO (Thread-3) [limitlessled.pipeline] Starting a new pipeline on group 2 (Fishtank) @ 192.168.1.83e[0m
e[32m2018-02-13 09:44:12 INFO (Thread-3) [limitlessled.pipeline] -> Running stage ‘on()’ on group 2 (Fishtank) @ 192.168.1.83e[0m
e[32m2018-02-13 09:44:12 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=light.fishtank, old_state=<state light.fishtank=off; friendly_name=Fishtank, supported_features=61 @ 2018-02-13T09:44:11.757089+10:00>, new_state=<state light.fishtank=on; brightness=255, min_mireds=154, max_mireds=500, rgb_color=(255, 73, 118), friendly_name=Fishtank, supported_features=61 @ 2018-02-13T09:44:12.836334+10:00>>e[0m
e[32m2018-02-13 09:44:12 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_executed[L]: service_call_id=22891462473040-34>e[0m
e[32m2018-02-13 09:44:12 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=group.all_lights, old_state=<state group.all_lights=off; entity_id=(‘light.fishtank’,), order=0, auto=True, friendly_name=all lights, hidden=True @ 2018-02-13T09:44:11.758601+10:00>, new_state=<state group.all_lights=on; entity_id=(‘light.fishtank’,), order=0, auto=True, friendly_name=all lights, hidden=True @ 2018-02-13T09:44:12.838163+10:00>>e[0m
e[32m2018-02-13 09:44:12 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_executed[L]: service_call_id=22891462473040-33>e[0m
e[32m2018-02-13 09:44:13 INFO (Thread-3) [limitlessled.pipeline] -> Running stage ‘transition(0, brightness=1.0, color=Color(R=255, G=73, B=118))’ on group 2 (Fishtank) @ 192.168.1.83e[0m

5

Port 5987 is the default for a ver6 bridge. Was there a reason you changed it? And you set a ver5 but said you have an ibox v2 which is ver 6.

6

If i log into the bridge it has the current port for the TCP server as 8899.

If i try changing the bridge to v6, or the port, it reports they python errors in my first post.

7

Using what? If it’s using 8899 and does not like ver6 it’s not a ver2 iBox (which you claimed in first post)

8

That looks like this bug.

1 Like
9

Ah!!! I’m using RGBWW so that would explain it. Apparently (according to your link) it’s fixed in 0.63.1

10

I did find this a bit weird also, however I bought this from Banggood which definitely says v2 iBox.

11

Does it say iBox2 on it?

12

If you want better support for Mi-light in HA I strongly suggest you to use https://github.com/sidoh/esp8266_milight_hub this allow you to emulate unlimited hubs and control your bulbs with MQTT .

If you have Mi-Light remotes also syncs the state in HA and/or you can use automations to use the remote to control anything in HA.

13

This project is beyond the abilities and interest of most people I’d say. Better to wait for it to be fixed here. The project also doesn’t support the newest RGBWW from my reading.

14

I totally discord of you.

Why do you want to connect something to HomeAssistant that does not have the correct state?
It’s very nice when you turn the bulb on Milight App or the remote and want to turn it off in HA and have to double press the button(?), or maybe everytime we want to turn on/off a milight we pull our mobile phone to open HA frontpage to keep the state correct.

iBox’s cost around 10euros each with a bulb limit! This device costs less then 5euros and has no bulb limit.

I don’t know if it supports rgbww or not (i find it hard to belive it doesnt) but @sidoh the creator of the “gateway” is a member on our forum and the project gets updated frequently.

PS: Oh and I almost forgot about the bulbs turning off when HA reboots, so much fun playing with HA and having Milights in the living room.

15

The device I’m using is exactly as per the listing I sent you - the Model number is clearly listed as iBox2

16

It’s not listed as supported.

The cost is not the issue. It’s more the fact this project is WAY beyond what most people on here can do.

17

Then configuring it as a v5 box is never going to work even when they fix it.