It's been on my mind since we moved into our new home that I wanted to somehow add our pool's temperature to HomeKit. Just being able to see if the pool is warm enough for swimming would be worth it alone, but a ton of other automations could follow.

After searching for existing products, for which there were none, I had to fall back to crafting my own solution. Other than woodworking, I really didn't have the means to create something that I felt was both safe and didn't look like total garbage.

Enter 3d printing...

A close friend of ours, who is really into 3d printing, knew we were interested in getting a 3d printer at some point and was keeping an eye on deals for us. A good price on a Sovol SV-01 popped up one day and we jumped on it.

I've had several ideas about how to do this, including inserting a temperature probe in our post-pump piping, inserting one in the strainer basket, and creating a floating temperature probe. The first option scared me since it required drilling a hole into our piping. The second and third options both seemed viable but I preferred the float approach.

Design

After getting the 3d printer dialed in and learning the basics of Meshmixer and Cura, I set about creating some prototypes. I eventually landed on a conical shape with the probe sticking out of the tip of the cone. This way, it would float due to the ballast at the top and the temperature probe would always be in the water since the battery weight would be in the cone. The electronics would sit at the top, above the battery and temperature probe. A screw cap would be sealed to the top to keep water out.




As you can see in the pictures, the probe sticks out of the tip and the wire runs inside the cavity past the NiMh battery to where the circuit board will be mounted to a mounting plate. After testing whether it would actually float the way I wanted it to (it did), I started working on the electronics

Electronics

I needed this project to be super low-power, so I opted to use a variant of the ESP8266 that is designed with low power applications in mind: the ESP-01. This version of the ESP8266 does not have UART, so you will need a USB to Serial adapter and a way of regulating the voltage down from the 5 volts USB provides to the 3.3 volts the ESP-01 requires. Some people say you can use 5 volts and get away with it, but I'd rather not risk it.

I also needed a power source. I considered using solar to charge a battery, but decided to keep version one simple. Besides, if I can get the battery usage low enough it can run for months and in some cases years on a single charge, battery characteristics being the major wildcard in that calculus. I decided to go with a 6V 2400 mAh NiMh battery since it's safer to use in the water as opposed to lithium ion. It too would need its voltage regulated down to a safe 3.3 volts, which I did with a MCP1700 voltage regulator.




In order to measure temperature, I used a simple water-proof version of the DS18B20 temperature sensor. As opposed to the bare DS18B20 that can be mounted direcetly to a PCB, the water-proof version comes within a sealed steel sleeve that fits nicely at the end of the probe. I used a small amount of sealant around the probe, but it was mostly sealed due to the tolerances between the probe and the float.


I am a novice when it comes to creating electronics so there was a bit of a learning curve here with regards to how to wire everything together, but I figured it all out pretty quick. Here is the first version of the PCB finished. I added some pins for easy programming in case I needed to reflash the firmware. I also added some comformal coating to the PCB just in case moisture gets in.



And here is the final product, sans lid.

One problem with the ESP-01 is that it doesn't natively support deep sleep. This is a mode you can put the ESP-01 into where it uses an extremely low amount of power, wakes itself up periodically to perform a task, and goes back to sleep. You can get literal years out of these on a single charge if your battery will allow for it and its done right. However, like I said, it isn't supported natively out of the box. In order to enable it, you have to do some extrenely precise soldering between a pin on one of the ICs and the reset pin of the board. I followed this Instructables guide in order to make sure I got it right. It took several attempts before I got it, but eventually I was successful. It was extremely tedious...

Software

Updating the firmware on an ESP-01 is done using the Arduino IDE. I would share the code, but it's fairly custom to my set up. I have the ESP-01 turning on, connecting to WiFi, reading the temperature, and logging the temperature value to an instance of Homebridge's HTTP Temperature sensor library and an InfluxDb instance I run on my server for historical data as well as Grafana graphs. After that, I tell the ESP-01 to sleep for 10 minutes and repeat.

After doing that, I can perform automations in HomeKit as well as render some pretty sweet graphs of the temperature changes throughout the day. As you can see, I've put these in a few places around the house to model how the temperature changes throughout the day. Needless to say, attics in Florida get extremely hot, and its not even summer yet!

Final Thoughts

This project is definitely still in progress and I have some thoughts on improvements for the next version. Some things I would do differently would be to not use a screw-top to seal the lid. The threads never really worked very well, making it nearly impossible to get it on very far. I'd also probably use a different shape as this took forever to print and could probably be made a lot simpler. Another change will be to switch out the batteries for LiPo after a while. Lastly, I wouldn't print it in PLA. From what I've read, it's not the best to use in water and may eventually fail. Luckily, it's not a hard project to recreate so we'll see how version one does.

In the end though, it's working well and I'm pretty proud of it. Battery life seems promising and if my current calcuations are correct, it should last for at least a year on one charge. Even if it only lasts a few months, that would be totally fine by me since charging doesn't take long. Updates forthcoming!

A few weeks ago we wrapped up our first job within Dusk City Outlaws, a game that I'd been really excited to play for quite some time. Some friends of ours had started a job with us pre-quarantine but getting together to finish it became somewhat of a chore and eventually it fell by the wayside. A couple months into quarantine and we all needed an escape, so it felt like a good time to get The Right Kind of People together and do some crimes.



After getting familiar with the rules and watching some videos of jobs (this Hat Films series where they play The Canal Job is a must watch), I wound up selecting The Ship Job for our playthrough. It took us 3-4 sessions to get through the job despite it being a game that in reality can be played through in a day. That's mostly due to the fact we can only play one day a week and only after hours since we have children. It's also due to us roleplaying way more than we should have, but I'll get to that later...

