Making a Heltec CubeCell Capsule based The Things Stack LoRaWAN sensor

 (Thurs 12th Feb 2026 16:10) What devices have we got?

A quick check shows 4 devices.

CubeCell Capsule devices

What is the status of each? I have a development interface board which allows me to check for any serial output and to do Arduino IDE development.

The one plugged into the interface board is labelled slan-008 and its serial output shows:

16:16:56.174 -> Copyright @2019-2020 Heltec Automation.All rights reserved.
16:16:56.505 -> 
16:16:56.505 -> 
16:16:56.505 -> Sketch: BME680_TTN_V3_slan_008_v1_3
16:16:56.505 -> Version: v1.3 Sat 7th Sept 2024 16:43
16:16:56.505 -> Board: CubeCell-Capsule (HTCC-AC0X)
16:16:56.505 -> 
16:16:56.505 -> 
16:16:56.505 -> AT Rev 1.3
16:16:56.505 -> +AutoLPM=1
16:16:56.505 -> 
16:16:56.505 -> +LORAWAN=1
16:16:56.505 -> 
16:16:56.505 -> +KeepNet=0
16:16:56.505 -> +OTAA=1
16:16:56.505 -> +Class=A
16:16:56.505 -> +ADR=1
16:16:56.505 -> +IsTxConfirmed=1
16:16:56.505 -> +AppPort=8
16:16:56.505 -> +DutyCycle=1740000
16:16:56.538 -> +ConfirmedNbTrials=4
16:16:56.538 -> +ChMask=0000000000000000000000FF
16:16:56.538 -> +DevEui=xxxxxxxxxxxxxxxx(For OTAA Mode)
16:16:56.538 -> +AppEui=xxxxxxxxxxxxxxxx(For OTAA Mode)
16:16:56.538 -> +AppKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx(For OTAA Mode)
16:16:56.538 -> +NwkSKey=00000000000000000000000000000000(For ABP Mode)
16:16:56.538 -> +AppSKey=00000000000000000000000000000000(For ABP Mode)
16:16:56.538 -> +DevAddr=00000000(For ABP Mode)
16:16:56.538 -> 
16:16:56.538 -> 
16:16:56.538 -> LoRaWAN EU868 Class A start!
16:16:56.571 -> 
16:16:56.671 -> joining...joined
16:17:03.012 -> Could not find a valid BME680 sensor, check wiring!

So what next? Let's find the BME680_TTN_V3_slan_008_v1_3.ino sketch. Cannot find sketch or entry on Heltec site for these devices (only V3). But found this:

https://iotci.co.uk/product/heltec-lora-node-asr6502-capsule-sensors-cubecell-sensor-for-arduino-lora-iot-waterproof-ip67-soalr-panel/

So lets our existing code and extend it to support more than just the BME680 sensor!

(17:07) That's done and code runs but just reports voltage on the serial line. So I will commit this code to GitHub as version 1.15

Looking at what capsule sensors I have I find four:

The BME680 is know and can be added to slan-008 (good test to reverting code to support BME680 in secrets.h file)

Fortunately, the above website lists all the capsule sensors:

Capsule sensors

So what code is needed?

Making a Heltec CubeCell-Board Plus based slan-031 environmental monitor

(Thurs 12th Feb 2026 16:03) Housing the units

The sensors and gateway now need to be housed. The following needs to be addressed:

1) Look attractive

2) Allow for display to be seen

3) Be water resistant (assume inside polytunnels will get wet)

4) Facilitate dismantling for maintenance

slan-031 and slan-093 (red tape)

A bit wet today so will return to this and search shed for materials another time.

(Weds 11th Feb 2026 20:10) Finalising the code

So over 24 hours the battery level has dropped from 4008 mV to 3980 mV. That's roughly 1 mV per hour. So will hit 3500 mV in 480 hours or 20 days - if everything keeps linear. Not bad. But what if I turned off the RGB LED after the first transmission? So here our tonight's tasks:

1) Turn off RGB LED after first transmission

