search

KaufHA / kauf-rgbww-bulbs

Files for the KAUF RGBWW Smart Bulbs
43 stars 19 forks source link

ignoring ddp packet with non zero data offset #50

Open ridl8349 opened 11 months ago

ridl8349 commented 11 months ago

Using 5 of the A21 sized bulbs in a Christmas xLights setup. Worked last year on v1.85. Updated all 5 bulbs to v1.92 and all 5 are showing the error referenced in the v1.86 in the verbose logs. xLights is setup according to YouTube guide.

xLights version 2023.20

I saw and read the reference in the release notes, but do not understand how it is affecting the DPP protocol over the network coming from xLights.

I did verify no other DDP is being broadcasted over the network All other functions of the bulb for correctly.

bkaufx commented 11 months ago

What is the error message?

bkaufx commented 11 months ago

oh data offset? I think there is a setting in xlights to make it zero.

ridl8349 commented 11 months ago

What is the error message?

The only thing in the log is "ignoring DDP with non-zero data offset". Then there is a bunch of random numbers and letters.

bkaufx commented 11 months ago

Try "Keep Channel Numbers" in the xlights config.

ridl8349 commented 11 months ago

Screenshot 2023-12-11 193811

Keep channel numbers is selected for all bulbs.

ridl8349 commented 11 months ago

Screenshot 2023-12-11 194204 Here is the log from the bulb.

It starts as soon as I press output to lights.

ridl8349 commented 11 months ago

Update, if I roll the bulb back to v1.85 it functions with xlights without problems. v1.86 and up seem to have this issue.

image

edit: to clarify I started to roll back the versions until it started working again.

cpuchip commented 4 days ago

I was running into the same issue running Firmware version 1.93(u) made using ESPHome version 2024.4.2. and xLights 2024.17, bulbs are pared into Home Assistant and I have them working there, I've enabled DDP on the bulbs, and get a similar error message, if I uncheck "Keep Channel Numbers" then they work, but xLights throws a connect error. I haven't figured that out yet, but I can output to the lights now in test and in my models

kjans commented 4 days ago

I had the same issue running 1.93... Unchecking "Keep Channel Numbers" appears to fix it... I will do more testing to be sure ...And I don't get a "connect error"...

cpuchip commented 4 days ago

I cleared up my connection error, I had a controller with no IP for ddp listed in my controllers tab in xLights. So look good to me, I wont know about any latencies until I get my other pixel lights up.