<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Time zone handling through nRFCloud</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/93301/time-zone-handling-through-nrfcloud</link><description>Hello everyone, 
 I&amp;#39;ve got a simple question here today. I&amp;#39;m making use of the nRFCloud on our nRF9160-based system. 
 When using the different APIs to nRFCloud, be it location history, messages, whatever, they may contain a &amp;quot;insertedAt&amp;quot; timestamp. I</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 28 Oct 2022 13:37:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/93301/time-zone-handling-through-nrfcloud" /><item><title>RE: Time zone handling through nRFCloud</title><link>https://devzone.nordicsemi.com/thread/393049?ContentTypeID=1</link><pubDate>Fri, 28 Oct 2022 13:37:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6b0ed7d0-89c7-49c7-9b07-f1bc5b4cf5d7</guid><dc:creator>Torje</dc:creator><description>&lt;p&gt;Thank you, H&amp;aring;kon.&lt;/p&gt;
&lt;p&gt;After a brainstorming session we figured that we would always want to see times in the users local time,&amp;nbsp;whether their in Norway or Nepal, regardless of where the actual device is. We just adjust the zulu time to the local users time zone. So it&amp;#39;s really not an issue to us&amp;nbsp;anymore.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks, have a nice weekend!&lt;/p&gt;
&lt;p&gt;- Torje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Time zone handling through nRFCloud</title><link>https://devzone.nordicsemi.com/thread/393046?ContentTypeID=1</link><pubDate>Fri, 28 Oct 2022 13:31:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ad6924fb-e369-4608-b962-7a4e167cc0d4</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi Torje,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
[quote user=""]&lt;p&gt;When using the different APIs to nRFCloud, be it location history, messages, whatever, they may contain a &amp;quot;insertedAt&amp;quot; timestamp. I would like to use this timestamp as a &amp;quot;last seen&amp;quot; feature on my website. But these do not contain time zone info. I can get the time with time zone correction from the modem/LTE-network, and send this with some messages or put it in the meta. But this does not cover all data I request (like cell location data which is stored in the cloud after requesting).&amp;nbsp;If I wanted to put the time from the modem in the meta, I would have to receive and resend every cell based position as well. With a low-power design, I would like to avoid this.&lt;/p&gt;
&lt;p&gt;Today, I am sending GPS fix data as per the standard scheme (or cell location with no reply to device as fallback), and sending battery info and actual timestamp in a separate message. When I want to see just the location history, I would have to get the messages as well and match the times of the locations with the times of the battery-and-time-message. This seems like the long way around, and I&amp;#39;m hoping someone has a more elegant solution to this.&lt;/p&gt;
&lt;p&gt;Does anyone have any tips as how to get time zone based on the data from the LocationHistory API? &lt;/p&gt;[/quote]
&lt;p&gt;I am checking internally wrt. to this question. I will update you once I get feedback from our cloud team.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I wish you a wonderful weekend!&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>