Scheduler and Remote Access

Scheduler and Remote Access

Scheduler

Volume² has its own task scheduler, separate from the Windows one. A task combines a trigger — a time, or an event such as a device change — with an action: set volume, change device, or run a program.

Giving each device its own volume level

Volume² does not store a volume level per device, so Bluetooth headphones can connect at 75 % when the speakers were at 12 %. The scheduler solves this:

1. Scheduler → new task.
2. Trigger: device change.
3. Action: set volume, at the level you want for that device.
4. Repeat for each device.

Other uses

• Lower the volume automatically late at night.
• Set a fixed volume at login.
• Launch a program at a set time.

Remote access

Settings → System → enable the remote-access option. Volume² then runs a small local HTTP server, by default on port 22222.

The control page

Next to the option is a button that opens the control page in your default browser. The page is minimal and contains a control such as Set Volume = 50.

With remote access enabled, Volume² accepts requests from any client — a browser, an iOS app or an Android app. The shipped page is a starting point: view its source and add your own buttons for the controls you use.

If the page loads but its controls do nothing, confirm the server is reachable at http://127.0.0.1:22222/ and check that no firewall rule is blocking the port.

HTTP endpoints

Method	Endpoint	Purpose
GET	http://127.0.0.1:22222/tasks	List scheduler tasks
POST	http://127.0.0.1:22222/tasks/execute?id=taskId	Run a specific task

Combined with the scheduler, these are the program's extension point: define the action as a task, then trigger it over HTTP from anything on your network.

Is the port exposed to the internet?

No. The remote-access server is intended for internal use and listens locally; it is not designed to be published to the internet.

Precautions:

• Keep the port on your LAN. Do not forward it through your router.
• Treat it as unauthenticated — anything that can reach the port can change the volume and run your defined tasks.
• To reach it from outside the network, use a VPN rather than a port forward.

Home automation

There is no native MQTT integration. The HTTP endpoints above are the supported path and work from Home Assistant's rest_command or a shell command; HASS.Agent is also commonly used alongside Volume² for this.

Remote access accepts volume and task commands only; arbitrary text commands such as shutdown are not supported, and there is no "remote command received" scheduler trigger. Defining the action as a scheduler task and firing it with /tasks/execute is the closest equivalent.