Posts

Posted on

Troubleshooting Flux Models in DiffusionBee: A Journey from Blurry to Brilliant

When I first heard about the Flux.dev/Flux Schnell model, I was eager to see what it could do on my Mac. With the recent update to DiffusionBee Version 2.5.3, which introduced the Flux model, I thought this would be a straightforward process. DiffusionBee is touted as a turnkey solution for running Stable Diffusion locally on your Mac—no need for additional setups like ComfyUI or Python dependencies. It’s as plug-and-play as it gets for AI art generation, making it an attractive choice for those of us who want powerful results without the hassle.

Setting Up the Flux Model

Getting started was easy. I downloaded DiffusionBee, and its seamless integration with Stable Diffusion meant that I could dive straight into the creative process. DiffusionBee’s ease of use is one of its standout features: it allows you to generate and manipulate images with simple text prompts, all while running entirely offline for full data privacy​ (AI Hungry)​ (AI Center).

I quickly installed both the Schnell and Dev versions of the Flux model. Schnell worked flawlessly right off the bat, producing impressive images without a hitch. However, the Dev model—known for being more processor-intensive and capable of higher-quality outputs—didn’t perform as expected. Instead of generating the sharp, detailed images I was hoping for, it produced nothing but blurry results.

The Problem: Blurry Outputs with Flux Dev Model

Prompt: A vibrant scene of diverse individuals joyfully rafting down the Delaware River, surrounded by lush greenery. Sunlight glimmers on the water, capturing their laughter as they sip drinks and share stories, with smoke curling in the warm air.

Initially, I thought the problem might be related to my Mac’s hardware. I use a relatively powerful machine, Apple MacBook Pro M1 Max with 64GB and since DiffusionBee is optimized for Apple silicon, I assumed it would handle the Dev model without breaking a sweat​ (StableBee). But despite playing with every possible setting within DiffusionBee, the images remained frustratingly fuzzy.

As an IT engineer who loves troubleshooting, I went down the rabbit hole, checking forums and online communities. Strangely, I couldn’t find anyone experiencing the same issue with Diffusion Bee. I kept reading about solutions and settings that were not present in the DB app. After hours of trial and error, I began to suspect something crucial was missing.

The Solution: Installing the DiffusionBee 0.1 Model

After much digging, I realized the DiffusionBee 0.1 model wasn’t installed on my system. Could the Dev model require something from this older version to function correctly? I quickly downloaded and installed the 0.1 model from within the app. The difference was immediate—the Dev model started generating the crisp, high-quality images I had been expecting.

Conclusion: A Quick Fix for a Big Problem

If you’re planning to experiment with the Flux models in DiffusionBee, especially the more demanding Dev version, make sure you have the DiffusionBee Default 0.1 model installed as well. This small oversight can save you hours of frustration and get you back to creating stunning AI-generated art in no time.

DiffusionBee Version 2.5.3 has indeed made it easier than ever to run Stable Diffusion models locally, but as with all new tools, a little troubleshooting might be needed to unlock its full potential. I hope this post helps you avoid the pitfalls I encountered so you can focus on the creative possibilities that these powerful models offer.

Posted on

Streamlining IT Workflows with TwoCanoes Automaton 2

As IT professionals, we constantly seek tools that streamline our workflows, especially when it comes to repetitive tasks. Recently, I’ve been exploring the TwoCanoes Automaton 2, a nifty device that has significantly boosted efficiency in my engineering testing processes. For those unfamiliar, Automaton 2 functions as a programmable macro keyboard, allowing automation of various inputs, including password entries during macOS recovery.

A Closer Look at Automaton 2

The TwoCanoes Automaton 2 stands out due to its versatility and simplicity. It’s a small device that plugs into a USB port, acting like a keyboard to input predefined commands or sequences. In my use case, it’s been invaluable for automating the entry of my Wi-Fi password. This might seem minor, but consider the time saved when setting up multiple machines or resetting them frequently.

Speeding Up Testing

In engineering testing, I often need to erase and reinstall macOS on test machines. The Automaton 2 makes this process less tedious by automating password entry, even in macOS recovery mode. Typically, entering credentials during setup can be a hassle, especially when repeated across numerous devices. The Automaton 2 effortlessly inputs the necessary details, allowing me to focus on other aspects of testing.

Programming Convenience

Programming the device is straightforward. It involves creating a script or sequence of keypresses that the Automaton 2 will execute. This feature is particularly useful in scenarios where precise timing and accuracy are critical, such as inputting commands or navigating menus in recovery environments. It’s akin to having a reliable assistant that never misses a step.

Final Thoughts

The Automaton 2 has become an integral part of my toolkit, providing convenience and consistency in testing workflows. It’s an excellent example of how simple hardware solutions can greatly enhance productivity. For anyone involved in IT operations or testing, I highly recommend considering the TwoCanoes Automaton 2 for your setup.

