HTML Trigger

Use a phone browser as a simple remote for exposed app actions

HTML Trigger turns the domain app into a small local web server. Open the served page from a phone browser on your trusted LAN, then tap action buttons to request app actions.

For ControlMyNikon, HTML Trigger is intended as a simple camera remote. The first exposed actions are small and camera-oriented, such as CameraShoot, CameraAutoFocus, and other actions explicitly made available by the app. The first exposed HTML action is shown as the primary remote button. For ControlMyNikon, CameraShoot is the primary action, while other exposed actions are shown as smaller secondary buttons away from the primary button.

Before you start

  • Use HTML Trigger only on a trusted private network.
  • Keep the bind address at 127.0.0.1 when testing from the same computer.
  • Use a LAN IPv4 address assigned to this computer when opening the remote from a phone.
  • Keep Actions disabled while testing page load.
  • Turn Actions enabled on only when the phone page is working.

HTML Trigger uses plaintext HTTP without a token. Do not expose it through router port forwarding, public Wi-Fi, untrusted VPNs, or internet-facing firewall rules.

Page controls

  • Start begins serving the phone remote on the configured address and port.
  • Stop ends the server and releases the port.
  • Open launches the current remote page in the default browser while the server is running.
  • Bind address sets the local address to listen on.
  • Port sets the HTTP port.
  • Actions enabled allows accepted phone-button requests to run exposed actions.
  • Actions disabled lets you test the remote page without running actions.
  • URL shows the address to open from the phone browser.
  • Copy URL copies the remote page address.
  • Event history shows server state, page requests, blocked actions, and action dispatch results.

If HTML Trigger is listening when the current profile is saved or the app closes, that profile starts the server again next time. If the saved address is no longer assigned to this computer or the port is busy, startup continues with HTML Trigger stopped and the event history explains the failure.

Phone remote page

Open the URL shown on the HTML Trigger page from your phone browser. The remote page is responsive and designed for touch:

  • One column on phones.
  • One large full-width primary action button.
  • Smaller subdued secondary buttons separated from the primary button.
  • Short request-status text below the action buttons.
  • Small subdued remote title text in the footer.
  • No hover-only controls.
  • A simple wider layout on tablets or desktop browsers.

The remote page does not show a large header. The browser title and footer provide context while the main page area stays focused on the remote-control buttons. The status line reports request state, such as an action being sent or blocked. It does not prove the camera completed the requested action.

The page follows the app theme where it can. The primary button uses the current Windows/app accent color and the page follows the app light or dark theme when the app theme is set explicitly.

The phone page does not ask for a token. This keeps the remote fast to open and easy to use, but it means the feature is for trusted private networks only.

Quick setup

  1. Open Triggers > HTML.
  2. Set Bind address to the computer's LAN IPv4 address when using a phone.
  3. Leave Actions disabled.
  4. Select a port, or keep the default.
  5. Start HTML Trigger.
  6. Use Open for same-computer testing, or copy or type the URL into the phone browser.
  7. Tap a button and confirm the page reports that actions are disabled.
  8. Turn Actions enabled on in the app.
  9. Tap the action button again.

For same-computer testing, use 127.0.0.1 and open the URL on the same computer.

Safety

HTML Trigger can request app actions without local keyboard, scanner, voice, or sound input. For that reason, it starts stopped, binds to loopback by default, and keeps Actions disabled until you turn them on.

Actions disabled blocks action dispatch while still allowing page-load testing. Use it before a real remote-control session.

LAN binding is trusted-LAN-only control. Anyone who can connect to the listener can request exposed actions while Actions enabled is on. Use it only on networks and devices you trust.

Troubleshooting

If Start is disabled:

  • Check that the port is between 1 and 65535.
  • Stop any previous listener state before changing the address or port.

If Start fails:

  • Another process may already be using the port.
  • The bind address may not be assigned to this computer.
  • Choose another port or address and try again.
  • Check the event history for the failure message.

If the phone cannot load the page:

  • Confirm HTML Trigger is started.
  • Confirm the phone is on the same trusted LAN as the computer.
  • Confirm the URL uses the computer's LAN IPv4 address, not 127.0.0.1.
  • Confirm Windows firewall or endpoint tools allow the inbound connection.
  • Confirm the bind address is assigned to this computer.

If a button is rejected:

  • Confirm Actions enabled is on when you expect actions to run.
  • Confirm the button is one of the actions exposed by the app.
  • Watch the app event history while testing.

Related setup

Use TCP/IP Trigger when a script or custom client should send JSON commands. Use Hotkeys when keyboard input should request actions. Use Voice Trigger when spoken phrases should request actions. Use Sound Trigger when audio level threshold crossings should request actions.