Using google translate I think you are asking how I’m powering it.
I bought a cheap micro usb connector and wired that up and then just power it off a 6 port usb power brick I have near the camera.
Using google translate I think you are asking how I’m powering it.
I bought a cheap micro usb connector and wired that up and then just power it off a 6 port usb power brick I have near the camera.
Can it work as a camera and a Bluetooth packets sniffer simultaneously? Has anybody tried something like that?
Yes, I had problems with esphome 1.14 though. Still on 1.13.6.
I have 3 miflora plant sensors all listened by esp32_ble_tracker.
platform: ESP32
board: esp-wrover-kit
OK, but i am talking about ESP32-Cam exactly. Can this board do 2 jobs at the same time? Have you tried?
Have you?
I can’t see why not, I’ll try mine sometime.
OK. So, how could i make it work? What would be the config?
The cam code is posted in this thread and in the esp docs. Then add the ble code, again it is on the esphome.io site.
As far as I can tell, you cannot run the BLE and camera components simultaneously. The ESP32 shares its antenna between wifi and bluetooth, and this can cause all kinds of problems with connectivity. If you want to track BLE devices, you’re likely going to need a dedicated ESP32 (not the camera variant) to do it.
I tried uploading code to have BLE and camera functionality running at the same time and my device won’t connect to the network any more. I don’t have the FTDI hooked up to see the logs, but it failed this basic test.
Thanks for trying.
And also just so you know, it can’t be used to track phones for presence detection. At least it doesn’t work with mine. To be fair the docs clearly say something (at the same time, both vague and specific) about it not working with all devices.
I think the problem with that is that phones don’t all do ble. There are Android apps for that though.
I’m pretty sure my phone (LG G6) has BLE
I’ve done more testing, and found both image quality, reliability and responsiveness are much better with the ESP-WHO demo from the IDF.
I will do further testing…
I have one of these ESP32cam and got it working locally on HA.
I have a Nabu Casa cloud service subscription.
When I try to view the cam on a mobile phone (android app) I get - picture card not supported yet.
Can you view the esp32cam remotely?
How??
Thanks…
Just to chip in, i managed to flash it like this:
edit: I gave up on trying to flash directly through HA and was doing trials on the pc until i figured out the above so, it might also work with the above combination of things hooked up on Hassio, didnt try it out.
Hey, just wondering if you ever fixed this issue. I’m seeing the exact same issue with by esp32 cam, it works perfectly fine on 3.3V, but as soon as I switch to 5V, the same sketch will not work.
Serial output is garbage, lamp is flashing. I even loaded an empty sketch so I don’t think the Wifi startup is the issue.
So I (was slightly surprised that I) managed to get my ESP32-cam flashed with a FT232RL FTDI TTL Serial Adapter using only hassio / rasp pi 4 and the cam appears to be fully integrated and working, along with OTA.
I loosely followed Harry’s wiring. But the thing is I was basically getting a bit trigger happy with what I was trying (and umm have had a few drinks - don’t judge!) , and so can’t remember exact steps.
I do recall (update: ignore this, see my edit at bottom)
So while this is ‘kind of’ but ‘not particulary’ useful, I do actually need to do a second one, so hopefully I can report back with specifics soonish.
esphome:
name: esp32cam_1
platform: ESP32
board: esp32dev
wifi:
ssid: "XXXXXXXX"
password: "XXXXXXXX"
# Enable logging
logger:
# Enable Home Assistant API
api:
ota:
# esp32_ble_tracker:
# scan_interval: 20s
# ESP32-CAM
esp32_camera:
name: esp33_cam1
external_clock:
pin: GPIO0
frequency: 20MHz
i2c_pins:
sda: GPIO26
scl: GPIO27
data_pins: [GPIO5, GPIO18, GPIO19, GPIO21, GPIO36, GPIO39, GPIO34, GPIO35]
vsync_pin: GPIO25
href_pin: GPIO23
pixel_clock_pin: GPIO22
power_down_pin: GPIO32
Edit: geez I even named it esp33!! Glug glug…
Edit 2 (next day):
Got the second one flashed and working via FT232RL FTDI with less but still a bit of a hassle.
Main issue was the initial serial flash either “failing to connect” or “A fatal error occurred: Timed out waiting for packet content”. I took a few notes and can provide if anyone needs. I mainly just kept switching raspberry pi usb ports (which of course also powercycles adapter) and kept trying. Ignore my comments about wiring/voltage in first attempt - just use the wiring in the pic Krash attached a few posts above. The rest of the workflow (wiring aside) was basically as in the intial writeup.
Ah those late-night drunk home automation sessions
I’m eagerly waiting on my FTDI adapter. Bought the cam thinking it was already with usb…
the quality looks pretty decent I must say
So the point of this post was what? We already know esp32 cam works!