<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ESPHome on wtip.net</title>
    <link>https://www.wtip.net/tags/esphome/</link>
    <description>Recent content in ESPHome on wtip.net</description>
    <generator>Hugo -- gohugo.io</generator>
    <managingEditor>websitecontact&#43;wtipnet@wtip.net (William Cooley)</managingEditor>
    <webMaster>websitecontact&#43;wtipnet@wtip.net (William Cooley)</webMaster>
    <lastBuildDate>Thu, 27 Jan 2022 15:00:00 -0500</lastBuildDate><atom:link href="https://www.wtip.net/tags/esphome/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building an ESPHome environmental multi-sensor</title>
      <link>https://www.wtip.net/blog/2022/01/building-an-esphome-environmental-multi-sensor/</link>
      <pubDate>Thu, 27 Jan 2022 15:00:00 -0500</pubDate>
      <author>websitecontact&#43;wtipnet@wtip.net (William Cooley)</author>
      <guid>https://www.wtip.net/blog/2022/01/building-an-esphome-environmental-multi-sensor/</guid>
      <description>Sometime early last year I replaced my SmartThings home automation hub with a Home Assistant VM running on an Intel NUC.
Not long after that I converted my Envirosense boards (see previous post) to run the ESPHome firmware and started scraping Prometheus metrics from Home Assistant.
There was one thing I wasn&amp;rsquo;t happy about with my original design. The PIR sensor was frequently showing false positive motion events.
This seems to have gotten worse with the switch to the ESPHome firmware.</description>
    </item>
    
  </channel>
</rss>