Posted on

If your HomePod mini isn’t showing up in the Home app

If your HomePod mini isn’t showing up in the Home app, it might need to be reset. Follow these steps to reset your HomePod mini:

Photo by Arthur Lambillotte on Unsplash
  1. Unplug the HomePod mini and then plug it back in.
  2. Wait for about 5 seconds, then touch your finger to the top of the HomePod and hold it there. The white spinning light will turn red.
  3. Siri will say that your HomePod is about to reset. Keep holding until you hear three beeps.
Posted on

Set Up Siri Shortcuts with ChatGPT on Your iOS or macOS Device

Photo by Omid Armin on Unsplash

Want a quick way to access ChatGPT on your iOS or macOS device? Follow these easy steps to configure Siri Shortcuts for ChatGPT and start asking questions in no time!

1. Download and Add the Shortcut

  • If you haven’t already, go ahead and download the Shortcuts app
  • Next, add the ChatGPT Shortcut to your iOS or macOS device

2. Give the Shortcut a Name

  • Open the Shortcuts app and tap and hold the newly added ChatGPT Shortcut
  • Rename the shortcut to a Siri command that feels natural to you (e.g., “Ask ChatGPT”)

Example: Say “Hey Siri, Ask ChatGPT [your question]”, substituting “[your question]” with whatever you want to ask

3. Modify the Shortcut

  • Tap Edit to tweak your new ChatGPT shortcut
  • Find the Get contents of section and tap the arrow to display Method > Headers

4. Insert Your API Key

  • Within the Headers section, look for the value [Bearer YourAPIKeyGoesHere]
  • Replace the placeholder text with your real API key, keeping the “Bearer” prefix

5. Try Out Your New Siri Shortcut

  • To start using your new Siri shortcut, simply say “Hey Siri, [shortcut name] [your question]”
  • Swap out “[shortcut name]” with the name you chose, and “[your question]” with whatever you want to ask

Now you have ChatGPT integrated with Siri Shortcuts on your iOS or macOS device! Enjoy seamless interactions with your AI assistant and get answers to your questions using only your voice.

Posted on

printtool is trying to modify the printer settings

Open Terminal

  1. On your Mac, do one of the following:
  • Click the Launchpad icon  in the Dock, type Terminal in the search field, then click Terminal.
  • In the Finder , open the /Applications/Utilities folder, then double-click Terminal.

2. Type the command below and replace USERNAME

sudo dscl . -append /Groups/_lpadmin GroupMembership USERNAME

Posted on

Add a Device to an Addigy Policy Using a Custom Script

Introduction: In this blog post, we’ll demonstrate how to create a script that automates the process of adding a device to an Addigy policy. The script will check if the logged-in computer has an Addigy AgentID and, if so, add that AgentID to a predefined policy.

Here’s the updated and improved script:

#!/bin/bash

# Replace XXXX with your actual policy ID
policy_id="XXXX"

# Function to extract the agent ID from the Addigy configuration file
get_agent_id() {
  awk '$1 == "agentid" {print $2}' /Library/Addigy/config/.adg_agent_config
}

# Function to add the device to a predefined Addigy policy using Addigy API
add_device_to_policy() {
  local agent_id=$1
  local policy_id=$2

  curl --request "POST" "https://prod.addigy.com/api/policies/devices" \
       --header 'client-id: YOUR_CLIENT_ID' \
       --header 'client-secret: YOUR_CLIENT_SECRET' \
       --header 'Content-Type: application/x-www-form-urlencoded' \
       --data-urlencode "policy_id=$policy_id" \
       --data-urlencode "agent_id=$agent_id"
}

# Main script execution
agent_id=$(get_agent_id)
if [ -n "$agent_id" ]; then
  add_device_to_policy "$agent_id" "$policy_id"
else
  echo "Agent ID not found. Please ensure Addigy Agent is installed and configured properly."
fi

Be sure to replace YOUR_CLIENT_ID and YOUR_CLIENT_SECRET with your actual Addigy API credentials. This script is compatible with macOS systems running the Addigy agent.

With this improved script, you can easily automate adding devices to Addigy policies, saving time and effort in managing your device fleet.

Posted on

Onboarding Workflow: Auto Create JumpCloud users with Google Forms and Zapier

How to take the boring out of onboarding

The process of IT onboarding new employees to an organization is typically dull and repetitive, a workflow where an authority fills a form, and form entries get converted to tasks. As an IT professional with over two decades of experience, I’ve created thousands of to-do lists; it’s a necessary part of being thorough. However, repetitive tasks waste valuable creative time and energy, are not scalable, and are error-prone. Making a to-do list for a new setup is a good practice, but the holy grail of completing a task list is automation. Automation allows you to remove the task from your checklist forever. Onboarding is a process, and every new hire is a project testing that process.