2) Make code generic. That is move all secrets and ids to secret.h (don't push this to GitHub)

(21:18) Happy days. All checked in to GitHub and secrets.h.slan031 emailed to myself (this must replace the GitHub secrets.h before an operational slan-031 can be built)

Now to use this code (https://github.com/kilnageer2/HTCCAB02_LORA_DISPLAY_BME680)  to build a slan-093 by just changing secrets.h

The website: https://shannontownwetlands.ie/environmental-sensors/drumgeely-polytunnels can then be used to monitor the polytunnels (once the gateway and two devices have been boxed and deployed).

I searched in spreadsheet "2025 Attic Boxes v4" on my Google Drive to fine more Heltec HTCC-AB02 devices - though I do have one more soldered to RJ45 socket on my desk). 

Only 433 MHz ones on attic list (other attic boxes not yet added to spreadsheet!), So will have a quick look in bedroom before desoldering the one in LoRaWAN draw of my four draw cabinet by my desk. (This draw also has CubeCell Capsules x5 and Vision Master E290 x2 to get going :) )

(21:47) Found slan-031 HTCC-AB02 which successfully transmits every 5 secs but has no pins soldered to it so no sensor attached! But its orange LED charge light is on which is good,

(23:16) got slan-03 online and found great woven 4-wire cable to connect BME680 to HTCC-AB02

After battery is charged I will correct LOW_BATTERY_LEVEL and then commit tweaks to main code (added device name print statement). No need changed it to 3300 which works OK. Great. So 3.3 V low level operation limit rather than 3.5 V from normal 4.1 V.

(Tues 10th Feb 2026) Refactoring the code

This board has a long history. It is labelled slan-031 and sends readings from a BME680 sensor over LoRaWAN.

Currently, it sends temperature, humidity, battery level and atmospheric pressure every 10 minutes.

slan-031 environmental sensor

However, its charging circuit and antenna connection are broken. So no PV panel input and antenna is glued on.

I have raised Bugzilla bug #2 to track the changes needed http://192.168.1.153/bugzilla/show_bug.cgi?id=2

These being:

1) Code to be refactored into main, display, sensor and comms files.

2) Would like info displayed on reset

3) Would like info display on USER button press

4) Would like red LED to flash when battery below 3.5 V

The transmitted values can be seen by anyone at site: 

https://shannontownwetlands.ie/environmental-sensors/drumgeely-polytunnels

Website view of data

I tried the Claude Code generated files but they would compile so doing the refactoring by hand. But first to add code to GitHub

https://www.geeksforgeeks.org/git/how-to-fix-support-for-password-authentication-was-removed/

 1449  git commit -m "2nd commit, still not on GitHub"

 1450  git branch -M main

 1451  git remote add origin https://github.com/kilnageer2/HTCCAB02_LORA_DISPLAY_BME680.git

 1452  git push -u origin main

 1453  git status .

 1454  nano README.md 

 1455  git status .

 1457  git add .

 1458  git status .

 1459  git commit -m "Updated README.md"

 1460  git status .

 1461  git tag

 1462  git tag -a v1.08 -m "Initial working baseline before moving code"

 1463  git tag

 1464  git show v1.08

 1465  git status .

 1466  git push -u origin main

 1467  # Nice that remote repo is now Private!

Successfully pushed code from rhubarb laptop to GitHub using above but now need GitHub to accept it!

(17:01) Next to start messing with the code!

(18:50) Code looking good now have displays at start of device info and before first transmission of sensor data

Display after a reset of device info

Display at first transmission of sensor data

So just three things to do now:

1) Move LoRaWAN code to lorawan.cpp and lorawan.h

2) Show last sensor data and number of transmission since reset when USER button pressed

3) Flash RGB LED as red if battery below 3.5 V

(20:24) Well that's me done for the day. Tag v1.12b just has USER button code to add,

Red LED flashed and this is displayed on low battery (< 3.5 V)

Celestron NexStar 130SLT Telescope automation

(Sun 8th Feb 2026 21:00)

Nearly got scope calibrated but clouds arrived at 10 pm. Need three bright stars and a clear sky now.

So why talk about this here?

Well a WiFi dongle for this scope cost 200 euros. Enough said.

https://www.amazon.co.uk/Celestron-93973-Skyportal-Wifi-Module/dp/B00OJ5Z2NM

Too cold for outside and no 12V power

