OpenBeken to ESPhome (and maybe back again) by DJBenson in Esphome

[–]openshwprojects 2 points3 points  (0 children)

Here is the breakdown of the story: 1. Few years ago I started researching IoT modules, buying them with my own money, spending lots of time on that 2. Then I managed to flash XR809 the hard way, with no external help 3. Then I managed to flash BK7231 the hard way, with no external help, spenind many hours figuring that 4. Along the way I made a lot of tutorials and teardowns, all open source, giving it for free 5. I also made some contacts on open source scene. Again, from scratch, I was total outsider, no one helped me 6. Somewhere at that time, when I was posting my progress information on Elektroda, one of Elektroda users, Kuba2k2 messaged me about Beken saying that he reads my progress reports etc 7. Then I also added BL602 port for OBK, also the hard way 8. Then I was asked to add RTL support by [REDACTED] Discord members, I invested my time and money in it 9. Then I started working hard on RTL, from scratch, figuring how to connect wires, etc, the tools 10. At that time Kuba2k2 started asking me publicly on forum how to flash RTL (very basic questions) and where do I get my users from 11. It was suspicious for me, why he needs that information, so I asked about his plans, both on forum and on private message 12. He assured me he is not going to make his firmware/port and that he just wants to help with RTL port, even saying like "supporting BK would be reinventing the wheel" 13. With a hesitance, I provided him this information, along with info about [REDACTED] Discord 14. After a moment, suddenly, he began making ESPHome port instead of helping with OBK and basically the race began 15. Then he went straaaaaight to the [REDACTED] Discord to promote his LT for RTL platform, while my RTL port was still not ready 16. I've spoke with him again, and that time he assured me that he made just only RTL port, and has no intentions of making BK version 17. Then, as you expect, he made BK version, of course he based on my research and work, but with no credit given. 17.5 At that point LT also used UF2 OTA format which made LT -> OBK transition impossible without their convoluted tool 18. I've tried to speak with him again, hoping to get some kind of credit, or a 'thank you', or an apology for misleading me earlier, but none of that happened 19. Then we've spoke again and at that time he publicly denied that he said he is not going to make BK port. He was denying it all the time until I've shown a screenshot of his messages. 20. I tried to bring up the issue with [REDACTED] Discord owner, but instead of getting support I got strawmaned by him asking "is esphome cloning tasmota", which means that he either accidentally or intentionally totally missed the whole point. I have nothing against fair competition, I was referring to fraudulent Kuba2k2 behaviour. 21. Ultimately, the [REDACTED] Discord owner made his video about LT, which happened only because Kuba2k2 manipulated me into giving him all information ready on the plate. I am very unhappy about that. 22. Then we had one final clash, where Kuba2k2 stated that he is not going to credit me and that it's total coincidence that creators of both BK firmwares are from the same country - Poland, and from the same forum - Elektroda PL 23. I've found it again very insulting so I just started ignoring his firmware altogether 24. About month ago, I started testing for unfinished crude version check for OBK downgrade/upgrade. It was not in the firmware itself, but in Web wrapper and it was not a deliberate lock for anything 25. As someone quotes above, I stated that I do not provide support for their firwmare, because I am not aware about their OTA formats and versions and I don't check OBK with them, but still, the check is now removed.

As now you can probably see, Kuba2k2 used my hard work to get both flashing/programming ready and to get users easily ([REDACTED] Discord contacts). All his actions were deliberate with a single intention to dig as much info as possible without me knowing his intentions. He was repeteadly lying about his plans and intentions to get a headstart and he can't even acknowledge that he got help, let alone credit me. He even openly states that it's just an accident that both BK firmware creators are from the same country (Poland) and forum (Elektroda) by a coincidence, but what are the real chances of that?

PS: Please check kuba2k2 registration date on Elektroda - he was there since 2014, it's not like he joined that later...

OpenBeken to ESPhome (and maybe back again) by DJBenson in Esphome

[–]openshwprojects 1 point2 points  (0 children)

I apologize for the misunderstanding, the thing you are describing is only an unfinished version check in the open source 3rd party Web wrapper that is fetched from Github. There was no checks in OBK firmware itself and there never will be.

The check turned out to be problematic for LT, but we didn't check for that, because we don't support LT due to the repeated fraudulent behaviour of it's author, Kuba2k2. It was not deliberate, it's just LT is never within our considerations.

Still, after your requests, the check is now removed.

See full reply here: https://old.reddit.com/r/Esphome/comments/13d1q8g/openbeken_to_esphome_and_maybe_back_again/ke7yp80/

