electronicsguy
commented
7 years ago hi.. good to know it's stable now. You can also increase the value of the sleep timer in the end of loop() to potentially increase stability.
Fingerprint is useful for mitigating man in the middle attacks. You can google for it.
you don't need to configure permissions separately. When you publish the app with the permissions as explained in the readme, google will ask you permissions (the first time) for the app to access sheets, calendar, etc. You have to say yes there. There is no other way, that I know of.
Security here is dependent on the secrecy of the published web-app's public URL. As long as you keep that secret, no-one should be able to access your data.
lorol
mik00
@electronicsguy Thank you for sharing this great work!
I managed to run the sample. On standard ESP8266 2.3.0 core , it works a bit fragile* (an UPDATE1 see below) and tricky in regards of connectivity from/to google. Could you please explain in more details: 1) What is the exact role of Fingerprint (UPDATE2: I found the details, just they can be more clear that it is optional and because of Google updating, it cannot be used as fixed string) ?
2) What best permissions for publishing and sharing levels need to be configured on Google online Calendar , Spreadsheet and Script respectively - I needed to set everything to be exposed maximally to Internet (less security) to run the push and pull of the sample - is this necessary or only certain access is enough?
*UPDATE1: after using the newest dev. core 2.4.x of ESP8266 as per https://github.com/esp8266/Arduino/issues/3330 , the example runs much more stable and smooth: at least several hours with no reboots or connections drop!