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

There are a few flags that currently don't have proper error checking. The ones I found are -gc, -scheduler and -size. Using the wrong value will lead to no or unexpected errors.

I think the best way to handle it is to add a new method to compileopts.Config that checks whether there are any faulty flags, which is then called from the main function.

Absolutely love the work you guys are doing and I firmly believe that javascript is the way to go with everything. I want to make a Chrome App using cylon.js and therefore stumbled upon this repo from this blog post. Looking through the README, it's documented that we have to write our code in the script.js file for instance and bundle it using Browserify like so:

 ./node_modules/.bin/brows

hzeller/rpi-rgb-led-matrix#962 proposes instructions on how to run arduino code with rpi-rgb-led-matrix
This is explained in more details in http://marc.merlins.org/perso/arduino/post_2020-01-01_Running-FastLED_-Adafruit_GFX_-and-LEDMatrix-code-on-High-Resolution-RGBPanels-with-a-Raspberry-Pi.html

Basically, it's a combination of:

• https://github.com/marcmerlin/Arduin

This issue is two part:

• https://periph.io/x/periph/conn/gpio doesn't document that Halt is the formal way to unblock a WaitForEdge function.
• https://periph.io/device/button/ and https://periph.io/device/pir/ should demonstrate that in a copy-pastable way.

Looking at the code vs the document I see that:

1. chipID listed in docs is actually not used for SPI
2. bus is not listed in docs
3. slaveselect is not listed in docs

This needs to be corrected to avoid confusing users.

Also, please note information from #781 and incorporate it as well.

As talked about in #826 the "bounce time" value in pigpio is actually a "glitch filter", and has a much smaller maximum-value than the debounce time in RPi.GPIO.

We should probably check for this in GpioZero and display a "GpioZero exception" rather than letting the exception from pigpio bubble all the way back up to the user.
(and optionally, explain this difference in the documentation?)

Hello Everybody,

I am trying to run HomeGenie but my ports: 80 and port 8080 is already being used.

I found systemconfig.xml where I change the port: 80 to 85 but I could not find the hard-coded port:8080 to change. I went through the documents but could not find any related information hence my being asked for help. Now while HomeGenie is no longer using port:80 but is now locke

I'm trying to use this library to receive signals with generic 433mhz receiver (sender is a door sensor operating on the same freq). it seems like set_async_interrupt runs a lambda on another thread and will reset interrupt handler back to none, so that next interrupt doesnt trigger any lambda.

However radio receiver will trigger many interrupts, so I was wondering if you could provide a us

Not really blaming this crate, but elaborating on pin numbering might be useful to the documentation reader.

I connected physical pin 24 on my Raspberry Pi 3, and now in hindsight, I think that pin really should be accessed via Pin 8, still not sure as SPI CS doesn't work as expected.

Output of gpio readall:

+-----+-----+---------+------+---+---Pi 3---+---+------+---------+-----+-

For Arduino programming using their language, a specific driver library exists for easy and simple control over Servo parts. This seems to be non supported at the moment when using tinygo.

This functionality would be very useful for especially Arduino users that want to use their servos, but I guess that it might be useful for other boards too, depending on implementation. I will mostly be usin