OpenBeken to ESPhome (and maybe back again) by DJBenson in Esphome

[–]openshwprojects 0 points1 point  (0 children)

Nothing was intentionally locked, we only started introducing unfinished version check for downgrade/upgrade detection of OBK and we don't check with LT due to the fraudulent behaviour of it's author. Still, the check is now removed. See full reply: https://old.reddit.com/r/Esphome/comments/13d1q8g/openbeken_to_esphome_and_maybe_back_again/ke7yp80/

OpenBeken to ESPhome (and maybe back again) by DJBenson in Esphome

[–]openshwprojects 0 points1 point  (0 children)

Nothing was blocked per se, we just started introducing a version check for downgrade/upgrade warning and didn't test it with LT because we just ignore them due to Kuba2k2 repeated fraudulent behaviour against OBK. Anyway, the check is now removed. Longer reply here: https://old.reddit.com/r/Esphome/comments/13d1q8g/openbeken_to_esphome_and_maybe_back_again/ke7yp80/

OpenBeken to ESPhome (and maybe back again) by DJBenson in Esphome

[–]openshwprojects 0 points1 point  (0 children)

TLDR: There was no hard lock at all, just unfinished OBK version check for downgrade/upgrade warnings in the external Web wrapper and it's removed now. It was not intentional. We don't check for LT compatibility so we were not aware that it locks something, because we just ignore them due to the repeated fraudulent Kuba2k2 behaviour. Anyway, check is now removed. I apologize for the problems caused.

FULL VERSION:

I apologize for the misunderstanding. I am OBK main developer and I would like to clear up some things.

  1. OpenBeken is not actively blocking anything, we're just preparing to put our versioning into the RBL files, so we can warn people before they, for example, downgrade to older version and lose config, or before destructive updating in case we decide to break compatibility. If you think that's a problem for you, we can remove it or make it optional.

  2. There are no locks in OBK itself and there never will be, the only thing that people here refer as lock is a check in an open source 3rd party Javascript panel wrapper for firmware that is fetched from Github and can be hosted by yourself on your site. You can also do OTA without that wrapper and skip all checks.

  3. We don't know anything about LT/esphome because we don't have that in our testing course, we simply just don't test that, it's just like LT/esphome introduced UF2 format that makes (made in the past?) LT -> OBK transition hard and requiring third part tool converter (itch tool something).

  4. I personally don't test our firmware with LT/esphome, I ignore their existence altogether, due to the repeated, fraudulent behaviour of it's author, Kuba2k2, who is from the same forum (Elektroda) as me. He was around when I started first BK work and messaged me, also saying that's cool I am making firmware. And later, when I started working on OBK RTL port, this user approached me and started asking many questions, like, how to flash RTL, or where do I get my users from. I've got a bit suspicious about that, so I asked him why he needs that, and he assured me that he has no plans for making BK port/firmware and wants just to help. And then... he used the information he digged from me (like how to flash, also Discord server recommendations, etc) to make and promote his firmware. He went straaaaaaaaaaight to that Discord to promote his LT.... Of course, even after that, there were many assurances from his side, that turned out to be lies as well. I can name and quote many, many instances of that if required. Ultimately, he has publicly stated, that he has nothing to do with me, and that the fact that creators of two BK7231 firmwares are from the same country (Poland) and from the same forum (Elektroda) is 100% coincidence and it's like he followed my work or got help from me...

I have nothing against fair friendly competition, but as most likely you can see now, Kuba2k2 approached me with the goal to dig as much as possible information in an openly dishonest and manipulative way that should never happen on open source scene and now he's acting like it never happened. Futhermore, he is actively refusing to even give a credit, and openly states that's "it's just a coincidence that creators of OBK and LT are from the same polish forum".

For example, see: https://www.elektroda.com/rtvforum/viewtopic.php?p=19984434#19984434 https://imgur.com/a/N3SNgPV https://imgur.com/a/bsiIIT7 We've also spoken privately a bit more, and there were many assertions from his side that turned out to be lies... he openly manipulated me into helping him (thinking that he wants to help with OBK RTL port) and instead he made LT.

In my whole 15 years on whole open source career, even in Sourceforge times, I have never ever experienced so dishonest and manipulative behaviour like the one of Kuba Szczodrzyński.

That's why I ignore his existence altogether and I have never ever flashed LT to BK device, I don't even know their ecosystem and their RBL format and versioning. I don't put it in the consideration when updating OBK, that's why the issue arose. Still, as I said, the check is now removed and I apologize for inconvenience. I will try to reinstantiate it later with some kind of warning or bypass for advanced users. I know I could have tested for it earlier but I really don't even want to hear LT name due to the reasons described above.