12V power and star finder fixed

Getting LoRaWAN Balena Cloud / The Things Network / RPi4 + RAK2245 Working

(Mon 9th Feb 2026 10:11)

Well couldn't compile but display and LoRaWAN code at the same time. So I will persevere this morning :) Let's log this fault BackLog (from NuLab) or switch to Bugzilla?

Let's install Bugzilla on sionnach via TigerVNC Viewer on rhubarb laptop.

http://bugzilla.readthedocs.io/en/latest/installing/quick-start.html

Hurrah after missing file (/etc/mysql/conf.d/bugzilla.cnf) and folder (/var/www/webapps/data) resolved Bugzilla is now live.

(12:00) Off for a celebratory walk now. I will migrate bugs from BackLog to Bugzilla as I work on them :)

Need to create a Tola Smart Home user and database next

(15:36) Successfully created first bug report:

http://192.168.1.153/bugzilla/show_bug.cgi?id=1

First Tola Smart Home bug report in Bugzilla

Fixed this bug by not including #include <Wire.h> so just commented it out and closed bug #1

But now would like to use VSC with integrated Github support to write, download and debug code. Looks like Arduino CLI should enable this: https://arduino.github.io/arduino-cli/1.4/

(18:06) I will then refactor my code and make it mode modular for re-usability. Amárach

(Sun 8th Feb 2026 14:26)

So leave the gateway for now and get 2x  Heltec Vision Master E290 going in Arduino. 

But first fix up slan-031 to tx every 10 mins (rather than every 15s) and to display stuff for first transmission. In Arduino IDE it's board: Heltec "CubeCell-Board Plus (HTCC-AB02)"

https://heltec.org/project/htcc-ab02/

Heltec CubeCell-Board Plus (HTCC-AB02) Pin Out

Circuit diagram of slan-031

(Sun 8th Feb 2026 13:26)

Next to get gateway on Ethernet and turn off WiFi.

Connecting to 4f00dab6411df9abd9d9166cbb1c5cde...
Spawning shell...
=============================================================
    Welcome to balenaOS
=============================================================
root@4f00dab:~# nmcli
wlan0: connected to TolaPark5G
        "wlan0"
        wifi (brcmfmac), B8:27:EB:E9:35:B4, hw, mtu 1500
        ip4 default
        inet4 192.168.1.182/24
        route4 192.168.1.0/24 metric 600
        route4 default via 192.168.1.1 metric 600
        inet6 fd4c:2987:22a0::47f/128
        inet6 fd25:407b:381c:0:1023:e3f0:7f52:c864/64
        inet6 fd4c:2987:22a0:0:1c38:5e60:285:e0e5/64
        inet6 fe80::4878:a26d:1000:4c02/64
        route6 fd25:407b:381c::/64 via fe80::4a5d:35ff:fef6:d1a8 metric 600
        route6 fd4c:2987:22a0::47f/128 metric 600
        route6 fd4c:2987:22a0::/48 via fe80::22f1:b2ff:fe5c:d4a metric 600
        route6 fe80::/64 metric 1024
        route6 fd4c:2987:22a0::/64 metric 600
supervisor0: connected (externally) to supervisor0
        "supervisor0"
        bridge, 02:42:51:7F:B1:2D, sw, mtu 1500
        inet4 10.114.104.1/25
        route4 10.114.104.0/25 metric 0
p2p-dev-wlan0: disconnected
        "p2p-dev-wlan0"
        wifi-p2p, hw
eth0: unavailable
        "0424 7800"
        ethernet (lan78xx), B8:27:EB:BC:60:E1, hw, mtu 1500
balena0: unmanaged
        "balena0"
        bridge, 02:42:0B:A7:D1:8E, sw, mtu 1500
resin-dns: unmanaged
        "resin-dns"
        bridge, 6E:5C:E1:9A:7D:84, sw, mtu 1500
lo: unmanaged
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
resin-vpn: unmanaged
        "resin-vpn"
        tun, sw, mtu 1500
DNS configuration:
        servers: 192.168.1.1
        domains: fritz.box
        interface: wlan0
        servers: fd4c:2987:22a0::1 fd25:407b:381c:0:4a5d:35ff:fef6:d1a8
        interface: wlan0
Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.
Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
root@4f00dab:~# 
root@4f00dab:~# 

