Build a private solar dashboard first, verify it locally, then add controlled remote access
SOLECTRUS is a self-hosted photovoltaic dashboard for viewing energy generation, consumption, battery use, grid exchange, costs, and savings. Its maintainers recommend installing it with HELIOS, a companion application that configures the required Docker containers, centralizes installation settings, and manages updates. This guide explains the supported production workflow without confusing it with the repository's developer setup. After the dashboard works on your local network, we will connect its actual local web endpoint to a Localtonet HTTP tunnel.
📋 What's in this guide
How SOLECTRUS, HELIOS, Docker, and Localtonet fit together
SOLECTRUS is an open-source solar monitoring dashboard designed to run on infrastructure you control. It brings photovoltaic production, household consumption, battery activity, grid exchange, and financial information into one web interface. The project is based on Ruby on Rails and InfluxDB, but a normal operator does not need to assemble those application components manually.
For a production installation, the SOLECTRUS maintainers recommend HELIOS. HELIOS is the companion application responsible for setting up the Docker containers, keeping configuration in one place, and installing updates through its interface. It can also generate a support package containing anonymized logs and configuration when troubleshooting assistance is needed.
This distinction matters because the main SOLECTRUS repository also documents a development environment. That workflow involves cloning the source repository, installing development dependencies, running bin/setup, and starting the application with bin/dev. It opens https://solectrus.localhost and is intended for contributors working on the code. It is not the recommended way to operate a regular self-hosted production dashboard.
Localtonet enters the architecture only after HELIOS has produced a working local dashboard. The Localtonet client runs on a device that can reach SOLECTRUS and establishes an outbound connection to one of our relay servers. An HTTP tunnel can then provide a public HTTPS address for the local web service without requiring inbound router port forwarding, a public IP address, firewall changes, or VPN setup.
The available project evidence does not establish a universal hostname or port for a production HELIOS deployment. Do not assume that production uses solectrus.localhost, a particular LAN address, or a standard port. Record the actual dashboard URL shown or created by HELIOS and use that exact endpoint during local verification and tunnel configuration.
Prerequisites and decisions to make before installation
A successful deployment starts with a stable Linux host and a clear networking plan. SOLECTRUS can run on a Raspberry Pi, another Linux server, a NAS capable of hosting the supported Docker-based environment, or a cloud VPS. For a home solar installation, a machine on the same local network as the relevant energy systems is often the practical choice because it may need to collect information from local devices or services.
The project documentation available for this guide does not specify universal CPU, memory, disk, Linux distribution, processor architecture, or Docker version requirements. Those values can change as SOLECTRUS, HELIOS, and their container images evolve. Check the current HELIOS compatibility information for the specific machine before beginning, especially when using an older Raspberry Pi or a NAS with vendor-specific container management.
Hardware and operating environment
Prepare a Linux system that remains powered on whenever you expect the dashboard to collect and display data. Use persistent storage rather than an ephemeral environment because historical measurements and installation configuration must survive restarts. Make sure the host has sufficient free space for the operating system, container images, application data, logs, and expected time-series history.
Keep the operating system current and verify that system time and time zone settings are correct. Solar charts and financial calculations depend on correctly timestamped measurements. A large clock error can make otherwise valid sensor data appear in the wrong reporting period.
Network and data-source readiness
Decide how the installation will obtain its solar and energy measurements. The project describes integrations involving systems such as SENEC, Shelly, MQTT, Home Assistant, ioBroker, evcc, and photovoltaic forecasting. Support for a named integration does not mean that every device model or firmware version uses the same settings. Gather the addresses and authorized credentials required by your selected integration, then validate them against its current SOLECTRUS setup instructions.
When the data source is on the local network, verify that the Linux host can reach it before troubleshooting SOLECTRUS. Network segmentation, guest Wi-Fi isolation, VLAN firewall rules, changed device addresses, and sleeping wireless devices can all prevent data collection even when the dashboard itself is healthy.
Access and security preparation
Plan separate local and remote access tests. During installation, keep SOLECTRUS reachable only from the trusted local network. Complete its authentication configuration and confirm that expected pages require the appropriate sign-in before publishing anything to the internet.
Also prepare the device that will run the Localtonet client. It can be the SOLECTRUS host itself or another machine that can reliably reach the dashboard's local IP address and port. The selected Localtonet device must stay connected for remote access to remain available.
| Requirement | Why it matters | What to confirm |
|---|---|---|
| Compatible Linux host | Runs HELIOS and the Docker-based SOLECTRUS installation | The current HELIOS release supports the host and architecture |
| Persistent storage | Preserves configuration and historical monitoring data | Enough free space exists and the storage survives restarts |
| Reliable network | Allows the dashboard to reach configured energy data sources | The host can reach each required local or remote endpoint |
| Correct system time | Keeps measurements aligned with charts and reporting periods | Time, date, and time zone are correct on the host |
| Protected administrator access | Prevents unauthorized configuration changes | Credentials are stored securely and are not shared in logs |
| Localtonet-capable device | Creates the outbound connection for later remote access | The device can reach the actual SOLECTRUS web endpoint |
Treat solar production, household consumption, battery behavior, and cost information as private operational data. Finish authentication, remove temporary credentials, and verify the application locally before creating a public tunnel. Remote connectivity does not replace application-level authorization.
Install SOLECTRUS with the recommended HELIOS workflow
HELIOS is the recommended installation method for operators who want to use SOLECTRUS rather than develop it. It manages the container setup and gives the installation a central place for configuration and updates. This avoids turning a production deployment into an unsupported reconstruction of the development environment.
HELIOS is a separate companion application, so its current installation screens and platform-specific bootstrap instructions may change independently of the SOLECTRUS application. The evidence supplied for this guide confirms HELIOS's role but does not provide a verified universal shell command, package URL, default path, port, or complete sequence of screen labels. We therefore do not invent those values. Use the current HELIOS entry point linked from the official SOLECTRUS project, and apply the following production workflow to the options it presents.
Prepare the Linux host
Update the host through its normal operating-system process, confirm that its clock is correct, and check available persistent storage. Assigning a stable LAN address through your router or network management system can make later access more predictable, but the exact method depends on your network and is not a SOLECTRUS setting.
Open the official HELIOS installation path
Start from the HELIOS link provided by the official SOLECTRUS project rather than copying an unverified installer command from a forum or old tutorial. Follow the current instructions for the Linux platform and architecture you are actually using.
Let HELIOS create the Docker environment
Proceed through the HELIOS setup so it can configure the containers required by SOLECTRUS. Do not separately launch the repository's development stack. HELIOS is intended to own the production configuration and keep its settings together.
Complete the installation configuration
Enter the site, account, and integration information requested by your current HELIOS version. Use real values for your installation rather than example credentials. When an integration requires access to another device, grant only the permissions needed to read or collect the relevant energy data.
Allow the managed services to start
Wait for HELIOS to finish creating and starting its containers. Initial image retrieval and service initialization can take time, especially on lower-powered hardware or slower storage. Avoid repeatedly restarting the machine while initialization is still in progress.
Record the actual dashboard endpoint
Note the hostname or IP address, port, and scheme shown by HELIOS for the working SOLECTRUS dashboard. Preserve whether it uses http or https. This exact local endpoint, not a guessed default, is what you will test and later connect to Localtonet.
Commands such as git clone, brew bundle, bin/setup, and bin/dev belong to the documented development environment. That workflow assumes macOS with Homebrew and opens https://solectrus.localhost. It is useful for contributing code, but it is not evidence of the hostname, port, dependencies, or startup method for a production HELIOS installation.
Configure data collection and dashboard access
A running web interface confirms that the application is available, but it does not prove that energy data is being collected correctly. Complete the integration requested for your photovoltaic system and check each measurement category against a source you trust.
Validate measurements by category
Start with current power values while the system is actively producing or consuming energy. Compare photovoltaic generation, household consumption, battery charging or discharging, and grid import or export with the inverter, meter, storage system, or established home automation data. Small timing differences may occur when systems refresh at different moments, but persistent sign errors, missing categories, or implausible totals usually indicate an integration or sensor mapping issue.
After live data appears, inspect longer periods. Confirm that daily and historical views place data in the expected dates and time zone. Financial calculations require correct installation-specific assumptions and input data, so review cost and savings results rather than accepting them solely because a chart rendered successfully.
Secure the application account
Configure the authentication options presented by HELIOS and SOLECTRUS. Use a unique password and store it in a password manager. A recent SOLECTRUS release notes that, when HELIOS is in use, the sign-in guidance identifies where the password can be found in HELIOS. Follow the current interface rather than searching through or publishing environment files.
Test the dashboard in a private browser session. A private session helps reveal whether ordinary visitors receive a sign-in challenge or can access views without an existing administrator session. If the application intentionally allows any public pages, review exactly what those pages disclose before enabling remote access.
Preserve ownership of configuration
Use HELIOS as the source of truth for the managed installation. Avoid editing generated container configuration directly unless the current project documentation explicitly instructs you to do so. Manual changes outside the companion application's management model can be overwritten by an update or make future diagnosis more difficult.
Verify the complete installation on the local network
Local verification should happen from two perspectives. First, test on the SOLECTRUS host if HELIOS provides a local way to open the dashboard. Second, test from another trusted device on the same network. The second check proves that the endpoint is not limited to a loopback address and can be reached by the device that will run the Localtonet client.
Open the exact URL supplied by HELIOS
Enter the complete local URL into a browser, including the scheme and any displayed port. Do not silently replace HTTPS with HTTP or remove a nonstandard port.
Test from the future tunnel device
From the machine that will run Localtonet, open the same address. If Localtonet will run directly on the SOLECTRUS host, test there as well as from another LAN device so you understand which address is reachable in each context.
Confirm authentication behavior
Use a private browser window and verify that the expected sign-in or access policy applies. Log in with the intended account and confirm that logout also behaves as expected.
Review current and historical data
Check live readings, at least one historical view, and the main financial or energy summaries relevant to your installation. A successful page load alone is not enough.
Restart once and repeat the test
Use the normal host or HELIOS-managed restart process, allow the services to recover, and confirm that the same local endpoint and historical data return. This checks that the deployment is persistent rather than dependent on a temporary session.
Record the verified local target as three separate values: the scheme, the host address, and the port. For example, your records should distinguish between an HTTP endpoint and an HTTPS endpoint even if both use the same machine. This guide intentionally does not provide a sample production port because no universal HELIOS port is established by the available evidence.
If HELIOS gives you a local hostname, test whether the Localtonet client device can resolve it. A name that works only on one computer may depend on local host-file entries or a resolver unavailable elsewhere. Use the working target produced by your environment and do not change it merely to match an example.
Expose the verified SOLECTRUS endpoint with Localtonet
Once local access is stable, an HTTP tunnel can make the web dashboard available remotely. The Localtonet client creates an outbound connection, so this workflow does not require opening an inbound port on the router or obtaining a public IP address.
An HTTP tunnel points to a local IP address and port reachable from the selected client device. HTTP tunnels can use a Random Sub Domain, Custom Sub Domain, or Custom Domain process type, and each option serves the content at a public HTTPS address. Availability can vary by current plan and dashboard configuration, so use only the options shown for your account.
The target side still needs to match the SOLECTRUS endpoint that HELIOS created. If that endpoint uses HTTPS locally, consult the current Localtonet HTTP tunnel documentation and the options displayed in the dashboard for the supported upstream configuration. Do not change the local scheme or assume certificate-validation behavior that is not shown in your current client and dashboard.
Install and run the Localtonet client
Install our client on the SOLECTRUS host or another device that passed the local endpoint test. Keep it running whenever the remote dashboard should be available.
Authenticate or select the client device
Use the device-specific authentication token through the supported client and dashboard workflow. Treat the token as a secret. Never paste it into a tutorial, support screenshot, public repository, or shared diagnostic log.
Select an available relay server
Choose from the relay servers or regions currently offered in the dashboard. Available server codes can vary, so obtain the value from the product rather than copying a hardcoded code from an older guide.
Create an HTTP tunnel to SOLECTRUS
Select the appropriate HTTP tunnel workflow and enter the verified local host and port. Choose the process type available for the desired public address. Preserve the local protocol requirements shown by HELIOS and supported by the current tunnel configuration.
Start the tunnel
Creating a tunnel does not automatically make it active. Use the Start button, then wait for the selected client and tunnel to show that they are connected.
Test the assigned public URL
Open the public HTTPS address from a device outside the home network, such as a phone using mobile data. Confirm that the SOLECTRUS authentication boundary remains in place and that dashboard pages load correctly.
A Localtonet device token identifies the client that can run the tunnel and must remain private. The public URL should also be treated as sensitive, but URL secrecy is not a substitute for SOLECTRUS authentication. Use a strong application password, apply least privilege to connected data sources, and stop the tunnel when remote access is not required.
Understand the tunnel lifecycle
The tunnel remains available only while the selected Localtonet client is connected and the tunnel is running. If the Linux host shuts down, the client exits, the network fails, or the tunnel is stopped, the public address cannot reach SOLECTRUS. This behavior is useful during troubleshooting because it separates public connectivity from application health.
Stopping a tunnel disables the active path without deleting its configuration. Deleting removes the tunnel configuration. Use the lifecycle action that matches your intention, and verify status in the dashboard after maintenance.
Test more than the landing page
From an external network, sign in and inspect several dashboard views. Confirm that current data updates, historical navigation works, and static resources load without browser errors. Then sign out and verify that protected information is no longer available in that browser session.
If the public URL opens but the application generates redirects to an unreachable local hostname, stop public testing and review the current HELIOS and SOLECTRUS guidance for externally accessed URLs. The supplied evidence does not establish a universal external-host configuration variable, so this guide does not invent one.
Operate, update, and maintain the installation
A solar dashboard is most useful when it runs continuously and preserves historical data. Routine operation should therefore cover application updates, host maintenance, storage capacity, authentication, data quality, and tunnel status.
Use HELIOS for application updates
HELIOS is designed to manage updates for the SOLECTRUS installation. Review release information, ensure that persistent data is protected, and use the update mechanism provided by the current HELIOS interface. Avoid replacing managed container images or configuration through unrelated commands unless the project explicitly documents that recovery path.
After an update, repeat a focused acceptance test: open the local endpoint, sign in, inspect current readings, inspect historical data, and verify the public URL if the tunnel is enabled. A dashboard can load successfully while a collector or integration remains unhealthy, so include data freshness in the test.
Watch storage and host health
Monitor free disk space and the general health of the Linux host. Time-series data, container images, and logs can grow over time. The available evidence does not establish a universal retention policy, storage growth rate, or minimum free-space threshold, so base capacity planning on the behavior of your installation.
Also check that system time remains synchronized and that the host does not enter a power-saving state that interrupts collection. On a Raspberry Pi, reliable power and storage are particularly important for a continuously running service.
Maintain an operational record
Keep a private record of the machine name, LAN address, local dashboard URL, selected integration, update date, and recovery notes. Do not place passwords, Localtonet device tokens, or unrestricted data-source credentials in that record unless it is stored in an appropriate secrets manager.
If support is needed, HELIOS can create a support package with anonymized logs and configuration. Review any diagnostic archive before sharing it, even when it is designed to be anonymized. A local review helps ensure that unrelated host information or manually added notes are not disclosed.
| Operation | Recommended check | Failure signal |
|---|---|---|
| Application update | Use HELIOS, then test local pages and data freshness | Dashboard loads but measurements stop advancing |
| Host restart | Confirm managed containers and the local endpoint return | The previous URL no longer responds |
| Remote-access test | Test the public URL from outside the LAN | Local access works but the public URL fails |
| Credential review | Confirm unique passwords and least-privilege integration access | Shared, default, expired, or overprivileged credentials |
| Storage review | Check free space and expected data growth | Low disk space, failed writes, or missing history |
| Tunnel shutdown | Stop the tunnel when remote access is no longer needed | The public URL remains reachable unexpectedly |
Troubleshooting the installation and remote connection
HELIOS does not complete the installation
First confirm that the Linux host meets the current HELIOS platform requirements and has enough storage. Check basic internet connectivity if installation images or packages must be retrieved. Make sure system time is valid, then use the status and logs exposed by HELIOS rather than guessing container names or composing replacement commands.
If the failure persists, generate the HELIOS support package where available. Describe the host platform, the stage that failed, and whether the problem is reproducible. Never publish credentials, full environment files, Localtonet tokens, or private energy-system addresses with a support request.
The dashboard works on the host but not from another LAN device
This usually points to local reachability rather than a SOLECTRUS rendering problem. Verify that the second device uses the exact host, port, and scheme provided by HELIOS. Check whether the hostname resolves on that device, whether the service is bound to an address reachable beyond the local host, and whether host or network firewall policy permits the intended LAN connection.
Do not proceed to Localtonet until the machine running our client can open the local dashboard. A tunnel cannot correct an unreachable local target.
The dashboard loads but no energy data appears
Separate application availability from data ingestion. Confirm that the selected integration is configured for the correct source and that the Linux host can reach it. Review authentication permissions and compare source timestamps with the host clock. If only one category is absent, focus on that sensor or mapping rather than reinstalling the entire dashboard.
Local access works but the public URL does not
Confirm that the Localtonet client is running and connected, that the correct device was selected, and that the tunnel was started after creation. Recheck the local target from the client device. A changed DHCP address, port, scheme, or local hostname resolution can break the route even though SOLECTRUS still works from another machine.
Also confirm that the selected relay server remains available in the current dashboard. Do not replace server codes with values copied from another account or old tutorial.
The public URL opens the wrong page or returns an upstream error
Compare the tunnel target against the verified HELIOS endpoint. Common causes include targeting the wrong local port, entering the Linux host address when the service is reachable only under a different address, or mixing HTTP and HTTPS. Correct the target based on observed local behavior rather than trying arbitrary ports.
The browser redirects to a local-only address
This indicates that the application or its surrounding web configuration may be generating an absolute URL based on local settings. Stop the tunnel while correcting the issue. Consult the current HELIOS and SOLECTRUS instructions for external access because the evidence available here does not define a stable production environment variable or field for this behavior.
Remote access stops after a restart
Determine which layer did not return. Test SOLECTRUS locally first. If it is unavailable, inspect HELIOS and the managed application. If it works locally, check whether the Localtonet client is connected and whether the tunnel is running. Remember that creating a tunnel and starting it are separate actions.
Check the data source, then SOLECTRUS locally, then reachability from the Localtonet client device, then tunnel status, and finally the public URL. This order isolates the failing layer and avoids changing a healthy component.
Frequently asked questions
What is SOLECTRUS?
SOLECTRUS is a self-hosted photovoltaic dashboard for monitoring energy production, consumption, battery activity, grid exchange, costs, and savings. It is open-source software based on Ruby on Rails and InfluxDB, and it runs on infrastructure controlled by the operator.
What does HELIOS do?
HELIOS is the recommended companion application for installing SOLECTRUS. It configures the Docker containers, keeps installation configuration in one place, manages updates, and can create an anonymized support package containing logs and configuration.
Can SOLECTRUS run on a Raspberry Pi?
Yes. The project explicitly identifies a Raspberry Pi as a suitable host and also supports other Linux machines. Confirm current HELIOS architecture and platform requirements before choosing a specific Pi model, operating system image, or storage size because universal minimum specifications are not established in the evidence for this guide.
Is https://solectrus.localhost the production dashboard address?
No assumption should be made that it is. That address is explicitly documented for the repository's macOS development workflow started with bin/dev. A production HELIOS installation may use a different hostname, address, scheme, or port. Use the actual endpoint supplied by your HELIOS deployment.
Do I need to clone the SOLECTRUS source repository for a normal installation?
Not for the recommended operator workflow. Cloning the repository and using bin/setup and bin/dev are documented development steps. For normal self-hosting, use HELIOS as recommended by the SOLECTRUS maintainers.
Which port should I enter in Localtonet?
Enter the port from the production endpoint created by your HELIOS installation. There is no verified universal production port in the evidence for this guide, so do not guess or copy the development address. Test the exact endpoint from the Localtonet client device before creating the tunnel.
Does Localtonet require router port forwarding?
No. Our client establishes an outbound connection to a Localtonet relay server. This allows the tunnel to provide a public URL without inbound router port forwarding, firewall changes, VPN setup, or a public IP address.
Is a Localtonet tunnel a replacement for SOLECTRUS authentication?
No. The tunnel provides network reachability to the configured local service. The application must still enforce appropriate authentication and authorization. Use a unique password, protect the Localtonet device token, and stop the tunnel when remote access is not needed.
Will the public URL remain available if the Linux host is offline?
No. The tunnel is usable only while the selected Localtonet client is connected, the tunnel is running, and the client device can reach the local SOLECTRUS endpoint. An offline host or stopped client interrupts remote access.
Can I use a custom domain for the dashboard?
Localtonet HTTP tunnels support Random Sub Domain, Custom Sub Domain, and Custom Domain process types, with availability depending on the current dashboard and plan. Custom-domain DNS requirements should be taken from current Localtonet documentation rather than inferred from this installation guide.
Connect your verified SOLECTRUS dashboard with Localtonet
Finish the HELIOS installation, confirm the real local endpoint and authentication behavior, then create an HTTP tunnel from a device that can reach the dashboard. You can stop the tunnel whenever remote access is no longer required.
Get Started Free →
