Alexa handshaker 4 software#
In my humble opinion, I came across a major software bug in the BIOS setting. A reboot again failed to have the Lenovo logo appear, no reaction on keys F1 to F12, no way to enter BIOS setup, let alone start an operating system. The "Save and Reboot" led to a bricked device, again: Black screen, nothing happened for 45 minutes. An Info Box popped op, saying the resetting with take "up to 15 seconds" with this option enabled.
Alexa handshaker 4 Patch#
Things went fine until I chose to "Enable" the "BIOS support for Thunderbolt", a setting suggested by the BIOS help appearing on the right quarter of the BIOS setttings screen for installation of Windows 10 before a certain patch level and for installation of Linux.
This time, trying to set up the BIOS for Linux installation, I always changed but a single setting and chose the "Save and Reboot" option. Customer support told me this was a technical defect, and I sent the device back to the dealer.Ī week later, the new Lenovo P52 arrived. No Lenovo logo appeared, clicking F1 (or any other function key) did not lead into the BIOS settings. After about 30 minutes, I tried a re-boot again, the screen stayed black. After changing some settings, I chose "change settings and reboot", and the device entered a nonresponsive state: Screen black with the exception of a single white pixel in the left upper edge of the screen. The device arrived, and I opened BIOS settings to prepare for the Linux installation I had planned. When you connect Teacup with the Alexa app, instead of asking for your Teacup password, it asks you to sign in from a real browser and generate a temporary device code.Relying on the information on the Lenovo website listing "Ubuntu" and "Redhat certified" under "Operating Systems", I chose a Lenovo P52. Rather than asking people to enter passwords in the Alexa app, I opted to solve this a different way while still being compatible with Amazon's service. This is the whole reason we have OAuth in the first place! You never want to train your users to enter their passwords into random apps. In Amazon's docs, it says "The user logs in using their normal credentials for your site." This is a really bad idea. They say that they'll launch your authorization URL from inside the iOS app, which is a known antipattern for apps in general. One thing struck me about Amazon's recommendations about building OAuth support in your app. Luckily, I'm pretty familiar with OAuth 2.0, so I was able to build this out pretty quickly. This is a pretty clever solution actually. Essentially, the Amazon Alexa app on your phone acts as an OAuth 2.0 client, and you have to build an OAuth 2.0 server into your app that it works against. Amazon provides great documentation on this, and thankfully it's all based on OAuth 2.0 rather than having made up some other model themselves.
The next challenge was linking user accounts between Amazon users and Teacup users. It isn't clear to me whether the list of keywords I provided is the complete set, because while I was testing, it managed to post the word "on" for the food, which is not in my list.
Alexa handshaker 4 mac#
A couple years ago, I wrote a small Pebble app that allowed me to quickly post common food and drink from my watch! Coincidentally around the time Pebble announced that FitBit had acquired their assets, my Pebble stopped working completely. If you know me, you probably know that I log everything I eat and drink and post it to my website.