Detecting wrong bulb type

Support
1

Finally got DYIhue docker running. learned my lesson on graceful shutdowns…

connected to hue essentials, AND philips app!! both apps see both hubs, real and diy!
so effing happy!

all my lights are “detected” but some are detected as wrong type.
mainly hue light strips.
this example is an official Hue Gradient lightstrip for 65" tv. (5 zone)

image
can you please list each “model number” and what product it is supposed to represent in the documentation?

half of these model numbers return no relevant results on google.

2nd image is a single color strip. same thing happens to my desk strip.
image

i asked last year, and got 2 conflicting answers from 2 people on which is official gradient light strip and which is DYI gradient lightstrip.

please put it in the documentation so there is no confusion. no guessing. and less asking in forum.

2
  • LCT001 - ?
  • LCT015 - Hue White and Color Ambiance A19 E26
  • LST002 - Philips Hue LightStrip Plus
  • LWB010 - Philips Hue White B22
  • LTW001 - ?
  • LCX002 - Philips Hue Play Gradient Lightstrip
  • LCX004 - Philips Hue Gradient Lightstrip 2m
  • LOM001 - Philips Hue Smart Plug

300 others found on Database of Zigbee devices compatible with ZHA, Tasmota, Zigbee2MQTT, deCONZ, ZiGate and ioBroker
LCT001 & LTW001 were not among the results.

3

so after correcting model ID and a reboot
deleting, finding, correcting ID, reboot
hue app reports the ID as I set. but light type is wrong.

DIY HUE screenshot:

image
image1080×2280 97.6 KB

Philips Hue screenshot of same device

image
image1080×2280 124 KB

If i hit “search for lights” again, it un-does my changes to model id

4

the “play gradient lightstrip” is the one i care the most about, as i want to make DIY versions.

my other non-gradient lightstrips, one is LST002 and the newer one is LCL001 (model not found Database of Zigbee devices compatible with ZHA, Tasmota, Zigbee2MQTT, deCONZ, ZiGate and ioBroker but should work as LST002)

5

and now it wont survive a reboot.

‘’‘ImportError: sys.meta_path is None, Python is likely shutting down
Exception ignored in: <function Light.del at 0x14d918b9c040>
Traceback (most recent call last):
File “/opt/hue-emulator/HueObjects/init.py”, line 307, in del
ImportError: sys.meta_path is None, Python is likely shutting down
Exception ignored in: <function Light.del at 0x14d918b9c040>
Traceback (most recent call last):
File “/opt/hue-emulator/HueObjects/init.py”, line 307, in del
ImportError: sys.meta_path is None, Python is likely shutting down
Exception ignored in: <function Light.del at 0x14d918b9c040>
Traceback (most recent call last):
File “/opt/hue-emulator/HueObjects/init.py”, line 307, in del
ImportError: sys.meta_path is None, Python is likely shutting down
Exception ignored in: <function Light.del at 0x14d918b9c040>
Traceback (most recent call last):
File “/opt/hue-emulator/HueObjects/init.py”, line 307, in del
ImportError: sys.meta_path is None, Python is likely shutting down’‘’

delete user data, reboot, set timezone, pair to hue hub.
search for lights
set model ID on 3 lights.
connect to hue essentials
connect to hue app…
stops responding.
stop diyhue docker gracefully from UNRAID gui.
start diyhue docker…
fails to boot.

FFFFFFFFFFFFFFF

OMG this app bumms me out some days.
no wonder its been over a year since i last tried.

6

I also have the same issue as above, is there a fix for this?

1 Like
7

updated docker to new version.
deleted appdata folder
started docker.

link to hue
scan for lights
change light model ID type.
half the lights show offline today. THIS IS NEW.
stop docker.
count to 3
start docker.
FAILS TO START.

i want to love this…
it doesnt want my love.

8

logs:

File “/opt/hue-emulator/HueObjects/init.py”, line 307, in del
ImportError: sys.meta_path is None, Python is likely shutting down
Exception ignored in: <function Light.del at 0x14c3e1d41550>
Traceback (most recent call last):
File “/opt/hue-emulator/HueObjects/init.py”, line 307, in del
ImportError: sys.meta_path is None, Python is likely shutting down
Exception ignored in: <function Light.del at 0x14c3e1d41550>
Traceback (most recent call last):
File “/opt/hue-emulator/HueObjects/init.py”, line 307, in del
ImportError: sys.meta_path is None, Python is likely shutting down
Exception ignored in: <function Light.del at 0x14c3e1d41550>
Traceback (most recent call last):
File “/opt/hue-emulator/HueObjects/init.py”, line 307, in del
ImportError: sys.meta_path is None, Python is likely shutting down
Exception ignored in: <function Light.del at 0x14c3e1d41550>
Traceback (most recent call last):
File “/opt/hue-emulator/HueObjects/init.py”, line 307, in del
ImportError: sys.meta_path is None, Python is likely shutting down
Exception ignored in: <function Light.del at 0x14c3e1d41550>
Traceback (most recent call last):
File “/opt/hue-emulator/HueObjects/init.py”, line 307, in del
ImportError: sys.meta_path is None, Python is likely shutting down
Exception ignored in: <function Light.del at 0x14c3e1d41550>
Traceback (most recent call last):
File “/opt/hue-emulator/HueObjects/init.py”, line 307, in del
ImportError: sys.meta_path is None, Python is likely shutting down

9

Did you ever get a resolution for this? I seem to get the same in that i can add lights, connect to the app etc etc. Then it stops connecting and fails to start

i’ve tried adding lights from home assistant one by one to try and find a troublesome bulb but it seemed random still

i’ve tried changing bulb types to see if that helps but still seems random.