Chat freely about the open source Javascript projects for ESP8266

User avatar
By kolban
#32214 As part of the work process to take the JavaScript (Espruino) support for ESP8266 out of beta, we are re-working some of the APIs so that they are consistent between the ESP8266 board and other boards on which Espruino runs. This means that some of the API calls that you may have used in the past will no longer be present in the future.

Specifically, many of the "ESP8266WiFi.xxx" methods have moved to a module.

A draft of the new docs for this can be found here:

https://github.com/nkolban/Espruino/blo ... r_Guide.md

Again ... this is only a temporary place to find docs and a week from now, you should be able to find the proper docs at the normal location of:

https://github.com/espruino/Espruino/bl ... r_Guide.md

The work items being tracked in Github for these changes can be found here:

https://github.com/espruino/Espruino/issues/589

and

https://github.com/espruino/Espruino/issues/630

Anyone interested in examining the specs for the new interface are welcome to come and join the conversations.

It is not envisaged that once these changes are made there will be any further disruption to the API (we hope) again.
User avatar
By kolban
#32220 Hopefully the changes that are shown in the temporary docs will be in the master Espruino Github repository on Monday. What we have right now:

1. Changes made in a development fork.
2. Binaries built from that development fork and uploaded to the binary distribution of Espruino for ESP8266.
3. Docs in the development fork consistent with code changes made in the fork.

What will happen next is:
4. Issue a pull request of the fork to Espruino master
5. Merge occurs

After about a week or so of community feedback, if all has gone well, the "ESP8266WiFi.xxx" functions will be removed (they are still present in parallel with the new APIs) and what will remain are the new APIs.

Assuming nothing horrible shows up, I would imagine final API stability about the 2nd or 3rd week of November.
User avatar
By jankop
#32239 Hi Neil,
when you enter a nonexistent SSID or wrong password, wifi.connect() function permanently blocked implementation of the program. Callback and error message are therefore unusable. I consider it a mistake.
And is disfunction without ESPWiFi.init().
Last edited by jankop on Sun Oct 25, 2015 4:03 pm, edited 1 time in total.