The Old Way

In most organizations, the process starts when IT receives a form from HR with a start date, first and last name, title, department; you get it. IT would then connect to an account creation tool to copy and paste all of the bits needed to create the new account; often, you had to do this in multiple systems. Once the account creation is complete, one would begin assigning the correct access permissions and system rights. Managing the correspondence between IT, HR, and the Hiring Manager by responding to queries with updates while actioning tasks can be challenging.

Sometimes the form details were inaccurate, a misspelling, or wrong last name. Once an account is created incorrectly, it was not easily corrected, requiring many of the steps repeated. IT relives this lengthy process every time someone is hired. If only there were a way to eliminate these tasks entirely and make the process more efficient, scalable, and accurate.

The New Way

Automation has been around since the dawn of computing but was not accessible or affordable to smaller organizations. It required programming teams to develop in-house solutions. There was no hope of connecting to external systems unless explicitly allowed by a vendor through a VPN. Things have changed a bit, and thousands of APIs are now accessible through SaaS platforms like Zapier with little to no programming knowledge.

The paper form and photocopied to-do list are now Google Forms, Zapier, and Trello cards. Their APIs and many others like them allow us to skip the dashboard altogether and build workflows that eliminate the most tedious part of our onboarding responsibilities. Identity Providers (IdP) like JumpCloud offer SSO/SAML integration with many services like Google Workspace, Slack, and Zoom. JC reduces complexity in your workflow script; you don’t have to create additional scripting. Add a user to the appropriate group and let JumpCloud provision the new account across multiple services.

The Task

In the following workflow, you will create a Zapier Webhook to connect to the JumpCloud API when someone fills a Google Form. This Zap (a Zapier automation) can be as simple or complicated as you like. We will only set up two tasks in this workflow, but I will suggest other ideas later in this article.

Requirements

Workflow Overview

Create a Google Form.
Consider creating a digital version of your paper form or linking to an existing form if you already use Google Forms.

  1. Create Zapier Zap that looks for new Google Form Response Google Sheet rows created by the form in the previous step.
  2. In the above Zap, use the form data to POST the creation of a new user via JumpCloud API.

Zapier Workflow Steps

1. Create a new Zap in Zapier

We are about to create a trigger that sets off a chain of events when your HR department fills out a Google Form.

2. Add a Trigger

  1. Choose your trigger app: Google Sheets
  2. Select your trigger event: New Spreadsheet Row

I will not detail the process of setting up a Google Sheet row update trigger. It’s pretty straightforward, and many other resources teach you how to do this.

3. Action: Condition Run

Your form variables should go into the right column. These details change with every new form entry.
I’m sure you already know that exposing your API key is a security risk. I encourage you to enable MFA in Zapier for added security.

Choose apps & event

WebHook by Zapier
Action Event: Post

Set up action

URL: https://console.jumpcloud.com/api/systemusers

Payload Type: JSON

Data:
username: Get from Step 1
firstname: Get from Step 1
email: Get from Step 1
activate: true
jobTitle: Get from Step 1
employeeType: Get from Step 1
department: Get from Step 1
Wrap Requests in an Array: no
File: Left Blank
Unflatten: yes
Basic Auth: Left Blank
Headers: x-api-key | JUMPCLOUDAPIKEY

4. Action: Condition Run (Additional Options)

Our onboarding form has a relationship field where HR selects one of the various paths. Initially, my onboarding Zap is configured for three distinct paths: Full-Time, Part-Time, No Email. I originally started with different Zaps for onboarding and offboarding. Recently, I combined them into one Zap, and I have created a simple flowchart to show you the logic. I’ve also started using Typeform because of the better logic it offers over Google Forms.

  • Send internal email to HR, Ops, Hiring Manager to notifying them of the new hire.
  • Post notification in a Slack channel.
  • Add to new hire date to an onboarding calendar.
  • Create a Trello card to track any tasks that have not yet been automated.
  • Create an IT Welcome letter and email it to the new hire’s personal email address.
  • Add the end-user to JumpCloud groups like staff or freelancers.

Final Thoughts

JC will ignore an API request to create a username that already exists. The following modification to my Zap will check JC to see if the new username exists, modify it, or get a notification to intervene. No more errors or recreating users manually; if your automation works, the only mistakes will come from insufficient data in the form. I ask my HR team to resubmit the request if, for any reason, the initial form entry was inaccurate. You are effectively making it no longer your problem – I can feel you smiling inside.

Workflows are always a work in progress. There are always more things to do. I am not a programmer, so I have spent countless hours searching for various solutions and figuring out ways of gluing them together. I’m getting better at asking for help. If I can figure this stuff out, anyone can.

Special thanks to the Mac Admins community. This is my first blog and my attempt to give back after listening, reading, and learning for so many years.