So Balena Console shows WiFi (wlan0) going well but no Ethernet (eth0) connection.

So after connecting up RJ45 lead to Fritz!Box I then got...

root@4f00dab:~# nmcli
eth0: connected to Wired connection 1
        "0424 7800"
        ethernet (lan78xx), B8:27:EB:BC:60:E1, hw, mtu 1500
        ip4 default
        inet4 192.168.1.202/24
        route4 192.168.1.0/24 metric 100
        route4 default via 192.168.1.1 metric 100
        inet6 fd4c:2987:22a0::a3a/128
        inet6 fd25:407b:381c:0:b405:53de:1ed:a1f8/64
        inet6 fd4c:2987:22a0:0:a91d:3544:96f:22c2/64
        inet6 fe80::f4c7:a40f:962e:d5e8/64
        route6 fe80::/64 metric 1024
        route6 fd4c:2987:22a0::/48 via fe80::22f1:b2ff:fe5c:d4a metric 100
        route6 fd25:407b:381c::/64 via fe80::4a5d:35ff:fef6:d1a8 metric 100
        route6 fd4c:2987:22a0::a3a/128 metric 100
        route6 fd4c:2987:22a0::/64 metric 100
wlan0: connected to TolaPark5G
        "wlan0"
        wifi (brcmfmac), B8:27:EB:E9:35:B4, hw, mtu 1500
        inet4 192.168.1.182/24
        route4 192.168.1.0/24 metric 600
        route4 default via 192.168.1.1 metric 600
        inet6 fd4c:2987:22a0::47f/128
        inet6 fd25:407b:381c:0:1023:e3f0:7f52:c864/64
        inet6 fd4c:2987:22a0:0:1c38:5e60:285:e0e5/64
        inet6 fe80::4878:a26d:1000:4c02/64
        route6 fd25:407b:381c::/64 via fe80::4a5d:35ff:fef6:d1a8 metric 600
        route6 fd4c:2987:22a0::47f/128 metric 600
        route6 fd4c:2987:22a0::/48 via fe80::22f1:b2ff:fe5c:d4a metric 600
        route6 fe80::/64 metric 1024
        route6 fd4c:2987:22a0::/64 metric 600
supervisor0: connected (externally) to supervisor0
        "supervisor0"
        bridge, 02:42:51:7F:B1:2D, sw, mtu 1500
        inet4 10.114.104.1/25
        route4 10.114.104.0/25 metric 0
p2p-dev-wlan0: disconnected
        "p2p-dev-wlan0"
        wifi-p2p, hw
balena0: unmanaged
        "balena0"
        bridge, 02:42:0B:A7:D1:8E, sw, mtu 1500
resin-dns: unmanaged
        "resin-dns"
        bridge, 6E:5C:E1:9A:7D:84, sw, mtu 1500
lo: unmanaged
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
resin-vpn: unmanaged
        "resin-vpn"
        tun, sw, mtu 1500
DNS configuration:
        servers: 192.168.1.1
        domains: fritz.box
        interface: eth0
        servers: fd4c:2987:22a0::1 fd25:407b:381c:0:4a5d:35ff:fef6:d1a8
        interface: eth0
        servers: 192.168.1.1
        domains: fritz.box
        interface: wlan0
        servers: fd4c:2987:22a0::1 fd25:407b:381c:0:4a5d:35ff:fef6:d1a8
        interface: wlan0
Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.
Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
root@4f00dab:~# 

(13:44) So just need to disable WiFi (wlan0) connection now and ensure I can reboot to eth0.

root@4f00dab:~# 
root@4f00dab:~# date
Sun Feb  8 13:45:04 UTC 2026
root@4f00dab:~# nmcli radio wifi
enabled
root@4f00dab:~# nmcli radio wifi off

Ooops! Lost connection

But waiting a few mins then refreshing Balena Clod page re-established connection..

Connecting to 4f00dab6411df9abd9d9166cbb1c5cde...
Spawning shell...
=============================================================
    Welcome to balenaOS
