Your projector, in your smart home.

• It publishes state. The projector shows up as a Home Assistant sensor, a Hubitat device, or a JSON payload on your webhook, carrying the same readings the app shows you.
• It publishes controls. Every Scene you save, plus power, each input, each color mode and each lens memory, becomes something an automation or a voice assistant can run.
• It runs serverless. Once the scripts are set up, Home Assistant sends commands straight to the projector's IP address. Your phone does not need to be on the network, and nothing routes through a cloud account.

Three ways in, one hub

Settings › Home Automation is the hub. Pick the platform you run - Home Assistant, Hubitat or Webhooks - and set it up there. You can wire up more than one at a time; they are independent.

1. Open Settings › Home Automation › Home Assistant.
2. Type your Home Assistant address (for example http://homeassistant.local:8123 or its IP), then tap Sign in. It is a browser sign-in against your own instance - there is no token to paste. Use your normal Home Assistant login, two-factor and all.
3. The app publishes the projector as a sensor, with an entity like sensor.projector_pilot_epson_qb1000b_qb1000w, carrying power, input, color mode, the picture figures and lamp hours.
4. Turn on Send the projector's state so those readings update in Home Assistant whenever they change while the app is open, and turn on Sync Advanced Controls to publish scripts for picture modes, inputs, lens memories and power.
5. Paste the one shell_command block (below) into your configuration.yaml, restart Home Assistant, then tap Sync With HA.

The shell_command block

This is the whole serverless trick. The app writes one command Home Assistant runs to talk to the projector's Web Control, and every script it syncs calls that command with a different verb. Tap Copy block in the app and paste it into configuration.yaml. The example below is illustrative - the app fills in your projector's own address and command name:

shell_command:
  projector_pilot_epson: >-
    curl -s --max-time 5 --digest -u 'EPSONWEB:'
    -H "X-Requested-With: XMLHttpRequest"
    -H "Referer: http://192.168.1.50/cgi-bin/webconf"
    "http://192.168.1.50/cgi-bin/directsend?{{ verb }}={{ value | urlencode }}"

Example only. The app generates yours with the projector's real IP and a name derived from its serial.

Test Connection, Sync, and cleanup

• Test Connection checks that the app can reach your Home Assistant and that the pasted shell_command is actually there, so you find a typo before you build anything on top of it.
• Sync With HA writes or updates the scripts for your Scenes and controls. Run it again any time you add a Scene or change a control - it updates in place rather than piling up duplicates.
• Remove orphaned scripts deletes scripts the app wrote that no longer have a matching Scene or control - for example after you delete a Scene. It only ever touches scripts Projector Pilot created; nothing else in your Home Assistant is disturbed.

• Automations can run them. "At sunset, if the TV turns on, run Movie Night" is a normal Home Assistant automation once the Scene is a script.
• Voice assistants can run them. Expose a script to your assistant and "turn on Movie Night" sets the input, the picture mode and the lens memory together.
• Only your real controls appear. The app writes a script for each input, color mode and lens memory the projector reports - not a generic list it guessed at.
• Removing sync removes only what the app wrote. Turn the sync off, or use Remove orphaned scripts, and Projector Pilot deletes the scripts it created and nothing else.

The dashboard

Copy a ready-made dashboard

You do not have to hand-build a Lovelace view. Tap Copy dashboard on the Home Assistant screen and the app hands you a complete dashboard: one card with the projector's state and a button for every Scene and control it synced.

1. In the app, tap Copy dashboard (after you have signed in and synced at least once).
2. In Home Assistant, go to Settings › Dashboards › Add Dashboard, create a new empty dashboard, and open it.
3. Open the dashboard's three-dot menu, choose Edit dashboard, then the three-dot menu again and Raw configuration editor.
4. Paste the copied YAML, save, and the card and buttons appear, already pointed at your projector's scripts.

The copied YAML looks something like this - a state card plus a button for each control (illustrative snippet):

views:
  - title: Projector
    cards:
      - type: entity
        entity: sensor.projector_pilot_epson_qb1000b_qb1000w
        name: Projector
      - type: button
        name: Power On
        tap_action:
          action: perform-action
          perform_action: script.turn_on
          target:
            entity_id: script.projector_pilot_power_on
      - type: button
        name: Movie Night
        tap_action:
          action: perform-action
          perform_action: script.turn_on
          target:
            entity_id: script.projector_pilot_scene_movie_night

Example only. Your dashboard carries your projector's real entity and your own Scenes.

1. In Hubitat, enable the Maker API app and note its access URL and token, and pick which devices it exposes.
2. In Projector Pilot, open Settings › Home Automation › Hubitat and enter your hub's Maker API details.
3. Pick the device that stands for the projector. The app suggests the likely one; choose it or select your own.
4. The app mirrors power, mute and input onto that device, sending only the commands the device accepts.
5. Build Rule Machine rules against that device the way you would any other - the projector's state drives them.

1. Open Settings › Home Automation › Webhooks.
2. Enter the URL to post to. A Home Assistant webhook looks like http://homeassistant.local:8123/api/webhook/your-id.
3. Choose which events fire the webhook: power on, power off, input change, Scene recall - and optionally filter to a specific input or Scene.
4. Optionally set a custom payload if the receiving service wants a particular shape; otherwise the app sends its default JSON.
5. Save. The app posts on each matching event from then on.

The default payload is plain JSON - an event, the projector, and the value that changed:

{
  "event": "scene_recalled",
  "projector": "Epson QB1000B/QB1000W",
  "scene": "Movie Night",
  "power": "on",
  "input": "HDMI1",
  "color_mode": "Cinema",
  "timestamp": "2026-09-23T20:14:07Z"
}

Example payload. An input-change or power event carries the fields relevant to it.