Hub & phone remotes

Use Connections for Hub, the phone connection method, and MIDI. Use Mobile control to create Viewer, Controller, or Worship Assist access for a phone.

Connect a phone

1. Open Connections → Phone remote.
2. Choose a connection method:
   • Same Wi-Fi: best for most venues; the phone and Presenter computer must use the same local network. Internet is not required.
   • Own server: advanced; use an MQTT server managed by your organisation.
   • Anywhere (Team): connects through ProWeave Cloud when the phone is on another network.
3. Wait until the connection status is ready.
4. Open Mobile control, choose a role, and scan its QR code or share its link.

Each role has a separate session. Extend session keeps the current QR and connected phones valid for longer. Refresh QR creates a new session and invalidates the old session for that role.

Opening or creating a song in Worship Assist changes the shared team screens. Sending it to Presenter asks to add it to the current section and present it. Presenter asks the operator to accept or decline, unless the operator has enabled automatic acceptance in Presenter. Check that preference before the service: with automatic acceptance enabled, a suggestion can change the live presentation.

Sync the song library with Hub

1. Open a deck collection in Presenter. Synced songs are stored in that collection's songs folder.
2. Open Connections → Hub, sign in, and choose the correct organisation.
3. Select Sync songs with Hub.
4. Read the result. It reports songs pulled from Hub, songs pushed from Presenter, conflicts, and any free-plan limit.
5. If a merge conflict appears, open the song in Lyrics Designer and resolve the local/cloud differences there.

The manual action is bidirectional: it pulls Hub changes and pushes saved local songs. The free plan can add up to 3 songs to Hub; existing cloud songs can still be updated. Team removes the new-song limit. Saving a song is not the same as running the manual sync, so use this action when a recent local change has not appeared in Hub.

Chords do not appear in Hub's Chords tab

1. In Lyrics Designer, use valid inline notation such as [C]Every eye on [F]him, or put valid chords on their own line, for example C G Am F or || C | G | Am | F ||.
2. Save the song and wait for Auto-saved if it is an existing song.
3. Confirm Presenter is connected to the organisation you are viewing in Hub.
4. Run Sync songs with Hub and check the result for a free-plan skip or a merge conflict.
5. In Hub → Songs, select Chords. That filter includes songs with recognised chord notation or a saved Chord Assistant chart.

A label such as [Chorus] names a stanza; it is not a chord. A chord-only line without bar marks must contain at least two recognised chord symbols.

Create a deck from a Hub event

1. Open a deck collection, then go to Connections → Hub.
2. Choose the correct organisation and event.
3. Review the preview: section order, estimated cues, linked lyrics, attachments, notes, unlinked songs, and any visual directions. Loading this preview does not change local files. The preview can count attachments on every plan; downloading event and item files into the deck requires Team.
4. Resolve important missing song links in Hub if needed.
5. Select Create & open auto-deck. Presenter creates a new deck file, downloads content included with the organisation's plan, and opens that deck.
6. Read the result summary, then review every cue before presenting.

Running the action again creates another uniquely named deck. It does not merge Hub changes into the deck you already edited.

Volunteer assignments, responses, and other Hub administration are not presentation cues and are not copied into the deck.