schluggi / aiosense Goto Github PK

Category

• Hardware / PCB
• Software / ESPHome

Year of the Voice Chapter 4 introduces wakeonword. It would be great to take advantage of this with the INMP441 microphone in this project.
...

I have an INMP441 connected to a C3 Mini.

This is what I have so far as config as a starting point. Everything looks reasonable to my eyes, but I haven't been able to get this working yet.

i2s_audio:
  id: i2s_in
  # i2s_lrclk_pin: GPIO5  # WS pin D1 Mini
  # i2s_bclk_pin: GPIO18  # SCK pin D1 Mini
  i2s_lrclk_pin: A5  # WS pin C3 Mini
  i2s_bclk_pin: A1  # SCK pin C3 Mini

microphone:
  - platform: i2s_audio
    i2s_din_pin: A0 # SD pin
    adc_type: external
    pdm: false
    id: mic_i2s
    i2s_audio_id: i2s_in

voice_assistant:
  microphone: mic_i2s
  on_start:
    - light.turn_on:
        id: led
        blue: 100%
        red: 0%
        green: 0%
        effect: none
  on_end:
    - delay: 1s
    - light.turn_off: led
  on_error:
    - light.turn_on:
        id: led
        blue: 0%
        red: 100%
        green: 0%
        effect: none
    - delay: 1s
    - light.turn_off: led

• [* ] missing something the docs

Would love to see some further docs re;

• A BOM. Could simply be a page that links to recommended parts on DigiKey and Mouser perhaps. This could help with confidence for some people.
• Some instruction / imagery that represents what a populated PCB looks like. This also helps to confirm visually that you've soldered your board correctly.
• A guide on how to test your board is soldered correctly with a multimeter? I'm not sure if this step is necessary given the simplicity of the PCB.

Also, i wanted to ask about PIR sensors and dirty power. I get a lot of false positives with my Panasonic PIR that I intend to use on this project - and read that its often a good idea to do something to avoid this. I wasn't sure if this is something that's covered in this project yet or not (or even if its required..).

Finally, THANK YOU for this! I can replace my hobbled together sensor with a decent PCB, finally. :0

Category

• Hardware / PCB
• Software / ESPHome

Whats your idea?
I want to order TO-5 3-pin socket but the shipping is extremely expensive. I tried to look for it in aliexpress, but without luck. Can you please help out?

For EKMC1603111 i managed to find https://www.aliexpress.com/item/1005003203976549.html?spm=a2g0o.cart.0.0.7d1f38dapwtcSv&mp=1 but I can't verify it is reliable yet

Category

• Hardware / PCB
• Software / ESPHome

Whats your idea?

Now that i2s microphones are supported (starting 2023.5) and the new assist functionality that comes with it, this project became even more awesome! But it ia missing one thing - the ability to hear the response. Can you add support for a speaker as well?
...

I guys, I really want to help on this project !
Is there any discord server available for the community ?

As described here: https://esphome.github.io/bluetooth-proxies/

Category

• [ x ] Hardware / PCB
• [ x ] Software / ESPHome

