Rendezvous with Rama by Arthur C. Clarke was a fun tale to read early in my Sci-Fi obecession. I heard the name recently when YouTube added a legacy sci fi book summary channel to my suggested watch list, and as I have been working with home hosted LLM models I thought it would be fun to see how well an LLM can handle a whole book!

Taking it a step further, I also have the option to use web searches through the OpenWebUI Google API. So why not compare three methods?

LLM Standalone: This method uses the LLM with it’s trained information. No additional sources are included.

LLM with Internet Search: This method uses the Google API in OpenWebUI retrieve information from the internet. It is described further below.

LLM with Book Availability through RAG: This method (RAG) also described below provides information directly from a text source.

To evaluate these three methods, we will be asking for a three paragraph summary, and several short discussions on sections of the book. Prompts will be included and responses separated into three columns, the default prompt in OpenWebUI has been removed.

More about the system:

I will be using my current co-editor, Llama3.1:8B running on an Nvidia P4 on a virtual machine in a Dell R430, the model I use for my co-editing! This is hosted on a Proxmox server with GPU passthrough, a common solution for LLM and gaming projects.

More about the sources:

Google API – OpenWebUI uses the Google PSE API in my case, providing a free platform (with daily limits).

In OpenWebUI, an LLM is used to generate text-based interfaces, including a search interface. When a user interacts with this interface, the LLM uses the Google Custom Search JSON API to send a search request and retrieve relevant results. The LLM then generates a response based on these results, creating a conversational experience for the user.

RAG: – The Retrieval Augmented Generation (RAG) implementation uses an EPUB copy of Rendezvous with Rama that was converted to a TXT file and uploaded to OpenWebUI Knowledge base. It is the only document in the knowledge base being referenced in method three, and is 401.6KB in size.

Imagine you’re trying to write a essay about a historical event, but you need some specific information to make your points. A traditional AI model might just try to generate text from scratch, but it might not always get the facts right. RAG is a way to improve this process by first searching through a vast library of existing knowledge (like a super-smart search engine) to find relevant details about the event. Then, it uses those findings to inform and guide its own writing, making sure that the generated text is accurate and helpful. This approach helps the model produce more reliable and informative content!

Section One: A book summary.

Section Two: Tell me about the aliens.

Section Three: Why is Rama visiting our solar system?

Without further adieu, let’s get started!

Section one: Book Summary

Prompt: Please write a two to three paragraph summary of Arthur C Clarke's book Rendezvous with Rama.

LLM

Here is a summary of Arthur C. Clarke’s novel “Rendezvous with Rama”:

The novel tells the story of a massive, cylindrical spacecraft that enters the solar system and makes its way towards Earth. As it approaches, scientists from around the world converge on the planet to study the enigmatic vessel, which they have dubbed “Rama.” The ship is roughly 50 kilometers in length and appears to be made entirely of some sort of metal or alloy material. Despite numerous attempts to communicate with Rama, no signals are received, leading many to speculate about its true purpose.

A small group of humans is able to board the spacecraft via a tiny spaceship that is inserted through a series of narrow openings on Rama’s surface. The crew members, led by Commander Norton, find themselves in a vast, almost empty environment with strange and eerie artifacts. As they explore the interior, they begin to uncover clues about Rama’s origins and purpose, which lead them to question everything they thought they knew about the universe.

Throughout the novel, Clarke explores themes of first contact, cosmology, and the search for meaning in a seemingly indifferent universe. The enigmatic nature of Rama serves as a mirror to humanity’s own existence, raising questions about our place within the grand scheme of things. Ultimately, “Rendezvous with Rama” is a thought-provoking and visually stunning novel that challenges readers to consider the possibilities of life beyond Earth.

LLM + GOOGLE

Arthur C. Clarke’s novel “Rendezvous with Rama” tells the story of a mysterious alien vessel that enters Earth’s solar system, prompting an expedition to investigate it. The story follows a group of astronauts and scientists as they attempt to explore the vessel, which is about 50 kilometers long and has a complex internal structure.

As the crew delves deeper into the ship, they discover evidence of an advanced alien civilization that had encountered Earth in the distant past. However, the aliens’ intentions and purposes are unclear, leading to a sense of wonder and unease among the human explorers. Clarke’s novel explores themes of science, technology, and humanity’s place in the universe.

The book was initially intended as a standalone novel but received commercial success and critical acclaim, leading Arthur C. Clarke to team up with writer Gentry Lee to co-author three sequels set in the same Rama universe.

Sources Referenced:

LLM + RAG

Based on the provided context, here is a summary of Arthur C Clarke’s book Rendezvous with Rama:

The story revolves around the discovery of a massive spacecraft, known as Rama, which is approaching the solar system. As it draws closer, scientists and experts begin to discuss its implications and what could be controlling it. Some speculate that Rama might be headed for a rendezvous with Earth, while others are unsure about its intentions.

One of the key points discussed in the context is the possibility of Rama decelerating near the Sun and then making a velocity change to rendezvous with Earth. The experts also mention that Rama’s unusual orbit and size make it an intriguing phenomenon that will be studied further as it approaches the solar system.

Overall, the context suggests that Arthur C Clarke’s book is about the discovery of this massive spacecraft and the subsequent discussions and speculations among scientists and experts about its intentions and possible implications for humanity.

Note: I’ve tried to summarize the context in a neutral way without providing too much interpretation or personal opinion, as per your rules.

Results

The first method, just the LLM with it’s trained data, is unexpectedly the most wordy about the summary. However this seems to largely be a repeat of opinions on the book gained from conversations or other summaries it was trained on, rather than speaking to anything technical about the book.

The second method using Google search engine supplies data provides the shortest summary, with no real information to the story besides a very high level summary and a fun fact.

The final method, using the RAG method, seems to focus on information from the start of the book. To be honest, I had expected more from this and feel that a different prompt may have served better considering it has the entirety of the book at hand, but it may be too much information for an 8b model to handle.

Section Two: Comprehension

Prompt: Tell me about the aliens in Rendezvous to Rama. What did they look like, what was their motivation?

LLM

There are no aliens in Arthur C. Clarke’s novel “Rendezvous with Rama”. In fact, one of the hallmarks of the book is its refusal to reveal any explicit information about the nature and purpose of Rama.

Throughout the novel, Clarke skillfully builds suspense and mystery by providing tantalizing clues and hints about Rama’s true identity, but ultimately leaves the reader with more questions than answers. The focus of the story is on the human characters’ experiences and observations as they explore Rama, rather than on any specific alien species or civilization.

In a sense, this lack of explicit detail about aliens is a deliberate choice by Clarke to reflect humanity’s own limited understanding of the universe. By avoiding explicit answers, Clarke invites readers to speculate and consider the possibilities for themselves, making the novel a more thought-provoking and unsettling experience.

