FEIT BPA800/RGBW/AG/2(P) Template issues

[Resterday]

Good morning all, I recently flashed some FEIT BPA800/RGBW/AG/2(P) bulbs I bought at Costco with kueblc's new-api branch of tuya-convert. I then updated to 6.6.0.

I have tried the following template for FEIT bulbs {"NAME":"OM60/RGBW","GPIO":[255,255,255,255,140,37,0,0,38,142,141,255,255],"FLAG":0,"BASE":18} but when the bulb first re-sets and I toggle it on, nothing happens, and there are no errors or other messages in the console. If I put in color 0,0,50,0,0 into console then teh bulb turns on at 20% brightness and a cool white. At this point, I can toggle it on and off but if I try to change any other settings the bulb just goes dark and I cant do anything until i put color 0,0,50,0,0 into console again. I have tried other template settings, but so far nothings working.

I opened up the bulb when trying to get the tuya convert to work and noticed that it appears the led driver might be different from other FEIT bulbs, but Im not sure. Maybe this has something to do with my issues? Its really hard to see whats written on the component but I have included the pictures that I took.

Hoping someone can help me identify next steps for getting these bulbs to work. Thanks!

[chelming]

@DSuds, I think you're referring to FCC ID SYW-A19RGBWAGT2 which from my sampling of bulbs carries a model number on the bulb of BPA800/RGBW/AG/2(P). The older bulbs from Costco do not have the "(2)" at the end and have an FCC ID of FCC ID SYW-A19RGBWAGT1. The print is small and it is easy to mistake what you are looking at.

The FCC ID on my bulb is SYW-A19RGBWAGT1

[mhightower83]

@cwhits then you want this template.

Piece of warning, using the Color command gives you unrestricted access to channel values. I.e. Color FFFFFFFFFF will turn full power to all channels and might well fry your bulb. Don't do it!

@cwhits this goes double for your bulb. With a fresh config reset, template ..., module 0, etc. The bulb starts off with {"Color":"1A1A1AFFFF"}. This is a bad default setting. Channels 4 and 5 at FF, places the Warm and Cold LEDs at full brightness. At full brightness, you have a 9 Watt string of Warm LEDs and a 9 Watt string of Cold LEDs on at the same time. That would be 18 Watts, I measure 16 Watt so the power supply is already being strained. A change in Warm/Cold slider will correct this or a CT command, eg. CT 500.

To avoid this, after flashing a new bulb or a config reset. Make sure if reports power Off. Then apply the template, etc. Then use a CT command to turn the bulb on. This appears to put things properly.

I think this latter approach should also be used with the BPA800/RGBW/AG/2(P) (FCC ID SYW-A19RGBWAGT2) as well. I observed that bulb starting off at 12-13 Watts after the module 0 command.

[s-hadinger]

@mhightower83 Thanks for the dive deep.

It's a surprise to me that the bulbs starts with {"Color":"1A1A1AFFFF"}. I will try to find out why and potentially fix it.

[chelming]

@cwhits then you want this template.

That's the template I started with, but it didn't work with my bulb. Only template 48 worked correctly (and everything does work correctly with that template now)

[mhightower83]

Hmm, I guess people will have to take the approach if one template doesn't work try the other.

@cwhits what is the date code on your bulb. My ...GT2 bulb is 228-19-24, which I take to be the 24th week of the year 2019. My ...GT1 is 228-19-21

[chelming]

mine is also 228-19-24

[s-hadinger]

@mhightower83 #6162 fixes the initial value of Color after flashing the firmware or doing a Reset 5 or Reset 6.

Default value is now {"Color":"1A1A1A0000"}, playing soft on the bulb power supply.

Thanks for reporting the issue.

[raptordemon]

so i have yet another version of this bulb. its a OM60/RGBW/15K/AG sold at lowes in Dec 2019. FCC-ID SYW-A19RGBW15KA it seems to be different but i have managed to make it work!

Esp is a TYWE2L with seems to be a tuya module. RGB driver is a SM726EC chip Chip on the white top plate seems to manage the WW CW BP5778 J8D22VE SB34J could not find on google.

and here is an approx pinout of the sm726EC and white pin header on the board:

this is my template: {"NAME":"Feit Bulb","GPIO":[255,255,255,255,141,140,255,255,38,142,37,255,255],"FLAG":0,"BASE":18} setoption37 1 was needed to correct the warm white and cold white being switched

hope this helps someone

[mhightower83]

... could not find on google.

@raptordemon, I sometimes have to resort to using a Chinese search engine and rely on google translate to help me get through. I found this datasheet for the BP5778DJ. Excerpt from Google translate:

... BP5778DJ is a dual-channel dimmable LED linear constant current driver chip that supports PWM and analog dimming signal input. It is mainly used to drive various types of dimming light sources and lamps for city power input. The BP5778DJ based on linear constant current technology can eliminate electrolytic capacitors and magnetic components, help LED drivers achieve small size, long life, and meet EMI standards. ...

[cyberplant]

Hello!

I'm here to comment that the bulb Nexxt AHIBUSO4U1 also works fine with the template:

template {"NAME":"BPA800/../2(P)","GPIO":[0,0,0,0,37,38,0,0,141,142,140,0,0],"FLAG":0,"BASE":48}

linked here in the comments.

[rezadast2]

Is it to be expected that the white brightness level greater than 50 doesnt actually change the brightness with gamma correction off, LEDTABLE 0? With LEDTABLE 1, my brightness was opposite, 100 > 50 worked, but anything less than 50 it turned off. Now with LEDTABLE 1, 100 > 50 doesnt change the brightness at all and stays at 100% brightness. 50 > 0 changes the brightness.

However, when I am using the RGB colors, the brightness scale seems to be fully operational from 100 > 0.

[JaimeZX]

So guys, here I am 10 months after the original discussion. Just flashed one of my four Costco-purchased FEIT Electric BPA800/RGBW/AG/2(P) bulbs using Tuya-convert. I wasn't going to do the rest until I get this thing dialed-in.

The template in the Blakadder page worked pretty well but I felt like the CW wasn't blue enough. (I did not compare with a stock bulb at that moment.) I tried upgrading the Tasmota firmware to 8.4.0. Overall I would say it works as expected... except for one thing. The CW <-> WW slider is reversed.

Based on this thread, I changed GPIO5 to PWM2i. So, 0,0,0,0,37,47,0,0,141,142,140,0,0.

Works perfectly, aside from what other posters have said about the brightness cutting off at about 35% on the slider.

I compared the brightness side-by-side with an un-flashed bulb in the FEIT Electric app. CW is identical. WW is identical. RGB seems to be identical. 100% brightness is identical.

NOW... interestingly... if I turn the stock bulb down to 1% in the app, it's about the same as ~42% in the Tasmota GUI. I CAN get the Tasmota bulb a LITTLE dimmer than that. Maybe down to 38% or so. I can actually get it to dim a little more, but it cuts off after about a second.

Hope this is helpful to anyone coming after me. :)

[s-hadinger]

@JaimeZX The difference in dimmer is probably due to Gamma correction. You can turn it on or off with LedTable 1/0. Some bulbs have hardware Gamma correction so adding a second one is worsening things.

Choose whichever feels the most visually linear when setting birghtness to 25%, 50%, 75%.

[JaimeZX]

That's a great input. I thought I was at ledtable 0 already, but I tried it again and now the bulb cuts off at just under 10% on the slider, which is much more natural. Thank you!