[CBU / BK7231N] WS2811C, Microphone, 4 Switch : PROGLO Obi Smart Light Bars, 2 Pack

jwp_nz 5169 2

Reply Cool? Ranking DIY | New topic

Notify about new articles

Helpful post? (0)

Post #1
21059212 25 Apr 2024 05:57

Kia ora/Hi all,

I picked up several of these : PROGLO Obi Smart Light Bars, 2 Pack H: 285mm Incl Base

Link

on special about a year ago and finally got around to getting them flashed with something useful.

They are a CBU BK7231N based PCB, with 12V input and step-up/down ladder along with a Microphone input (unused/untested as I never paired them to tuyacloud) and oddly a USB-C connector for 12V VCC and Data to the strips which use the SM16703P driver in openbk with GRB colour order.

Everything seems to be working fine, except that I get continuous press SPAM from Pin14 which is SW1 in the console- I am wondering if this is possibly something to do with how the Microphone on the board is wired in? Inverting the pin doesn't resolve. It doesn't seem to affect functionality and you could just leave pin14 undefined If you want to silence it.

The controller board is very nice to open, just pop from an easily priable gap along the USB-C connector, no hot-glue etc . There are convenient solder pads on the reverse of the board for initial flashing.

Pin-map sketch with PCB

Reverse

LED Strip inside case/diffuser:

For some brain-dead reason the output is a USB-C connector and the input a mini-12V DC barrel, this is actually relatively dangerous as the USB-C output port doesn't have any sort of PD trigger so just spits out 12V all the time when plugged; don't go using the USB-C port for anything other than the supplied lights. This should have been the Feeder in the original design , but am guessing they dropped the PD controller to save some money and used the connector on the output side instead.

Cat approved result:

They are using WS2811C 12V Controllers in Groups of 3 LED (for a total of 6 addressable segments per Light). For whatever reason (probably voltage drop) Each of the pairs are wired in parallel so the second light in a chain just mimics the first. You could probably, cut the 2nd light cord , drill a hole and solder the second light to the top of the first and get a single strip of 12 addressable, but I didn't try as the form factor and diffusion of these units is quite nice as is.

