Built for my homelab. Shared with the community.
iSSU Open Homelab is a collection of personal projects created to solve real needs in my home infrastructure.
These projects are designed, tested and improved through everyday use. Some are stable tools, while others are public experiments still under development.
The goal is simple: build practical solutions, document them clearly and share what may also be useful to others.
Interfaces, integrations and tools for managing the home through Home Assistant and related platforms.
Documented and reusable network configurations, with a focus on segmentation, security and maintainability.
Projects for self-hosted services, virtualization, containers and homelab management.
Tools that reduce repetitive work and connect different parts of the infrastructure.
Documentation, templates and common resources used across the iSSU ecosystem.
A modular LCD-inspired climate card for Home Assistant.
ThermoMatrix provides a compact interface, visual configuration, responsive controls and support for different languages and themes.
Area: Home Automation
Status: Active Development
Documentation: In progress
A native and configurable climate controller for Home Assistant.
ThermoPilot combines multiple environment sensors, presets and hardware commands in reusable thermostat instances, with optional dedicated power feedback for confirmed physical state and manual-operation detection.
Area: Home Automation
Status: Active Development
Documentation: Available
A native Home Assistant integration for resilient consumption accounting, monthly cost reports, forecasts and portable CSV archives.
Energy Report supports cumulative-energy sensors, instantaneous power sensors or both, while preserving its ledger across meter resets and replacements.
Area: Home Automation · Energy Management
Status: Stable
Documentation: Available
An AppDaemon application for managing electrical loads through Home Assistant.
It monitors power usage and automatically controls configured devices, with photovoltaic support, notifications and MQTT discovery.
Area: Home Automation · Automation
Status: Active Development
Documentation: Available in Italian; revision planned
A self-hosted dashboard for personal services and homelab applications.
It provides a central interface for organizing and accessing services, with Docker deployment, multiple themes and optional authentication.
Area: Infrastructure
Status: Active Development
Documentation: Available in Italian; revision planned
A reproducible Matrix-inspired i3 desktop theme for local and remote sessions.
It packages the i3, i3blocks, Rofi, Picom, GTK and terminal configuration used in the homelab, with automatic backups and checksum-verified installation of the historical Matrix icon theme.
Area: Infrastructure · Shared Resources
Status: Active Development
Documentation: Available
An archived AppDaemon climate controller for stateless infrared devices.
It uses power consumption as real-world feedback to verify commands, detect external operation and keep Home Assistant synchronized with the controlled device. It has been superseded by ThermoPilot and remains available for reference.
Area: Home Automation · Automation
Status: Archived · Superseded by ThermoPilot
Documentation: Historical reference
A modular and documented framework for managing MikroTik RouterOS configurations.
The project focuses on structured firewall rules, VLAN segmentation, routing policies and reusable configuration modules.
Area: Networking
Status: Active Development
Availability: Coming later
Projects can be public at any stage of development. Their current maturity is always stated clearly so that users know what to expect.
| Status | Meaning |
|---|---|
| 🟢 Stable | Used regularly and considered reliable for its documented purpose. |
| 🟡 Active Development | Used and actively developed. Features or configuration may change. |
| 🔵 Experimental | Published for development and testing. Not recommended for regular or production use. |
| ⚪ Archived | No longer actively maintained, but kept available for reference. |
A public repository does not automatically mean that a project is ready for everyday use. Experimental projects include a clear warning in their documentation.
- Solve a real problem.
- Build for actual use.
- Keep the structure simple and reusable.
- Treat documentation as part of the project.
- Test changes in a real homelab.
- State limitations and maturity clearly.
- Improve projects gradually.
Most projects begin as solutions for my own infrastructure.
They may be published early when a public repository is useful for testing, versioning or working across multiple systems. When this happens, the documentation clearly explains that the project is still experimental or under active development.
The priority is not to make every project appear finished. The priority is to make its current condition clear.
Unless otherwise stated in an individual repository, projects in the iSSU Open Homelab ecosystem are released under the MIT License.