Changing firmware increasingly difficult? Smart Switch on T34 and QFN soldering

I tried 1.18.83 but the problem persist.
Now I'm also facing a new problem with 2 out 4 modules, the relay won't switch anymore.
Both the relay and the transistor are good, so I guess the problem is the gpio pin.

Are you really sure that you soldered back T34 correctly?
No cold solder joins, etc, no poor contacts?
Because, you know... in like 4 years of development we never had a GPIO control failure in OpenBeken.

Futhermore... poor contact on WiFi antenna pads would also explain WiFI quality issues. Hmmm.

Or maybe you have lost template while updating/testing? Is given GPIO still configured as Relay?

Well, I actually double/triple checked it by resoldering it again, but the problem persist on two devices.
Template is ok

Which pin exactly is not working? Give exact pin index. Is it still configured as "Relay" in configure module? And does it work when toggled from GPIODoctor?

Pin26, configured as "Rel" in the template.
Using gpio Doctor doesn't change anything. It just can't toggle the relay anymore. I think they just die after using them for a while...

Remember that GPIODoctor will reassign a channel of given pin, so you need to set it back in configure module.

That really sounds like a soldering issue. Especially that you're saying that it happens for some of the BKs, not all of them.

@divadiow does P26 work fine on your BK7231N?

p.kaczmarek2 wrote:

@divadiow does P26 work fine on your BK7231N?

I am able to PU/PD P26 as expected yes - 1.18.212

Can you measure it on the module PCB?

I think all of them are gonna stop working eventually, since there is no flyback diode across the relay coil. Weirdly enough the transistor did survive, but I think the gpio got cooked by the back EMI

Those modules are completely unreliable. Just got other 4 on my hands and flashed one. After a reboot, it resetted itself. What a mess

Are you sure there is no flyback diode? Can you show a photo?

Enable PowerSave 1 in OBK to make sure that you're not overheating the power supply.

Sure, here it is

As you can see on the first pic, the left relay track leads directly to the transistor collector, while the other is connected directly to 5V. The are 5 diodes on the PCB, the two on the bottom are connected in series from L-IN to the transformerless IC, while the other 2 near the IC are connected to the low voltage output after the inductor. Oddly enough, there is one M7 diode in parallel to the N-IN, which makes no sense to me 😅

Another one just died in 4 days. I think it's cause the input switch pin is not isolated from main voltage, in fact it's using neutral as ground. I think that's the problem

I think it would be worth to compare their longevity with non-flashed devices (Tuya firmware - without desoldering T34). This would eliminate the possibility that some pads of T34 weren't soldered correctly.

I don't think those smart switches should die that fast. They are low quality, but not that bad...

I bought some similar devices, with RF433 feature. Looks the same, but have some more components populated on the pcb.


They come with battery powered remotes, but can be paired with any ordinary RF433 remote.
In order to pair, the device button must be pressed 3 times, then the remote 2 times. To forget all remotes the device button must be pressed 8 times.
Pairing can also be done via Tuya app.
I have desoldered the chip, flash with OBK, then solder back.
Configuration is the same as for devices w/o RF433 feature.
Original firmware attached.
readResult...4RF_01.bin Download(2 MB)
Device works ok, but without the RF433 feature.
It is not possible to add a remote by pressing the button 3 times.
Is any possibility to setup OBK in order to have RF433 feature available?

We're working on it. This device requires Beken to be able to decode raw IR data from the receiver chip.

rchristescu wrote:

Is any possibility to setup OBK in order to have RF433 feature available?

We are close to getting this to work, experiments are on the way and so far we have managed to get the reading, and get the consistent data.



This is a capture from Princeton protocol remote, Roger protocol also works - more tests are needed...

Stay tuned!

@divadiow do you have device with RF receiver?

I have a few somewhere I think.

https://www.elektroda.com/rtvforum/topic4042000.html
https://www.elektroda.com/rtvforum/topic4021221.html#21144422

+SH4 https://www.elektroda.com/rtvforum/topic3975921.html#21234412

divadiow wrote:

https://www.elektroda.com/rtvforum/topic4021221.html#21144422

We are working on the same device 😎😎😎 that other one will be interesting. Do you have any time to test?

sure, but not tonight. I'm sooo tired

Cool, it's an ongoing process it will wait for you 😉

and this. don't think I posted about it anywhere

>>21780903

same device, based on SNY590 I think it can be done, just more testing and polish.

Hey @insmod , what would you say, can we keep it enabled by default, with current flash sizes? I think we should finally stop growing binary so T LFS is not removed.
https://github.com/openshwprojects/OpenBK7231T_App/pull/1900

Princeton RF remote that comes with these devices is now supported. Some more tests before release is needed and some time tweaks but overall expect it very soon.

This is test autoexec that is working on my test device:



We had the same approach to get to read data first so you'll have an ability to see the code your remote is transmitting and set the autoexec.

More to come...

addEventHandler2 can be used to detect whether button is doing initial press or kept held. Second event argument is bHold (0 or 1).

Just to explain more, important for addEventHandler2 it accepts 2 arguments - RC <CODE> ( or IR <CODE> ) 0 or 1 then action.



This means that all the relays will be toggled to ON state (1 after POWERALL, change to 0 for OFF state) on the first CODE received as the feature of detecting the signal will give you this output



on every button press.

So 0 for toggle and 1 for possible dimmer application, not for relays.

RF guide available BK7231 RF receiver driver tutorial - how to use SYN590R or similar to control multiple devices

>>21776839 Tested, it works, great! Thanks a lot!
So, I downloaded the latest flasher - BK7231GUIFlashTool-v178, extract config from Tuya binary backup, see RF remote on P6.
Update device to OBK 1.18.227, set P6 as RCRecv, execute command "startDriver RC" and that's it.
I can read the remote code.
To control the relay I execute command: addEventHandler2 RC <code> 0 POWER TOGGLE
But can do a lot more, actually it can be used as a RFBridge.

Later edit: I've noticed something strange. The driver does not work in combination with "powersave 1".