Ivan Banha
banner
banha.bsky.social
Ivan Banha
@banha.bsky.social
Software Engineer. I work with TypeScript, React, Node.js stack. Learn Golang and tinker with electronic and microcontrollers when have free time.

Also, I like nature, 🗻 mountains and picking mushrooms in a forest.
December 20, 2025 at 4:11 PM
The best thing for me is that it's easy to use a debugger within an app. So far, I was able to make a sample project with #MobX, #Valtio, and #Dockerode libraries. The project is still in early stages, but I see the potential.
December 20, 2025 at 4:08 PM
It lets you create a desktop app with React and TypeScript, but it uses native #GTK4 widgets to build your #UI. For dev, widgets look like regular React components. It runs on #Node.js, which means it's possible to use a variety of available libraries in the Node.js ecosystem.
December 20, 2025 at 4:08 PM
Wow 😲
November 4, 2025 at 6:34 PM
What’s the use case of such setup?
October 6, 2025 at 6:06 AM
1 + making tiny pet projects
May 5, 2025 at 7:11 PM
Hey 👋. I would like to clarify one thing about Core Time 2. Will it have barometer and compass as well as Core 2 Duo?
May 5, 2025 at 7:32 AM
Ubuntu 24.04 seems to be pretty stable.

I have AMD GPU and only Ubuntu (from relatively fresh distros)is supported by AMD’s official drivers.
November 24, 2024 at 8:55 AM
DDR3 🤔 It’s not that old 😄 I have an old laptop with DDR2. It still runs Debian perfectly with Home Assistant on it.

What’s the new purpose of that pc though?
November 23, 2024 at 7:38 PM
I believe you can assign static IPs for some of your devices on a router level. In my case, I use MikroTik router and my servers have assigned static IPs. So bulbs can't steal them.

Additionally, there is an option to assign IP for a device in ESP Home config. But I haven't tried it yet.
November 16, 2024 at 4:38 PM
And the result 😄
November 15, 2024 at 4:33 PM
If the config file is correct, the controller should connect to the Wi-Fi. All next updates will install as OTA. Now you can add your device to Home Assistant dashboard and create scripts and automations for it.

Moreover, there are other ways to control the device, such as #MQTT or via #HTTP.
November 15, 2024 at 4:33 PM
Long story short.

The process of the first firmware is as follows:
1. Add a device to the dashboard and write basic config.
2. Compile the firmware and download its UF2 file.
4. Flash the file using ltchiptool.

Done! 🥳

Guides:
esphome.io/guides/getti...
docs.libretiny.eu/docs/flashin...
Getting Started with ESPHome and Home Assistant
Getting Started guide for installing ESPHome Dashboard as a Home Assistant add-on and creating a basic configuration.
esphome.io
November 15, 2024 at 4:33 PM
Then, install the initial firmware on the microcontroller. All further updates will be installed via OTA updates over Wi-Fi.

The documentation says that initial firmware can be flashed through a browser, but it didn't work for some reason. So I flashed it via the USB-TTL converter.
November 15, 2024 at 4:33 PM
I chose option #2 because my 10-year-old Dell laptop doesn't have UEFI. However, its power is more than enough to run HAOS directly. Also, with turned off screen and unnecessary devices, it consumes only 10 watts!

Here is a description of how to install Supervised HAOS: github.com/home-assista...
GitHub - home-assistant/supervised-installer: Installer for a generic Linux system
Installer for a generic Linux system. Contribute to home-assistant/supervised-installer development by creating an account on GitHub.
github.com
November 15, 2024 at 4:33 PM
Below are some of the important details based on my experience.

There are several options to install HAOS:
1. Docker. Not suitable because add-ons won't work.
2. Supervised HAOS on #Debian (other distributions aren't supported).
3. HAOS as the main OS on a computer (UEFI required) or on VirtualBox.
November 15, 2024 at 4:33 PM
Before installing the new firmware, you MUST back up the original firmware in case something goes wrong.
The firmware is compiled through the #ESPHome plugin.

The process is described here: docs.libretiny.eu/docs/flashin... docs.libretiny.eu/docs/flashin...
ltchiptool GUI manual - LibreTiny
docs.libretiny.eu
November 15, 2024 at 4:33 PM
To flash the firmware, you need:
1. A soldering iron.
2. A laptop with #Windows.
3. USB-TTL converter based on #CH340G. Others may not work.
4. An app for flashing called ltchiptool.
5. Installed HAOS with the possibility to install add-ons.
6. Oscilloscope (optional) - just to see cool signals 😄.
November 15, 2024 at 4:33 PM
The rest of the pins are attached to the chip. I even managed to send a signal out of them using PlatformIO. I could not identify only a 2 or 3 pins. But I'll do that in the future.

Now it's time to flash the new firmware. Let's talk about required equipment.
November 15, 2024 at 4:33 PM
Now, some info about the module itself. It has 15 pins. The pins TP1 and TP2 are used for UART, TP3 and TP4 are used to power the module.

TP1: TX
TP2: RX
TP3: GND
TP4: +3.3V

TP12 - PWM. This pin controls current flow to the LED. It's named as PA14 in the config.
November 15, 2024 at 4:33 PM
The only disadvantage is the need for a dedicated server with HAOS to control all devices. Luckily, there are many ways how and where to install the HAOS. Starting from installing it on an old laptop, virtual machine, Raspberry Pi or even running as a #Docker container.
November 15, 2024 at 4:33 PM