I received the email from IFTTT this morning as well stating the applet that WeatherFlow created had been turned off. The last recorded observation that my Google Sheets received from the IFTTT applet was February 5, 2019 at 08:44AM. This is probably the exact time that @iladyman received his last observation at February 6, 2019 at 01:44AM which stands to reason due to the time zone difference from US to Australia.
I signed into IFTTT and turn the applet back on and so far the observations have been steadily recorded to my Google Sheets. You got to love those complex computer science problems.
I had the same problem as @KJ.Davis and @iladyman. Turning the applet off and on again seemed to solve the problem, bit it is weird it happened to us all!
I missed only 2 hours 11 minutes of observations from 08:44am to 10:55am before finding out the applet was turned off. Not a big deal since I caught it early on.
Have you noticed any data losses during other days? I see the odd skipped minute every day and I am trying to work out why this is. The observation is not missing in the web/app graphs so clearly it is reaching the WF servers. Is there therefore an error with the IFTTT applet that means the odd observation is not being added to the Google Sheet, or is the missing observation arriving late at the WF servers (i.e. it is being backfilled by the hub) and therefore quite correctly is not being added to the sheet.
@dsj is there anyway to know if a specific observation was backfilled to the WF servers, or whether it arrived on time?
Every day I have seen observations missing from the Google Sheets file. I never get the 1,440 total. I imagine the data is being lost somewhere within IFTTT or lost in transit to Google Sheets. This is very similar to my experience with my other weather station. My Ambient Weather Osprey WS-2902A sends 1 minute observations to Ambient Weather Network and then forwards that data to Wunderground, PWS Weather, and Weather cloud.
It is with PWS Weather that I noticed missing 1 minute observations throughout the daily log. The February 5, 2019 Observation Log recorded only 1,349 out of 1,440.
Overall, I am not complaining since the data logging by Ambient Weather and WeatherFlow is free. Much thanks to what these companies provide for free to us. If I can get the bulk of the observations logged then it’s a win/win.
I think it might have to do with the time stamp having the seconds dropped. I have asked before what happens when the Hub sends two observations in the same minute. There is documented proof this happens as the clocks in the Air and Sky run fast.
I’m inclined to think that this is the issue too with at least some of the missing observations. The fact that right now the timestamp of the observations in the Google Sheet is a minute ahead of the timestamp of the observation in the app/web lends weight to this argument.
I’ve noticed that recently the observations have stopped being recorded every minute - sometimes there is as much as a 10 minute gap between them. Is it just me or a general slow down?
The past few days the applet was only recording an observation every two hours. Last night, I turned off the applet and re-saved my preferences and the applet started working again like it should normally. After scanning through the data this morning, I noticed gaps started to form between observations. Now observations look between 14-15 minutes apart. So data does seem to be lost in the void somewhere, Dan.
Hi, I’m new to IFTTT so I apologize if this is a stupid question. I’m got the Google-Sheets applet up and running. Is there a way to change the update frequency? I don’t actually need it updated once a minute, so was hoping I could edit it or duplicate the applet and customize it. Is this possible?
I played with IFTTT to google sheets and I dont think you can reduce the update frequency. However as a suggestion you might be able use Google sheets to run something that deletes your extra rows. My suggestion would be to try running something every hour to summarise your data into another sheet then delete those rows from where IFTTT is populating. This should also avoid the row limit problem.
There have also been other topics describing using sheets:
If you have the new IFTTT Pro, you can run a filter that would, for instance, only post data every 5 minutes, or hourly, or whatever. You wouldn’t be able to use IFTTT to summarize the data, so if you’re looking for that you’d need a different way to do it.
Is it possible to simply create a spreadsheet that pulls data when it rains and the total accumulated amount? I don’t want a spreadsheet that receives data every minute. I simply want a 24 hour log of total accumulated precipitation for my location.
Yes and no.
The current standard weatherflow IFTTT applet can create a spreadsheet that gets the data every minute which you could then automatically read the data to make the decision on what you wish to do. It could read the rain value … save the rain value to your new spreadsheet of rain… then delete the row from the observation log.
You might be able to get clues from @cswilly where he demonstrates and offers solutions:
Not sure if this is a IFTTT issue or a tempest issue, but I’m wondering if anyone else has run into this issue. I’ve got 2 IFTTT rules setup that when the brightness drops below 6500 brightness, it turns my lamp on and when it rises above 20k brightness, it turns the lamp off. The rule has been working and the turn off has worked 38 times as seen in the screenshot, and the turn on has worked about 14 times. As of April 21, it stopped running. In the picture you can see the brightness is @ 21k brightness and the lamp that is supposed to turn off is behind the tablet and is in the ON state. I have the IFTTT app to always run in the background so it should not be getting shutdown(not that this should matter). My WF has not gone offline. I’m not sure what else to check, any help would be greatly appreciated. I’m also using a teckin smart plug with the smart life app. I have a “tap-to-run” feature set in the smart life app as this the only way I could get the IFTTT to recognize the teckin smart plugs.
