iOS App — unauthorized role: node after device pairing
Setup: OpenClaw 2026.2.6-3 on Mac mini (macOS Tahoe, ARM64). iOS app on iPhone 15 Pro Max.
Steps taken:
1. Gateway bind set to lan (0.0.0.0:18789), TLS disabled
2. iOS app connects and device appears in openclaw devices pending
3. Approved via openclaw devices approve
4. Device pairs successfully and shows connected
Problem:
After pairing, the iOS node sends config.get and voicewake.get requests but gets unauthorized role: node errors. A2UI asset requests return 404. The node disconnects shortly after.
Logs:
- config.get -> unauthorized role: node
- voicewake.get -> unauthorized role: node
- /a2ui/* -> 404
Question: Is there a config flag or role permission needed to allow paired iOS devices to access config and voicewake endpoints? Or is this a known issue with the current iOS app version?
Steps taken:
1. Gateway bind set to lan (0.0.0.0:18789), TLS disabled
2. iOS app connects and device appears in openclaw devices pending
3. Approved via openclaw devices approve
4. Device pairs successfully and shows connected
Problem:
After pairing, the iOS node sends config.get and voicewake.get requests but gets unauthorized role: node errors. A2UI asset requests return 404. The node disconnects shortly after.
Logs:
- config.get -> unauthorized role: node
- voicewake.get -> unauthorized role: node
- /a2ui/* -> 404
Question: Is there a config flag or role permission needed to allow paired iOS devices to access config and voicewake endpoints? Or is this a known issue with the current iOS app version?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Similar Threads
Was this page helpful?
