
I'm a jack of all trades with deep expertise in infrastructure, cloud, networking, and devsecops. In my spare time I also like to play around with self-hosting, embedded devices, camping, permaculture, sailing, and scouting
Search for a command to run...

I'm a jack of all trades with deep expertise in infrastructure, cloud, networking, and devsecops. In my spare time I also like to play around with self-hosting, embedded devices, camping, permaculture, sailing, and scouting
No comments yet. Be the first to comment.
This is a series that goes into how I built a zwave & zigbee access point and installed it into my kitchen island leveraging zigbee2mqtt, zwavejs2mqtt, and traefik.
Adding docker to a bare Pi3 and running zwavejs2mqtt in a container
Don't bother!

With Typescript and CDK

Lets think about why we allow streaming updates to production, and what might be some other options
DampRid is great stuff for dealing with excess humidity. Lots of boaters (and hunters, and countless other folks) use it to keep less frequently used spaces fresh and free of mold and mildew. The only real downside is that it's expensive. A 3 pack of...

Overall, the boat is in pretty good shape, or so it seems to me. Reminder: I'm very new to boat ownership - This is my first! After giving it a thorough once over, I've worked out the following... Airflow Unfortunately, the docks at the lake do not h...

Sometimes it seems like home automation protocols are isolated islands, preventing devices from being truly useful. Sure, you can find integrations for the big services, but what about the obscure devices? I'm a fan of interoperability and local control wherever reasonable. It's not that I'm against Alexa's or other cloud controlled systems, but I try to keep them where they can't do that much damage if they stopped working. As such, I embrace Home Assistant and the more open protocols where-ever possible. So when the opportunity came up to redo my automation setup and introduce a lot more controllable tech into my life, I jumped on it. This is the first post in a series on how I implemented my Home Assistant <-> Z-Wave/Zigbee bridge.

Here's the opportunity: my kitchen as it stands now... It's a bare canvas! With everything open like this, and new fixtures being selected, it's the perfect time to add a serious dose of control-ability into my home.
My goals for this project are fairly simple: I want a device that can bridge my Zigbee and Z-Wave devices to Home Assistant via MQTT. I want it to be stable, relatively secure, and easy to maintain. Now, just because the goals are simple, doesn't mean the implementation will be... Because, to me, stability and ease of maintenance means putting it in Docker containers... And that brings some complexity with it.
Further, I want this to be a stable platform that I can build on over time. My kids love RGB LEDs and other cool tech, so having a reliable home control network is important to nurture that love going forward.
What devices do I want to support, exactly? Here's a list, with handy Amazon links. They're not affiliate links yet, though. I'm not sure if I want to get into that whole world or not, yet.
In the next post in this series, I'll dive in and configure docker and zwavejs2mqtt on an old Raspberry Pi 3 that I had lying around. I don't have controllable devices installed, yet, but I can at least start getting some signal data.