193fe3593e
* Allow configuration of debugOutput to be performed * don't send to own IP or update own data * Use same socket to send and receive. Avoid problems in many opened and closed sockets to send * Add callback for REMOVEed hosts * Send broascast messages if seedList is empty * Adapt yeelink to new luacheck rules * Fix building of luac.cross for win to win2019 and VS 2019 |
||
|---|---|---|
| .. | ||
| README.md | ||
| bh1750.md | ||
| bme280.md | ||
| cohelper.md | ||
| ds18b20.md | ||
| ds3231.md | ||
| fifo.md | ||
| fifosock.md | ||
| file_lfs.md | ||
| ftpserver.md | ||
| gossip.md | ||
| hdc1000.md | ||
| httpserver.md | ||
| imap.md | ||
| liquidcrystal.md | ||
| lm92.md | ||
| mcp23008.md | ||
| mcp23017.md | ||
| redis.md | ||
| telnet.md | ||
| yeelink.md | ||
README.md
NodeMCU Lua modules directory
Reviewing, hosting and thus potentially maintaining an ever growing list of NodeMCU Lua modules (the ones here) does not scale well for the project team. Instead, we give the community a chance - and the responsibility - to maintain a directory of Lua modules found in the wild through the GitHub wiki.
In the (hopefully not too distant) future, we will request that Lua modules to be hosted in this repository come with a test program in whatever framework we end up adopting.
A module being listed on the wiki does NOT mean the NodeMCU project team endorses it in any way.
→ https://github.com/nodemcu/nodemcu-firmware/wiki/Lua-modules-directory