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.

Since switching to Octoprint, I no longer need an LCD controller for operating my machine. However, when my filament runout sensor triggers the advance_pause_feature, there is no way to exit the wait loop without a physical button. For those that run their machines on Octoprint, PrintRun, or some other external host, it would be useful to be able to have a software-button to initiate filament relo

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

My DSTIKE WiFi Deauther Monster V4 just arrived. Can you point me to a document/video that tells me how to assemble and get started?

The following code compiles without problem:

func main() {
	ch := make(chan bool)
	js.Global().Call("setTimeout", js.FuncOf(func(this js.Value, args []js.Value) interface{} {
		println("sending")
		ch <- true
		println("sent")
		return nil
	}), 2000)
	println("waiting")
	<- ch
	println("done")
}

When executed in the browser, the following is outputted:

waiting
s

a detailed documentation is missing about WebServer example "HelloServer.ino":
what is #include <ESPmDNS.h> for?
what is void handleRoot() for?
what is void handleNotFound() for?
what is server.on("/", handleRoot) for?
what is server.on("/inline", ) for?
what means: server.send(200, "text/plain", "this works as well");
(i.e., as well to what?)
what is server.onNotFound(handleNotFo

This is fixed in development, port fixes over to hotfixes

Currently, user should pass --save option to save porject dependencies in platformio.ini. Default behavior should by --save and provide new option --no-save.

Bug Report

I don't know if this is a bug or I just don't have the upload stuff set up correctly

Current behavior

arduino-cli upload -p /dev/ttyACM0 --fqbn STM32:stm32:Nucleo_64 myfirst.ino

I am confused about how the upload command is supposed to work with my board. I am using an s

https://github.com/WebAssembly/bulk-memory-operations

I'm always frustrated when is see the code of OMG and can't read it because the indentation is not correct or variable names are only one letter.

Can you define a code style guide for this project and apply this style guide to all existing code.
This style guide should be defined in CONTRIBUTING.md and should have IDE support, so you can easily apply indentation rules to new code.

This wo

I'll get this added to the documentation shortly, but in the meantime here is a list of some relevant issues and comments which I'll use for it:

SmingHub/Sming#1992 (comment)
SmingHub/Sming#1724 (comment)
#2002

It seems that this was changed from
bool globalInputHandler(const HomieNode& node, const String& property, const HomieRange& range, const String& value)
to:
bool globalInputHandler(const HomieNode& node, const HomieRange& range, const String& property, const String& value)

...took me a while of digging to find out... maybe to update the V3 documentation:
https://homieiot.github.io/homie-esp

Do you have any explanation or reference for this formula?
https://github.com/mysensors/MySensors/blob/f4fd69eb131cd5df5572bc9018d3aa2245020123/examples/DustSensorDSM/DustSensorDSM.ino#L136

e.g. the demo implementations in this sub-directory
https://github.com/particle-iot/device-os/tree/v1.3.0-alpha.1/user/tests/app/ble
or some code snippets in the docs and tutorials still use #include "application.h".

Although Particle.h (formerly Spark.h) should have replaced application.h (as per #249) we keep finding internal/official code using application.h while we try to get t

TinyGSM version: current
Hardware: Feather32U4FONA

Scenario, steps to reproduce

use example on Feather32U4FONA

Expected result

Feather32U4FONA example usage of TinyGSM

Actual result

Example is for MKR1400 which use different modem ublox vs SIM800

AT command log

no relevant - wrong modem