After trying your data, I realized that something in my script was ordering things by date when I didn’t want it to. Turns out the row_number() function I was using doesn’t use the existing rows # - it orders things. After switching to the row names() function, I do see a substantial amount of chunking in the Export data. And completed year vs uncompleted year doesn’t seem to matter.
2021 (completed year)
2022 (unfinished year)
I’m guessing my daily data is only perfectly ordered because there isn’t much of it yet from July 28 until yesterday. The hourly data is twelve times larger and then gets subjected to this chunking.
I wonder if there is some kind of memory management working inside the Sense, allocating chunks of memory to hold data. But the Export just exports it sequentially???
I’m guessing that’s it. Sense bundles up and exports internal data tables without an additional sort (CPU time at Amazon costs money). I’m guessing they don’t need to sort because most display packages don’t needs sorted data to do the nice graphs - the packages order/bin/aggregate etc. as they need to. That’s why I haven’t even noticed until now.
Sense support acknowledges the problem but does not have an ETA for a fix.
I found another way to work around. Chrome allows the time zone of a single tab to be set to something different than the PC’s time zone. It’s in Menu, More Tools, Developer Tools, Console, Sensors, Location. I added a location for Tucson. With that location selected, the displayed and exported data are as they should be. And this workaround doesn’t mess up other things, like times for emails and saved files.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