Whats your idea?
I played around with these small and inexpensive OLED Displays (https://esphome.io/components/display/ssd1306) and thought they might be a great addition to AIOSense. I think it would be great to see some of the values of the sensors directly on the AIO Sense without having to set up extra devices with screens.

Some things you could display on the display

• Temperature, Humidity, Pressure,
• Voice Assistant Answers for deaf people
• Notifications from Homeassistant
• Weather
• RSS Feeds (Scrolling text)
• Occupancy status
• House Alarm status (Armed or not armed)

Here is a Picture of the screen showing Sensor Values from ESP Home

I know space is tight on the board. Maybe we can squeeze it onto the IO extensions and release an additional case Verison that can handle the screen on the bottom. That way we don't have to make the PCB bigger.

This is the test code for the display i used:

font:
  # gfonts://family[@weight]
  - file: "gfonts://Roboto"
    id: roboto
    size: 12
display:
  - platform: ssd1306_i2c
    model: "SSD1306 128x64"
    reset_pin: D0
    address: 0x3C
    lambda: |-
      // %% - literal % sign
      it.printf(0, 0, id(roboto), "Temperature: %.1f°C", id(temperature).state);
      it.printf(0, 15, id(roboto), "Humidity: %.1f%%", id(humidity).state);
      it.printf(0, 30, id(roboto), "Pressure: %.1fhPa", id(pressure).state);

The Sensor code also needs to be modified to have an id
Example for the BME280

sensor:
  - platform: bme280
    id: bme280_sensor
    address: "${bmex80_address}"
    update_interval: "${bmex80_update_interval}"
    temperature:
      name: "Temperature"
      id: temperature
      filters:
        - offset: ${temperature_offset}
        - lambda: "return x + id(temperature_offset_ui).state;"
    humidity:
      name: "Humidity"
      id: humidity
      filters:
        - offset: ${humidity_offset}
        - lambda: "return x + id(humidity_offset_ui).state;"
    pressure:
      name: "Pressure"
      id: pressure
      filters:
        - offset: ${pressure_offset}
        - lambda: "return x + id(pressure_offset_ui).state;"

Categories:

• HW: Case
• Mounting/Installation technique or method

Description:
I want to submit the installation technique i used to bring AIOsense devices to my household because i think it blends in very good with the surroundings.

Method:
1. I took the .stl file for the AIOsense stand and created an easy M3 Mount out of it. The advantage of this is that it is usable with typical M3 camera statives and other M3 mounting rigs! For example, i used this aluminum wall mounting rig for security cameras:

(source: https://www.amazon.de/dp/B0B5Y4Z7KY?psc=1&ref=ppx_yo2ov_dt_b_product_details)

You can find the M3 Mount i designed and used together with some imagery showing an example installation from my home in the attached .zip file!

2. I also thought of a method to install AIOsense devices in a way that hides the cables neccessary for the voltage supply of the device. The final Installation (also using the M3 mount from 1.) looks like this:

This is what you need:

• XH-2A port and XH-2Y plug with crimp equipment (example: https://www.amazon.de/Crimpwerkzeug-Set-Dechengbao-Dupont-Ratschen-Crimpzangen-Set-Steckern/dp/B09SWXF9Q6/ref=sr_1_29_sspa?keywords=XH+plug&qid=1695031004&sr=8-29-spons&sp_csd=d2lkZ2V0TmFtZT1zcF9tdGY&psc=1
• some white wire with dc positive and negative (example: https://www.amazon.de/gp/product/B081QLJHX5/ref=ewc_pr_img_5?smid=A18X01B3A742H7&psc=1)
• a PCB (example: https://www.amazon.de/Lochrasterplatte-Leiterplatte-Lochrasterplatine-Leiterplatten-Prototyping/dp/B08YXKRJY1/ref=sr_1_6?crid=28MDC8YAS3TG9&keywords=lochrasterplatte&qid=1695031078&sprefix=lochrast%2Caps%2C90&sr=8-6
• A small DCDC dropdown voltage regulator (example: https://www.amazon.de/gp/product/B0BN1N88F6/ref=ox_sc_act_title_6?smid=A1A7E5ILEFA1R3&psc=1)
• copper tape, 6mm wide (example: https://www.amazon.de/dp/B09C1WPMZK?psc=1&ref=ppx_yo2ov_dt_b_product_details)
• mounting tape (example: https://www.amazon.de/tesa-Tesa-Schaumstoff-Montageband-5X18-55714-0000-03/dp/B07F46SMV6/ref=sr_1_24?crid=LV50459VL50W&keywords=tesa+schaumstoff+klebeband&qid=1695033240&sprefix=tesa+schaum%2Caps%2C89&sr=8-24)
• some masking tape (example: https://www.amazon.de/tesa-Malerband-einfache-Malerarbeiten-50mm/dp/B0014EFTWK/ref=sr_1_6?keywords=kreppband&qid=1695031487&sr=8-6&th=1)
• You also need stuff to solder. Addtitionally, depending if the coppertape you use has an insulating adhesive (like the one i used and linked), you may need to solder the coppertape also!

1. You need to add the DCDC dropdown converters to your AIOsense. Glue it on the AIOsence PCB using the mounting tape. The general Idea is to use an 230v AC to 12v/24v DC converter from any smart home enabled LED lamp you want to install on the ceiling as the power supply for the AIOsense later on. This requires you to permanently power the ACDC powersupply of the LED you want to use, otherwise AIOsense would loose its powersource! Do not forget to set the DCDC converter to 5v output before glueing it into the AIOsense!!!
2. Solder the cable with a XH-2Y plug crimped to the 5v DCDC converter (i cut the cables to about 30cm but 20cm should be sufficient too). Since the case has no hole in it to fit the plug, you need to put the cable through one of the ventilation holes BEFORE soldering it to the 5v converter! Depending on components, the AIOsense may look something like this:

3. print the coppertape connectorbox and cut the pcb into pieces (about 18mm x 10mm, doesn't have to be perfect) that fit into the connectorbox. glue coppertape around the two ends of the pcb pieces and solder the XH-2A port to it. The poles of the port have to contact the copper tape.

4. glue the finished pcb's to the wall/ceiling/etc. close to where you want to install the AIOsense and another pcb where you put your voltagesource/LED ceilinglight.
5. connect the two pcb's electrically using the coppertape (watch out that you get the positive/negative polarity right!!!). depending on your coppertape, you may need to solder a bit! Thest the electrical connections afterwards! (i used a 12v acdc converter and an rgb led strip i had lying around to test if everything worked)
6. tape some masking tape above the coppertape wires (for physical protection, and you can color it using the exact same color from your wall/ceiling (for a mostly invisible installation). Also, you can put wallpaper over it later for a completely invisible installation! If you followed these steps corectly, your installation (befor coloring or putting wallpaper on) should look something like this:

A finished Installation looks like this (well, the lamp construction is not so final yet... ;-)):

More pictures in the attached .zip!

aiosense_ceilingmount.zip

https://github.com/marketplace/actions/yaml-lint

Category

• Hardware / PCB
• Software / ESPHome

Whats your idea?
Hi, I'm a newbie to ESP32 & hardware in general (although I am a professional software dev, so I'm not completely naive).

I'm looking into building something like this, but I have a few unique requirements and I wondered if there was plans for anything similar with this project.

• Thread support, as far as I see, there is an ESP32 board with Thread incoming. I see that the FP2 went to wifi (I believe that the FP1 was Zigbee IIRC) and Aqara explained this as being because Zigbee didn't have the bandwidth for their sensor. I wondered if this device could realistically be run using Thread or would it have the same bandwidth limitations?
• I'm also considering hard wiring some sensors & using PoE. Can this sensor support the PoE ESP board (obviously the case won't fit this board version...)
• Are there any plans to build a waterproof version of the sensor? I would like to mount one in bathrooms, so having one with something similar to IPX4 would be useful for mounting in bathroom zone 2 or above. Has something like this been considered?

Thanks for creating this exciting project, I'm looking forward to hopefully using it as my springboard into building my own sensors & hardware to power my smart home! 🙇‍♂️

Category

• Hardware / PCB
• Software / ESPHome

Error during config-validation in ESPHome (looks like the "external component" does not get loaded ?!
ESPHome-Version: | v2023.2.4

INFO Reading configuration /config/esphome/esphome-mmwave-schlafzimmer.yaml...
Failed config

sensor.bme680_bsec: [source /config/esphome/esphome-mmwave-schlafzimmer.yaml:141]
  
  Component sensor.bme680_bsec requires component bme680_bsec.
  platform: bme680_bsec
  temperature: 
    name: aiosense-c3-mini Temperature
    sample_rate: lp
    filters: 
      - median
  pressure: 
    name: aiosense-c3-mini Pressure
    sample_rate: lp
    filters: 
      - median
  humidity: 
    name: aiosense-c3-mini Humidity
    sample_rate: lp
    filters: 
      - median
  iaq: 
    name: aiosense-c3-mini IAQ
    id: iaq
    filters: 
      - median
  co2_equivalent: 
    name: aiosense-c3-mini CO2 Equivalent
    filters: 
      - median
  breath_voc_equivalent: 
    name: aiosense-c3-mini Breath VOC Equivalent
    filters: 
      - median
text_sensor.bme680_bsec: [source /config/esphome/esphome-mmwave-schlafzimmer.yaml:172]
  
  Component text_sensor.bme680_bsec requires component bme680_bsec.
  platform: bme680_bsec
  iaq_accuracy: 
    name: aiosense-c3-mini IAQ Accuracy

Category

• Hardware / PCB
• Software / ESPHome

What would you like to improve?
ESPHome has an package feature to easily import external packages. I'll create one for each ESP to cleanup the yaml files.

On the D1 mini the led is controlled by D4. At the moment this is also the pin for the motion sensor.

Category

• Hardware / PCB
• [ X] Software / ESPHome

Version of ESPHome / AIOsense
...

Describe the bug

it wont compile with s2 mini or c3 mini

INFO ESPHome 2023.7.0
INFO Reading configuration /config/esphome/s2-all.yaml...
Failed config

switch.template: [source /config/esphome/.esphome/packages/f7a0b76d/esphome/packages/sensors/sen0395.yaml:17]
  platform: template
  name: mmWave Sensor
  id: mmwave_sensor
  entity_category: config
  optimistic: True
  
  The restore_state option has been removed in 2023.7.0. Use the restore_mode option instead.
  restore_state: True
  assumed_state: True
  turn_on_action: 
    - uart.write: sensorStart
    - delay: 1s
  turn_off_action: 
    - uart.write: sensorStop
    - delay: 1s
switch.template: [source /config/esphome/.esphome/packages/f7a0b76d/esphome/packages/sensors/sen0395.yaml:31]
  platform: template
  name: mmWave LED
  id: mmwave_led
  entity_category: config
  optimistic: True
  
  The restore_state option has been removed in 2023.7.0. Use the restore_mode option instead.
  restore_state: True
  assumed_state: True
  turn_on_action: 
    - switch.turn_off: mmwave_sensor
    - delay: 1s
    - uart.write: setLedMode 1 0
    - delay: 1s
    - uart.write: saveConfig
    - delay: 3s
    - switch.turn_on: mmwave_sensor
  turn_off_action: 
    - switch.turn_off: mmwave_sensor
    - delay: 1s
    - uart.write: setLedMode 1 1
    - delay: 1s
    - uart.write: saveConfig
    - delay: 3s
    - switch.turn_on: mmwave_sensor

Category

• Hardware / PCB
• Software / ESPHome

Version of ESPHome / AIOsense
ESPHome version 2023.7.0
Project Schluggi.AIOsense version 2.0.0

AIOsense Configuration
Lolin ESP32-C3 Mini
BME 680
BH1750
LD2410 mmWave
PIR
PCB V2.0-RC4 02/23

Describe the bug
Relates to PR #45.

Flashed the CPU with the appropriate config mods to my esp32-c3-mini. See config below:

substitutions:
  name: "aio-garage"  # lowercase only, have to be unique
  friendly_name: "aio-garage"  # device name and entity prefix
  version: "2.0.0"  # your AIOsense version

  bh1750_update_interval: 5s

  bmex80_address: "0x77"  # for some modules you have to change it to 0x77
  # bmex80_offset_humidity: "0"
  # bmex80_offset_temperature: "0"
  # bmex80_update_interval: 30s

  # bme680_bsec_sample_rate: lp # lp -> 3s, ulp ->5min
  # bme680_bsec_temperature_offset: "0"

  ld2410_max_distance_move: 4.5m
  ld2410_max_distance_still: 4.5m
  ld2410_timeout: 5s

  pir_delayed_off: 1s
  pir_delayed_on: 0s

packages:
  remote_package:
    url: https://github.com/schluggi/AIOsense
    ref: main
    refresh: 1d
    files:
      - esphome/packages/config/base.yaml

      # --- select your board ---
      - esphome/packages/config/esp32-c3-mini.yaml
      # - esphome/packages/config/esp32-d1-mini.yaml
      # - esphome/packages/config/esp32-s2-mini.yaml
      # - esphome/packages/config/esp8266-d1-mini.yaml

      # --- select your sensors ---
      - esphome/packages/sensors/bh1750.yaml
      # - esphome/packages/sensors/buzzer.yaml  # AIOsense >= 2.1.x only
      # - esphome/packages/sensors/bme280.yaml  # enable for bme280
      - esphome/packages/sensors/bme680.yaml  # disable for bme280
      # - esphome/packages/sensors/bme680_bsec.yaml  # does not work yet
      - esphome/packages/sensors/occupancy.yaml  # only if pir & mmWave are on
      - esphome/packages/sensors/pir.yaml
      - esphome/packages/sensors/rgb_led.yaml  # esp32-c3-mini only
      # - esphome/packages/sensors/led.yaml  # d1-mini only

      # --- select your radar sensor ---
      - esphome/packages/sensors/ld2410.yaml
      #  - esphome/packages/sensors/sen0395.yaml


# Enable Home Assistant API
api:
  encryption:
    key: !secret aio_garage_api

ota:
  password: !secret aio_garage_ota

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  # manual_ip:
  #   static_ip: 192.168.1.111
  #   subnet: 255.255.255.0
  #   gateway: 192.168.1.1

# bluetooth_proxy:

Upload was successful. All sensors worked except LD2410 as shown below with the "Unknown" status indicators:

Recommended Solution

Change the following uart config in packages/sensor/ld2410.yaml from this:

uart:
  # switching rx & tx is not a mistake but necessary
  tx_pin: "${uart_rx_pin}"
  rx_pin: "${uart_tx_pin}"
  baud_rate: 256000
  parity: NONE
  stop_bits: 1

To this:

uart:
  # enable for all cpu's but esp32-c3-mini
  # rx_pin: "${uart_tx_pin}"
  # tx_pin: "${uart_rx_pin}"
  # enable for esp32-c3-mini
  rx_pin: "${uart_rx_pin}"
  tx_pin: "${uart_tx_pin}"
  baud_rate: 256000
  parity: NONE
  stop_bits: 1

Result:

My disclaimer is that I don't have any of the other cpu's so I can not confirm when you must swap the uart pins to enable coms with the LD2410. This does work with the esp32-c3-mini though.

Hi Schluggi,

I suggest to redesign the power input to not use a "Male PIN-Header" but a "wire-to-board-terminal-block" like this one --> WUERTH Terminal-block

At least on the ESP32, the USB port is on the top. I'm not sure if the ESP8266 has it on the bottom, like your 3D model. Since you won't be supporting the 8266 anymore anyway, it would at least be worth considering, because with a terminal block you might have more strain relief

Cheers Flo

I found a low cost mmWave Sensor on Ali Express, https://de.aliexpress.com/item/1005004786874722.html
Datasheet
I haven't tried it yet, but if it works, it might be worth to add pin headers for it, for being able to produce a low cost version of the AIOsense

Category

• [?] Hardware / PCB
• [X ] Software / ESPHome

Version of ESPHome / AIOsense
ESPHome 2023.3.2 / 2.0.0 board

Describe the bug
The esp8266 (D1 Mini) PIR pins are configured incorrectly as reported by esphome, GPIO13 does not have an internal pulldown

Failed config

binary_sensor.gpio: [source /config/esphome/.esphome/packages/6d7fe4d6/esphome/packages/sensors/pir.yaml:6]
  platform: gpio
  name: PIR
  id: motion_pir
  pin: 
    number: GPIO13
    
    Only GPIO16 supports pulldown.
    mode: INPUT_PULLDOWN
  device_class: motion
  filters: 
    - delayed_on: 0s
    - delayed_off: 1s

I managed to fix 2 other small bugs for the esp8266 (D1 Mini), I don't know if i should send a PR.

• ESP8266 does not have a CPU Temp sensor: CappyT@61ed64b
• ESP8266 led is inverted: CappyT@4c86ee1

How can I fix the PIR sensor? I don't know much about electronics, I just know enough about ESPHome

First of all thank you for making this project available, it's exactly what I was looking for.

I got a bit excited and ordered the version 1 pcb without reading the warning, is there somewhere that lists out the things that don't work on v1?

To the point, when testing the EKMC1603111 PIR it's not responding to motion when attached to the v1 pcb. I have 2 test pcbs, one is fully soldered with all components/female headers, the other just the dev board and PIR socket (assuming that's the bare minimum requirements).

If I attach the sensor directly with a nodeMCU or Wemos D1 mini ESP32 it works perfectly, attached to an Olimex POE ISO I have to use a pull down resistor from ground to out. I have still not been able to get the Wemos D1 mini ESP8266 to work, which behaves the same as when connected to the pcb.

Any help would be amazing!

Category

• [v ] Hardware / PCB
• Software / ESPHome

Whats your idea?
...
691210910002 << what is this part used for?
I am trying to build the sensor with these components.

ESP32-C3 mini (PCB)
BME280(PCB)
HLK-LD2410C (PCB)
GY-302-BH1750 (PCB)
im going to skip pir sensor, and i am in middle of ordering other parts. i was wondering what 691210910002 terminal block 2pos is intended for.

Thank you in advance.

Category

• Some docs are wrong or outdated
• I miss something the docs

Description
I realized that I forgot to include the LCSC number for the capacitor parts. While searching for the missing components on the LCSC website, I noticed that there are various versions available for this part. As my electronics knowledge is a little rusty, do you have any additional information about this part?

I assume that it is a Multilayer Ceramic Capacitor, but I'm not sure whether it is leaded or non-leaded. Also, what voltage rating should I use? On the LCSC website, I can see that there are several options available for the same capacitance - 50V, 100V, and 250V. Can you advise me on which voltage rating to choose?

I will update the documentation accordingly OF😄

We just bought some AIOsense v2.0-rc2.

They will arrive late January.

Things we have to test:

• mmWave
• PIR
• generic I²C ports
• BME280 (onboard)
• BME680 (onboard)
• onboard power
• IO pins
• CPUs
  • ESP32-C3
  • ESP32-S2
  • ESP32-D1
  • ESP8266-D1
• Modules
  • BME280
  • BME680
  • BH1750

Category

• Hardware / PCB
• Software / ESPHome

What would you like to improve?
I would suggest to use the "own" integrated ESPHome feature for driving the sen0395 sensor so no specific effort is needed to take care on an own integration.

Changelog

Cheers

• BOM
• Better structure
• Badge
• Fix readme link
• Quickstart guide

Category

• Some docs are wrong or outdated
• I miss something the docs

There should be an info that the two resistors R1/R2 must not be populated when using the I²C modules BME280/BME680. I got quite bad readings because I soldered them on the board in the beginning - sometimes no values were entered at all at startup - I had to do several restarts.

Maybe I'm missing something or misinterpreting something - but since I removed the two resistors, everything works fine.

Cheers

Add templates for:

• Bugs
• Feature Requests
• Docs
• Enhancements
• Other / general questions

Category

• Hardware / PCB
• Software / ESPHome

Whats your idea?
...
it seems that in ld2410 yaml, a substitution is declared for
ld2410_max_distance_move: 4.5m
ld2410_max_distance_still: 4.5m
but can not find anywhere it is used for. can i change this value to change the detection range?

Category

• Hardware / PCB
• Software / ESPHome

Whats your idea?
LD2450 seems to be the new kid on the block, its a new mmWave sensor with the ability to track up to 3 people at once. Screek just released a new product the 2A which utilizes this new sensor and is using esphome with it.

#22 (reply in thread)

Category

• Hardware / PCB
• Software / ESPHome

v2 - RC4
...

It looks like that the PIR does not fix together with SEN0395 (at least when mounted via "socket")
Did you guys managed to get this together?
...

Both resistors and the capacitor are only for the BME chips. These chips can only soldered by using a heatgun or a heating plate.
So everyone who hasn't access to this kind of equipment will use a BME module instead and does not need to solder these parts.

So there is no need to make this parts consumer friendly (alias THT).

Category

• Hardware / PCB
• Software / ESPHome

Version of ESPHome / AIOsense
ESPHome: 2023.3.2
AIOsense: latest

Describe the bug
I get an error with the bme680 initialization. It wants me to append "_m" to several variables in the cpp file. I searched to find this error but couldn't come up with anything. I apologize if there is already a solution. See the link for my logs.

logs_aio-utility-room_run.txt

Hello,

This project looks great, thanks for sharing!
I'm really interested in it but I was wondering if it is possible to simplify the pcb board, let me explain. I'm quite unexperienced in electronics and I found that soldering the BME280/680 sensor might be quite challenging, just soldering the pads on the bare sensor.

This might be a lot of work but, could it be possible to make a version using standard sensors, the same way the BH1750 is used? Or at least point me in the right direction to do it myself.

Thank you

I'm new to this project, but I believe the labels need to be corrected for J1 on v2.0 (maybe v1 as well, I didn't check).

Category

• Hardware / PCB
• Software / ESPHome

Describe the bug
Apologies this doesn't appear straightforward!

When booting the board with a Panasonic PIR attached (EKMC1603111) the reading for Motion in Home Assistant is constantly Detected. In ESPHome logs the sensor appears unresponsive.

Initially when setting up the board everything was fine for about a week, then the behaviour started so I replaced the PIR which fixed the issue; around a week later the same issue occurred :-( I question whether this was actually triggered by an outlet change.

The testing setup I now have:

1. AIOSense board setup with all components, including resistors on a ESP32 Lolin C3 Mini - reports Detected
2. AIOSense board setup with only the PIR, no resistors on an ESP32 D1 Mini - works, though only running for a couple of days
3. custom board with all components, no resistors on an ESP8266 D1 Mini - works, has been running for a while and hasn't faced this issue yet
4. breadboard mimicking the schematic with all components, no resistors on a ESP32 Lolin C3 Mini - works, though only running for a couple of days

If I switch the ESP32 boards over on 1 and 2 then both report detected, switching them back and it appears board 2 has now broken 😮‍💨 Update changing power source and board 2 is working again, board 1 started working again after 7+ days of detected no change to PSU.

In the above scenario 1-3 are on a shared extension brick whilst 4 is on a separate outlet, the reason I mention is that the breadboard also displayed this behaviour but only on the shared extension brick and not when connected to my laptop or the separate outlet.

If anyone can think of anything, wants me to try anything then by all means let me know.

Category

• [*] Hardware / PCB

Version of ESPHome / AIOsense
2.0 RC4

Describe the bug
The PCB sensor pin orientation forces the sensor boards to be mounted upside down. This means the sensor chips themselves end up facing down / toward the PCB - rather than up. Secondarily, it means the pins on the sensor boards need to be soldered in an uncommon way (upside down..) which in turn means soldering is a bit more difficult.

This runs true with the sensor boards linked in the documentation.

Would it make more sense to have these pin holes swapped around?

Image above represents the same sensor board with pins soldered each way to help illustrate the problem. The top sensor board is how you would normally solder the pins, however - this causes the board to extend outside of the main PCB. The bottom sensor board is pinned in reverse in order to have it oriented correctly.

• for voltage
• for additional sensors

• Hint for PCBWay
• Tested ESP-Hardware

Category

• Hardware / PCB
• Software / ESPHome

What would you like to improve?
Include a similar LED for the ESP32 D1 Mini board as is included on the Lolin C3 Mini, useful if trying to identify which board is in front of you and whether the boarding is booting.

There is a new version of LD2410 called LD2410C link: https://de.aliexpress.com/item/1005005047841163.html

It has 0.1" pins so it could be easier to mount/solder. Can you make make PCB for that?

Category

• Software / ESPHome

Whats your idea?
Adding a feature that allows to exclude specific regions in the fov of the mmwave sensor to be prohibited from occupation detection.

Example:
If AIOsense is mounted in the bedroom, it would be useful to remove the bed from occupation detection, so the light in the room will turn off if i lie in bed.
With zones, it could turn on the bedside lamp and turn off the ceiling lamp.

The aquara FP2 sensor for example can do something like that, but a little more advanced.

Category

• [*] Hardware / PCB

Version of ESPHome / AIOsense
2.0 RC-4

Describe the bug
The PIR sensor interferes with the mmWave sensor. Accordingly - the PIR doesn't fully seat into the socket.

The socket is fully seated, it's designed to sit a couple of mm above the board, as per the spec here. Note this is the spec'd TO-5 socket from the documentation.

The PIR sensor itself can't be fully seated due to its pin length (you could of course cut these down if required..) however, in its default state the PIR sensor interferes with the soldered pins on the DFRobot mmWave sensor.

Secondarily, the current printable case doesn't work at all with this configuration because its cutout sits far too high to even seat into the socket at all. I assume the case would have an update to resolve this we haven't seen yet.

You'd either need a TO-5 socket that sits higher, or would need to adjust the position of the PIR sensor to resolve this.

ESPHome does not support I²S input yet but to be prepared for the future, this would be nice.

esphome/feature-requests#1254

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

I am currently having issues with the mmwave GPIO pin on the ESP32-S2. Sometimes when the pin i high, it isn't detected by the ESP. I checked the connection, which seems to be okay. Maybe the issue is the internal pulldown.

Anyways I was searching for other solutions. I found out that the mmwave sensor is also sending the value over UART so i tried to write a custom binary sensor component for that, but haven't gotten far due to my horrible C skills.

But i now also found that someone else might have already done the work: esphome/esphome#4203

We could evaluate this solution and maybe save a gpio pin, which can then be used for something else, like audio output.