Posts

Temp-Humidity Sensor on the Cheap - DHT22, ESPHOME, Wemos D-1 Mini

Image
I picked up some DHT22 and Wemos D-1 Minis for a bathroom-vent project - if it gets too humid from the shower, turn on the fans. When the humidity drops, turn off the fans. This is the story on how they were actually used. A kitten-based project. Frida developed dry coughs this past week. Environmentally, nothing had changed. Food was normal, litter box normal, no chaos. We took her to the vet - no lungworm, no asthma, no cancer in the xrays. Maybe the house is just too dry? Step One: Find the components DHT-22 Sensors - I bought some "HiLetgo 2pcs DHT22/AM2302 Digital Temperature And Humidity Sensor Module" from Amazon. These have three connections: power, sensor, and ground. Some other DHT-22's have 4...one apparently is just not connected. The AM2302's have an advantage later as we will discover, but will an extra line of code. Came with appropriate female-female wires. Wemos D-1 Mini: I found 5 for $16 on Amazon. Not the actual Wemos brand, but they worked. They c

TryFi integration with helpers, scripts, and automations

Image
This article is being written on August 29, 2022 using Home Assistant 2022.8.7, HACS 1.27.1, and TryFi 0.0.17.  First and foremost: TryFi integration devs - thanks for your hard work! This is also not strictly a "home" automation, although all of the data and actions are being handled on Home Assistant. This home project is tied to my dog's Fi collar - I am not receiving payment of any kind from Barking Labs/TryFi nor am I claiming any kind of license/trademark over anything mentioned here. There are two projects - a basic notification automation if Astrid hasn't met her step goals for the day by a certain time, and a more complex automation mimicking a "Safe Zone" in TryFi terms, or something similar to a "Zone" in Home Assistant. What the Projects Need Nabu Casa, or some method to reach your Home Assistant instance remotely. HACS (to install TryFi) TryFi integration (through HACS) Your Fi login & password, and an active Fi collar subscription

Zones and Automation

Image
Project Overview Turn on door alarm alerts to the phone when not at home, and turn off door alarm alerts when at home. Receiving alerts outside of the home assistant's network requires some kind of remote access for your phone app. Nabu Casa is an easy and secure way, but there are other methods. The Panel This is from a dashboard. "Door Alarm Notify Only" is an input boolean. When this is on, doors being opened will trigger an automation to message users whenever a door sensor turns on. When it is off, no messages are generated. This is called Door Alarm Notify Only, as opposed to when the security alarm is engaged. (Code was removed from this blogger post.) "Smoke Alarm Notify Only" [clear] is not part of the automation. (When it is not clear, it uses an automation to send a notification.) "Door Ajar Notify" is an input boolean. When on, if a door sensor is open for more than 15 seconds, it generates an alert. (This is always on, but if it is generat

Troubleshooting a broken Octoprint Integration

Image
A situation came up - my Octoprint/printer page wasn't working like it should. Power could turn on and off - not a problem Sensors would show temperatures and status - not a problem Buttons that sent commands back to Octoprint no longer work - PROBLEM The electrical power for each printer is managed by a TP Powerlink, each plug is managed by a different entity. It does not use Node-Red, and buttons for the power worked for both printers. This was not helpful. The Octoprint integration shouldn't be touching the button flows. The sensors were live, so the HA integration was probably not the case. This is using Home Assistant Core 2022.5.3. With a recent release, the developers changed things up. For example, to check your configuration.yaml and restart your server - previously it was found at Settings>System. (As a caution, the "help" text for that option still indicates the reboot is found there.) Instead, it is found under Developer Tools>YAML - both the confi

More Octoprint Integration Issues

Image
Sadly, I didn't take screenshots of the immediate issue. But fortunately the solution is simple once you find it.   Temperature Problems Temperature numbers from printer bed AND printer nozzle, for both printers were no longer registering any data. (Instead, they read -18 degrees, which is what the Farenheit-to-Celsius template sensor returns when it doesn't have any data.) It had been working several weeks ago, the last time I printed. It could have been a Home Assistant or Octoprint update, or some kind of data corruption. Regardless of the cause, it needed to be fixed. Start in Configuration Go to Configuration>Integrations>(Choose a printer)>(Select the entities).  In my screenshot, you'll notice 7 exclamation marks in red circles. This is normal, as the printer is not connected - it doesn't have any temperatures to report or printer states. When I was working on the problem, the 4 temperature rows - instead of an exclamation mark in a circle - there were e

Fixing Octoprint Integration in Home Assistant

So, Home Assistant has an integration for Octoprint. Seems like it would be really solid - a great thing! Well, it is, unless you already have two printers set up in Home Assistant. I considered tearing it all out and rebuilding it. Delete it, and see what it comes back as. That probably would have been more sane. If you go this route, skip to Octoprint side fixes. Identify what needs to get changed The first step was that none of my sensors were correct. Fortunately, my input booleans (buttons for turning things on and off, retracting - those all go through MQTT topics in Node Red and were untouched.) Octoprint side fixes First, I went to two Octoprints and their Home Assistant Discovery plug-ins and changed the device name to be unique. (The names of the two printers showed up as "Octoprint", resulting in "Octoprint****_2" for some of the entities.) Next, you do NOT need to change anything in MQTT. These are untouched. Back in Home Assistant In the configuration.y

Fixing Fahrenheit-to-Celsius as a one-off conversion template

As someone living in the United States, we use Fahrenheit for temperatures and imperial measurements for measuring things. (Including measuring ingredients by weight or volume, depending!) Which is why my HA uses Fahrenheit/imperial. But in 3D printing, I use Celsius. Sometime in August/September 2021, Home Assistant broke part of my process. It could be that my customization.yaml file's "C" designation broke, or that Home Assistant figured out what was going on and decided to "help" me by converting Celsius from the printer into Fahrenheit. Doesn't matter - end result: my Octoprint sensors were reporting Fahrenheit temps instead of my desired Celsius. First step: Create conversion template entities I added this to my configuration.yaml file: sensor:   - platform: template     sensors:       octoprint_micro_actual_bed_temp_c:         friendly_name: "Micro Bed (°C)"         value_template: "{{ ((states('sensor.octoprint_micro_actual_bed_tem