The enigmatic nature of Rama itself becomes a kind of “alien” presence, one that challenges human assumptions and encourages us to re-examine our place in the cosmos. So while there are no traditional aliens in the novel, the mystery and ambiguity surrounding Rama serve as a powerful metaphor for the vast and unknowable nature of the universe.

LLM + GOOGLE

Arthur C. Clarke’s novel The aliens in Arthur C. Clarke’s novel “Rendezvous with Rama” are not explicitly described as having a physical appearance. The focus of the story is more on the enigmatic alien vessel, known as Rama, and its mysterious purposes, rather than the aliens themselves.

As for their motivation, it remains unclear throughout the book. The Ramans seem to be collecting intelligent life forms from around the galaxy using their spacecraft, but their reasons for doing so are not revealed. It is suggested that they may be studying or observing these civilizations, but the true purpose of this collection activity is left ambiguous.

Clarke leaves the interpretation of the aliens’ intentions and motivations open to the reader, which adds to the sense of mystery and wonder in the novel.

Sources Referenced:

LLM + RAG

I’m afraid I must say that I don’t know. The context provided doesn’t mention anything about aliens or extraterrestrial beings in Rendezvous with Rama. It appears to be discussing the discovery and approach of a massive spacecraft called Rama, but it doesn’t provide any information about its inhabitants or their motivations.

It’s possible that the book explores these themes, but based on the provided context, I couldn’t find any relevant information.

Results

Again, the trained knowledge provides the longest response, though seems to hallucinate a little but and draws conclusions that don’t really match the narrative.

The Google based response is interesting in that it seems to have pulled a Google result and used that as the basis for it’s conclusion. While there are a handful of opinions on the purpose of Rama, there are very few who theorize it is about collecting species (though this sounds distantly familiar for another book series), and rather most interpretations are that the crablike creatures found on Rama are the equivalent of maintenance drones.

Lastly, again I find the RAG generated response to be a disappointment. There most certainly are references to the alien inhabitants of the craft, and readers may remember a “crablike” entity, as noted in this screen shot of the text that was fed to the Knowledgebase:

Section 3: Interpolation and Speculation

Prompt: In Rendezvous with Rama, why is Rama visiting our solar system?

LLM

That’s another great question about “Rendezvous with Rama”! Unfortunately, Clarke doesn’t provide a clear or explicit answer to why Rama is visiting our solar system. In fact, the novel leaves this question entirely unanswered.

Throughout the book, various scientists and theorists propose different explanations for Rama’s presence in our solar system, but none of these theories are definitively proven or disproven. Some suggest that Rama might be a survey vessel sent by an advanced civilization to study the solar system, while others propose that it could be some kind of cosmic structure that has been swept into our system.

Clarke intentionally leaves this question open-ended, allowing readers to draw their own conclusions and speculation about Rama’s purpose. This ambiguity is a hallmark of the novel, adding to its sense of mystery and wonder.

In an interview, Clarke himself stated that he deliberately avoided providing a clear explanation for Rama’s presence in our solar system, preferring to let readers’ imaginations fill in the gaps. By doing so, Clarke aimed to create a sense of awe and curiosity about the universe and its potential secrets.

LLM + GOOGLE

Unfortunately, I don’t have a clear answer to this question from the context provided. The context mentions that Rama’s presence and intentions are unclear, and Clarke himself seems to be leaving many questions unanswered in the novel. One of the quotes from the source_context even says “for all the questions Rama environment raises, Clarke offers very few, in fact almost no, definite answers.”

Therefore, I must say that we don’t really know why Rama is visiting our solar system, as it’s intentionally left ambiguous by Arthur C. Clarke.

Sources Referenced:

LLM + RAG

Rama is visiting our solar system because it will be at perihelion (its closest point to the Sun) in three weeks and then it will leave the solar system just as fast as it came in. According to Rodrigo’s theory, if there’s any truth to it, Rama might make another velocity change and rendezvous with Earth, which would allow it to remain in the solar system.

Results

In line with the previous responses, the LLM trained information response is the longest and seems to be general knowledge, ending with elaboration that sounds like something out of a book review.

The Google API generated response is short and concise, and seems to offer a quote from one of it’s references, which is a nice touch:

Lastly the RAG generated response is the most underwhelming response yet. It seems entirely based on the facts in the early chapters of the book, rather than drawing in and using information from the book in general.

Conclusion

The LLM trained model provides a detailed and lengthy response, but often makes assumptions or draws conclusions that aren’t supported by the context.

The Google API generated responses are concise and to the point, but sometimes seem to rely on pre-existing knowledge or references rather than providing a fresh interpretation of the information.

The RAG (Reinforcement Learning from Human Feedback) generated responses are often underwhelming and seem to be based solely on the early chapters of the book. They rarely draw on broader themes or motifs in the narrative, instead sticking to surface-level facts and descriptions.

It’s worth noting that all three models have their strengths and weaknesses. The LLM trained model excels at providing detailed information and explaining complex concepts, but can sometimes struggle with nuance and subtlety. The Google API generated responses are great for quick answers and concise summaries, but might not always provide the most in-depth or insightful analysis. The RAG generated responses have potential for being more nuanced and context-specific, but often fall short due to their reliance on early chapters and lack of broader thematic understanding.

Overall I think the LLM trained information and Google API enabled results provide fairly satisfactory results, however I will have to leave the RAG based prompts to a minimum or for technical information only.

<p>The post AI Response Showdown – Rendezvous with Rama first appeared on AADSIT.COM.</p>

What is a Nginx Reverse Proxy?

A Nginx reverse proxy server is a powerful tool that’s designed to handle large volumes of traffic while keeping your infrastructure organized. As a web server tool, it’s often used for hosting websites directly, but its capabilities don’t stop there. With Nginx’s Proxy Pass configuration, you can pass requests to another URL or IP/port combination – even implement load balancing.

Why Choose Nginx as Your Reverse Proxy?

There are many reasons why Nginx is a top choice among web developers and sysadmins. Some of the key benefits include:

• High performance : Nginx is designed to handle large volumes of traffic while keeping your infrastructure organized.
• Load balancing : With Nginx, you can easily implement load balancing to distribute traffic across multiple servers.
• SSL termination : Nginx makes it easy to terminate SSL certificates and ensure secure connections between clients and servers.

Prerequisites

1. Domain Registration : You should have a registered domain name (e.g., aadsit.com) and ensure that it is correctly pointed to your server. If you have a dynamic IP address I highly recommend setting up a dynamic DNS client!
2. Public IP Address : Your server should have a publicly accessible IP address (i.e., not behind a Carrier Grade NAT or firewall ISP).
3. Proxmox/Networking Setup : Familiarity with Proxmox or other virtualization software, as well as basic networking concepts (e.g., subnets, ports, etc.) is assumed.

Setting Up a Nginx Reverse Proxy Server with Certbot