I have these attached as DDP segments to existing WLED controlled lights. In the example I provide basic stand-alone dimmer and colour control (taken directly from https://www.elektroda.com/rtvforum/topic4036716.html ) as commented section in the attached autoexec.bat script. I would like to use the 4 switches and have local colour/brightness control along-side the DDP receiver. Currently however it appears that any local dimmer controls etc override the DDP. So I leave them configured as basic DDP targets OOTB. WLED handles this by poping up an overide when a DDP packet is received asking the user if they want to ignore DDP in tthe WebUI once or until reboot. Something like this could probably be scripted so that a button press for power down overrides the DDP until another press. But I haven't investigated how openbk handles button actions.

Since there are 4 available momentary switches on the control unit, I would ideally like to map each one to a rolling over 0-255 per color channel control and the 4th as a On - Off + Long Press Dimmer. If anyone has an example for doing any of the above - would be keen to see how.

There are some more photos and videos and commentary on my fediverse thread here:
https://cloudisland.nz/@jwp/112317522315834359

The only flag I have set is the MQTT one, if you want to use with local only you'll need to set flag4.

Attached original firmware dump (no useful config for cloudcutter). Also I couldn't use the gui tool and used hid_downloader to flash along with openbk tools to dump the full original bin from Fedora40.

Cheers

-Joel

example autoexec.bat
Code: text Expand Select all Copy to clipboard
///By default we just run the driver for the LED and setup NTP and DDP(poorman's e1.31) which can be added to an existing WLED controller triple commented blocks can only be run individually startDriver SM16703P startDriver NTP startDriver DDP SM16703P_Init 6 GRB /// This will allow for basic WebUI control - currently will overide DDP so we disable it by default ///Also need to set flag Flag 4 - [LED] Force show RGBCW controller (for example, for SM2135 LEDs, or for DGR sender) //Dimmer //again: //SM16703P_SetPixel all $led_enableAll*$led_red*$led_dimmer/255 $led_enableAll*$led_green*$led_dimmer/255 //$led_enableAll*$led_blue*$led_dimmer/255 //SM16703P_Start //delay_s 1 //goto again /// Dimmer only follows choose this or the above - can't use both // number of LEDs //setChannel 5 18 // init //SM16703P_Init $CH5 // on channel 1 dimmer change, refresh //addEventHandler OnChannelChange 1 startScript autoexec.bat refresh // refresh function //refresh: // iteration variable //setChannel 6 0 // loop for each LEd //again:

template.json

Code: text Expand Select all Copy to clipboard
{ "vendor": "Proglo/OBI", "bDetailed": "0", "name": "PROGLO Obi Smart Light Bars, 2 Pack H: 285mm Incl Base", "model": "PGLSB100-2PK", "chip": "BK7231N", "board": "CBU", "flags": "1024", "keywords": [ "WS2811C", "4 Buttons", "Microphone" ], "pins": { "14": "Btn_Tgl_All;0", "15": "Btn;0", "20": "Btn;0", "22": "Btn;0" }, "command": "", "image": "https://obrazki.elektroda.pl/6705621000_1714016724_thumb.jpg", "wiki": "https://www.elektroda.com/rtvforum/topic4050771.html" }

Attachments:

proglo-pgslb100-2pk.bin Download (2 MB)

Cool? Ranking DIY
About Author
jwp_nz jwp_nz

Level 2
Offline

Joined: 23 Apr 2024

Posts: 2

Points: 130
Pākehā with a strong Māori bi-cultural upbringing and Identity (Ngati Ngorongo - Taranaki hapu). Engineer, Geek, Psyc/Social researcher, Red hat employee. Always have an opinion, sometimes it's worth something

Wellington, New Zealand based.

May contain #dog #cat #electronics #linux & #social #psychology

@aenertia on other things

Unless otherwise noted any original media posted here is done so on a CC:BY:SA licence

they/them/he
jwp_nz wrote 2 posts with. Live in city Wellington. Been with us since 2024 year.
ADVERTISEMENT
#2 21059308 25 Apr 2024 17:39

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home
Helpful post? (0)

Post #2
21059308 25 Apr 2024 17:39

Thanks for sharing. It's really not good to see them using USB-C connector for 12V. Using it for some other devices would certainly end badly.

Regarding the buttons on the device, I am planning to make an extended version of per-pixel lights driver, but currently, if you are using RGBW method:
Code: text Expand Select all Copy to clipboard
SM16703P_SetPixel all $led_enableAll*$led_red*$led_dimmer/255 $led_enableAll*$led_green*$led_dimmer/255

then you can use both button roles like SmartButtonForLEDs, Button_NextColor you can also use click events with commands like led_basecolor_rgb, etc. I would need to think about that wrap.

Added after 8 [hours] 51 [minutes]:

jwp_nz wrote:

Everything seems to be working fine, except that I get continuous press SPAM from Pin14 which is SW1 in the console- I am wondering if this is possibly something to do with how the Microphone on the board is wired in? Inverting the pin doesn't resolve.

So both Btn and Btn_b are spamming? But wait, is P14 really a button? Why do you think it's mic? Isn't mic on ADC, P23?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#3 21060564 26 Apr 2024 01:41

jwp_nz jwp_nz

Level 2
Topic author Helpful post? (0)

Post #3
21060564 26 Apr 2024 01:41

Thanks I am still a bit lost about button actions and mapping maybe lets try and achieve the most basic use case I want. Which is to turn the lights off on a button press when they are connected to DDP only and then turn them on again on second press.

Using Switch4 (p22) to avoid the spammy p14 pin for the moment.

The Pseudo code would be something like:

Code: text Expand Select all Copy to clipboard
/// on P22 press trigger statechange //statechange check current state of pixels ; if ( current state is anything other than off ) then save current state to variable; disable DDP listener; turn off all pixels; else read state from variable; set pixels to variable state; re-enable DDP listener; // ///

Now how to implement this using openbk's scripting and bindings - I am a little lost in, even after reading through examples and docs. I basically want to expand my existing autoexec.bat with the above logic.
Create an account, log in and become active in a forum and ads will not appear. You will receive points by participating in discussions.
Join this discussion.

Install the application

Didn't find an answer? Ask Artificial Intelligence

*I agree to send the question to OpenAI, Anthropic PBC, Perplexity AI, Inc., Kagi Inc., Google LLC - owners of language models in order to prepare the best response. The companies may monitor and log information entered into the form.

*I agree to publicly display my question and answer. The question and answer will be publicly available to everyone. The process may take a few minutes. Upon completion, you will be redirected to the page with the answer.

Wait...(2min)