This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
oak:tutorials:api_reference [2016/11/11 22:03] pfeerick [ESP8266 API] |
oak:tutorials:api_reference [2017/01/30 14:00] (current) weaslyd [Particle API] |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== Particle API ===== | ===== Particle API ===== | ||
| - | There is a [[https://docs.particle.io/reference/firmware/photon/#cloud-functions|comprehensive user guide]] over on the Particle.io site, which provides detail descriptions and examples of the different built-in functions that you can use. | + | There is a [[https://docs.particle.io/reference/firmware/photon/#cloud-functions|comprehensive user guide]] over on the Particle.io site, which provides detailed descriptions and examples of the different built-in functions that you can use. |
| The following Particle Cloud Function APIs are working, whilst the remainder are not available for use (yet). Please note that there is a [[https://community.particle.io/t/doing-something-wrong-with-particle-publish-subscribe/14926/10|known]] [[https://community.particle.io/t/particle-subscribe-unique-device-id-not-returning-correct-values/18422/5|bug]] in the Particle.subscribe() function, where specifying a unique device ID to subscribe to has no effect. This is a bug on their side, and the current workaround is the specify the MY_DEVICES constant instead, in order to limit the subscription to just the devices you own, rather than including all public events also. | The following Particle Cloud Function APIs are working, whilst the remainder are not available for use (yet). Please note that there is a [[https://community.particle.io/t/doing-something-wrong-with-particle-publish-subscribe/14926/10|known]] [[https://community.particle.io/t/particle-subscribe-unique-device-id-not-returning-correct-values/18422/5|bug]] in the Particle.subscribe() function, where specifying a unique device ID to subscribe to has no effect. This is a bug on their side, and the current workaround is the specify the MY_DEVICES constant instead, in order to limit the subscription to just the devices you own, rather than including all public events also. | ||