I have already pointed you to this page, but it recommends the idf framework for the S3
Try that.
Also if that is your complete log in the first part of your post, where does the last part with the error come from?
2 Likes
Thanks, I’ll take a look at that page again.
The last part of my post is the output when I try to compile the yaml. It fails to compile and program due to an error with the assignment of gpio for the RGB LED.
Clearly something has compiled on it though, otherwise it wouldn’t be running in the first part of the log.
I can get it to compile, but only when I remove the sections that define the gpio pins.
Thought I would put in my vote of sorts here. Just so someone with the right skills knows others are interested.
I’m really looking forward to ESPHome working on the AtomS3. I am hoping the BT5 implementation on it will give better BT signal strength than the plane esp32 boards I have used so far. Hopefully closer to a Raspberry pi 4 with its bluetooth 5 experience.
2 Likes
I just got my s3 devices and was able to configure the bluetooth proxy and plug in illuminance sensor using this config. I haven’t tried to setup the light and onboard button yet. Hope this helps someone else along the way…
#M5 AtomS3
esphome:
name: "esp-device-name"
friendly_name: Device Room Name
esp32:
board: esp32-s3-devkitc-1
framework:
type: arduino
# Enable logging
logger:
# Enable Home Assistant API
api:
encryption:
key: "y7lp0eZgbOp+M+PwPeFq3a17VLDVJNibjp/jn3Y4rVc="
# Over the Air Updates
ota:
password: !secret ota_password
# Wifi Setup
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Bluetooth Proxy
esp32_ble_tracker:
scan_parameters:
interval: 1100ms
window: 1100ms
bluetooth_proxy:
active: true
# Illuminance Sensor
i2c:
- id: bus_a
sda: 2
scl: 1
scan: true
sensor:
- platform: bh1750
name: "${friendly_name} Illuminance"
address: 0x23
update_interval: 5s
4 Likes
I managed to get my AtomS3 devices working with Bluetooth proxy. All good so far. I would say that Bluetooth performance is not as good as some larger esp32 I’ve used. I occasionally see my temperature sensor data become ‘Unavailable’.
I managed to get the onboard button working.
I did quite a bit of investigation on the RGB LED and it seems that fasted is not supported for S3 yet.
1 Like
What other esp32 boards have you tried with better BT signal range?
Thanks.
The ESP32 DEV KIT DOIT or WEMOS D1 Mini boards seem to work a bit better with fewer dropouts.
Thank you for the code. Helped me get going instantly. Airthings Wave+ was detected seconds after the Atom came online. Truly amazing that it was that easy considering that M5stack doesn’t even mention that the AtomS3 Lite even has Bluetooth. Next, I would like to get the LED working if only to know the unit is on. Thinking that it would be nicefeedback to turn the LED Green from HA that way I would know that it is connected and the Airthings Wave+ is up and sitting out data. Thanks -Dave
I was able to get the Atom Lite working on ESPHome with this:
substitutions:
device_name: atomlitedemo
friendly_name: Atom Lite Demo
esphome:
name: ${device_name}
esp32:
board: m5stack-core-esp32
framework:
type: Arduino
Enable logging
logger:
Enable Home Assistant API
api:
encryption:
key: “xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx”
ota:
password: “xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx”
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: “Atomlitedemo Fallback Hotspot”
password: “xxxxxxxxxxxxxxxxxx”
captive_portal:
Device-specific
light:
- platform: fastled_clockless
chipset: WS2812B
pin: 27
num_leds: 1
rgb_order: GRB
id: status_led
name: ${friendly_name} Light
effects:- random:
- flicker:
- addressable_rainbow:
binary_sensor:
- platform: gpio
pin:
number: 39
inverted: true
name: ${friendly_name} Button
on_press:
then:
- light. Toggle: status_led
Post your yaml properly please.
Here’s a working config for the M5Stack Atom S3 Lite
- Working RGB Leds
- Working IR Led
- Working button
- Working status LED
4 Likes
this post has been very helpful. I ended up with an M5AtomS3U with the usb A connection as that was all i could get in a reasonable amount of shipping time. After countless issues trying to flash any of the yaml code found here i ended up realizing that the web installer wouldnt see past the jtag programmer when using chrome or edge through a windows machine. I ended up having to plug the thing directly into my HAOS server. It worked to program it initially, but apparently it fails to update OTA. so eveytime i make a change i have to bring it back to the server for programming. anyone else had this issue with any of their m5 devices or is this unique to this specific product.
I am tring to use the Atom S3 Lite with a 4 channel relay. I have loaded the above code and that works well, but when trying to include a I2C portion to talk to the relay not allowing me to use GPIO 21 &22. Says GPIO22 is not valid.
Any ideas on how to use the grove Atom 4 channel relay?
Thanks!
I have the same problem. OTA Never Ever works on the Atom S3 Lite. Either timeout, stuck at 4% or 10%, bricks the device completely.
It does NOT reboot into safe mode. It’s totally bricked.
Only option is to plug the device into an USB port of a computer and do esphome run XXX.yaml with local (USB) upload.
It’s so frustrating 
.
Has anyone been able to use a sensor connected to the groove connector? I have a temp sensor I would like to use.
I’m playing around with this at the moment. I want to use a GPIO port as an input for a thin film pressure sensor.
If I succeed, I’ll post the resultant yaml.
I have connected several m5stack sensors to the groove port with i2c
fonske/AtomS3_lite (github.com)
2 Likes
Hi,
With
esp32:
board: esp32-s3-devkitc-1
framework:
type: arduino
It is working but not with
esp-idf
Is there a way to make it working with esp-idf framework? No matter how I try I’m getting the following after successful build
Serial port /dev/ttyACM0
Connecting...
Chip is ESP32-S3 (QFN56) (revision v0.2)
Features: WiFi, BLE, Embedded Flash 8MB (GD)
Crystal is 40MHz
MAC: 24:58:7c:5c:f4:f4
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Auto-detected Flash size: 8MB
Flash will be erased from 0x00010000 to 0x00146fff...
Flash will be erased from 0x00000000 to 0x00005fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x00009000 to 0x0000afff...
Compressed 1270368 bytes to 825150...
Wrote 1270368 bytes (825150 compressed) at 0x00010000 in 8.6 seconds (effective 1185.1 kbit/s)...
Hash of data verified.
Warning: Image file at 0x0 is protected with a hash checksum, so not changing the flash size setting. Use the --flash_size=keep option instead of --flash_size=8MB in order to remove this warning, or use the --dont-append-digest option for the elf2image command in order to generate an image file without a hash checksum
Compressed 20848 bytes to 13064...
Wrote 20848 bytes (13064 compressed) at 0x00000000 in 0.3 seconds (effective 476.8 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 134...
Wrote 3072 bytes (134 compressed) at 0x00008000 in 0.0 seconds (effective 549.6 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 31...
Wrote 8192 bytes (31 compressed) at 0x00009000 in 0.1 seconds (effective 896.1 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting via RTS pin...
INFO Successfully uploaded program.
INFO Starting log output from /dev/ttyACM0 with baud rate 115200
[14:08:13]ESP-ROM:esp32s3-20210327
[14:08:13]Build:Mar 27 2021
[14:08:13]rst:0x7 (TG0WDT_SYS_RST),boot:0x28 (SPI_FAST_FLASH_BOOT)
[14:08:13]Saved PC:0x400454d5
[14:08:13]SPIWP:0xee
[14:08:13]mode:QIO, clock div:1
[14:08:13]load:0x3fce3808,len:0x16c4
[14:08:13]ets_loader.c 78
Thanks
L: