Utilities help
Remote Access
Remote Access lets you open a secure tunnel through a gateway to reach a device or service on its local network, without needing to configure port-forwarding or a VPN.
Gateway MID
The Molecule ID (MID) is the unique identifier for the gateway you want to connect through. You can find it printed on the gateway label or in the Molecule admin portal.
Host
The host tells the gateway which device to forward your connection to. It is always relative to the gateway — not your own computer.
| Host value | When to use it |
|---|---|
localhost | Access the gateway itself — its own web interface or SSH service. |
192.168.1.50 | Access another device on the same local network as the gateway (e.g. a meter or inverter). Replace with that device's actual IP address. |
If you are not sure of a device's IP address, check its label, your router's connected devices list, or ask your network administrator.
Port
The port tells the gateway which service on that host to connect to. Every service listens on a specific port number. Some examples shown below.
| Port | Service |
|---|---|
22 | SSH : opens a remote command-line session on the target device. |
80 | Web admin (HTTP) : the default port for most device web pages. Try this first if you want to open a device's browser-based admin panel. |
9100 | InHand gateway web admin : the built-in administration page for InHand routers and gateways. |
443 | HTTPS : secure web pages. Use this if the device's web interface requires a secure connection. |
Example
| Example | Description |
|---|---|
Host: localhost, Port: 9100 | Connect to port 9100 on the local gateway. On an InHand gateway device, the local admin web application runs on port 9100. |
Force close existing connections
If a tunnel to the same destination is already open from a previous session, enabling this will close it before starting a new one. Leave it off unless you are sure the previous session is stale.
Tunnel auto-close
All tunnels automatically close after 1 hour. Click Disable at any time to close the tunnel and all active connections immediately. It is good practice to disable the tunnel when you are finished.
Step-by-step
- Enter the Gateway MID and click Connect.
- Set the Host, use
localhostfor the gateway itself, or the IP address of another device on its local network. - Set the Port for the service you want to reach (e.g.
80for a web page,22for SSH). - Click Enable and wait for the tunnel to become active.
- Use the SSH or Web connection details shown in the status panel to connect.
- When finished, click Disable to close the tunnel.
Remote Debug
Remote Debug is a live WebSocket diagnostic tool. It connects directly to a gateway and lets you send commands, inspect responses, and stream device logs in real time.
Gateway MID
Same as Remote Access — enter the Molecule ID of the gateway you want to inspect. The MID is on the gateway label or in the admin portal.
Live data tiles
Once connected, any real-time data broadcast by the gateway is parsed and displayed as tiles. Each tile shows a label and its current value. Tiles automatically disappear after 10 seconds if no updated value is received — this indicates the gateway has stopped sending that data point.
Log filters
The log panel can show a lot of traffic. Use the filters to focus on what matters:
| Filter | What it shows |
|---|---|
| System | Connection events, auth results, errors, and status messages generated by this tool. |
| Realtime | Raw real-time data messages from the gateway — the same data that feeds the tiles. |
| Responses | Replies to commands you send. Useful for confirming a command was received and acted on. |
| Device Logs | Plain-text log lines streamed from the gateway. Only appears when log streaming is active. |
Log streaming
The gateway can stream its internal debug logs directly to this tool. Use the Activate Logs button to start a 30-minute streaming session.
DBG bits control which categories of log are included. They can be combined:
| Bit | Meaning |
|---|---|
| 1 | Standard application logs |
| 2 | Extended / verbose logs |
| 3 | Low-level system logs |
Start with only DBG 1 checked. Add bits 2 and 3 only if you need deeper output — higher bits produce a lot of traffic and can make it harder to find what you are looking for.
The streaming session expires automatically after 30 minutes. You can stop it early at any time by clicking Stop Logs. DBG bit selection is locked while streaming is active, stop streaming first if you need to change the level.
Sending commands
Select a target from the dropdown, type your command in the input field, and press Send or hit Enter.
| Target | Description |
|---|---|
| MOS-EMS | The main energy management application running on the gateway. Most commands go here. |
| System | Low-level system service. Used for system-level queries and configuration. |
| S-System | Secondary system service. Used for subsystem-specific commands. |
Commands are sent as raw JSON. Refer to the gateway API documentation for the correct command structure for each target. (MOS API services running on the server will convert this to Communication Framework )
Step-by-step
- Enter the Gateway MID and click Connect.
- Once connected, the live data tiles will populate automatically if the gateway is broadcasting.
- Use Log filters to choose which message types to display in the log panel.
- Optionally click Activate Logs to start streaming device logs. Select DBG bits before activating.
- Type a command in the send bar, choose the correct target, and press Send.
- When finished, click Stop Logs (if active), then Disconnect.