Does anyone, but especially MallocArray, have any experience getting either of the mentioned AirGradient devices to operate as a Bluetooth discoverable device (and having the initial setup and all of the ongoing communication with the device done via BT instead of WiFi)?
If not, is it something that seems not just theoretically possible, but realistically possible, using esphome and yaml files? Would it require extensive development of and flashing of a totally new bin file, or is there any existing esphome yaml code for the esp32-c3 controller, itself, that could be added to my devices that are already running the MA esphome firmware to enable that BT functionality?
I understand that running a Bluetooth service on these devices might strain the limited resources of the controller, but also have read that other things that are not being used might be able to be disabled (like the captive portal for WiFi), thereby freeing up more resources for the BT.
I get that this may seem like a pointless thought exercise to many AG device users who are happy (or need) to use the device via WiFi, but it seems to me that this alternate use case could appeal to some users and I would appreciate it if any voices of experience can speak to the real world feasibility of operating the devices this way.
Extra background info for my use case:
I have been operating one AG One and one OpenAir device for the past 9 months. During that time I have been successfully running both devices using MallocArray’s airgradient_esphome firmware from GitHub, connecting via WiFi to a Home Assistant OS server running on an old Raspberry Pi 3.
Before I originally purchased the devices, I read that the esp32-c3 controller in these devices supported Bluetooth and 2.4GHz WiFi, and I was planning to use only BT as I live in a small apartment where BT covers the entire area. As I have also been running several Switchbot temp / humidity sensors that connect to HA only using BT, I have been happy with that mode of operation and not needing to go through the trouble of configuring the devices to work with WiFi when HA easily detects local Bluetooth discoverable devices.
I use the full_config yaml files from MallocArray, and don’t have any desire to have any kind of automatic updates that would require WiFi. I do not connect my devices to the AG Dashboard, upload my data to OpenAQ (as I prefer to keep my data local) or access my sensors from anywhere other than the local network.
Even though I went through the extra configuration necessary to get my two AG devices working with my WiFi, and they have been working well, I still would be interested in running them as Bluetooth only devices if that were realistically possible.
I searched through the AG forums and only found one previous post that references this idea of BT only use (Outside unit bluetooth), but what looked like an official AG response indicated that they never used the devices that way, even though it would be theoretically possible.