Oh wow, great it merged. Now i'm tempted to upgrade my beken devices to have them in esphome dashboard. I was unlucky with libretuya to upload some wrong version from git in past (lost wifi in one case, boot loop in other case), so i'm little affraid to upgrade yet.
Keep in mind this is a list of devices that profiles have been turned in. You could take a new device that no one has and just pull the config with the LTChipTool and it will build the ESPHome YAML right there for you with all the pins on most devices. So damn cool.
getting a weird message from the generated config file "The LibreTiny component is now split between supported chip families. Migrate your config file to include a chip-based configuration, instead of the 'libretiny:' block. For example 'bk72xx:' or 'rtl87xx:'
Not sure what you mean. ESPHome has libretiny in it now. Just like with ESP based devices, Beken devices need some means of flashing the firmware whether OTA or via serial.
@@milandzuris it does have BLE hardware wise, its just that the current iteration of esphome not supported it... yet, only time will tell but when it does, every single tuya device you have basically can act as BLE proxy.
What do you mean by don't overwrite the OTA password? Don't remove it from the yaml file like in previous videos, or don't change it, or something else?
If you have an existing device flashed with a OTA password, do NOT lose this password as the device will always ask for it until you set it to something else or blank. I've seen people just delete the key out of the yaml without a backup and this locks them out of the device for future OTAs since this is the design.
@@digiblurDIY Ok makes sense. I left the OTA blank. Is Esphome laggy in your experience? I set up some smart plugs ( Sylvania 75702). This is my first experience with Esphome. It's running in a docker on my RPi3b. HA is in a docker on the same Pi. When I toggle the relay through HA, sometimes it takes a couple seconds and sometimes it doesn't go through at all. They respond instantly through their web interface.
When trying to compile my firmware in esphome I get a fatal error everytime. arm-none-eabi-g++: fatal error: Killed signal terminated program cc1plus Does anyone know what this means? I have Kickstart loaded on my device, the device is seen by esphome I am just trying to download the esp firmware that I built with the upk website yaml
I haven't seen that one before but I've never tried it on a Pi3. Might have to try the esphome github or discord to see if there are any other reports.
@digiblurDIY I tried to just compile the default esp32 yaml to the firmware file on my pi3 and the compilation failed. I might have to build a test HAOS on an old laptop just to compile these firmware files. This has been a fun adventure so far. But if the laptop route doesn't work for some reason I will definitely hit up the github
@digiblurDIY pi3 was what was holding it back. Upgraded my instance to an N95 mini PC. I got a plug fully flashed and into ESPHome. For some reason the LED on the smart plug to work correctly. Tried led inverted true and false, but all that does is turn the led off or on and it doesn't change with the relay. But other than that, I am very happy!
OK So I expect this might be simple question. I have been looking at this I cant see to create LibreTiny targets for new projects in the standard ESPHome stable. Mine only shows ESP32, ESP8255 and raspberry pi pico targets. Am I missing something that will enabled BK72xx and RTL87xx targets? I cant find any notes online about this yet I can see its available in the release notes. Is this currently only available in the beta or dev version?
Did as you described but did I miss something. I get the following error when I try to update. INFO ESPHome 2023.9.2 INFO Reading configuration /config/esphome/be271.yaml... Failed config output.ledc: [source /config/esphome/be271.yaml:48] Component output.ledc requires component esp32. platform: ledc id: output_cold pin: P7
Dude the haircut is infinitely better...
Just like with my LASIK...should have done it sooner!
@@digiblurDIY lasik is the best money I have ever spent
Yeah, i was there too. My wife could not watch me getting bald, so she made me bald ;)
Awesome video thanks, learnt a lot . Love the relationship you have with youngster. Pretty cool
Thanks! We definitely have fun a good bit.
You are one of the lucky ones, you have a round head! Looks great, own it!
Loving it!
Oh wow, great it merged. Now i'm tempted to upgrade my beken devices to have them in esphome dashboard.
I was unlucky with libretuya to upload some wrong version from git in past (lost wifi in one case, boot loop in other case), so i'm little affraid to upgrade yet.
Everything seems to be working for fine for folks the past while now which is why it made it into ESPhome stable.
Looking sharp mate and thanks for the video! 👍
Thanks. No burn yet.
Looking good, ma dude! Nice video too, as always.
Appreciate it!
well perfect timing
Love the tiny NodeRed comment slid in at the end 😀...give it more due next time 😛😁
That's quite the reflection you got going on there, i'm impressed ;)
Shine that puppy up!
Thanks for this info Travis.
You bet!
Hair looks good, bro!
I like your style better!
This looks cool. I'll have to see if there are any cool devices in that supported list.
Keep in mind this is a list of devices that profiles have been turned in. You could take a new device that no one has and just pull the config with the LTChipTool and it will build the ESPHome YAML right there for you with all the pins on most devices. So damn cool.
@@digiblurDIY Very nice!
Thanks for making this video! Successfully migrated. -bootypipe
Glad it helped!
I'm so sad they have already started patching devices :(
Tried to libre'rate an tuya plug but no dice because its patched...
Bro...bald suits you well, i have an odd shaped head i wish id look that good bald😂
Thanks bro! Saves so much time and a bit of money as well.
Hey, do you have a services for people to send in Tuya devices to you to add custom firmware?
I’d love to do it, but we have a newborn. 😂
Depends on the devices and number of things really. Hit me on Discord or shoot me an email at the channel name on Gmail
@@digiblurDIY will do!
it's all about the YOML
It's Yawmillz as we call it in Discord. Even have an icon for it now with the saw and all.
getting a weird message from the generated config file "The LibreTiny component is now split between supported chip families.
Migrate your config file to include a chip-based configuration, instead of the 'libretiny:' block.
For example 'bk72xx:' or 'rtl87xx:'
10:05
Not weird at all. I did talk about this in the yaml changes chapter that starts at 9:10
" Libretiny is HERE! Everything you need to know" - except... What is LibreTiny?
Try 2:46 if you missed it plus the link in the description for the guide.
Do you still need to use CloudCutter first and flashing with new firmware before adding a device to ESPHome?
If you want to flash it via serial you don't need cloudcutter.
@digiblurDIY but you still need to flash it separately first i.e remove the old firmware.....it can't be done from ESPhome with libretiny added to it
Not sure what you mean. ESPHome has libretiny in it now. Just like with ESP based devices, Beken devices need some means of flashing the firmware whether OTA or via serial.
Waiting for BTProxy on Beken
beken dont have ble
I have heard it is being looked into.
@@milandzuris it does have BLE hardware wise, its just that the current iteration of esphome not supported it... yet, only time will tell but when it does, every single tuya device you have basically can act as BLE proxy.
What do you mean by don't overwrite the OTA password? Don't remove it from the yaml file like in previous videos, or don't change it, or something else?
If you have an existing device flashed with a OTA password, do NOT lose this password as the device will always ask for it until you set it to something else or blank. I've seen people just delete the key out of the yaml without a backup and this locks them out of the device for future OTAs since this is the design.
@@digiblurDIY Ok makes sense. I left the OTA blank.
Is Esphome laggy in your experience? I set up some smart plugs ( Sylvania 75702). This is my first experience with Esphome. It's running in a docker on my RPi3b. HA is in a docker on the same Pi. When I toggle the relay through HA, sometimes it takes a couple seconds and sometimes it doesn't go through at all. They respond instantly through their web interface.
When trying to compile my firmware in esphome I get a fatal error everytime.
arm-none-eabi-g++: fatal error: Killed signal terminated program cc1plus
Does anyone know what this means? I have Kickstart loaded on my device, the device is seen by esphome I am just trying to download the esp firmware that I built with the upk website yaml
I haven't seen that one before but I've never tried it on a Pi3. Might have to try the esphome github or discord to see if there are any other reports.
@digiblurDIY I tried to just compile the default esp32 yaml to the firmware file on my pi3 and the compilation failed. I might have to build a test HAOS on an old laptop just to compile these firmware files. This has been a fun adventure so far. But if the laptop route doesn't work for some reason I will definitely hit up the github
@digiblurDIY pi3 was what was holding it back. Upgraded my instance to an N95 mini PC. I got a plug fully flashed and into ESPHome. For some reason the LED on the smart plug to work correctly. Tried led inverted true and false, but all that does is turn the led off or on and it doesn't change with the relay. But other than that, I am very happy!
OK So I expect this might be simple question. I have been looking at this I cant see to create LibreTiny targets for new projects in the standard ESPHome stable. Mine only shows ESP32, ESP8255 and raspberry pi pico targets. Am I missing something that will enabled BK72xx and RTL87xx targets? I cant find any notes online about this yet I can see its available in the release notes. Is this currently only available in the beta or dev version?
Just pick one as there is no blank option. You will just overwrite it all anyways
Shhh.. ota password is a secret. Oh, we have a special place for secrets ;-)
OTA who? :)
Did as you described but did I miss something. I get the following error when I try to update.
INFO ESPHome 2023.9.2
INFO Reading configuration /config/esphome/be271.yaml...
Failed config
output.ledc: [source /config/esphome/be271.yaml:48]
Component output.ledc requires component esp32.
platform: ledc
id: output_cold
pin: P7
yes, I talked about this in the YAML changes chapter (on the slider) or jump to 9:10
@@digiblurDIY Of course, thank you very much
@johanalvedal4884 sounds like you got it?
Was that Nick Cage at timestamp 0.40. He uses esphome!?!?!
He does videos for HA of course! Pointing at the logos plus he even has the white outline around his body. 😎