xarmoda
(Antonio Von Carmo)
July 12, 2023, 3:44am
1
Hi,
I’m having some issues getting a LTR390-UV sensor working with a XIAO ESP32S3 card.
The problem occurs after I upload a configuration yaml to enable the sensor (see below). The device drops on and off the API and I am unable to view logs, see whats up.
i2c:
sda: GPIO5
scl: GPIO6
scan: true
sensor:
- platform: ltr390
uv_index:
name: "UV Index"
id: uv_sensor_uv_index
light:
name: "Ambient Light"
id: uv_sensor_ambient_light
gain: "X3"
resolution: 18
window_correction_factor: 1.0
update_interval: 1s
i’ve tried setting a bus id (ESPs have two). no banana.
any thoughts?
nickrout
(Nick Rout)
July 15, 2023, 11:43pm
2
In the diagram you posted the gpios are sda<->6 scl<->7
In your code you have sda<->5 scl<->6
xarmoda
(Antonio Von Carmo)
July 16, 2023, 1:03am
3
yes, apologies, i had seen that error. this is what i have currently:
i2c:
id: bus_a
sda: GPIO6
scl: GPIO7
scan: true
sensor:
- platform: ltr390
uv:
name: "UV Index"
light:
name: "Light"
i’m thinking it might be because i’m not using the ‘absolute’ board type in my YAML, just the generic one. there is a work around i haven’t implemented.
board: esp32-s3-devkitc-1
either-way, its dropping off the API when i try to upload a new config.
this issue:
(Novice with HA, ESPHome)
I have just received a Seeed Xiao ESP32S3 Sense board and I’m trying to use ESPHome to access it from my HA running with the latest updates on a Rpi4.
When I edit the .yaml file with the:
esp32:
board: seeed_xiao_esp32s3
I get a red underline. Following that link to the list of boards, I can see both that and the ESP32C3 options. The seeed_xiao_esp32c3 name is recognised but the seeed_xiao_esp32s3 name is not.
What am I missing here?
(BTW I got here because I fi…
xarmoda
(Antonio Von Carmo)
July 17, 2023, 10:34pm
4
The issue is the lack of support in ESPHome with the XIAO ESP32S3. I’m rebuilding with an ESP32ThingPlus.