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.

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.

Basic Infos

Hardware

WiFimanager Branch/Release:

• Master
• Development

Esp8266/Esp32:

• ESP8266
• ESP32

Hardware: ESP-12e, esp01, esp25

• ESP01
• ESP12 E/F/S (nodemcu, wemos, feather)
• Other

ESP Core Version: 2.4.0, staging

• 2.3.0
• 2.4.0
• staging (master/dev)

Description

I am trying out the OnD

Bug Report

I have copied the bug report from here:

I set up virtual ports on Windows with com0com and mapped COM5 to ARDUINO:

I

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

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