=============================================================
root@4f00dab:~# date
Sun Feb  8 13:49:21 UTC 2026
root@4f00dab:~# nmcli
eth0: connected to Wired connection 1
        "0424 7800"
        ethernet (lan78xx), B8:27:EB:BC:60:E1, hw, mtu 1500
        ip4 default
        inet4 192.168.1.202/24
        route4 192.168.1.0/24 metric 100
        route4 default via 192.168.1.1 metric 100
        inet6 fd4c:2987:22a0::a3a/128
        inet6 fd25:407b:381c:0:b405:53de:1ed:a1f8/64
        inet6 fd4c:2987:22a0:0:a91d:3544:96f:22c2/64
        inet6 fe80::f4c7:a40f:962e:d5e8/64
        route6 fd25:407b:381c::/64 via fe80::4a5d:35ff:fef6:d1a8 metric 100
        route6 fd4c:2987:22a0::a3a/128 metric 100
        route6 fd4c:2987:22a0::/48 via fe80::22f1:b2ff:fe5c:d4a metric 100
        route6 fe80::/64 metric 1024
        route6 fd4c:2987:22a0::/64 metric 100
supervisor0: connected (externally) to supervisor0
        "supervisor0"
        bridge, 02:42:51:7F:B1:2D, sw, mtu 1500
        inet4 10.114.104.1/25
        route4 10.114.104.0/25 metric 0
wlan0: unavailable
        "wlan0"
        wifi (brcmfmac), 52:83:40:6F:38:59, sw disabled, hw, mtu 1500
p2p-dev-wlan0: unavailable
        "p2p-dev-wlan0"
        wifi-p2p, sw disabled, hw
balena0: unmanaged
        "balena0"
        bridge, 02:42:0B:A7:D1:8E, sw, mtu 1500
resin-dns: unmanaged
        "resin-dns"
        bridge, 6E:5C:E1:9A:7D:84, sw, mtu 1500
lo: unmanaged
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
resin-vpn: unmanaged
        "resin-vpn"
        tun, sw, mtu 1500
DNS configuration:
        servers: 192.168.1.1
        domains: fritz.box
        interface: eth0
        servers: fd4c:2987:22a0::1 fd25:407b:381c:0:4a5d:35ff:fef6:d1a8
        interface: eth0
Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.
Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
root@4f00dab:~# 
root@4f00dab:~# 

So last test to power off and then  on! Excellent all works and removed 2x 18560 UPS from RPi3. So ready to take it to Drumgeely once I have 2nd LoRaWAN temperature sensor and all have been boxed up :)

Balena Cloud for late-meadow (eth0 and no UPS)

RPi3 and RAK2245 LoRaWAN gateway (Balena/TTN)

(Sun 8th Feb 2026 9:49)

This morning I'm going to prepare late-meadow and 2x LoRaWAN sensors to take with me to Drumgeely.

Will get LoRaWAN sensor going first with gateway as is (i/e/WiFi not Ethernet)