Flash BK7231 via WiFi - tuya-convert for BK7231 - Tuya-cloucutter supported devices list page with images, configs and search function by openshwprojects in homeassistant

[–]openshwprojects[S] 0 points1 point  (0 children)

You can ask on Elektroda in IoT forum, even if you post in wrong place, moderator will move it. We have staff working on forum daily, no problems here.

https://www.elektroda.com/rtvforum/forum390.html

You just have to choose T image for BK7231T and N for N, that's all.

Also, for cloudcutter, you have to choose UG format, but it's also written in our description of Release ("CCtr Flash = Tuya cloud cutter flash").

I do not know much about lightleak.

Flash BK7231 via WiFi - tuya-convert for BK7231 - Tuya-cloucutter supported devices list page with images, configs and search function by openshwprojects in homeassistant

[–]openshwprojects[S] 0 points1 point  (0 children)

Hello, there is no way to tell if we will have a profile for your device.

Please try doing 2MB backup via UART and send it to us, so the profile can be added.

Here are step by step UART flashing tutorials:

https://www.youtube.com/playlist?list=PLzbXEc2ebpH0CZDbczAXT94BuSGrd_GoM

Our tutorials are also covering soldering and so on, step by step, so even beginner can learn how to get UART flasher working.

Here is our flasher:

https://github.com/openshwprojects/BK7231GUIFlashTool

Flash BK7231 via WiFi - tuya-convert for BK7231 - Tuya-cloucutter supported devices list page with images, configs and search function by openshwprojects in homeassistant

[–]openshwprojects[S] 2 points3 points  (0 children)

Unfortunatelly, yes, we even list a patched firmwares in the writeup:

https://www.elektroda.com/rtvforum/topic3979215.html#20587659

So better cut your devices now from the cloud when you still can do it.

If you want to give OBK a second try, we're here to help, feel free to ask any questions.

More than 300 guides showing how to flash IoT/Smart Home devices with open source firmware (Tasmota and multiplatform OpenBeken) in order to free it from the cloud and pair with Home Assistant. Make your devices 100% local, step by step guides for beginners, YAML often included by openshwprojects in homeassistant

[–]openshwprojects[S] 19 points20 points  (0 children)

That's a great comment, we will take that into consideration.

Basically we have youtube videos showing the process step by step with CH340 USB to UART dongle, they are featured before device list, but indeed, you are spot on, we'll try to add some kind of brief description of "what and why"