One of the first things a new Dusk City criminal will notice is that a lot of the world building is done by the players themselves. The job gives a basic outline of who the NPCs are in the story, their motivations, and the setting but everything else is decided by The Judge or the players. When a player sets out to Case The Joint, they usually describe what the area they are casing looks like. The Judge then decides what, if any, intel the person gathers from that particular scene or if they run into any trouble.

This was a lot of fun as it involved everyone in worldbuilding and didn't place a huge upfront burden on The Judge to flesh out a full campaign as something like 5e does (if you're rolling your own campaign). This lead to some great scenes such as our Gravedigger player (my wife) inciting hysteria about a plague near the docks to help clear some of the dock workers during the heist.

As with all new things, I also made a lot of small mistakes in this campaign. I now have a better feel for the mechanics and things to avoid. One of the bigger mistakes I made was letting my heat build up. Heat is the resource that The Judge spends to introduce complications to the job. I introduced the players to a couple small complications, but I was enamoured with the prospect of a plot twist later on in the job. The only issue is if you wait too long in the job to reveal the plot twist, you may run into a situation where the players don't have much time to react to it.

In this job in particular, I introduced a plot twist on the last day of the job. The plot twist was that while they were executing the job, pirates attacked the harbor. Because it was the final day of the job, the only real thing the players could do was to take advantage of the situation and try to get out during the mayhem. They succeeded, but it felt like I had pulled the rug out from under my players. They had spent the whole job setting up their plans and even had contingency plans in place if that fell through and then I literally and figuratively blew up their plans by throwing this huge obstacle at them without any time to react in a meaningful way.

Kind of a bad move in hindsight...

Next time I'd like to play in a way that adds suspense over time and maybe save a little extra for something special towards the end, but no way will I be hoarding heat like I did this time.

Some other points I got out of this playthrough was the importance of really limiting planning to planning scenes and not making everything into a drama scene. Planning in Dusk City Outlaws happens in 15 minute scenes and is limited to that scene. You literally start a timer. We have a talkative bunch of players and they can easily eat that time up twice over if you let them. Let that happen enough and you look at your clock to see it's midnight. The Judge needs his/her beauty sleep after all...

Related to the last point, in 5e campaigns roleplaying is what we spend a lot of our time doing. That doesn't quite work in Dusk City if you want to finish a job in a reasonable amount of time. If someone has an ability to do something and it's reasonable that they could do that thing, you don't need to roleplay. If a Gravedigger wants to oversee a burial somewhere, why would you make that any more difficult than it needs to be? Let them describe the scene and get on with your day. Roleplaying took up a lot of our time when it didn't have to.

I don't mind roleplaying more than Dusk City expects, but a line does need to be drawn somewhere or else it can make things take significantly longer than they need to.

Overall, I really really enjoyed playing Dusk City Outlaws. It's become my go-to when we want to play a short RPG campaign. Definitely check it out if you like table top gaming even the slightest.

Building a RetroPie based bartop arcade has been something I've had on my project list for quite some time now. As I mentioned with the bay window seat project, for our family quarantine has been a time of taking on smaller projects that we've been putting off for some time. This is the one I've been most excited about, especially since I've been slowly earmarking parts for it for a while now. I couldn't be happier with how it turned out.


After finishing the bay window seat project, I had a 4'x8' sheet of ¾" plywood left over which is more than enough to build a bartop arcade. I decided to go with a modified version of the popular Weecade design after taking into account the size of my screen. I decided on those plans mostly because I liked the profile of the cabinet a bit more than the oft mentioned Galactic Starcade cabinet from Instructables.

My woodworking skills are still novice at best so I made a lot of mistakes, but nothing that I couldn't cover up or account for in some other way. The plans for this project had many more odd angles that I had to account for which was a challenge but I learned quite a lot in the process. Here are some more pictures of the finished cabinet. I've had a blast playing with it and I'm so glad I've been able to share a little slice of my childhood with my children.



 

For our family, quarantine has been a time filled with the same emotions most other compassionate human beings have had. Like many other families who are so lucky to still have both their jobs and health, we've taken to working on home projects to fill the time. We bought a new house about a year ago in a new city and have been slowly making it our own.

One of the bigger projects we wanted to undertake was adding a window seat to our office's bay window. I've done one or two small wood working projects in the past (to very little success) but never anything of this magnitude. This seat was to be a 10'x2.5' monster that also contained hidden storage and cubbies along the front. Way over my pay grade, for sure.

I was lucky enough to inherit some great tools over the years, including a bandsaw, drill press, and table saw which absolutely helped me get over some of the harder aspects of this project. I had a lot to learn even with those tools. Even still, things turned out pretty well and I'm really happy with the results. The animals seem to like it and it got the official napping okey-dokey from me earlier today.

I have a couple more projects that I plan on working on now that I have some new found confidence including a RetroPie Bartop Arcade and a nice dog bed. For now, I need to clean my garage for christ's sake...

My wife and I have been using YNAB for several years now and really enjoy it. We have our ups and downs with it, but on the whole it's been a great addition to our financial lives. The main problem we have with it is just getting off the rails sometimes and not checking our balances before we purchase things (ahem, more groceries).

I've wanted a way to make certain category balances appear more prominently in places where I'm likely to passively see them. Places like on my Apple Watch, my Today Widgets, and within the app in a large, easy and quick to read way. It's not that YNAB makes it hard to see your category balances, but that I want them in my face in ways I'm not sure they'd ever add.

So that's how Allowance for YNAB was born. The You Need a Budget team announced an API a couple months ago and I jumped on it.

I also saw a potential for this to be used by people in a YNAB household who just want an answer to the question, "How much money can I spend on X right now?" People like kids in your family that have an allowance or maybe other members of the family that just aren't as interested in actively maintaining and monitoring the budget.

Hopefully it can help some of those people make better financial decisions. It's already been helpful for me.