10:22:44.045 -> Copyright @2019-2020 Heltec Automation.All rights reserved.
10:22:44.310 -> name:slan-031_HTCC-AB02_BME680 built:Sun 20th July 2025 13:18 version:1.06
10:22:44.310 -> 
10:22:44.310 -> AT Rev 1.3
10:22:44.310 -> +AutoLPM=1
10:22:44.310 -> 
10:22:44.310 -> +LORAWAN=1
10:22:44.310 -> 
10:22:44.310 -> +KeepNet=0
10:22:44.310 -> +OTAA=1
10:22:44.310 -> +Class=A
10:22:44.310 -> +ADR=1
10:22:44.310 -> +IsTxConfirmed=1
10:22:44.310 -> +AppPort=8
10:22:44.310 -> +DutyCycle=15000
10:22:44.310 -> +ConfirmedNbTrials=4
10:22:44.310 -> +ChMask=0000000000000000000000FF
10:22:44.343 -> +DevEui=70B3D57ED004ADB9(For OTAA Mode)
10:22:44.343 -> +AppEui=0000000000000000(For OTAA Mode)
10:22:44.343 -> +AppKey=3B45BA293945C9C1C6ACC00C61D9E6A5(For OTAA Mode)
10:22:44.343 -> +NwkSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)
10:22:44.343 -> +AppSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)
10:22:44.343 -> +DevAddr=007E6AE1(For ABP Mode)
10:22:44.343 -> 
10:22:44.343 -> 
10:22:44.343 -> LoRaWAN EU868 Class A start!
10:22:44.343 -> 
10:22:44.475 -> joining...joined
10:22:50.660 -> 
10:22:50.660 -> Starting I2CDemo example program for BME680
10:22:50.660 -> - Initializing BME680 sensor
10:22:50.660 -> - Setting 16x oversampling for all sensors
10:22:50.693 -> - Setting IIR filter to a value of 4 samples
10:22:50.693 -> - Setting gas measurement to 320°C for 150ms
10:22:50.693 -> 
10:22:50.693 -> 33.92°C 100.00%Hum 680.13hPa 130.02m 8121.46mOhm
10:22:51.949 -> 19.88°C 57.72%Hum 997.71hPa 130.19m 148.76mOhm
10:22:53.241 -> 20.12°C 57.77%Hum 997.69hPa 130.36m 147.91mOhm
10:22:54.530 -> 100x (Temperature+30)= 5012 C, 100x Humidity= 5776 %, 100x Pressure= 99769 Pa, BatteryVoltage:4052 mV, 1000x Gas=147910
10:22:54.530 -> confirmed uplink sending ...
10:22:59.891 -> received unconfirmed downlink: rssi = -59, snr = 14, datarate = 5

So what device is this? All good from above log it's slan-031 and it  is successfully sending data.. and I have a TTN IotPanel connection to graph it on my phone :)

But it's sending data too often. I want every 10 mins not every 10 secs...

So next to use Arduino to change this

(Sat 7th Feb 2026 19:45)

Final attempt is to put old software release on RPi4 and use the VARIABLE settings from the late-meadow gateway which is working in Tola Park. (See above images)

I tried but failed (see below images). So I leave this for now and pack away the RAK2245 with other LoRaWAN stuff and re=use RPi4 to drive a 7" touch display :)

Changed my mind! Decided to work through instructions below using Balena CLI

https://docs.balena.io/learn/getting-started/raspberrypi4-64/nodejs/

Got CLI going but it was just for a "Hello World" webserver

(Fri 6th Feb 2026 11:00)

Tried to get LoRaWAN gateway working over ethernet. But failed wouldn't connect to Balena. So took it home.

Tried at home with lots of BasicStation images but I could never get the BasicStation code to execute on the RPi4. The Host login always worked. Gave up in the end. Maybe hardware broken? Tried old RAK board from Kilnageer. But same result,

(Mid-Jan 2026)

This combination was working in the Drumgeely 40' container but as of Jan 2026 wasn't.

So I started to investigate how to fix it.

Making a ESP32-CAM into a Smart Home sensor

This device couldn't be programmed with a Tasmota binary https://ota.tasmota.com/tasmota32/release/ from the Webinstaller https://tasmota.github.io/install/ 

Maybe I'm not holding the RST and PRG buttons properly to enable programming>

But let's try the factory binary...

Making an ESP32-C6-LCD a Smart Home monitor

This device can be programmed wit the factory C6 binary.. and use SVGL to control LCD display

Making a ESP32-C3 based Smart Home Monitor

This device is well supported by Tasmota so the easiest path is to FLASH the binary image from https://ota.tasmota.com/tasmota32/release/tasmota32c3.bin on to it using the Tasmota Web based Installer at: https://tasmota.github.io/install/

Remember to press and HOLD the bott button when plugging in the cable so the USB serial port can be seen. Also remember to erase device first and load tasmota32c3.factory.bin before loaded the above binary and check wiith the LOG & CONSOLE option and RESET that it has booted OK.

Then ensure the IP address of 192.168.1.156 is reserved for it by the router and set up MQTT (Configure > MQTT) and rename it TasmotaESP32C3156 using the menus (Configure > Other > Device Name & Friendly Name) the device will reset itself after each setting change and you can use the WebInstaller to check its logs.

You are now ready to make it a MQTT connected Smart Home sensor!

Here are a few screen shots from the Linux Mint 22 laptop during the flashing process...