rubin110

# ESPHome config to drive a simple stepper as part of a cat / pet feeder.
# The 3D project I printed is:
# Pet Feeder Treat Dispenser Web App Enabled by n9jcv
# https://www.printables.com/model/142993-pet-feeder-treat-dispenser-web-app-enabled
# device_base includes your standard esp config, logger, api, ota, web_server, wifi,
# and a few sensors to provide HA with more info.

substitutions:
  device_name: "cat-feeder-1"
  friendly_name: "Cat Feeder 1"

rubin110

# https://style.oversubstance.net/2021/08/diy-use-an-ikea-vindriktning-air-quality-sensor-in-home-assistant-with-esphome/
# https://github.com/Hypfer/esp8266-vindriktning-particle-sensor

logger:
  baud_rate: 0

i2c:
  sda: 4
  scl: 5
  scan: True

rubin110

Keybase proof

I hereby claim:

• I am rubin110 on github.
• I am rubin110 (https://keybase.io/rubin110) on keybase.
• I have a public key ASBIfg3P57FLQM6ACVUiw6JhV2PKY4w8NMDTDvz-__iBGQo

To claim this, I am signing this object:

rubin110

Generate AQI from PM2.5 on the great Apollo Automation AIR-1!
# https://apolloautomation.com/products/air-1
# https://wiki.apolloautomation.com/books/air-1
# https://github.com/ApolloAutomation/AIR-1

# This can also be applied to basically any other PM2.5 sensor.

# ESPHome doesn't provide a simple means to generate an AQI value from a PM2.5 sensor.
# AQI is subjective based on where you live in the world, so this is something you need
# to put together by hand. This can be done within ESPHome (as shown here) or a template

rubin110

TEST

rubin110

substitutions:
  name: sunroom-atom-echo
  friendly_name: "Sunroom Atom Echo"
  micro_wake_word_model: okay_nabu  # alexa, hey_jarvis, hey_mycroft are also supported

esphome:
  name: ${name}
  name_add_mac_suffix: true
  friendly_name: ${friendly_name}
  min_version: 2025.2.0

rubin110

2025-02-28 21:53:56.503871737  [INFO] Preparing new go2rtc config...
2025-02-28 21:53:56.503955305  [INFO] Preparing Frigate...
2025-02-28 21:53:56.504352560  [INFO] Starting NGINX...
2025-02-28 21:53:56.507807391  [INFO] No TLS certificate found. Generating a self signed certificate...
2025-02-28 21:53:56.541504001  [INFO] Starting Frigate...
2025-02-28 21:53:56.818154407  [INFO] Starting go2rtc...
2025-02-28 21:53:56.891509411  21:53:56.891 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2025-02-28 21:53:56.891512158  21:53:56.891 INF config path=/dev/shm/go2rtc.yaml
2025-02-28 21:53:56.891854714  21:53:56.891 INF [api] listen addr=:1984
2025-02-28 21:53:56.891856392  21:53:56.891 INF [rtsp] listen addr=:8554

rubin110

2025-03-01 17:34:33.471254698  [INFO] Preparing new go2rtc config...
2025-03-01 17:34:33.471451390  [INFO] Preparing Frigate...
2025-03-01 17:34:33.471847126  [INFO] Starting NGINX...
2025-03-01 17:34:33.475263994  [INFO] No TLS certificate found. Generating a self signed certificate...
2025-03-01 17:34:33.507017360  [INFO] Starting Frigate...
2025-03-01 17:34:33.749940309  [INFO] Starting go2rtc...
2025-03-01 17:34:33.821603907  17:34:33.821 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2025-03-01 17:34:33.821606595  17:34:33.821 INF config path=/dev/shm/go2rtc.yaml
2025-03-01 17:34:33.822116351  17:34:33.822 INF [api] listen addr=:1984
2025-03-01 17:34:33.822117987  17:34:33.822 INF [rtsp] listen addr=:8554

rubin110

---
#
# HA Default Red
#

ha_default_red:
    modes:
        dark:
            primary-color: "#ff0000"
            accent-color: "#e34040"

rubin110

# Hey! This is the docker-compose file for DeepHarbor.
# It defines all the services that make up the DeepHarbor application,
# including the database, main application service, dispatcher,
# business logic services, worker services, and the gateway service.

# Are you having weirdness with your containers? Try running:
# docker-compose down -v
# to remove all containers and volumes, then start fresh with:
# docker-compose up --build -d
# Also, if you _really_ want to start fresh, run: