There is an optional board param than may be passed in the constructor opts for all device classes. Simply put, it allows the user to specify which board they want to use in projects that have multiple boards. It is currently not documented anywhere and should probably be added to all the classes.

I'm following https://gobot.io/documentation/platforms/chip/ on macOS and seeing a compilation error in the sample program:

undefined: gobot.On

Repro steps

I ran go get -d -u gobot.io/x/gobot/... (worked)

Pasted the sample listed to main.go:

package main

import (
    "fmt"

    "gobot.io/x/gobot"
    "gobot.io/x/gobot/drivers/gpio"
    "gobot.io/x/gobot/platfor

A Dockerfile for each server [ai, main] and docker-compose.yml would make development and deployment easier.

Instead of rebuilding the whole system via docker every development iteration, we would only build the parts that have been modified.

Is your feature request related to a problem? Please describe.
For now there is no documentation on how to disconnect from device when it is connected after state restoration. Look at #278 for more information.

Describe the solution you'd like
Add documentation as a Wiki page

When we released Bluejay 1.0, Rob and I reviewed the API and pointed out a couple confusing names or parameters. We should do this again before locking everything down for 1.0.

It's not an issue than a question:
I'm using this very nice project to use joy-cons on Dolphin (with this gyro server thingy)
and I'm impressed how well this works. 👌🏻
Has someone figured out a good Dolphin controller config and would share it?
(nunchuck left joy-con - wiimote right)

Pi0 devices can miss event broadcasts that announce a new master. Based on my testing this is rare and only on pi0 devices due to them barely being able to run balena-sound stack.

An option to remedy this could be adding an env var FORCE_MASTER_SERVER that:

• forces all devices on the fleet to point to that server
• disables autoconfig on stream start

You should add 'not installed' section of plugins to plugin manager, so users know what plugins exist and can download them from there, or have links there...

I followed the steps shown here and I got the following error.

Maybe I did something wrong, but in this case there should be a proper error message telling me what I did wrong.

The dead zone range in the editors matches an 8bit axis. It is scaled internally according to the axis resolution of the emulated controller type.

The dead zone range in the editors should be adjusted according to the axis resolution of the emulated controller. For example the Xbox 360/One have 16bit axes for sticks.