Purpose Id 34 data was being updated while other frog1 sensor data was not being updated #28
Description
All of the frog1 state timestamps for webctrl were stuck at 8-3-18. There was a hole in the data source from 8-10 till 8-17. The state timestamp for purpose id 34 was being updated by scrape-util and the program didn't have problems dealing with the hole in the data. Scrape-util did however, have a problem with all of the other purpose ids that had that same hole in the data. We would like to know why.