|
1 | 1 | # Changes
|
2 | 2 |
|
| 3 | +## 26-May-2022 (claiming and ota) |
| 4 | + |
| 5 | +- claiming: Make self claiming as the default for esp32s3 and esp32c3 |
| 6 | +- ota: Make "OTA using Topics" as default and provide a simplified API for that |
| 7 | + |
| 8 | +Self claiming is much more convenient and fast since the node directly gets the |
| 9 | +credentials from the claiming service over HTTPS, instead of using the slower BLE based |
| 10 | +Assisted claiming, wherein the phone app acts as a proxy between the node and the |
| 11 | +claiming service. However, with self claiming, there was no concept of |
| 12 | +[Admin Role](https://rainmaker.espressif.com/docs/user-roles.html#admin-users) and so, it was |
| 13 | +not possible to access the node via the RainMaker or Insights dashboards. This was one |
| 14 | +reason why Assisted Claiming was kept as a default for esp32c3 and esp32s3 even though |
| 15 | +they support self claiming. |
| 16 | + |
| 17 | +With recent changes in the Public RainMaker backend, the primary user (the user who performs the [user-node |
| 18 | +mapping](https://rainmaker.espressif.com/docs/user-node-mapping.html)) for a self claimed |
| 19 | +node is now made as the admin. This gives the primary user the access to the node for OTA and Insights. |
| 20 | +So, self claiming has now been made as the default for all chips (except esp32) and the OTA Using Topics |
| 21 | +has also been made as the default, since it is convenient and also the correct option for |
| 22 | +production devices. A simpler API `esp_rmaker_ota_enable_default()` as also been added in esp_rmaker_core.h. |
| 23 | + |
| 24 | +Note: Nodes that are already claimed via Assisted/Host Claiming will not have any effect, even if the |
| 25 | +new firmware is enabled with self claiming. The self claiming will take effect only if the flash is |
| 26 | +erased. **This will result in a change of node_id, since mac address is the node_id for self claimed nodes.** |
| 27 | +If you want to contine using Assisted Claiming (probably because there is quite some data associated |
| 28 | +with the node_id), please set is explicitly in your sdkconfig. |
| 29 | + |
3 | 30 | ## 25-Jan-2022 (app_wifi: Minor feature additions to provisioning workflow)
|
4 | 31 |
|
5 | 32 | Added a 30 minute timeout for Wi-Fi provisioning as a security measure. A device reboot will be
|
|
0 commit comments