Name the hardware
Specify the PiEEG board and connected accessories.
BOARD / HOST / POWERContact / signal routing
Send the questionto the right layer.
Technical issue, builder discussion, direct inquiry, or partnership: choose the channel that matches the question and keep the context intact.
Builder discussion
Use Discord for community questions, setup discussion, and shared experiments.
Join Discord →02 / CHANNELReproducible software issue
Use GitHub for bugs, feature requests, source changes, and technical context.
Open GitHub →03 / CHANNELDirect inquiry
Use email for support, general questions, and conversations that should not begin in a public issue.
pieeg@pieeg.com →01 / Before sending
Preserve the
useful evidence.
For technical issues, include the device, host platform, PiEEG Server version, the action you took, and the exact output. A visible signal path is easier to diagnose.
Capture the route
Include the server version, connection method, and relevant command.
VERSION / PORT / MODEKeep the exact error
Share reproducible steps and the complete error without credentials or private data.
STEPS / RESULT / EXPECTED02 / Public channels
Follow the work
where it happens.
Official PiEEG channels cover product releases, tutorials, open-source work, community projects, and physical designs.
03 / Collaboration
Have a concrete
project in mind?
For research, institutional, product, or event collaboration, begin with the partnership brief before sending the inquiry.