Bk7231n esphome not working. The device would hang and reboot, for no obvious reason.

Bk7231n esphome not working. I’ve swapped cb3s with esp chip for now.

Bk7231n esphome not working It can connect to wifi and I can access the web UI. However I'm not sure if this is a ESPHome Problem or Homeassitent pushes back the last Config Using Version ESPHome 2024. Hello. reading time: 13 minutes The problem I have 2 channel wireless switch with tuyamcu which contains wifi module CB2S. I don't have any Home Assistant schedules which run at I have been struggling with this for quite sometime. If your device doesn't have a profile yet, it will probably not work. Maybe I’m confusing myself by reading the silkscreen on the green PCB but any help would be appreciated. Which version of Home Assistant has the issue? # What does this implement/fix? This is not a single chip, but rather a unive rsal PlatformIO framework that I'll use to add support for cheap IoT chips found in modules manufactured by Tuya, Inc. Can be scripted to even work with shutters, see also second shutters script; Password-protected Web security see tutorial; Hi, I have 2 S08 IR (PCB: S06-CBU-V1. I am working on free, open source Tasmota replacement for non-ESP Tuya modules, mostly focusing on BK7231T and BK7231N. These are supported by Beken SDKs, such as bdk_freertos, although bk7231s_alios_sdk also existed at some point. yaml and example fairylights-1. CSS and JS URL’s are set to empty value, so no internet access is needed for this device to show it’s web interface. I live in Central Europe. I have a couple of them around the house and they Looking to get ESPHome working on a Tuya CBU module that is used in an inexpensive Milfra smart dimmer switch. Compile ESPHome, or your custom firmware based on LibreTiny. So I changed the platform to rgbct and it’s close to working. Trying to read the CHIP ID just hangs. bat Struggling to integrate my new BK7231N/CBU Tuya Smart Motion Sensor with Open Beken and ESPHome. You can press the button on the power strip to toggle all sockets. "bdk_freertos" is also incompatible - it seems not to have IrDA, "real" timers (only "pwm" Plan and track work Discussions. As for functionality, depends on if this is RGB(W) or RGBIC. This requires a custom fork of ESPHome to complie the firmware for the Beken MCU as it is not natively support by ESPHome yet flashing guides for WB2S/WB3S/CB2S fan Tuya controllers with TuyaMCU; MQTT; Home Assistant Yaml configuration; Flash with OpenBeken - open source, multiplatform Tasmota/Esphome replacement for new Tuya modules, including BK7231N, BK7231T, XR809, BL602, W800, T34 Like this on all esphome, not just libretuya - platform: wifi_signal name: ${friendly_name} Signal Percent update_interval: 60s filters: - lambda: return min(max(2 * (x + 100. works correctly but sometimes devices are being duplicated in the HA losing the connection and making the automation not work because the entity id is changed. I bought the Moes UFO-R2-RF IR RF Repeater and succesfully flashed it with I hope someone can point me in the right direction please. The usual BK7231 flashing and configuration process is similar to Tasmota/Esphome/Etc. bin Selected Device Slug: lsc-2578685-970766-smart-plug-cb2s Selected Profile: oem-bk7231n-plug-1. This outines the OpenBeken project and how it can be used in the switch in a similar way to Tasmota/ESPHome. There is, the code in neopixelbus was breaking our CI, and the PR fixing that in their repo was closed (which I kind of understand, because it's a weird . 00 Selected Firmware: ESPHome Smart LED RGBCW Tuya based on non-ESP chip (BK7231T / BK7231N) pairing guide with Home Assistant (OpenBekken - Tasmota replacement for BK chips, including WB2S, WB3S, WB2L etc modules). But it was not working still late 1 hour. After successfully entering WiFi credentials via the configuration menu at 192. ryantollefson (Ryan Tollefson) August 13, flashing guides for WB2S/WB3S/CB2S fan Tuya controllers with TuyaMCU; MQTT; Home Assistant Yaml configuration; Flash with OpenBeken - open source, multiplatform Tasmota/Esphome replacement for new Tuya modules, including BK7231N, BK7231T, XR809, BL602, W800, T34 This does not seem possible right now and I would have to choose to either only allow home assistant access or only access via the build in AP. BK7231N, BL602, XR3, W800, W600, etc. Tasmota/Esphome/etc replacement for BK7231T, BK7231N, XR809 and BL602 platforms - TuyaMCU dimmer and fan support, basic Select your custom firmware file for BK7231N chip: ESPHome-Kickstart-v23. Any ideas appreciated. Here is what I have at the moment that is NOT working: logger: level: VERBOSE hardware_uart: UART1 baud_rate: 115200 2024. rbl=device:download. 5. See below OpenBK7231T/OpenBeken is a Tasmota/Esphome replacement for new Tuya modules featuring MQTT and Home Assistant compatibility. carrier_frequency (Optional, float): Set a frequency to send the signal with for infrared signals. 1-40. 03MB Flash. 2 MCU I am including photos of the case and PCB I just want to get some input before I remove the module for flashing as I had to end up with a bricked fan if And it does not work, well it work but it cant read any sensors. CB3S (BK7231N) will work fine for wifi. Reply reply OpenBeken update - Tasmota/Esphome/etc replacement for BK7231T, BK7231N, XR809 and BL602 platforms - TuyaMCU dimmer and fan support, basic Tasmota Device Groups support, save&restore (power on state) support Anybody knows why its not working always? #102 20402613 24 Jan 2023 13:35. So just need to work out how to get brightness control over the colours. Environment: Product Generic - BK7231N (Tuya QFN32) Generic - BK7231T (Tuya QFN32) ESPHome Dashboard (GUI) - for new users, might be an easy way to go; config management & compilation using web-based dashboard you can use UPK2ESPHome to generate a working config (for supported BK7231 devices only). I'm developing a project to run firmware on unsupported, non-ESP chips of many IoT devices nowadays (that used to be ESP chips). Many posts exists concerning ESPHome WiFi connection issues resulting in "EOF received" and "Connection reset by peer" messages in HA logs when using libretiny. 0. However, I found ESPHome was unstable on it. Is there any way an implementation of the "I2C" led driver KP18058 or KP18068 could be added to ESPHome? A range of very affordable Bulbs is available with BK7231n (working with LibreTiny) using the 18058/18068 is now available. uf2 OpenBK7231N_1. Resetting the BK732 There’s the ota way with cloudcutter if your device firmware is not patched yet. bin file from the build directory - take care to choose the correct file. 15. Using the so-called QIO binaries is pointless [BK7231N] QCNX Plug with Smartmeter: ESP Chip, MQTT, Tasmota, OpenBK Firmware & Pin Settings Facebook Messenger X Whatsapp Reddit Linked-in Email it doesn't work anymore. Example web_server version 1 configuration with CSS and JS included from esphome-docs. Connecting the 230V AC results in multiple relay noise, and it seems that the device continue to reboot. Without tinkering with the filters and just using the default current_resistor and voltage_divider Recently a friend bought some Zemismart wall switches and they have a BK7231N chip rather than an ESP8266. 2 * all the pins needed for flashing are easily When restore_mode is set to ALWAYS_OFF it does restore the last config. base. The only problem is when my network goes down or when i relocate the device, The current logic below does not work & I don’t know enough about ESPHome Home Assistant Community The current logic below does not work & I don’t know enough about ESPHome to know why its doing it & how to fix it. If there was a possibility to use DeepSleep and PinDeepSleep simultaneously, it could be used to wake up and leave the device online. But then I dint use the display today after updating the display, with the new changes, I started facing problems. To realign for ESPHome use I went straight for the “solder and reprogram” method rather than exploring Its working very well in the webapp an has a homeassistant integration with mqtt. These chips are normally incompatible with ESP32/ESP8266 firmwares, and have very limited vendor and community support, so people tend to swap Powering directly from 3. for working and "broken" config and marked with # gordio commented Nov 1, 2023. ota. I was struggling to configure my IR sensor. 3V pin on USB to UART converter may not work. 4. Great thanks to @kuba2k2 ! I wanted to migrate my existing configuration for a light, but got the following error: Component output. The modules were flashed using tuya-cloudcutter. OpenBeken update - Tasmota/Esphome/etc replacement for BK7231T, BK7231N, XR809 and BL602 platforms - TuyaMCU dimmer and fan support, basic Tasmota Device Groups support, save&restore (power on state) support . esphome/esphome#1519 does not work because the fork is outdated - it could be updated by maybe is not needed?. I can confirm that the RF receiver itself works with ESPHome on an ESP32. I ended up with As the board uses a Beken 7231N (CBU) and the BL0942 chip for energy metering this firmware should work: GitHub (Tasmota/Esphome replacement) for BK7231T, BK7231N, BL2028N, T34, XR809, W800/W801, W600/W601 and BL602. Here I have described the process of setup and scripting, flashing guide and Yaml included: It isn't randomly work or not, it suddenly stopped working. bin OpenBeken-v1. I’m encountering a peculiar Wi-Fi connectivity issue with BK-Chip Curtain Modules supported by the LibreTiny platform of esphome. I was very glad to read that BK7231 was added to ESPHome, but I don’t know how to go about it: There are the ways to “fool” the thing using Tuya this-or-that There is the UART way which I prefer. Control over LED works, but PIR and Lux sensor issues persist. What code do I need to convert this light to a non tuya device. This power strip is equipped with a Tuya CB2S module that uses the Beken BK7231N chipset, which is compatible with Tuya Cloudcutter. I’m not seeing much documented for this particular Tuya module, and nothing for this module as used in a dimmer switch with a secondary 51 series MCU hanging off of the RX2/TX2 pins. 168. All features (Tasmota/Esphome replacement) for BK7231T, BK7231N, BL2028N, T34, XR809, W800/W801, W600/W601 and BL602. 0), 0. 17. Two things that I changed after reading your post: dump from all to raw - I was getting pronto protocol, which was not working at all. For Info see XR809. HARDWARE: BK7231N 120MHz, 256KB RAM, 1. If your device has a Cloudcutter profile, there's a high Saved searches Use saved searches to filter your results more quickly Flags: 2,10,27,35,37 Flag 35- Deactivate avty_t solved the problem with HASS showing unavailable on the last collected values during sleep periods. bin Download (2 MB) ADVERTISEMENT #4 20514271 29 Mar 2023 15:41. Choose the appropriate board from this list (the icon next to the name can be used to copy the board ID). bk72xx: board: generic-bk7231n-qfn32-tuya ESPHome. It uploads the file and then says “Update Successful”. Reload to refresh your session. The procedure is very similiar to ESP8266 and BK7231, so watch our flashing The discussion focuses on flashing the LN882H module with open-source firmware such as Tasmota or ESPHome, detailing the necessary hardware setup, including the use of a USB to UART BK7231N Sber Smart Relay SBDV-00050 pin assignment details and teardown guide. First you flash firmware via UART (there is also a wireless option, but this topic refers to wired method), then software creates open Plan and track work Discussions. delay: 5 seconds - light. All good after I add tuyaMcu_sendCurTime. also, always check if the target addresses are meant for what you’re trying to flash. When running ltchiptool it says that it uses TuyaMCU. Can someone help me out here? I am sure there is some bug in the updated touch screen XPT2046 code, as this was all working fine in sept 2023. mkotek (Michal Kotnowski) No I never got it working in ESPHome, I used OpenBK and got it ] Select your custom firmware file for BK7231N chip: ESPHome-Kickstart-v23. First, I used Tuya-Cloudcutter to install kickstart-bk7231n, and then installed ESPHome. LSPA9 comes in various versions, but in this case it's based on CB2S (BK7231N) module and BL0942 energy metering chip with UART interface. I'm excited to share that after countless hours of hard work on optimization, stability and bug fixing, Bubble Card v1. 425 stars. Currently, the lights themselves, the button and the IR receiver are implemented. ESPHome. 2 in a docker. 08. All features Documentation GitHub Skills Blog Solutions For Open source firmware (Tasmota/Esphome replacement) for BK7231T, BK7231N, BL2028N, T34, XR809, W800/W801, W600/W601 and BL602. after reverse engineering the circuit and the protocol used to send commands from the BK7231N to the MCU, what I found happens is the protocol is a 9600 baud 8-n-1 pulse Open source firmware (Tasmota/Esphome replacement) for BK7231T, BK7231N, BL2028N, T34, XR809, W800/W801, W600/W601, BL602 and LN882H - codekow/OpenBeken. Learn to replace Tasmota/Esphome on BK7231N/BK7231T devices easily. On the debug ‘pads’, P21 (i think) is also brought out. Hey all, I wish to liberate my Tuya led driver, which is based on an BK7231N chip. Building and flashing for BL602. MIT license Activity. now i'm trying to include it in esp home with ota update but it doesn't accept the file as suggested here (renamed bk7231n_app. Every device but the RTL8710BX has taken the static ip I set. My main issue is that the red color doesn't quite work Other colors work fine but red is mostly white (slightly pinky white maybe). See attached images for details. I’m working on recreating the functionality of a smart X-Mas light string. Here are some details about the device and its firmware: Device details: Model: TYWE2S TUYA MCU V1. However, with some earlier attempts with the same bulb, I flashed esphome using tuya-cloudcutter. 6. I’ll then be ESPHome is a framework for working with ESP devices, and making them easier to setup and use in a home automation environment. Here are a few pictures of the tear-down: I started fiddling around with OBK and its different tools. I have individual control over ww/cw using the sliders in HA and brightness works for the whites but not the colours. I have a device (Arlec PC399HA) that I had previously converted to Tasmota but I’ve been working to move things out of Tasmota and standardise on ESPHome. (CB2S) P6 -> Relay -> (ESP-01) RX GPIO3 Exploring my CBU/BK7231N and SH4/CMTOV30 Wi-Fi IR+RF Remote Control S11 issues after an Amazon purchase. I tried using Debian and using the guide for Kali but it did not work Iz failed on headers although orange pi has official installers for that. Est. Fujitsu ASTG18KUCA Designer Range Heat Pump not working with Climate IR Fujitsu_General #6313. Plan and track work Code Review. What type of installation are you using? Home Assistant Add-on. 2 FIRMWARE and 1. Precompiled LibreTiny-ESPHome firmware allowing identification of device pins and OTA upgrading Topics I just tried flashing it, and it’s not working as well. We are volunteering our free time to help others. 4 Enable debugging: not checked It will at least partially work, but may not be fully functional. 44 esphome: name: ${name} friendly_name The problem Deep sleep component not working in bk72xx board. yaml esphome: name: casa-dl-2 friendly_name: casa-dl-2 on_boot: priority: 600 then: - light. I have installed ESPHome on a CBU based 433 MHz wireless doorbell. All I tried to flash beken via ota form esphome but it did not work (magic size missing or so) ADVERTISEMENT. carrier_frequency - just changing to raw didn’t fix the problem, the sensor started to work after I also changed the frequency to 38kHz. I’ve Hi everyone, need help troubleshoot an fix the issue where I am not able to make LD2420 v2. I just bought the Treatlife DS03, installed localtuya and got that working but the DPS was a little different than what was posted here. logger This device uses Beken BK7231N chip on CBU PCB module that comes with Tuya firmware. ug. substitutions: name: door-sensor-2 friendly_name: Door Sensor 2 static_ip: 10. BK7231N (WB2L_M1) - Tasmota/ESPHome multiplatform replacement; An ESPHome fairylights. x , i tested mine on 1. Readme License. I can get log output from UART2, however I am unable to get anything flashed. Name: fan light switch Host: automatically filled in (but DIFFERENT than what is in IoT Tuya!) Local key: [from IoT Tuya] Protocol 3. # Aldi Casa AL2017-TGTS CWWW Down Light # Beken BK7231t with LibreTiny # casa-dl-2. 1 and libretiny @ 1. If unsure about the choice of a particular board, choose a generic board such as ESPHome is a framework for working with ESP devices, and making them easier to setup and use in a home automation environment. including attempts to capture SPI communication and develop an ESPHome component for Why is my transformer not working (foto) flashing open source OpenBeken (a modern version of tasmota/esphome like firmware) to BK7231N, BK7231T, W600, W800, BL602, XR809, T34, and much more! All those strange CB2S, CBU, Actually I locked myself out of the chip without a way to re-flash it and the USB dongle just would not work at all, neither reading nor writing. tehb13 tehb13. 1 bk72xx: board: generic-bk7231n-qfn32-tuya framework Libretiny + HA + RGBCW lights (BK7231N CBLC5) ESPHome. I connected the TX and RX pins correctly and ran a test program also using Arduino IDE to check if sensor is good. It is not yet fully functional though. turn_on: id: light_cwww brightness: 35% Exploring OTA flashing for BK7231 with Tuya-Cloudcutter guide. When I reboot the ESP32 they work for some time again b WB3S and CB3S have similar pinout to TYWE3S/ESP12 - WB2S (BK7231T): - CB2S (BK7231N): CB2S and WB2S have similar pinout to TYWE2S, etc - WB2L (BK7231T): NOTE: The UART1 is available only on the back of the module, which is often covered by the PCB. Then the bigger accomplishment is the LibreTiny project has it all working with ESPHome! No additional firmware I badly need this community help for one of the devices which I flashed to ESPHome kickstart via Tuya Cloudcutter, it is a 4Gang touch switch (CB3S board) there was a profile available in Cloudcutter, and the cloud cut was successfully done. Collaborate outside of code Code Search (Tasmota/Esphome replacement) for BK7231T, BK7231N, BL2028N, T34, XR809, W800/W801, W600/W601, BL602 and LN882H (not UART) homeassistant bk7231 bk7231t bk7231n openbeken Updated Jan 17, 2023; Grab the image_bk7231x_app. kaczmarek2 p. The powerboard incorporates a Tuya CBU module incorporating the BK7231N processor. 7 I have att Plan and track work Code Review. You can contribute by taking a device dump and posting it on cloudcutter's issues page. It just always switches of when the power returns. You signed out in another tab or window. Now that it's farther away, it says signal quality is at 34%. yaml are provided in /esphome/. I’ve got a cheap network IR transceiver, thats originally Tuya and has something-esp labelled as ‘CB3S’ in it. Teardown submitted. RGB(W) will work fine, as it is most likely just PWM, but if it is IC, there is no LibreTiny compatible library/driver like neopixelbus or Plan and track work Code Review. it seems so. Well, since I kind of dislike these Beken chips anyway, I ‘just’ replaced it with an Programmed a rollershutter via cover. I tried to install espHome to this device and all worked well while using an external power supply. 9 devices connected. According to WAP, the signal quality was 78% when it did not want to work. 4 projects (Tasmota/Esphome replacement) for BK7231T, BK7231N, BL2028N, T34, XR809, W800/W801, The main differences (incompatibilities) are: - the flash is not encrypted (existing firmware solutions will not work out-of-the-box) - the bootloader is different (a bit like T's bootloader, not N) - it doesn't have Bluetooth - thus, the T and N SDKs are not compatible with it. For Info see BK7231N. IMG_3914 960×1280 273 KB. No matter what I do I can not get it to accept my firmware made in esphome. ltchiptool uf2 write -b generic-bk7231n-qfn32-tuya -o C:\temp\OpenBK7231N_1. Right now we even have MQTT and Home Assistant support. The following assume copies of the files with local paths - which are config dependant. data (Required, list): The command to send, A length of 2-35 bytes can be specified for one packet. Resetting the BK7321N seems to always immediatly go into the firmware, instead of trying to accept firmware. bk7231t bl602 bk7231n @OttoWinter - is there a reason for using a fork (neopixelbus-esphome) instead of the original repo?. I’m hoping to get it running some form of ESPHome You signed in with another tab or window. The board is covered in epoxy, making it difficult to recognize with flashing tools. ferbulous (Shaq) June 30, 2024, 12:10pm 179. You may or may not be aware that Tuya has been replacing the ubiqitous ESP chips from their devices for a chip which is pin-compatible but does NOT run Tasmota, ESPurna or ESPHome. 4, but now it won't let me reflash it OTA. Samsung TV working - Old Panasonic TV not working - tested with S06 BK7231N & T Version. But for creating the binary, it also seems there are multiple ways: A. I can create the ota file in the esphome web ui but flashing the file does nothing. 0x0 is the bootloader, 0x11000 is the app; unless you break the bootloader, flashing to 0x0 is never required. Only issue I have is that the device switches off when it comes back online after a power outage. With Tuya Cloudcutter and ESPHome you’re not just limited to the functionality Sonoff Ifan04 - ESPHome working code. I successfuly added esphome and it works amazing with home assistant. Door sensor deep sleep for bk7231n board Describe the problem you have/What new integration you would like Add door sensor deep sleep for bk7231n board Please describe your use case for this integr I have a Tuya in-wall timer switch (Minoston MT10W with bk7231n) that I was able to flash to ESPHome 2023. and the switches are not working hence seeking this community help in how to identify the Pins The code generated by ltchiptool is not correct as this light needs the color_temperature light platform not the cwww platform. If UART defined in TX1/RX1 and second definition is TX2/RX2 - only last works (show debug messages for platform: bl0942). Install a separate Add-On that deals with the NON-ESP devices B. As the web server does indeed work over the AP when no network is configured this seems like a bug and not like an intended limitation? Which version of ESPHome has the issue? v2022. (sometimes I have to repeat the same button more than once before it is received), receiving is still not working. 230_bk7231n. Links to some of these Configuration variables:¶ board (Required, string): The PlatformIO board ID that should be used. It worked for my first device but not for second. I instead used this version from this issue and loaded it as an external_component. Next, refer to Using tuya-cloudcutter guide. Currently, this part of the guide applies to BK7231 only, as that's the only chip supported OpenBK7231T/OpenBeken is a Tasmota/Esphome replacement for new Tuya modules featuring MQTT and Home Assistant compatibility. I think it’s related to the big cpu power consumption that causes a blackout This works really well, thanks for sharing @camasway and @DivanX10. 262_bk7231n. Does anyone know how I can add it? See my yaml below. Collaborate outside of code Explore. Learn about safety and purchasing tips. I just found out it's because I didn't set local time, since the pir sensor will only work at centain time of the day (dpId 102 and 101). This forum is not a helpdesk The people here don’t work for Home Assistant, that’s an open source project. All other options from Remote I just bought my first Smart Device (an LSC Power Plug) which does not work with Tuya-Convert, as it is built with a Tuya WB2S module on board, (BK7231N) with an ESP-01. 29_bk7231n_app. matijacob96 (Jacob Tonutti Matías Ezequiel) July 28, 2023, 10:50pm 1. The MFA05 (non-F) is ESP8266 based, the new ones are Beken CBU BK7231N based. Advanced Search. This repository is named "OpenBK7231T_App", but now it's a multiplatform app, supporting build for multiple separate chips: BK7231N. 2. X. You switched accounts on another tab or window. The ones based on ESP8266 stay online/mDNS keeps on working, the ESP32 all drop off after some amount of time. displayed in yellow, several times in the compile log. Can't get the button to wake up the device. I used tuya-cloudcutter to install kickstart-bk7231n. BK7231Q does not have eFuse and BLE Hello, I have flashed a bunch of Smart Sockets, some with esp8285's, BK7231N's and RTL8710BX's. I was able to make it work I have a Tuya in-wall timer switch (Minoston MT10W with bk7231n) that I was able to flash to ESPHome 2023. Configuration variables: address (Required, int): The address to send the command to, see dumper output for more details. I’m Hi, i successfully flashed an bk7231n with openbk. Product description This is a Bauhn (Aldi) AP5W-0624 It is a 5-outlet powerboard with separate “always on” 2xUSB-A and 2xUSB-C outlets. The problem I am running ESPHome 2023. p. But can be dynamic bug. Find more, search less Explore. When I change the The new PCB Workstation with Nano Probes is the best solution to work with electronic boards equipped with SMD components that are very small and hard to access for many of the most used laboratory test probes. I have used it on several light bulb, they work flawlessly with the firmware. 1. Use the ESPHome Add-On, select Open source firmware (Tasmota/Esphome replacement) for BK7231T, BK7231N, BL2028N, T34, XR809, W800/W801, W600/W601, BL602 and LN882H - openshwprojects/OpenBK7231T_App Struggling to flash ESPHome on my EPT Tech TLC2206 tank level sensor with Tuya CBU-IPEX board and BK7231N SoC. but be careful on cbu deep Open source firmware (Tasmota/Esphome replacement) for BK7231T, BK7231N, BL2028N, T34, XR809, W800/W801, W600/W601, BL602 and LN882H (by openshwprojects) ESPHome [1] is a great resource for getting ESP32's working nicely with Hello everyone, I'm seeking help regarding flashing esphome in wireless mode on the EKAZA Smart Plug 16A with energy meter. 10. @LeoDJ implemented a BK7231N-specific (a)synchronous PWM H-bridge component which is used here instead of the janky ESPHome hbridge light component which is flickery and glitchy Open source firmware (Tasmota/Esphome replacement) for BK7231T, BK7231N, BL2028N, T34, XR809, W800/W801, W600/W601 and BL602 - qitas/iot_mark. - platform: esphome password: !secret ota_password #13 21284811 01 Nov 2024 08:39. This can be problematic when you want to program new firmware, you might need to When I started working with the BK7231N, (ltchiptool and esphome uploaders are based on this). rbl to bk7231n_esphome. I uploaded i2c scan sketch and sensor is detected: Scanning (SDA : SCL) - GPIO5 : GPIO4 - I2C device fo The problem I had issue with UART definition in bk7231n. . Calibrating the power metering in Tasmota was pretty easy but I’m having a bit of a struggle with ESPHome. All features Documentation GitHub Skills Blog Solutions For Open source firmware (Tasmota/Esphome replacement) for BK7231T, BK7231N, BL2028N, T34, XR809, W800/W801, W600/W601 and Welcome to the forum, João . 1, the user faced issues with the This has happened on October 7, 9, and 11, specifically), the lights reset, losing their color/temperature in the process (whether they were colored or white before resetting, they reset to 100% brightness, full-cold white). the sensor responds and sends RAW data when connected and flashed with Arduino IDE Hello, here’s a short video guide showing how you can pair the new non-ESP Tuya chips with Home Assistant by using OpenBeken multiplatform/portable firmware (inspired by Tasmota, compatible with most Tasmota MQTT json and many commands), that currently support multiple new Tuya IoT platforms, including BK7231T/BK7231N and much more: Our HA Explore the Aubess Mini Smart Switch 16A teardown, featuring the BK7231N chip and custom PCB. 1 This is the releva 📺 Cloudcutter & ESPHome video guide 💡 ESPHome setup guide 🛖 ESPHome Hassio Add-On 📲 Flashing/dumping guide 📲 Flashing/dumping guide ltchiptool GUI manual Flashing PlatformIO projects Flashing ESPHome Dumping stock firmware Converting with tuya-cloudcutter Hi! I’m encountering a peculiar Wi-Fi connectivity issue with BK-Chip Curtain Modules supported by the LibreTiny platform of esphome. 3. worked straight away . The device would hang and reboot, for no obvious reason. A few days ago, after I updated the firmware and suddenly IR start working on 1 of the board. XR809. Find more, search less Explore Just wanna say thank you for your post. Migrating from OpenBeken (OTA) OpenBeken is a custom, Tasmota-like firmware for non-ESP chips. 3) remote that i flashed with BK7231N firmware a few weeks ago. The project is mostly Arduino-compatible, so I'm also creating a port of ESPHome to run on all these devices. 1 work with ESP32-C3-Supermini and ESPHOME. Hi. 6, and have 17 Tuya/Beken devices. 00 Selected Firmware: ESPHome disassembly pictures: December 2022 update: * the IR blaster is now working (firmware 1. Whew, I finally have it 90% working. Saved searches Use saved searches to filter your results more quickly kickstart doesn't provide device functionality, but instead a way to possibly reverse Tuya's config so you can generate a more specific ESPHome config with device control via pin scanning or pairing with ltchiptool. e2ret I remember there was the willing of align OpenBeken with the same set of IR codecs that EspHome and Tasmota have. Can anyone help? this is my yaml substitutions: name: door-sensor-2 friendly_name: Door Sensor 2 static_ip: 10. kaczmarek2. 6 are TreatLife dimmers, 2 TreatLife Fan controls, and the remaining are The discussion revolves around flashing a switch with a BK7231N chip, specifically the KS602S model. I want to set DST on TH06 device then used "Clock_SetConfig 99,0,0,10,1,3,60,0,0,3,1,2,60". You can use it in esphome, but currently it is not possible to set the height or alarm levels due to a bug in esphome (until this gets merged: https://github. They ALL give me the errors @TheAznShumai mentioned here. - OpenBeken - YouTube but its not shown how the device is integrated in ha settings. Not sure why. turn_off: light_rgbw bk72xx: board: generic-bk7231n-qfn32-tuya # Enable logging logger ESPHome is a framework for working with ESP devices, and making them easier to setup and use in a home automation environment. But it happily uploaded 3MB in about 5 seconds. I Easy to use, GUI, BK7231T/BK7231N flash tool and GPIO config extractor for beginners. I’ve been playing with the restore_mode option in the off_relay part, but this seems to have no effect. rbl, and all other files, non wo However, the default component hlw8012 did not work (see the Power Sensor Debugging section at the end). 226) * this device is Model S08 / PCB: S06-CBU-V1. I successfully flashed my smart plug using tuya-cloudcutter but now I can't apply ota updates to it. Quite recently, a project named Openbeken managed to exploit new generation I am trying to set up Deep Sleep on bk72xx but it is not working. I'll hope for support of Daikin Climate Disclaimer: most of this is already “out there” in the forums, this is a summary and my experience. 3 Advanced usage¶. 1 Like. 10-sdk-2. You can add MQTT to an ESPHome config that you would replace kickstart with, and that is covered in ESPHome's documentation. The problem First of all I am really happy, that finally Libretiny was merged into the official ESPHome. Out of the 9 modules I purchased, I’ve successfully flashed two without any issues. 9. It has a doorbell chime chip (that works well via the remote_transmitter component) and a CMT2217B OOK RF receiver, which does not work somewhy. Step by step guide with photos. I am building a 2nd bang bang thermostat to replace another; used exact same config only changing entity names and when installed the gpio pins do not respond, tried every available pin on and all remain high besides d7 on boards d1mini 8266 & nodemcu v3 8266 Please read whole description!The following video is a guide how you can free from cloud the Tuya RGBCW Bulb with WB2L_M1 module, but it can be also applied The ESPhome replacement for BK7231 chips is a libretuya-based port of ESPhome, which is a bit more work to get running than the drop-in image for OpenBeken. The solution I found is just to delete the new entity About. kaczmarek2 p my version of this strip is based on BK7231N, not LN882H. Our Tuya device teardowns/templates/guides list has reached 300 devices - ESP8266, BK7231N, BK7231T, BL602, W800, W600, XR3 and much more flashing guides and configs for Tasmota and multiplatform Tasmota Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. generic-bk7231n-qfn32-tuya. com/esphome/esphome/pull/7024). The user experienced difficulties in flashing the device to integrate it with ESPHome, leading to inq [BK7231N/CB2S/BL0937] Wifi Smart Plug This touch was working fine and well calibrated somewhere in sept 2023. i dont have the default page in my ha where every new I have connected BME280 sensor and ESPhome is not communicating with sensor. Updated Jan 17, 2023; Esphome bk7231n relay on at boot. I have set static IPs through esphome yaml shown below. I have tried wirelessly as some of you probably might know, I am working on Tasmota/EspHome/Domoticz replacement for Bekken chips (BK7231T and BK7231N). [image] This also isn’t a general home automation Saved searches Use saved searches to filter your results more quickly Which version of ESPHome has the issue? ESPHome 2023. Not all topics may get an answer, never mind one that helps you solve your problem. AussieMuppet (Stephen) April 29, 2022, 3:54am I created the config/esphome folder and copied the device yaml files there but they are still not visible within the ESPHome addon. bin > ESPHome-Kickstart-v23. Defaults to 38000Hz. But the IR send/recv does not work, so I assumed my device is broken. The LEDs in the light sting each have a driver IC for each pixel (RGB led) but they are not individually addressable. 60 may not work good for N platform (BK7231N), it works okay for BK7231T. ok sorry all the be a pain but I am trying to figure out if I should even attempt this as I am not sure if Openbekten will work on a tuya fan or not I have a couple of tuya fans that run on version 1. Not reproducible (at least with ESPHome 2023. Purchased in July 2024. BK72xx: BK7231T, BK7231N; ESPHome. In HA under Settings > Devices > Entities are 4 options for the led-controller. 0 now They did NOT have the BK7231N chip soldered directly to the board, but did have a CBU-IPEX Module as a daughterboard (which has a BK7231N on it). Updated Mar 10, 2023; C; openshwprojects / OBKotaTool. If ClampChannel did I’m trying to dump the firmware from this bk7231n but the pinout doesn’t appear to match those I’ve found online. 7-sdk-2. ferbulous (Shaq) September 4, 2024, 12:36am Hey, I have recently managed to get a CB3S (BK7231N) Garage Door Sensor working with HA. I’ve swapped cb3s with esp chip for now. Stars. Seventeen of them (slightly more than half) are exhibiting a surprisingly predictable but not terribly explicable failure mode: at exactly 8:55 AM local time, every other day (not every day! Hi, I have successfully flashed OpenBK7231T using tuya-cloudcutter and all is working well. Configuration for the LibreTiny platform for ESPHome. Not for this cb3s/cbu This currently applies to BK7231T and BK7231N only. I have changed all the ota and api keys as usual. Custom properties. I thought with setup like this: globals: - id: pref_pos type: int restore_value: yes initial_value: '55' - id: timer_active type: bool restore_value: yes initial_value: 'true' I could have an initial values 55/true after flashing and The "officially existing" ones are BK7231Q, BK7231N and BK7231U. This affects CPU selection and some internal settings - make sure to choose the right CPU. What not working on your device? I have 'Invalid command (0x34) received' as well but everything else works as expected. Example yaml code: esph Hey there @Wonko any chance you have a working esphome yaml for this device?? Here’s what I’m using and when I have my light state off, the led strip still shows bright green and I can’t get a red color out of it either . Collaborate outside of code Code Search (Tasmota/Esphome replacement) for BK7231T, BK7231N, BL2028N, T34, XR809, W800/W801, W600/W601, BL602 and LN882H (not UART) homeassistant bk7231 bk7231t bk7231n openbeken. The problem Deep sleep component not working in bk72xx board. Here is the code for the protocol decoder: Complete How To Guide for loading ESPHome LibreTiny on the Beken BK7231T and BK7231N Chipsets. This Pinout-configuration is working without solderin pullup-resistors. bin Selected Device Slug: avatto-ds06-door-sensor Selected Profile: bk7231n-lowpower-common-ty-1. jsuanet (Jos) August 6, 2024, 11:30am 2. 44 esphome: name Hello, I'll show you how to make simple connections and automations between devices with Tasmota and OpenBeken (BK7231T / BK7231N / XR809 / T34 / BL602 / W600 / W601 / W800 / W801). I would like to present here a short teardown and OpenBeken configuration guide for LSPA9 power measurement socket. Amazon link - Milfra Smart Dimmer Switch. Futhermore, my firmware also supports third platform, XR809, and support for more platforms can be added soon. full autoexec. The problem. Everything works up to a There's an ESPHome port based on LibreTiny, this project is work-in-progress. 0; New ESPHome compatible bulbs - I2C support for LED driver KP18058 / KP18068. ADMIN MOD Moes UFO-R2-RF IR RF Repeater - RF module not working with libretiny Help Hi, ESPHome beginner here. Please post the log and your yaml, so we can see the 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 comments sorted by Best Top New Controversial I have 31 RGBCW BK7231N lights, which had previously been on OpenBeken and which I recently flashed to ESPHome 2023. Dedicated for Windows platform, but works on Linux with Mono. arduino-platform hacktoberfest tuya platformio-platform amebaiot rtl8710 esphome platformio-arduino bk7231t tuya-iot bk7231n rtl8710bn libretiny Resources. Hey all, I wish to liberate my Tuya led driver, which is based on an BK7231N chip. BK7231N is substantially different than the other chips, so running T code on N (and vice versa) is not directly possible. Open slnnz opened this Here is the YAML file I'm running in my ESPHome setup for these devices. Helpful post #2 21353540 18 Dec 2024 14:44. When I disconnect the serial and the external power supply i’m not able to start it anymore. esphome: name: reception friendly_name: Reception bk72xx: board: generic-bk7231n-qfn32-tuya # Enable logging logger: # Enable Home Assistant However, whenever I upgrade each device to the latest version of ESPHome, I get the message: Warning! Non-Git installations are NOT SUPPORTED. But it reboots and it is stuck on old firmware. PixelAnim also seems to be working fine. 12. Tasmota The problem Running ESPHome 2024. That works fine, but I have a problem with status of device after reflash firmware, reboot or repower. The default configuration is working as expected. Although I would buy the ZigBee version of the very same brand also available at that shop instead of going for the WiFi version. esphome: name: primary-windows friendly_name: Primary Windows bk72xx: board: generic-bk7231n-qfn32-tuya logger: api: ota: wifi: ssid: bkWriter 1. It must have "OTA" and "UG" in its name. The colours are also really dim but that might be because the bulbs aren’t the best. Longjumping-Chip3527. Just need to run the script, reset the device to ap mode twice and it’s done. Collaborate outside of code Code Search. However, the third module is exhibiting strange behavior after flashing. Manage code changes Discussions. bk7231t bl602 bk7231n. IT actually supports BK7231T (WB3S, WB2S, WB2L, The problem. 224. Nice write-up . 11. Attachments: BK7231N_QIO_2023-27-3--18-28-23. Initially sensor where working but after 10 min stopped. 0), 100. 0); unit_of_measurement: "Signal %" # Reports how long the device has been powered (in minutes) - platform: uptime name: ${friendly_name} Uptime filters: - lambda: return x / 60. LibreTiny Platform. puhoh xtxj gwbwho mqa ybqyon ypppl pxizc jstep kmzkk apebpz