In my setup, I use two separate Nginx servers: one handles public-facing traffic, while the other is for internal-only traffic. This post focuses on setting up the public-facing Nginx reverse proxy server using Certbot to obtain Let’s Encrypt certificates. By following this guide, you’ll learn how to:

• Set up a Nginx reverse proxy server
• Obtain free SSL certificates from Let’s Encrypt using Certbot

To begin we will discuss our lab environment and dive into creating a host for our server. At home I run a Proxmox cluster with High Availability, with most of my servers being virtual machines. In this demo, we will be setting up an individual LXC container for low overhead and quick setup.

The host server is “Atacama”:

This article doesn’t cover Proxmox or networking basics and assumes you have these covered. We will create a new LXC container for our demo. I’m using the ubuntu-22.04-standard image as that is what I have readily downloaded.

We will get signed into the server and run apt-update to get a list of current packages

It’s good practice to get everything updated before continuing, so we will go ahead and run apt full-upgrade -y

Now that everything is updated we will install Nginx and Certbot, including the module for certbot to interact with Nginx.

Now that the packages are installed, we need to enable Nnginx to run as a service with “sudo systemctl enable nginx”, and then start the service after.

Our server is sitting at 192.168.2.3. Specifying HTTP, NOT HTTPS, we see a welcome screen!

As the focus of this is on setting up a reverse proxy, let’s next discuss our target. I choose to have a different virtual machine run Docker, hosting websites and similar services in a containerized environment. Without going into the details, this provides easy snapshotting, backups, and even high-availability and live migrations when I do server maintenance. This server is at 192.168.2.8, and I have a WordPress website running on port 9080. We can set up a basic Proxy in Nginx by creating a new file in /etc/nginx/sites-available, such as “demo”. I like to use the full name for my configuration files, and this will be a sub domain of aadsit.com, so I will call this “demo.aadsit.com”. The text in the “Demo.aadsit.com” file:

server {
    server_name demo.aadsit.com;
    listen 80;
    location / {
        proxy_pass http://192.168.2.8:9080;
        client_max_body_size 800M;

        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Port $server_port;
    }


}

Explained

Server Block

