Posts

Showing posts from November, 2021

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)"         ...