{"id":13190,"date":"2017-02-07T13:47:04","date_gmt":"2017-02-07T18:47:04","guid":{"rendered":"http:\/\/embedded-lab.com\/blog\/?p=13190"},"modified":"2017-02-07T13:47:04","modified_gmt":"2017-02-07T18:47:04","slug":"animated-iot-clock-cant-trusted","status":"publish","type":"post","link":"https:\/\/embedded-lab.com\/blog\/animated-iot-clock-cant-trusted\/","title":{"rendered":"Animated IoT clock that can&#8217;t be trusted"},"content":{"rendered":"<p>An <strong><a href=\"https:\/\/www.youtube.com\/watch?v=RZ90ruADrI4\" target=\"_blank\">animated IoT clock<\/a><\/strong>\u00a0shared by <em>Tobozo Tagada<\/em>\u00a0does not use any\u00a0RTC module orconnect to a NTP server to retrieve the time. It rather scans the open WiFi access points in its surrounding\u00a0and extract the date\/time from the &#8220;Date&#8221; HTTP header, if sent out by some. Trust this clock&#8217;s accuracy at your own risk. It uses WeMOS ESP8266 board and an OLED screen to display the time along with a pong animation in the background to &#8220;cut on the boringness of the clock&#8221;, as he said.<\/p>\n<blockquote><p>Expecting unknown networks to provide a HTTP header value and relying on it to estimate time is like counting on other people&#8217;s wealth to survive, hence the Hobo name.<\/p>\n<p>The exclusive use of open access points removes the hassle of hardcoding SSID\/password into the sketch but also compensates its lack of auth plus the fact that the optional NTP connexion attempt will always fail, unless the AP acts as.<\/p>\n<p>The Pong animation with a bouncing rotating cube is there to cut on the boringness of the clock but also to demonstrate how this tiny OLED can animate fast (nearly 60fps).<\/p>\n<p>Since it has trust issues, don&#8217;t trust this clock more than you would trust a stranger&#8217;s watch! The available space and power consumption won&#8217;t let it run more than a couple of hours on the LiPo anyway.<\/p><\/blockquote>\n<div id=\"attachment_13191\" style=\"width: 524px\" class=\"wp-caption aligncenter\"><a href=\"http:\/\/embedded-lab.com\/blog\/wp-content\/uploads\/2017\/02\/hobo.jpg\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-13191\" class=\"size-full wp-image-13191\" src=\"http:\/\/embedded-lab.com\/blog\/wp-content\/uploads\/2017\/02\/hobo.jpg\" alt=\"Animated IoT clock\" width=\"514\" height=\"383\" \/><\/a><p id=\"caption-attachment-13191\" class=\"wp-caption-text\">Animated IoT clock<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"<p>An animated IoT clock\u00a0shared by Tobozo Tagada\u00a0does not use any\u00a0RTC module orconnect to a NTP server to retrieve the time. It rather scans the open WiFi access points in its surrounding\u00a0and extract the date\/time from the &#8220;Date&#8221; HTTP header, if sent out by some. Trust this clock&#8217;s accuracy at your own risk. It uses WeMOS ESP8266 board and an OLED screen to display the time along with a pong animation in the background to &#8220;cut on the boringness of the clock&#8221;, as he said. Expecting unknown networks to provide a HTTP header value and relying on it to estimate time<\/p>\n","protected":false},"author":1,"featured_media":13191,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1044],"tags":[1626],"class_list":["post-13190","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-esp8266","tag-esp8266-clock"],"_links":{"self":[{"href":"https:\/\/embedded-lab.com\/blog\/wp-json\/wp\/v2\/posts\/13190","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/embedded-lab.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/embedded-lab.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/embedded-lab.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/embedded-lab.com\/blog\/wp-json\/wp\/v2\/comments?post=13190"}],"version-history":[{"count":2,"href":"https:\/\/embedded-lab.com\/blog\/wp-json\/wp\/v2\/posts\/13190\/revisions"}],"predecessor-version":[{"id":13193,"href":"https:\/\/embedded-lab.com\/blog\/wp-json\/wp\/v2\/posts\/13190\/revisions\/13193"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/embedded-lab.com\/blog\/wp-json\/wp\/v2\/media\/13191"}],"wp:attachment":[{"href":"https:\/\/embedded-lab.com\/blog\/wp-json\/wp\/v2\/media?parent=13190"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/embedded-lab.com\/blog\/wp-json\/wp\/v2\/categories?post=13190"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/embedded-lab.com\/blog\/wp-json\/wp\/v2\/tags?post=13190"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}