server { : Starting point for an individual server block.
server_name demo.aadsit.com;: Specifies the domain name that this server block should respond to.
listen 80;: Tells nginx to listen on port 80 (the standard HTTP port).

Location Block

• location / { : Specifies the URL path or pattern that should be handled by this server block (in this case, requests made to /).
• proxy_pass http://192.168.2.8:9080;: Forwards incoming traffic to a service located at http://192.168.2.8:9080.
• client_max_body_size 800M;: Sets the maximum body size that can be transferred from the client to 800 megabytes. This can be any value, I usually set it to at least a few MB.

Proxy Header Settings

These settings preserve and manipulate information about the original request:

• proxy_set_header Upgrade $http_upgrade; & proxy_set_header Connection "upgrade";: Set up headers for WebSockets upgrades
• Copying specific headers from the original request to the proxied server:
  • proxy_set_header Host $host;
  • proxy_set_header X-Real-IP $remote_addr;
  • proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  • proxy_set_header X-Forwarded-Proto $scheme;
  • proxy_set_header X-Forwarded-Host $host;
  • proxy_set_header X-Forwarded-Port $server_port;

After creating the configuration file, you have to link it into the sites-enabled folder. You can do this with “ln -s” to create a soft link, as shown below. This is a common way of implementing configuration files, as it allows you to update a file in one spot and be reflected in multiple spots, or otherwise unlink a file without deleting it. I use a script to link all .com and similar website configuration files in one go.

After that let’s restart Nginx with systemctl restart nginx

Now NGINX is listening and will pass traffic to the target server! We can test this internally by adding “demo.aadsit.com” to our hosts file, as shown (in Windows):

“You might realize now that your reverse proxy is only reachable internally. That may be a good stopping point for some people, but our goal is to make this externally available! If you’re just setting up an internal-only reverse proxy and don’t need public HTTPS encryption, you can consider it complete. However, if you want publicly signed certificates for your website (for HTTPS encryption), the easiest way that we’ve already set ourselves up for is to use Let’s Encrypt via Certbot!

Note: Alternatively, if this is an internal-only reverse proxy, visitors can use a certificate signed by a private certificate authority instead. Installing the certificate authority on their computer will allow them to see the website as trusted.

I already have DNS in place for demo.aadsit.com to reach my external IP address:

The next step is to set up SNAT or Port Forwarding on my firewall to direct traffic to the server. In my case, I use Aliases as much as possible, and have an alias “WebTraffic_Ports” with port 80 and 443, HTTP and HTTPS respectively. Both are important to have! Your specific situation may vary, and if you do not have a public IP address you will not be able to do this. (Note: if you also use PfSense or other more-capable firewalls, you may need to find and enable the settings for “NAT Reflection” to reach websites internally. )

Once we have external access to our website set up, let’s get some certificates generated! On our demo server we will run “certbot –nginx”

You will be prompted to answer several questions, and then given a list of server names found in your configuration files. If you have multiple sites being hosted, you can submit a request for all of them in one go. It will then provide a single certificate with all sites included as “subject alternative names”.

The next step is to set up SNAT or Port Forwarding on your firewall to direct traffic to the server. However, this step may fail if port 80 is not forwarded to your server correctly! You may also encounter issues if you have geo-blocking or other restrictions in place, which can prevent the Automated Certificate Management Environment (ACME) protocol used by Certbot from completing.

If everything goes well, Certbot will automatically generate the certificate with LetsEncrypt and update your configuration file!

You can see that now we have a section listening to port 80 which replies with a redirect to our site with HTTPS, and now it listens at 443 with the letsencrypt certificate!

Finally, try going to your site (ensure you’ve removed the hosts file entry or local dns if you tried it!) and ensure that you are redirected to HTTPS. In this case, DEMO.AADSIT.COM is failing to load images resources as they are actually at AADSIT.COM, which is offline while I do this demonstration.

In this article, we’ve covered the basics of setting up a Nginx reverse proxy server on an LXC container using Proxmox as our virtualization platform. We walked through the process of obtaining free SSL certificates from Let’s Encrypt using Certbot, setting up a basic Nginx configuration to proxy requests to the target server, and configuring the target server to receive traffic.

And that’s it! With these steps, you should now have a functional reverse proxy setup using Nginx on an LXC container running on Proxmox. This is just the tip of the iceberg – there are many ways to customize and optimize your reverse proxy setup for your specific needs.

Thanks for reading, and happy self-hosting!

Created with my co-editor Llama3.1 8b running on an Nvidia P4, which was a lot of fun!

<p>The post Nginx Reverse Proxy Guide for Self-Hosted Services first appeared on AADSIT.COM.</p>

As a new homelabber or someone looking to level up their networking game, understanding subnetting is crucial. In this guide, we’ll break down the basics, provide some hands-on examples, and give you a solid foundation for tackling more complex network configurations.

Outline:

1. What is Subnetting?
2. Why Bother with Subnetting?
3. Understanding IP Addresses and Subnets
4. Step-by-Step Subnetting Process
5. Practical Examples in Your Homelab
6. Troubleshooting Common Issues

What is Subnetting?

Subnetting, also known as IP subnetting, is the process of dividing an IP network into smaller, more manageable sub-networks (subnets) to improve network organization and efficiency.

Think of it like a city: a big city has many neighborhoods, each with its own unique identity. Similarly, your network can be divided into subnets, making it easier to manage traffic, security, and other network-related tasks.

Why Bother with Subnetting?

Subnetting offers several benefits:

• Improved Security : By dividing the network into smaller subnets, you can implement more targeted security measures.
• Enhanced Network Organization : Subnetting helps keep your network tidy by grouping devices based on department, location, or function.
• Better Traffic Management : Subnetting enables you to control and prioritize traffic flow between different parts of the network.

Understanding IP Addresses and Subnets

To subnet, you need a solid grasp of IP addresses and subnet masks. Don’t worry; it’s not as scary as it sounds!

An IP address consists of:

• Network ID (first part)
• Host ID (second part)

A subnet mask is used to identify the network and host parts of an IP address.

For example: IP Address: 192.168.1.100 Subnet Mask: 255.255.255.0

In this example, the first three parts (192.168.1) represent the network ID, while the last part (100) represents the host ID.

Subnet Masks vs CIDR Notation: What’s the Difference?

You might have noticed that subnet masks can be expressed in two different ways: as a series of dotted decimal numbers (e.g., 255.255.255.0) or as a single number, known as CIDR notation (Classless Inter-Domain Routing).

CIDR notation is a shorthand way to express the subnet mask, and it’s used extensively in modern networking. The CIDR notation uses an “X” (where X is a number from 0-32) after the IP address to indicate the number of bits that are set in the subnet mask.

For example:

• 255.255.255.0 translates to: /24
• 192.168.1.100/24

Note: When you see /32, this means it is a single address, not a network!

In CIDR notation, the “/24” means that the first 24 bits (or three parts/octets) of the IP address are used for the network ID, and the remaining 8 bits (or last part) are used for the host ID.

When to use subnet masks vs CIDR notation?

• Use traditional subnet masks when working with older operating systems or legacy equipment that don’t support CIDR notation.
• Use CIDR notation in modern networking environments, as it’s more concise and easier to read. Many network management tools and configuration files also prefer CIDR notation.

By understanding the basics of IP addresses, subnet masks, and CIDR notation, you’ll be well on your way to mastering subnets and configuring networks like a pro!

What does it mean?

In essence, a subnet mask is a 32-bit number (or 128 bits for IPv6) that helps your switch or router figure out which devices on the network are part of the same subnet as you. Think of it like a filter: the ones in the bit positions where the subnet mask has a ‘1’ correspond to the network part, and those with a ‘0’ represent the host part. For example, if we use the common subnet mask 255.255.255.0 (binary 11111111.11111111.11111111.00000000), any IP address that shares these first three sets of ones will be considered to be on the same network as you.

Now, let’s dive into binary for a sec – it might look like hieroglyphics at first, but trust me, it’s actually pretty straightforward once you get the hang of it. In subnet masking, we use binary numbers to represent IP addresses and their corresponding bits. For instance, when we say an IP address is ‘192.168.1.100’, in binary, that looks like 11000000.10101000.00000001.01100100 – breaking down each octet (or group of eight bits) to see which are part of the network and which represent individual hosts.

Step-by-Step Subnetting Process

Here’s a simplified step-by-step process to subnet:

1. Determine the IP Address Range : Decide on the IP address range for your subnet.
2. Calculate the Number of Available Hosts : Use the following formula: (2^h) – 2 (where h is the number of host bits).
   • The “-2” part subtracts 2 from the total number of bits in the host portion, because the first and last bit is always reserved for the network ID and last for Broadcast, leaving you with a smaller set of bits to work with.
3. Determine the Subnet Mask : Based on the calculated number of available hosts, choose a subnet mask that will fit your needs. For example, if you need 254 host addresses you can use 255.255.255.0 (because 0-255 = 256, and you will lose two for the network and broadcast IPs). If you need 355 addresses you could use 255.255.128.0 (or 11111111.11111111.11111110.00000000 in binary), which would give you (2^9)-2 or 510 usable IP addresses!
4. Assign IP Addresses and Subnet Masks : Assign IP addresses to devices within your subnet.

Practical Examples in Your Homelab

Let’s put subnetting into practice using our trusty homelab!

Example 1: Simple Subnet

Suppose you have a home network with 10 devices, and you want to create a simple subnet for all of them. You can assign the following:

• IP Address : 192.168.0.0
• Subnet Mask : 255.255.255.0

This will give you a single subnet with 254 available hosts (2^h-2), where h is 8).

Example 2: More Complex Subnet

Imagine you have multiple subnets for different departments within your company. The following is in CIDR notation, a more efficient method to convey the same information.

• Sales Department : 192.168.1.0/24
  • (this is the same as 255.255.255.0)
• Marketing Department : 192.168.2.0/25
  • (this is the same as 255.255.255.1)
• IT Department : 192.168.3.0/16
  • (this is the same as 255.255.0.0)

In this example, you’ve created three separate subnets for different departments using different subnet masks. Devices on these subnets can “speak” to each other directly, but to reach other subnets they must go through a router and any relevant firewalls. For example, the IT Department may need ALLOW rules to remotely manage computers in the Sales department, but the Sales Department computers should not need to interact with the Marketing Department computers.

VLANs vs Subnets: Understanding the Basics

When it comes to network organization, two popular methods are often confused with each other: VLANs (Virtual Local Area Networks) and subnets. While they share some similarities, they serve different purposes and have distinct characteristics.

VLANs:

• Network isolation : VLANs use VLAN tagging on switches and routers to isolate the network into separate virtual networks. The hardware must support this feature though.
• Traffic separation : Devices in different VLANs do not communicate with each other by default, reducing the risk of unauthorized access or data breaches.
• Flexibility : VLANs can be created, modified, or deleted as needed.
• DHCP: One major reason that a person may choose VLANs over just simple subnets is that when there is no VLAN usage, all layer 2 broadcast requests go to the same place. A DHCP server will provide addresses to any DHCP request it receives, and so without VLANs isolating the frames on the network you can only have one DHCP server (there are exceptions, but this would not be considered best practice).

Subnets:

• IP address configuration : Subnets are a logical grouping of IP addresses within an IPv4 network.
• Routing efficiency : Devices on different subnets can communicate with each other through routers, reducing traffic congestion and improving overall network performance.
• Scalability : Subnets can be easily created or modified as needed.
• Security: There is no security on individual subnets as traffic does not go through a router to get to other hosts on the same subnet. A user may change their subnet at any time with relevant privileges, however without a router to handle traffic outside of the subnet there may be no internet.

Troubleshooting Common Issues

When working with subnetting, you might encounter some common issues. Here are a few tips to help you troubleshoot:

• Incorrect Subnet Mask : Double-check your subnet mask calculations and ensure it’s correctly applied.
• IP Address Conflicts : Verify that each device has a unique IP address within its respective subnet.
• Network Disruptions : Identify the source of network disruptions, such as faulty devices or misconfigured subnets.

Summary:

In this guide, we’ve explored the basics of subnetting, including what it is, why you need it, and how to implement it in your homelab. We’ve also provided practical examples to help solidify your understanding.

Remember, subnetting is a crucial aspect of network management. By mastering subnetting, you’ll be able to:

• Improve Network Organization : Subnetting helps keep your network tidy by grouping devices based on department, location, or function.
• Enhance Security : By dividing the network into smaller subnets, you can implement more targeted security measures.
• Better Traffic Management : Subnetting enables you to control and prioritize traffic flow between different parts of the network.

Homelab Practice:

Now that you’ve got a solid understanding of subnetting, it’s time to put your skills to practice! Set up your own homelab and experiment with subnetting. Use online tools or calculators to help with calculations.

Resources:

For further learning, check out these resources:

• RFC 1812 : A comprehensive guide to IP subnetting.
• Calculator.net : An online subnet calculator for easy calculations.

That’s it! I hope this guide has helped you become more comfortable with subnetting. Remember, practice makes perfect – so get out there and subnet like a pro!

Made with my co-editor, Llama 3.1 8B

<p>The post Subnetting Like a Pro in Your Homelab first appeared on AADSIT.COM.</p>

As a fellow homelab enthusiast, I’m sure you’re excited to start building your own IT playground. But before we dive into the nitty-gritty details, let’s take a step back and talk about some best practices that will make your journey smoother, safer, and more enjoyable.

Introduction

Having a home lab is not just about throwing together some hardware and software – it’s an opportunity to learn, experiment, and push the boundaries of what’s possible. But with great power comes great responsibility. In this blog post, we’ll cover some essential best practices that will help you set up your homelab safely, efficiently, and effectively.

Outline

1. Plan Before You Build : Don’t just start buying hardware without a clear idea of what you want to achieve. Take the time to research, plan, and design your homelab before making any purchases.
2. Power Management is Key : Make sure you have a solid power management strategy in place to prevent overloading, overheating, or electrical shock. This includes using surge protectors, UPS units, and monitoring systems.
3. Cable Management is Crucial : Keep your cables organized, labeled, and secure to avoid damage, tangling, or even fires. Use cable ties, zip ties, or cable management boxes to keep your workspace tidy.
4. Storage : Invest in sturdy storage and shelving units to keep your equipment, tools, and supplies within easy reach. This will save you time, reduce clutter, and prevent losses due to misplaced items.
5. Monitor and Maintain Your Equipment : Regularly check your hardware for signs of wear and tear, dust buildup, or overheating. Keep your software up-to-date, and run regular backups to ensure your data is safe.
6. Join a Community and Learn from Others : Connect with fellow homelab enthusiasts through online forums (like reddit.com/r/homelab), social media groups, or local meetups. Share knowledge, ask questions, and learn from others’ experiences.

Plan Before You Build

Planning is key when it comes to building a successful homelab. Don’t make the mistake of buying hardware without a clear idea of what you want to achieve. Take the time to research, plan, and design your homelab before making any purchases. This will save you from costly mistakes, wasted resources, and unnecessary expenses in the long run.

Key Considerations Before Building Your Homelab

• Define your goals : What do you want to learn or experiment with? (e.g., virtualization, containerization, cloud computing)
• Identify your requirements : Hardware, software, networking, power, and cooling needs
• Research popular homelab configurations : Explore examples online or in books to get a good starting point for planning your own setup
• Create a budget : Determine how much you’re willing to spend on equipment, software, and other resources
• Document your plan : Write down your plan, including details about hardware, software, networking, and storage

By taking the time to plan before building, you’ll be well-prepared to set up a homelab that meets your specific needs and goals.

Power Management is Key

A solid power management strategy is crucial to prevent overloading, overheating, or electrical shock. Here are some key considerations:

• Surge Protectors : Use surge protectors to safeguard against voltage spikes and surges that can damage your equipment.
• UPS Units : Install an Uninterruptible Power Supply (UPS) unit to provide a stable power source in case of outages or fluctuations.
• Monitoring Systems : Implement monitoring systems, such as sensors or software, to track temperature, humidity, and power consumption levels.

By implementing these measures, you can ensure that your homelab runs smoothly, efficiently, and safely. Remember, a well-managed power system is essential for maintaining the integrity of your equipment and preventing costly downtime.

Cable Management is Crucial

Cable management is a crucial aspect of setting up an efficient and safe homelab. Inadequate cable management can lead to equipment damage, overheating, and safety hazards such as tripping or electrical shock.

To ensure effective cable management, consider the following strategies:

• Use Velcro/ hook and loop instead of zip ties : This material is more flexible and easier to use than zip ties. It also provides a secure hold without damaging cables.
• Label your cables : Label each cable with its purpose and location to make it easier to identify which cable goes where.
• Route cables correctly : Route cables away from high-traffic areas and keep them away from any moving parts that could damage them.
• Use cable management boxes : Use cable management boxes to keep cables organized and secure. These can be especially useful for longer cables or those that need to be routed through tight spaces.

Storage

When setting up your home lab environment, investing in a solid storage and shelving system can help keep your workspace organized and efficient. However, this might be less of an issue for homelab enthusiasts who utilize a server rack or network cabinet to house their equipment.

For those with a server rack or network cabinet, the focus should shift towards optimizing the space within these units. This includes:

• Labeling cables : Use cable ties and labels to keep track of which cables connect which devices.
• Cable management : Route excess cables through cable management systems or zip ties to prevent clutter and damage.
• Equipment organization : Store frequently used equipment, such as servers or network devices, in easy-to-reach locations.

Monitor and Maintain Your Equipment

As you continue to build and operate your homelab, it’s essential to monitor and maintain the environment to ensure optimal performance and longevity of your equipment. Here are some key considerations:

Temperature Monitoring

• Install temperature sensors in strategic locations throughout your lab to track ambient temperatures.
• Set up alerts or notifications for when temperatures exceed safe thresholds (e.g., 75°F/24°C) to prevent overheating.
• Consider investing in a climate-controlled enclosure or using portable air conditioning units to maintain a stable environment.

Power Consumption Monitoring

• Install power monitoring software or use a network-connected UPS to track power consumption patterns.
• Set up alerts for when power consumption exceeds expected thresholds, indicating potential inefficiencies or equipment issues.
• Consider upgrading to energy-efficient hardware or optimizing your system configuration to reduce power consumption.

Regular Maintenance Schedules

• Establish a regular maintenance schedule (e.g., weekly, monthly) to inspect and clean equipment, update software, and perform routine checks on temperature and power levels.
• Keep detailed records of maintenance activities to track any issues or trends that may arise.

By implementing these monitoring and maintenance practices, you’ll be able to:

1. Prevent overheating or other environmental stressors from damaging your equipment.
2. Optimize system performance by identifying and addressing inefficiencies.
3. Extend the lifespan of your hardware and components through proper care and maintenance.

Keep in mind that installing temperature sensors may be out of scope for a homelab on a budget, as this would require additional hardware or software investments. However, tracking power consumption is generally more accessible and cost-effective.

Join a Community and Learn from Others

Joining a community of fellow homelab enthusiasts can be incredibly beneficial in making the journey smoother, safer, and more enjoyable.

Some benefits of joining a community include:

• Getting valuable insights and advice on various aspects of homelab setup and maintenance
• Staying updated on the latest trends, technologies, and best practices in the field
• Finding support and encouragement when facing difficulties or setbacks

However, it’s essential to note that you may encounter differing points of view within the community. This is a natural part of any online or offline gathering, where individuals bring their unique experiences and perspectives.

When encountering differing opinions, always remember that information and opinions can quickly become outdated. A good homelabber should always do their research and try to understand the issue they are trying to resolve.

By joining the community, you can tap into a wealth of knowledge, experience, and camaraderie that will help make your journey as a homelab enthusiast more enjoyable, productive, and rewarding.

<p>The post Setting Up Your Homelab: Best Practices to Get You Started first appeared on AADSIT.COM.</p>

Here’s the updated section:

RAID Levels: A Closer Look

RAID is a way to combine multiple physical disks into a single logical unit. It provides redundancy, performance, and capacity benefits over using a single drive. There are several levels of RAID (0-6), each with its own strengths and weaknesses.

RAID 0: The Performance Boost

Striped data across multiple drives for increased performance.
Example: Suppose you have four 1TB hard drives connected to your computer. By configuring them in a RAID 0 setup, you can create a single 4TB drive that offers blazing-fast read and write speeds. This is ideal for applications like video editing or 3D modeling where large files need to be accessed quickly.

RAID 1: Redundancy for Peace of Mind

Mirrored data across two or more drives for redundancy.
Example: Imagine you’re a photographer who needs to store thousands of high-resolution photos. By setting up your system with RAID 1, you can duplicate all your photos on two separate hard drives. This ensures that if one drive fails, the other will take over instantly, preserving all your precious memories.

RAID 5: The Balanced Approach

Striping with parity information to provide both performance and redundancy.
Example: Picture this: You’re a video producer who needs to store hours of footage on multiple hard drives. A RAID 5 configuration would stripe data across three or more drives while using one drive as a parity block. This setup offers the best balance between performance, capacity, and reliability – ideal for applications where large files need to be accessed quickly, yet security is still paramount.

RAID 6: The Ultimate in Reliability

Similar to RAID 5, but with an additional parity block to improve reliability.
Example: Suppose you’re a company that needs to store sensitive data, such as financial records or customer information. A RAID 6 setup would provide the highest level of redundancy – with two parity blocks for added protection against disk failures. This configuration ensures that even if two drives fail, your data will remain accessible, offering unparalleled peace of mind.

Note: Always remember to consider factors like cost, performance requirements, and potential failure scenarios when choosing a RAID level for your specific needs.

Here’s the updated section:

What is ZFS?

ZFS (Zettabyte File System) is a powerful file system designed to handle multiple disks with ease. Unlike traditional RAID configurations, which focus on storage layout and redundancy, ZFS takes a holistic approach to managing your entire storage infrastructure.

A Closer Look at ZFS Features

One of the most significant advantages of using ZFS lies in its robust feature set:

• Data Integrity: ZFS ensures that data is accurate and complete through its checksum-based system. This means you can trust your files to be intact, even after experiencing power failures or hardware crashes.
• Snapshots: With ZFS, taking snapshots becomes a seamless process. Snapshots are point-in-time copies of your data, allowing you to roll back to previous versions in case something goes wrong. This feature is particularly useful for backup and recovery purposes, as well as tracking changes over time.
• Clones: ZFS enables the creation of identical copies of your data for testing, development, or disaster recovery scenarios. Clones are essentially read-only copies of your original data, ensuring that you can experiment without risking any damage to your primary files.

ZFS in Action: Proxmox and High Availability

Proxmox is a popular hypervisor that leverages ZFS to provide enterprise-grade storage solutions. By utilizing ZFS’s advanced features, Proxmox enables replication and high availability configurations that ensure business continuity even in the event of hardware failures or other disruptions.

The Power of Replication

In a replicated setup, data is mirrored across multiple disks, providing a safeguard against data loss due to single-point-of-failure events. This ensures that your systems remain operational, even if one disk fails.

High Availability with ZFS

ZFS’s snapshot and cloning features make it an ideal choice for high-availability configurations. By creating snapshots or clones of your critical data, you can ensure that your systems can be quickly recovered in case of a disaster.

By combining the robustness of ZFS with the versatility of Proxmox, you can create powerful storage solutions that cater to your business needs.

Hardware RAID vs. Software RAID (with ZFS)

Now that we’ve covered the basics, let’s compare hardware RAID with software RAID using ZFS:

Hardware RAID

Pros:

• Native support : Most operating systems and BIOS/UEFI have native support for hardware RAID.
• Low overhead : The CPU doesn’t need to handle the RAID calculations.

Cons:

• Limited flexibility : Once configured, changing the RAID setup can be difficult or impossible.
• Hardware dependence : If your RAID controller fails, you’ll need to replace it (and potentially lose data).

Even many Dell Optiplex workstations have support for RAID these days!

Software RAID (with ZFS)

Pros:

• Flexibility : Easily modify or change the storage configuration without affecting performance.
• Scalability : Add or remove disks as needed to scale your storage resources.
• Memory efficiency : ZFS can utilize available memory (RAM) to improve performance, especially for larger datasets. This is known as the “ARC” (Adaptive Replacement Cache), which helps reduce I/O operations and increase throughput.

Cons:

• CPU overhead : The system needs to calculate and manage the RAID setup, which can impact performance.
• Complexity : ZFS requires a good understanding of its features and settings to get the most out of it.

Other Solutions

If hardware RAID and ZFS don’t fit your needs, there are other options to consider.

mdadm: A Software RAID Solution

mdadm, or Multiple Disk Administrate, is a software RAID solution for Linux systems. It allows you to create and manage software RAID arrays, providing features like redundancy, performance enhancement, and capacity expansion. While its popularity has waned somewhat in favor of other solutions, mdadm is still widely used and supported by the Linux community.

Bitrot File System (Btrfs)

Btrfs, or B-tree file system, is a copy-on-write (CoW) file system designed for Linux. It provides redundancy features through its CoW mechanism, where changes are written to new locations on disk rather than overwriting the original data. This allows Btrfs to maintain previous versions of files, reducing the risk of bitrot.

While not as widely used as ZFS or XFS, Btrfs is still an actively maintained file system with some notable features:

• High reliability : Btrfs uses CoW and checksums to ensure data integrity.
• Efficient use of space : Btrfs can reclaim unused disk space by merging CoWs.
• Self-healing : Btrfs can recover from errors using its built-in repair mechanisms.

These alternatives can provide effective solutions for specific use cases, so be sure to consider them when choosing a storage setup that suits your needs.

Summary

In conclusion, both RAID and ZFS are powerful tools for managing storage resources in your homelab. Hardware RAID offers native support and low overhead but is limited in flexibility and dependent on hardware. Software RAID with ZFS provides flexibility, scalability, and data integrity features, but requires more CPU power and a good understanding of its configuration.

Ultimately, the choice between hardware RAID and software RAID (with ZFS) depends on your specific needs and preferences. If you value ease of use and don’t mind sacrificing some flexibility, hardware RAID might be the way to go. But if you’re willing to invest time in learning about ZFS and want a more flexible storage solution, then software RAID with ZFS is definitely worth considering.

<p>The post Weighing the Benefits of Hardware RAID and Software RAID for Your Homelab first appeared on AADSIT.COM.</p>

While it’s uncommon to see a need for a private Certificate Authority to be installed on a decentralized work force, there may still be the occasion where you have internal resources that you want to have a valid SSL certificate on but do not want to, or cannot, use a Let’s Encrypt certificate from the web.

In my case it makes my life a tiny bit easier to use pfSense to manage certificates and create a wildcard certificate for my local domain, giving me an easy to install option for local services not running through my web-accessible reverse proxy. For example, we use Paperless-NGX for document management and I would rather keep that as far away from the internet as possible.

In JumpCloud, every two hours the following command runs:

::https://learn.microsoft.com/en-us/powershell/module/pki/import-certificate?view=windowsserver2022-ps

Import-Certificate -FilePath "C:\Windows\Temp\AADSIT-SUB1-CA.crt" -CertStoreLocation Cert:\LocalMachine\Root

_{You might notice, I make it a habit to start code with comments linking to any reference material used in case I need it again and Microsoft hasn’t broken the link yet.}

This is configured as so, applied to all relevant device groups for my home:

JumpCloud allows you to upload files <1MB in size, a .crt is an easy task for this.

After manually running, we can check the results to confirm that the certificate installation exited with Powershell Code 0, or successful completion:

And indeed we can see this certificate authority is now in the Machine Certificates:

Now so long as we reach a server through DNS at the correct port we will have a valid certificate and no warning for our users:

If you’re pretty new to certificates and stumbled your way into here, please note that the DNS part is pretty important. If the server certificate says “I am xyz.local” but your browser is looking for “192.168.0.1”, they won’t match and you will get an warning unless the certificate has a matching Subject Alternative Name.

If you are interested but haven’t learned how to set up a certificate authority yet, there are a plenty of videos on YouTube that discuss the process. Find one that closely matches your setup; if you have an AD server then AD Certificate Services may be best for you, or if you have pfSense or opnSense you can use that. I believe you can also install the Certificate Services function in regular Windows 10 so there’s no hurdle too difficult to get over to start learning.

<p>The post Installing Trusted Certificate Authority with JumpCloud first appeared on AADSIT.COM.</p>

I had seen Youtube videos of people glueing LEDs to their ceiling or jammed inside paper lanterns, gluing cotton all over it, and calling it good. The effects can be pretty nice but I wanted something smarter. While I’m pretty happy with the end result of this project, if I was to do this again I would design 3D printed spheres instead of using paper lanterns to simplify things.

Hardware:

• WS2811 12v LED Strip (2-3 meters, prices vary)
• ESP8266 ( $3-$5 on AliExpress, I usually use D1 Minis) (1/18/2025: I’ve almost exclusively switched to ESP32s with enough RAM for OTA updates. HomeAssistant allows ESP32s to host a Bluetooth proxy which makes coverage significantly better)
  • Any ESP32 or ESP-01 will also work, but ESP-01 will not usually have enough memory for OTA updates.
• 1x 12v Power Supply with standard size Barrel Plug
• Others:
  • A 12v to 5v adapter
  • 12v female barrel plug
  • 5v+ capacitor
  • 6″ paper lanterns (I got a 10 pack on Amazon for under 10 dollars).

Printables:

There are two main components in my design: The interlocking mount that holds the paper lanterns and LEDs, and the controller box. The ZIP has two different lids for the controller box as I like to make my designs modular.

Construction:

After printing 5 of the mounts and making adjustments as I went I set to screwing, and later gluing, them together. This created a fairly sturdy structure to mount everything to before attaching the paper lanterns to the mount’s hooks and running LEDs throughout.

My workspace is limited, so I chose to use an old painting to protect our mini fridge.

At this point I spent some time working on the controller; I had pieces on order but had to wait for the right power adapters to come in.

You might notice that the controller box is bright blue; it turns out that Pin 4 on this board controls the status LED and should NOT be used for the LED strip pin if you sleep in the same room.

Shot of a “strike”.

Code:

Right now I am getting the best effect out of Twinkle and Fireworks, but it’s my intention to write several Node-Red automations that will randomly change the color to regular lightning colors during the flashes, as well as set brightness and color for normal bedroom ambiance throughout the day.

esphome:
  name: "ledcloud"

esp8266:
  board: d1_mini

# Enable Home Assistant API
api:
  encryption:
    key: "123456789123456789123456789123456789123456789"

ota:
  password: "1234567891423456789123456789"

wifi:
  ssid: !secret wifi_ssid5
  password: !secret wifi_password5

# Enable logging
logger:

status_led:
  pin:
    number: D0
    inverted: true

light:
  - platform: neopixelbus
    type: BRG
    variant: WS2812
    pin: D3
    num_leds: 60
    name: "LED Cloud"
    effects:
      - addressable_color_wipe:
      - addressable_color_wipe:
          name: Color Wipe Effect With Custom Values
          colors:
            - red: 100%
              green: 100%
              blue: 100%
              num_leds: 1
            - red: 0%
              green: 0%
              blue: 0%
              num_leds: 1
          add_led_interval: 100ms
          reverse: false
      - addressable_twinkle:
      - addressable_twinkle:
          name: Twinkle Effect With Custom Values
          twinkle_probability: 5%
          progress_interval: 4ms
      - pulse:
      - pulse:
          name: "Fast Pulse"
          transition_length: 0.5s
          update_interval: 0.5s
      - pulse:
          name: "Slow Pulse"
          # transition_length: 1s      # defaults to 1s
          update_interval: 2s
      - flicker:
      - flicker:
          name: Flicker Effect With Custom Values
          alpha: 95%
          intensity: 1.5%
      - addressable_fireworks:
      - addressable_fireworks:
          name: Fireworks Effect With Custom Values
          update_interval: 32ms
          spark_probability: 10%
          use_random_color: false
          fade_out_rate: 120

Coming up in Part 2:

One of my intentions with this project was to include a real lightning detector; this would be a great addition to my unnecessary HomeAssistant sensors and create the potential for real-time lightning strike simulations during storms; something I know my wife would enjoy.

I purchased a JMCU AS3935 Lighting Sensor and configured it for I2C communication, per ESPHome’s documentation and other online resources. Unfortunately I either have a faulty unit, or the I2C protocol on this device (as reported by some online) is not following the standard and is unreliable; the same setup worked with another I2C device so it’s hard to tell.

I intend to sort out the issues with the live lightning detector as well as add my own automations for part 2, and complete the writeup with several example videos.

1/18/2025: We ended up moving before this could be revisited as we needed more space for our growing family, and while this project gave us a very unique and enjoyable bit of color we ultimately put this in the garage before scrapping the project. The best effects we found were to use the Fireworks mode with a yellowish tint, with Node-Red randomly switching to Blue or even Red for a split second to provide some extra flair. I hope to revisit this someday, maybe even on a larger scale for our daughter!

<p>The post LED Storm Cloud first appeared on AADSIT.COM.</p>

In this case we use ESPHome and some basic hardware with a 3D printed case to create an aquarium friendly sensor and set up some notifications. This assumes you have ESPHome set up and know the basics for creating custom devices and are able to solder; the case requires access to a 3D Printer or creativity and duct tape.

Hardware List:

• ESP8266 (~$3-$5 on AliExpress)
  • _{You can use an ESP8266, ESP32, or ESP-01 but this case design is for the ESP8266 on the Wemos D1 Mini board, and the ESP-01 usually does not have enough memory for OTA updates and requires an external programmer.}
• DS18B20 Temperature Sensor Kit (~$3 on AliExpress)

Code:

#Sources: 
# https://esphome.io/components/sensor/dallas.html
esphome:
  name: "30gallon-aquarium-sensor"

esp8266:
  board: d1_mini

# Enable logging
logger:

# Example configuration entry
dallas:
  - pin: D3

# Individual sensors
sensor:
  - platform: dallas
    address: 0x85000000161dee28
    name: "30G.HOB.Sensor"

# Enable Home Assistant API
api:
  encryption:
    key: "123456789123456789123456789123456789123456789"

ota:
  password: "123456789123456789123456789"

wifi:
  ssid: !secret wifi_ssid5
  password: !secret wifi_password5

This uses the Dallas sensor component in ESPHome. You will likely see a different sensor address at first, which will require reprogramming. I highly recommend using the ESP8266 or ESP32 with enough memory for OTA updates because of this; it just makes life easier.

Case:

I created this model in Fusion 360. The gap is large enough to fit over the lip of a normal rimmed aquarium, at least up to 30 Gallons. Larger aquariums with thicker rims may need adjustment or some reshaping with heat.

I use a Creality Ender 3 Pro, a budget friendly printer which does decently with PLA but not great with ABS without a cover of some sort. My cases were all printed with regular PLA.

I recommend orienting the base face down and reducing the support settings; in Cura you can open Settings Visibility and enable more Support options, reducing the density for example. Because of the weird angles this has been the best printing option I have found without cutting off the sensor neck. Every printer is different though so it may take some adjustments to get the best result for you.

Putting It Together

Once you have the hardware and case ready, remove the supports, slide the sensor up the case neck, trim the cables, and wire everything up. I chose to dip my sensor/neck in liquid silicone to water proof things. Once everything is jammed in there you the USB port should line up with the opening, providing enough space for a USB cable to power the device.

Home Assistant

At this point you should be able to connect it to HomeAssistant, add it to your dashboards, whatever you will do.

I also set up a warning notification if the temperatures in my tanks go out of range. I use Node-Red like this:

I have a maintenance button that will turn off notification checks for an hour and a half; if I’m doing water changes I don’t want notifications.

var states = global.get('homeassistant.homeAssistant.states');
var temp5G = states["sensor.5g_hob_sensor_2"].state;
var temp10G = states["sensor.10g_hob_sensor"].state;
var temp30G = states["sensor.30g_hob_sensor"].state;
//Values
var warningHighTemp = 80.5;
var warningLowTemp = 75;
var emergencyHighTemp = 82;
var emergencyLowTemp = 72;
msg.payload = "";

//temp10G = 40; //override test


if (temp5G < emergencyLowTemp || temp5G > emergencyHighTemp) {
    msg.payload = msg.payload + "Emergency, 5 Gallon aquarium is out of range! " + temp5G + " degrees!";
} else if (temp10G < emergencyLowTemp || temp10G > emergencyHighTemp) {
    msg.payload = msg.payload + "Emergency, 10 Gallon aquarium is out of range! " + temp10G + " degrees!";
} else if (temp30G < emergencyLowTemp || temp30G > emergencyHighTemp) {
    msg.payload = msg.payload + "Emergency, 30 Gallon aquarium is out of range! " + temp30G + " degrees!";
} else if (temp5G < warningLowTemp || temp5G > warningHighTemp) {
    msg.payload = msg.payload + "Warning, 5 Gallon aquarium is out of range! " + temp5G + " degrees!";
} else if (temp10G < warningLowTemp || temp10G > warningHighTemp) {
    msg.payload = msg.payload + "Warning, 10 Gallon aquarium is out of range! " + temp10G + " degrees!";
} else if (temp30G < warningLowTemp || temp30G > warningHighTemp) {
    msg.payload = msg.payload + "Warning, 30 Gallon aquarium is out of range! " + temp30G + " degrees!";
} else
    msg.payload = "All good!"

return msg;

I haven’t taken a coding class in over a decade and learning to optimize my functions hasn’t been a priority, so don’t judge. The long story short is that every few minutes (if Maintenance is off) the JavaScript function checks each tank’s temperature against the lows and highs I have set with the above code.

It passes the results to a switch which ignores the “All good!” message, directs warnings to a Push notification link, and Emergencies to a Push notification link as well as a function that will pass the message to the Google Nest Minis we have in every room that has detected occupancy, ensuring that emergencies will wake us up or other. TTS will announce exactly what tank and temperature set off the warning. Triggers prevent the notifications from occurring constantly once activated.

If you haven’t switched to Node Red yet, I highly recommend it; the ability to link automations alone is worth it.

That’s really all there is to it. Please do not take this design and and try to sell it online, STLs are protected by copyright and eventually I’ll figure out the right disclaimer to add.

<p>The post HomeAssistant Aquarium Temperature Sensor first appeared on AADSIT.COM.</p>