| • Introduction to episode 68 of Self-Hosted and welcome to Chris and Wes Payne
|
| • Discussion of the upcoming Jupiter Broadcasting East Coast meetup on Saturday
|
| • Description of the town event happening during the meetup, including food trucks and activities
|
| • Tour of Alex's new house, including its size and layout
|
| • Explanation of Alex's solar setup, including an 8 kilowatt array and monitoring system
|
| • Technical details of how power is brought into the house through a metal conduit and SolarEdge inverter
|
| • Discussion of a Wi-Fi bridge and its connection to the internet
|
| • Mention of a Zigbee bridge that kept dropping out
|
| • Explanation of how devices are connected using Ethernet cables and solar panels
|
| • Reference to Home Assistant software and API access
|
| • Discussion of smart breaker panels and energy monitoring technology
|
| • Analysis of home power usage using machine learning
|
| • Comparison between different appliances' power consumption
|
| • Proposal for a whole house UPS system
|
| • Inspection of a server basement with custom-built rack
|
| • APC UPSs
|
| • Modem and router setup
|
| • Server rack with multiple disks (spec not mentioned)
|
| • OpenSense firewall
|
| • Network switches (POE switch with cameras and access points)
|
| • Temperature sensor (ESP8266 and DHT22) and future placement consideration
|
| • Zigbee setup (Combi USB and connections to UPS)
|
| • Proxmox box and its components
|
| • Home assistant installation on i5-8500 system
|
| • KVM switch and H-top keyboard sharing software
|
| • Future projects: rewiring, Ethernet upgrade, camera additions, wall mounting switches
|
| • Server location and backup systems
|
| • Potential damage to servers in case of a natural disaster
|
| • Storage for equipment and gear
|
| • Backup power supplies and switch gear
|
| • HD tuner and over-the-air TV setup
|
| • Blue Iris server and automation system
|
| • Temperature sensors and control buttons
|
| • The speaker is using an ESP32 to connect Bluetooth sensors throughout a building
|
| • Various objects have been augmented with 3D printing solutions
|
| • The speaker has many projects in progress or to-do, including home automation gear and Wyze cameras
|
| • There are multiple Raspberry Pi computers within arm's reach of the speaker
|
| • A vulnerability was discovered in the Wyze V1 camera, prompting concerns about security
|
| • Wyze camera vulnerability allows remote access
|
| • Wyze responded to the issue, stating local network access is required to exploit
|
| • V1 cameras were vulnerable, while V2 and 3 had an update released months ago
|
| • Wyze handled the situation poorly by discontinuing the model without proper communication or support for users
|
| • The company's handling of the vulnerability could harm their reputation and aspirations as a major IoT vendor
|
| • Discussion of Wyze cameras' quality and price
|
| • Concerns about data collection and monetization by Wyze
|
| • Using a blocked DNS request as a workaround for camera internet access
|
| • Trade-offs between convenience, cost, and functionality
|
| • Wyze's expansion into the smart home ecosystem and its implications
|
| • Discussion of Linode's support for running Matrix server
|
| • Upgrading Linode to 96 gigs of RAM and 48 CPU cores
|
| • Using WiseBridge on Linode for remote access
|
| • Comparison of Linode pricing to other hyperscalers
|
| • Features of Linode's command line tool and API
|
| • Availability of 24-7 customer support by phone or ticket
|
| • Introduction to Plex's new universal watch list feature
|
| • Discussion of Plex's transition from Plex Pass to ad-supported model
|
| • Concerns about data upload to servers
|
| • Client-side changes in Plex app
|
| • Business model and feasibility of searching across multiple streaming services
|
| • Challenges with DRM (Digital Rights Management) and maintaining a smooth user experience
|
| • Comparison to other apps like Trakt.tv and JustWatch.com
|
| • Features and functionality of the new Plex search feature
|
| • Discussion of Plex and its evolution, with the speaker noting that it's no longer primarily focused on pirated content
|
| • Comparison of Plex to Jellyfin as a viable alternative for media streaming and home entertainment
|
| • New features in recent Jellyfin releases, including transcode fixes and DLNA improvements
|
| • Criticism of Jellyfin being written in C# and its potential impact on community contributions
|
| • Discussion of music hosting and playback options outside of the Plex ecosystem, specifically Sonic XD and Symphomium
|
| • Personal experience with Plex Amp and its limitations for large music collections
|
| • Reflections on Spotify and other music streaming services, including a personal decision to remain cancelled.
|
| • The speaker used to use Google Play Music and now uses Plex Amp
|
| • Discussion about uploading personal music collections to streaming services (Google Play, Apple Music)
|
| • Snoop Dogg removing his album "Doggy Style" from Spotify to sell as an NFT on Plex Amp
|
| • New version of Home Assistant released with various new features, including group management and entity hiding
|
| • The speaker is unhappy that their Z-Wave integration was dropped in the latest version, preventing them from upgrading
|
| • Upgrading to a new version of Home Assistant is required but difficult due to Z-Wave migration issues
|
| • User is frustrated with the timing of the upgrade, which coincides with their travel and need for remote work setup
|
| • Learning Python or alternative solutions like Tailscale and Node-Red are considered to maintain control over system
|
| • Migration wizard failed to assist in upgrading to supported versions
|
| • Alternative VPN solution (Tailscale) is promoted as a convenient option for secure remote access
|
| • Tailscale network setup for kids' computers
|
| • Device compatibility with Tailscale (Arch x86 boxes, Raspberry Pi, iPads, Android devices)
|
| • Benefits of using Tailscale (consistent network IP, single sign-on provider integration, two-factor authentication)
|
| • Feedback from Josh on self-hosting and SBC-based NAS
|
| • Discussion on power consumption and compromise between low power and small form factor solution
|
| • Introduction to Compute Module 4 and its advantages for building a reliable NAS
|
| • Wildcard TLS certificate distribution across multiple Linode servers
|
| • Propagating certificates automatically each month using various methods (SSH, Ansible Vault, cron jobs)
|
| • Ensuring security and protection of SSH keys, certificates, and connection credentials
|
| • Exploring alternative solutions such as S3 object storage for storing and distributing secrets
|
| • Discussion of secure authentication mechanisms for accessing stored secrets
|
| • Discussing a hypothetical solution to a problem
|
| • Decryption password stored in plain text on remote systems
|
| • Difficulty with synchronizing data across multiple systems
|
| • Seeking listener suggestions and solutions for the mentioned problems
|
| • Shoutouts and thank yous to SRE subscribers, Boosters, and listeners
|
| • Discussion of the show's contact page and social media presence (Twitter and Discord)
|
| • Mention of a self-hosted matrix server and its community
|
| • The host shares horror stories about self-hosting Matrix in Linux Unplugged
|
| • Self-hosting is manageable for small groups of people (5-100) but can be problematic for larger groups (hundred+)
|
| • A specific episode on Linux Unplugged covers issues with default config settings (link provided: linuxunplugged.com/452)
|
| • The host mentions Coda Radio and its show notes website (notes.jupiterbroadcasting.com) for more information
|
| • The podcast is self-hosted and the current episode can be found at self-hosted.show/68 |
