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.

Currently comment on runout sensor configuration says:

• By default the firmware assumes HIGH=FILAMENT PRESENT.

which is quite confusing and not very informative for regular user. As we test filament sensor status by M119 command It should clearly say when filament present on M119 we should see either "open" or "TRIGGERED" status and we can flip FIL_RUNOUT_INVERTING otherwise. Nobody really

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.

WiFiClient setTimeout is documented to accept milliseconds (sane) but value is used as seconds directly (loss of resolution is not sane). Protoype expects u32 instead of f32/f64.

Documentation (inheritance) on value being milliseconds, not seconds
https://www.arduino.cc/reference/en/language/functions/communication/stream/streamsettimeout/

/path/to/sketch.ino: In function 'void loop()':
sk

Solutions

1. Convert INO files to CPP

2. Manual prototype declaration

#ifdef DO_NOT_USE
typedef int32_t delaytype;
void thisShouldNotAppearInTheBinary(delaytype timer); // aded manually
void thisShouldNotAppearInTheBinary(delaytype timer) {
  delay(timer);
}
#endif

This is fixed in development, port fixes over to hotfixes

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

Bug Report

This happened on Windows with the Pro IDE. This is all I can see in the logs:

root ERROR Uncaught Exception:  Error: 2 UNKNOWN: error getting port list from serial-discovery: read |0: The handle is invalid.
root ERROR Error: 2 UNKNOWN: error getting port list from serial-discovery: read |0: The handle is invalid.
    at Object.callErrorFromStatus (c:\Users\kittaakos\Desktop\

Implement Python 3 bindings, so wasm3 can be easily used from Python.

Before submitting a problem please check the troubleshooting section
https://docs.openmqttgateway.com/upload/troubleshoot.html

Describe the bug
The Config published for illumination:

homeassistant/sensor/80EACA890C56-MiFlora-lux/config {"stat_t":"home/OMG_Garage/BTtoMQTT/80EACA890C56","name":"MiFlora-lux","uniq_id":"80EACA890C56-MiFlora-lux","dev_cla":"illuminance","val_tpl":"{{ va

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

I'm doing some minor testing whether TinyGSM works with the FreeRTOS Arduino port and running into problems. The data object in waitResponse (an Arduino String) is always empty.

It seems to related to
https://stackoverflow.com/questions/39551941/arduino-string-not-working-inside-freertos-task
and/or
feilipu/Arduino_FreeRTOS_Library#3

Getting rid of the String cla

The speed commands (s+ and s-) are reversed in this example. Just needs the 1.2 and 0.8 multipliers swapping around. Thanks for a great library.