| • The user is experiencing issues with their Starlink connection in an area they frequently visit
|
| • The user is located near the border of two service areas, resulting in inconsistent connectivity
|
| • A website (satellitemap.space) was mentioned that shows the country divided into hexagons representing different Starlink cells
|
| • The user notes that this representation may be oversimplified and actual cell boundaries are more nuanced
|
| • The user discusses the issue of moving with Starlink, as it's designed to be stationary and can't accommodate frequent relocations
|
| • The conversation also touches on the potential for a mobile version of Starlink and its implications for rural areas
|
| • 5G technology is mentioned as another option that could potentially compete with or complement Starlink in terms of connectivity
|
| • Government contract worker lives on a boat and uses 4G
|
| • RV owner struggles with integrating Home Assistant for their vehicle
|
| • Z-Wave support in Home Assistant will be deprecated due to Python version updates
|
| • Migrating to Z-Wave.js has been problematic and may require re-pairing devices one by one
|
| • Matter protocol is expected to arrive soon, but Home Assistant's planned deprecation of Z-Wave support may make it difficult for users to wait
|
| • Mixed messaging from developers about recommended upgrades to Home Assistant
|
| • Breaking changes causing user fatigue and hesitation to upgrade
|
| • Comparison of Home Assistant's complexity to other smart home systems like Apple's HomeKit
|
| • Discussion on the need for better documentation, education, and accessibility for users
|
| • Acknowledgment that Home Assistant's modular design is a strength, but also a challenge
|
| • Hope for future improvements in automation and user experience as the project matures
|
| • Recognition of the importance of considering the needs of new users who will arrive with hardware devices
|
| • Home Assistant compatibility with various devices and platforms
|
| • Comparison between Apple, Echo, Google smart home systems
|
| • Maintenance and updating of Home Assistant Core and its impact on security
|
| • Linode cloud services and their benefits for hosting Home Assistant
|
| • TrueNAS Scale release and its shift from FreeBSD to Debian 11
|
| • TrueNAS product still focuses on ZFS as primary storage file system
|
| • Can scale out storage across multiple systems with Gluster and Helm management
|
| • Use case is for companies that need high-performance storage, potentially larger than home users or small businesses
|
| • May target companies with similar needs to Linus Media Group, such as KVM virtualization and GPU pass-through
|
| • Comparison made to Unraid, another popular NAS software option
|
| • The speaker is discussing a local backup system using TrueNAS Scale on a LAN box to duplicate a ZFS array between two locations in their home.
|
| • The speaker installed TrueNAS Scale and noticed an available update, but the update also required a significant amount of additional updates (2GB).
|
| • The speaker encountered issues with importing a ZFS pool after updating, which seemed to resolve itself after a reboot.
|
| • The speaker experienced further difficulties attempting to import the pool via the command line, requiring multiple reboots and attempts.
|
| • The speaker expresses frustration with the lack of documentation and support for TrueNAS Scale.
|
| • The speaker returns to using Proxmox after struggling with TrueNAS scale
|
| • They prefer simple and basic setups, managing them with Ansible for ease of recovery from failure
|
| • Tailscale is mentioned as a zero-config VPN solution for secure remote access to devices and servers
|
| • A listener asks about maintaining Nextcloud in a home lab, seeking advice on monitoring and security measures
|
| • The speaker advises loading only necessary apps in Nextcloud and double-checking their usage
|
| • Importance of two-factor authentication for Nextcloud
|
| • Keeping Nextcloud up-to-date with regular updates and SSL enabled
|
| • Challenges of updating multiple instances of Nextcloud
|
| • Using containers (e.g. Docker Compose) for repeatable deployment methods
|
| • Deploying Nextcloud using different methods (Snap, container, host)
|
| • Need to keep track of deployment settings to avoid data loss
|
| • Unraid as a GUI-based option for containerization and self-hosting
|
| • Unraid and its simplicity in data management
|
| • The community support for Unraid, including YouTube tutorials
|
| • Potential drawbacks of Unraid as user complexity increases
|
| • Alternative options for managing disks and applications, such as FreeNAS Scale and Docker Desktop on Mac OS
|
| • The possibility of using Home Assistant for app management and containerization
|
| • Other alternatives like CentOS or Ubuntu with Cockpit, and the importance of aligning with one's values in software choice
|
| • Plans for a JB East Coast meetup and potential crowdfunding options
|
| • Planning a meetup in Raleigh, NC on April 9th
|
| • Proposed event will take place at Prime Barbecue and Oak City Brewing
|
| • Details to be posted on meetup.com closer to the time
|
| • COVID-safe location with outdoor space for gathering
|
| • Weather in Raleigh expected to be pleasant in April
|
| • Invitation extended to join the meetup and Jupyter Broadcasting group
|
| • Sponsorship and support options mentioned, including Tailscale and network support at jupiter.party |
