SEN55 Air Quality Sensor with ESPHome and Home Assistant

Поділитися
Вставка
  • Опубліковано 9 січ 2025

КОМЕНТАРІ • 40

  • @juliusgauckler3144
    @juliusgauckler3144 9 місяців тому +2

    Nice integration of the SEN5x.

  • @robertebob
    @robertebob 10 місяців тому +2

    This makes me wonder what kind of reading I'd get while roasting coffee beans indoors.

    • @TechDregs
      @TechDregs  9 місяців тому +1

      Anecdotally, it looks like just making espresso may influence it.

  • @Fmstrat
    @Fmstrat 5 місяців тому +1

    Great video, but where is the wiring diagram/explanation for thr Sen55? Thanks!

    • @Fmstrat
      @Fmstrat 5 місяців тому

      Note: I did find the basics on page 13 of the data sheet, but curious if you did anything unique or used resistors like others have suggested.

    • @TechDregs
      @TechDregs  5 місяців тому

      @@Fmstrat Nothing special. The YAML shows the pins I used for SDA/SCL. The other two pins are just 5V and GND.

    • @Fmstrat
      @Fmstrat 5 місяців тому +1

      @@TechDregs Thank you. Just fired it up on an 8266.

  • @simonsayshomeassistant
    @simonsayshomeassistant 10 місяців тому +2

    Great video mate, just subscribed!

  • @74357175
    @74357175 10 місяців тому +1

    Nice package! Are the PM measurements absolute, at least? It's hard to find VOC measurements that are not relative🙁

    • @TechDregs
      @TechDregs  10 місяців тому

      Yes, PM measurements are in ug/M^3. Micrograms per cubic meter.

  • @miked3655
    @miked3655 9 місяців тому +5

    I liked the video and the project, however I would like to have seen how you mounted the ESP32 module in the case. I printed your case and I see it fits in that defined area, but it isn't secured in any way. Did you glue it in place? Also when you connect the e-paper display up I see it has 4 more pins than the just MOSI and the Clock pin. Do you not need them in this setup? It would be nice to see how you connected this project up.

    • @TechDregs
      @TechDregs  9 місяців тому

      The Xiao is hot glued down to keep it from moving. For the pins, look in the YAML. It tells you what pin everything is wired to.

    • @miked3655
      @miked3655 9 місяців тому +3

      @@TechDregs Thanks for the reply. I was able to find that in the YAML code. I did not check there before posting. Just my opinion here, when I see someone make something no matter what it is, I like to see as much detail as possible. For me I am not looking to critic how someone did something but see how what they did worked for them.

    • @doggyporn
      @doggyporn 7 місяців тому

      @@miked3655 I agree, did you find out where the other 4 pins are connected to the Xiao - says pin 20 and 21?? Cheers

    • @doggyporn
      @doggyporn 7 місяців тому

      @@TechDregs Awesome Project !! From what I see, besides ground and power, these are the connections to XIAO C3
      i2c: For the SEN55
      sda: 6
      scl: 7
      spi: for the Waveshare
      clk_pin: 8
      mosi_pin: 9
      Not sure about these pins? is it 5 and 10 on XIAO going to 20 and 21 on Waveshare
      cs_pin: 20
      dc_pin: 21
      busy_pin:
      number: 5
      reset_pin: 10
      Cheers

  • @neilos2085
    @neilos2085 2 місяці тому

    Hey is there anything you need to do with the fonts etc to get this to work? Im using with an ESP32-S3 but cant seem to get the display to show anything (doesnt look powered on), is that normal?

    • @TechDregs
      @TechDregs  2 місяці тому

      I'd double check your wiring for the display. The fonts should pull from the internet when the YAML builds in ESPHome.

    • @neilos2085
      @neilos2085 2 місяці тому

      @@TechDregs If the Sen55 isnt powered on and displaying, would you expect to see anything on screen (i assume not). Also do you power via 5v or 3.3v?

    • @TechDregs
      @TechDregs  2 місяці тому

      I think I powered it with 3.3v but I don't recall exactly. You should see the static text on the screen even if there's no data coming from the sensors, unless the firmware build fails.

  •  6 місяців тому

    Thank you for your video! I printed the case and everything fits perfectly! The sensor is working fine in ESPHome but I cannot get the 4.2 screen to work. Like yours it is the rev2.2. I used the same yml as yours but the screen remains blank and I get this message in the logs: [E][waveshare_epaper:159]: Timeout while displaying image!
    Do you have any idea of what the issue could be? Does yours still work if you compile with a recent ESPHome?

    • @TechDregs
      @TechDregs  6 місяців тому

      Mine is still working fine. You have the external component set up for the rev2.2 set up? I would perhaps double check the wiring and all the pin configs to make sure everything matches up. FYI, they did just push a breaking change for OTA updates, you now have to add a - platform: esphome above the password. See: esphome.io/components/ota/esphome.html

    •  6 місяців тому

      @@TechDregs Thanks...It finally works after hours of searching and debugging 🙄As always the solution was very simple... I connected the screen pwr to 5V! When changing to 3.3V it worked immediately. I thought it would work with 5V as it is stated that it can take from 3.3 to 5.
      Thanks again for your work, the case looks very nice and I love the final result 👌😛

  • @neilos2085
    @neilos2085 2 місяці тому

    With the time being on this, how often do you update the screen?

    • @TechDregs
      @TechDregs  2 місяці тому

      I'm only updating the screen every 15min. The time is just for a reference because it's nice to know when the last readings were.

    • @ghabcorr5686
      @ghabcorr5686 2 дні тому

      @@TechDregs Is there a limitation with this components for the time ? can't you read every second or something ?

    • @TechDregs
      @TechDregs  2 дні тому

      @@ghabcorr5686 Yeah, e-ink screens don't refresh that fast. It takes a second or two every time you want to update the screen.

  • @darknessblades
    @darknessblades 3 місяці тому

    I recently found something that might be a even better solution than a separate ESP32 and a e-ink display
    A M5stack M5paper
    or
    A Lilygo Ttgo T5S
    these look to be all-in-one solutions with a E-ink display
    Would something like this work with the current firmware

    • @TechDregs
      @TechDregs  3 місяці тому

      You'd definitely need to make some adjustments to the display component because the ESPHome component I'm using is specific to this panel. Different e-ink screens need different components sometimes. Everything else would be pretty similar though.

    • @darknessblades
      @darknessblades 3 місяці тому +1

      @@TechDregs AAH OK, was already looking for near identical parts, though the only Issue I encounter every time is that they do not specify which revision it is for the E-ink panel.

  • @darknessblades
    @darknessblades 4 місяці тому

    Where can I get the STL files for the casing

    • @TechDregs
      @TechDregs  4 місяці тому

      Look in the video description.

    • @darknessblades
      @darknessblades 4 місяці тому

      @@TechDregs Its a STEP file, not STL.
      Will have to use a autocad program to convert or modify it

    • @TechDregs
      @TechDregs  4 місяці тому +1

      Yes, it's a STEP. That's a much more robust format than STL for editing. If you really need an STL, just convert it. There are online STEP to STL converters or some slicers (like Prusa slicer) can natively import STEP files directly.

    • @darknessblades
      @darknessblades 4 місяці тому +1

      @@TechDregs Have already edited it in onshape. made a angled stand as well so it can be sitting on a desk/cabinet

  • @bob_mosavo
    @bob_mosavo 10 місяців тому +1

    Thanks 👍

  • @TilmanBaumann
    @TilmanBaumann 10 місяців тому +1

    That github link is dead

    • @TechDregs
      @TechDregs  10 місяців тому +2

      Apologies, I forgot to make it public. Should work now. Thank you for letting me know.

  • @asdkjh4370
    @asdkjh4370 10 місяців тому

    If janks playing with HA it just mean that it's not longer "safe" platform. Actually never was.