| • Starlink kit arrival and expectations
|
| • Setup requirements for Starlink at home, including a dedicated PC
|
| • Geographic restrictions on Starlink usage, such as grid reference points and service address updates
|
| • Potential issues with high power consumption of the dish (150 watts)
|
| • Cost of the Starlink kit ($485) and monthly service fees
|
| • Benefits of reliable internet, especially for remote work and online learning
|
| • Ping times and latency expectations for Starlink (40-60 ms)
|
| • Comparison to LTE connectivity and potential advantages of Starlink
|
| • Concerns about rural internet access and the limitations of current options
|
| • Starlink as a potential solution for reliable internet connectivity
|
| • The impact of limited internet access on remote work and personal life
|
| • Excitement about Home Assistant's official Tuya integration, but concerns about cloud dependence
|
| • Preference for local control protocols such as Zigbee or Matter over cloud-dependent solutions
|
| • Discussion of Z-Wave and Zigbee devices
|
| • Release update for Home Assistant
|
| • Statistics on Home Assistant usage and user behavior
|
| • New features in Z-Wave.js integration, including improved security and reliability
|
| • Migration to Z-Wave.js from OpenZW or original Z-Wave setup
|
| • Developers' confidence in the new Z-Wave.js integration
|
| • Potential official certification of Z-Wave.js from the Z-Wave group
|
| • Improved pairing process for Z-Wave devices
|
| • The host discusses opening a repository in VS Code using the browser on github.com
|
| • Features of VS Code in the browser are demonstrated, including automatic commit and merge requests
|
| • The Linux kernel course on A Cloud Guru is announced
|
| • Home Assistant releases a new hardware project called Amber based on the Compute Module 4
|
| • Concerns about upgrading to a future CM5 module are raised due to the Raspberry Pi 4's lifecycle
|
| • I/O limitations of the Raspberry Pi 4 are mentioned and how EMMC or SSD solves this issue
|
| • The speaker discusses their experience with a device that is no longer available, the "blue", and notes its limitations compared to other devices.
|
| • They speculate about the future of the blue board, which may be phased out in favor of newer models.
|
| • The conversation turns to Home Assistant and its software updates, including the addition of 400 new icons.
|
| • The speaker expresses enthusiasm for the updated icons and mentions a rumored icon picker feature.
|
| • A sponsor advertisement is inserted, promoting Linode's cloud computing services.
|
| • Linode cloud computing services, including VLAN support, DNS manager, Terraform, and Kubernetes integration
|
| • Benefits of using Linode, such as lower pricing (30-50% cheaper) and flexibility in deployment across multiple clouds
|
| • Importance of avoiding vendor lock-in and having a multi-cloud strategy
|
| • Discussion of recent Facebook outage and its impact on user experience
|
| • Comparison of the Facebook outage to other tech companies' outages, including speculation about intentional sabotage or whistle-blower-related motives
|
| • Home Assistant energy monitoring support and setup for smart plug integration
|
| • User has difficulty getting energy monitoring working in Home Assistant
|
| • Home Assistant wants data in kilowatt hours, but user's smart plugs report in watts
|
| • Need to use a math integration to convert watts to kilowatt hours
|
| • Must create template sensors for each smart plug to format data correctly
|
| • Process is more complex than expected and requires learning about templating and sensor creation
|
| • Energy utilities built into Home Assistant can then pull stats from the formatted devices
|
| • The speaker felt overwhelmed by the complexity of Home Assistant and the introduction of new energy monitoring features
|
| • Many resources for Home Assistant are outdated due to its fast-paced development
|
| • Setting up utility meters and history stats integrations allowed the speaker to collect and display historical power usage data
|
| • Virtual sensors were created using these integrations, enabling dashboards that provide valuable insights into energy consumption patterns
|
| • The speaker prefers their custom-built solution over the built-in energy support in Home Assistant
|
| • Discussion of TubeSync, a tool that pulls down YouTube videos and provides a dashboard with features such as video source tracking and upcoming content.
|
| • Mention of MediaCMS.io, a self-hosted YouTube front-end clone that allows for curation of approved channels and playlists.
|
| • Potential use of TubeSync to download videos from YouTube and then importing them into Plex for archiving.
|
| • Discussion of using MediaCMS.io to create a pseudo-Youtube instance for personal use.
|
| • Review of MediaCMS.io features, including dark mode, light mode, and multiple transcoding profiles.
|
| • Experimental support for remote workers
|
| • Backing up iPhone photos using iCloud and a tool called Gimme-iPhotos
|
| • iOS restrictions on background APIs
|
| • Comparing iOS to Android in terms of device management
|
| • Using Python to automate tasks with the Gimme-iPhotos tool
|
| • Two-factor authentication mechanism supported by the tool
|
| • Discussion of a tool that can download photos from iCloud
|
| • Tool uses an official Apple API and can run on a NAS box
|
| • Killer use case: accessing iOS phones' photos via a NAS box, especially for elderly relatives who struggle to transfer photos
|
| • Uncertainty about two-factor authentication token expiration time
|
| • Proposal to test the tool with parents' devices and report back in 6 months
|
| • Backblaze's 30-day money-back guarantee and return policy
|
| • Peace of mind with physical hard drive backup via FedEx
|
| • Additional features, including retention history extension and mobile apps for accessing files on-the-go
|
| • Reviews and recommendations from reputable sources such as New York Times, Macworld, and Tom's Guide
|
| • Availability of a free 15-day trial at backblaze.com/SSH
|
| • Company background and growth, with over 500,000 customers in 175 countries
|
| • Mention of Tailscale and its availability on Synology
|
| • Discussion of Tailscale and its ease of use compared to WireGuard
|
| • Setting up Tailscale with Synology NAS devices for remote access
|
| • Positive feedback from listeners about using Tailscale
|
| • Comparison between setting up Tailscale and setting up WireGuard
|
| • Various ways to install and use Tailscale (e.g. on phone, desktop, server)
|
| • ZeroTier, a distributed WAN solution and alternative to Nebula
|
| • Comparison with Tailscale and WireGuard protocols
|
| • Discussion of self-hosted options for networking solutions
|
| • Mention of upcoming DNS solution from ZeroTier
|
| • Plug for Nebula and discussion of various networking projects
|
| • Home Assistant setup for energy monitoring and automation
|
| • Z-Wave device updates and potential lag issues
|
| • Using Matrix, Discord, or Telegram for community support
|
| • Integrating devices to avoid circuit overloading concerns
|
| • Solutions for energy monitoring in self-hosting communities |
