That mistake is really easy to make because of the way the url redirects so I’ve updated the documentation to point that problem out.
In version 1.0.2, which I released last night, I added a label below that field that shows what the url should start with. I also made it check the url when you tap Done and if it starts with a url it writes a warning to Live Logging and doesn’t attempt to run. It will also write a warning to Live Logging if the url looks like, but doesn’t work.
Yes, there is a risk of data lost because if more than 5 events occurred within 5 minutes, they will get lost. The SmartApp only logs events that were generated by the device so if there are other events like the platform polling a device, they will be counted towards those 5 even though they don’t get logged.
I just counted the number of devices mine is logging and I was mistaken. I’m only logging events for 47 devices, but I have the maximum event setting set to 50 and I only see the occasional time out.
I know this isn’t ideal, but you could split your device list in half and run 2 instances of the SmartApp that are able to log a lot more events. You might be able to have both instances point at the same Google Sheet, but I haven’t tested it so I’m not sure what happens if they both send events to be logged at the same time.
My Dome Siren came in this morning so once I’ve finished writing that DTH, I’ll start working on a workaround for that timeout error.