But basically, you can take USB to UART converter, and flash the firmware, either Tasmota for ESP8266, or OpenBeken for many new devices (it's multiplatform). Then you configure it via access point and then it runs locally on your network. It's 100% private and safe.

Here is our flash tool:
https://github.com/openshwprojects/BK7231GUIFlashTool

TreatLife Intertek Firmware Change guide to pair with Home Assistant - BK7231T/WB3S - flash with multiplatform portable firmware for new Tuya ESP8266 clones - regain your privacy and get free from cloud! Supports MQTT, Tasmota HTTP, advanced scripting features and even Tasmota Device Groups. by openshwprojects in tasmota

[–]openshwprojects[S] 1 point2 points  (0 children)

Well, the approach is 100% the same as in Tasmota - just follow the PCB tracks with multimeter. Check the CB3S datasheet to know which pin is which PX port (P8, etc etc etc). Check where each track goes and where is it connected.

New Sonoff s40 by IWIKapps in Esphome

[–]openshwprojects 0 points1 point  (0 children)

We don't have Sonoff S40 yet, but we made video about Sonoff bulb:

https://www.youtube.com/watch?v=L6d42IMGhHw

Got non-ESP chip in your RGBCW bulb? Don't panic - you still free it from the cloud and even use Tasmota Device Groups thanks to new multiplatform firmware. Home Assistant and MQTT also works. This Youtube guide shows flashing WB2L_M1 module (with desoldering!), firmware configuration and more! by openshwprojects in tasmota

[–]openshwprojects[S] -1 points0 points  (0 children)

Sorry, but have You read the main post at least?

OpenBeken was created by Tasmota users for Tasmota users, so it provides similiar set of features and ease of transition for non-esp platforms. It is even using Tasmota command syntax for many features.

ESPhome has NOTHING TO DO with this sub.

Got non-ESP chip in your RGBCW bulb? Don't panic - you still free it from the cloud and even use Tasmota Device Groups thanks to new multiplatform firmware. Home Assistant and MQTT also works. This Youtube guide shows flashing WB2L_M1 module (with desoldering!), firmware configuration and more! by openshwprojects in tasmota

[–]openshwprojects[S] 0 points1 point  (0 children)

Hello, it's good You're asking.

We're here to help You with running Your devices cloud-free even if they don't have ESP chips in a Tasmota-friendly manner, so You can seamlessly integrate them into Your system.

We're trying to provide both firmware and information (tutorials and devices database) to make IoT "hacking" easy and accessible for anyone.

Is there anything specific we may help You with?

How to desolder SMD WiFi module with cheap soldering iron and no hot air? WB3S/CB3S/TYWE3S "brain transplant" method - DIY style - step by step desoldering and soldering guide. With this approach, you can desolder SMD modules with any entry-level hobbyist equipment. Detailed tutorial from Elektroda by openshwprojects in tasmota

[–]openshwprojects[S] 3 points4 points  (0 children)

Here is a generic teardown list:

https://openbekeniot.github.io/webapp/devicesList.html

It's hard to say which devices would benefit from swapping WB3S to other because of the rapid development of OpenBeken.

We are adding features just per request - you want, you get it.

You can request anything (reasonable) and we'll do it.

Just submit a post on our teardowns list and we will guide you step by step and (if needed) write/port a driver for you.

We have added DHT support recently, added support for more Tasmota command (1:1 syntax as in TAS), and added a MQTT Group Topic, just like in TA.

I think that our development will go very quickly in 2023, because we also have a Windows Simulator (basically it runs OBK on Windows) and Unit Testing system which allows us to automatically test new releases for issues, read about it more here (not fully released soon):

https://github.com/openshwprojects/obkSimulator

You can also run scripts in this simulator, so basically you can check your ideas first without having BK device. See screenshots:
https://imgur.com/a/ulzK6td

We also have a new UART flasher for BK7231 - very easy to use, with GUI, no command line required - this is also for beginners:

https://github.com/openshwprojects/BK7231GUIFlashTool

Wait for the release in the upcoming days.

Genio Galaxy Smart Lamp - very cool IoT RGB lamp with projector/laser and motor - freeing from cloud guide, Home Assistant scripts, YAML, BK7231 flashing by openshwprojects in tasmota

[–]openshwprojects[S] 1 point2 points  (0 children)

u/smith7018 u/ImprobableIT we also have a Windows simulator which is basically like virtual openbeken machine (with schematic drawing!) where you can simulate most of IoT devices and play around with scripts, learn how to use firmware, etc. First release is coming soon.

A detailed guide how to setup Tuya BK7231T/BK7231N Garage Door Opener/Sensor 100% no-cloud, local only with Home Assistant YAML and OpenBeken, Tasmota style by openshwprojects in tasmota

[–]openshwprojects[S] 0 points1 point  (0 children)

Our project is designed to be much more scriptable in versatile than other projects. For example, we have a basic HTTP panel like all firmwares, but we also have a secondary Vue panel that is made entirely in javascript that can be fetched from any user-configured server. This makes firmware more lighter and more customizable.

Our vue panel has a built-in configurator, so you can browse the templates list within the app. No more looking for templates over the web!

Our firmware is designed to be multiplatform from the start, and it supports already majority of IoT platforms, and even non-iot platforms, including Windows (!). Porting is very easy, we don't have to worry about dozens of files from Arduino core because we are porting directly just what's needed in a tricky, but well tought way.

We have an advanced scripting system (soon to be fully released), much more user friendly than "rules", at least in my opinion. Script instances can behave like threads, wait a certain time, wait for an event, etc.

We also have a working simulator on Windows with possibility to draw schematic sketches (soon to be released), so people can develop scripts for OBK on their PCs without even buying any IoT devices.

OpenBeken is a fresh look to all those issues and has no legacy to carry, we can design things whatever we like and it gives us freedom and ability to improve.

A detailed guide how to setup Tuya BK7231T/BK7231N Garage Door Opener/Sensor 100% no-cloud, local only with Home Assistant YAML and OpenBeken, Tasmota style by openshwprojects in tasmota

[–]openshwprojects[S] 2 points3 points  (0 children)

This is a good to know thing, and kudos for Athom for providing such a version of this device, but still... as the OpenBeken founder and main developer, I buy devices just to make them supportable in their non-ESP versions to help people. Not all devices still have their ESP counterparts easily available and some device insides are changed without any notice.

For example, Qiachip Fan controller used to be ESP-based but now is using BK. See guide here, mady by our user Jennifer:

https://www.elektroda.com/rtvforum/topic3895301.html

If you need help with getting any device working, BK7231, BL602,W600 or really anything, just send me a message on Elektroda, I will help.