Expected behavior

During firmware configuration
Should be easy to select the value for LUA_FLASH_STORE in user_config.h
Options and/or units should be clearly documented so that the setting can be used.

Actual behavior

current default setting is:
//#define LUA_FLASH_STORE 0x10000

Comments

0x10000 corresponds to 64kb in hex, What are the other possibl

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

Hi This project is amazing and I want to contribute but I noticed there is no developer documentation also this project doesn't not seem to use platformIO or Arduino ...so no clue how to start ....is possible to provide documentation ...like which module does what and how compile /build .........even better if its possible to convert to platformio project

Is your feature request related to a problem? Please describe.

ref #1864 , there needs to be a concise way to check that utility functions (brightness calculation, channel setting, value conversion etc.) work without problems with some set of expected inputs and outputs.

Describe the solution you'd like

• special build option to replace application code with bunch of assert calls. i

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

Mongoose OS only currently supports running ESP32 on single core, basically leaving the second core completely unused.

Yes i've seen the thread at:
https://forum.mongoose-os.com/index.php?p=/discussion/comment/2356/#Comment_2356

And ticket #253

I opened this issue as technically this is an issue that only single core devices are supported, and multi-core devices that are supported .

I've successfully completed the hardware configuration, serial flashing, and wifi configuration steps from the instructions, and I've got it connected to (and powered by) a Raspberry P

In Readme.md, the macOS build instructions yields the error (Sierra):

checking for gobjcopy... no
checking for objcopy... no
configure: error: missing required tool: gobjcopy objcopy
make[1]: *** [_ct-ng] Error 1
make: *** [crosstool-NG/ct-ng] Error 2

Adding the following to the path fixes it:

export PATH="/usr/local/opt/binutils/bin:$PATH"

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

Aside from some examples in the readme, and the intro article, there is no documentation for the API. It was only by examining the unit tests, mjs_builtin.c, and reading the v7 documentation through the internet archive, that we were able to figure out how to set and get properties in the VM and make calls into javascript functions with complex values.

This is less than ideal

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

https://github.com/Links2004/arduinoWebSockets/blob/c038f100d68b8e5d0a96f25dd1609ff28592b02f/src/WebSocketsServer.h#L128

I need to override default handleHeader to support for POST/OPTIONS other methods since running a simple web server on top of WebSocket one.
I have requested in the past that virtual is added to handleNonWebsocketConnection but now realized same is needed for handleHeader,

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

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.