If anyone has heard of HomeAssistant then you would know that is is a an open-source home automation/control platform.
I will be getting the Vivokey Spark 2 installed sometime shortly but I would like to end up using it to login to the web frontend. I will have the NeXT implant installed first and would like to incorporate that into my home automation server also.
Once you have your Spark 2 installed you will have access to the Vivokey Forum @torynfarr was working on / looking at something similar around setting up a voice phrase trigger with Alexa / Google Assistant / Cortana, I imagine this would be the same principle.
Checking out the Home Assistant github repo, it looks like it’s all in Python. If they have plugins a la Wordpress, I’m sure you could write a Vivokey authentication plugin and have it play nicely. If Home Automation does not support plugins, you’ll have to fork it and change the base code itself. If they already support another OAuth method (especially if it uses OpenID Connect), it shouldn’t be too hard to copy and paste and change a couple of URLs. If Home Automation doesn’t support plugins or any current OAuth logins, that’ll be more of a chore but I’m sure there’s some drop-in-ready Python library that handles OpenID Connect authentication that you should be able to drop in. I don’t have time to dig into their code right now, so sorry for the generalities. I’m not so much a Python guy, but I have set up Vivokey auth in Node a few times and will be working on it in PHP soonish, so I’m happy to share any insight that might be useful.
I found this while searching openID connect in the forum.
I think it would it be possible to make just a few modifications and get this to work. Could any one help me with testing as I don’t have the vivokey implanted yet. I may be able setup a test home assistant server for someone to try and login to.
I’m not sure that would work. That appears to have the user type their third party username and password into the commandline, but of course Vivokey doesn’t have a password like Google, Twitter, or another OAuth provider would.
Appear that they’re grabbing the credentials from STDIN when the user manually runs the python program (e.g. py auth.py username=thunderblaster password=MySecretPassword).
I believe you would need to get the client browser to present the Vivokey login page to prompt the user to scan their implant (or else be doing some pretty next level hacks). Reading between the lines on their thread, I take it that the “new auth provider system” would allow flexibility maybe meaning plugins but you’d have to write the OpenID stuff “from scratch”. That might not be too bad as I’m sure somebody has implemented OpenID Connect in Python and it’d just be a matter of linking that up to Home Automation and dropping in the Vivokey API endpoints.
When will we be able to actually have a human-like conversation with Alexa, with context awareness and all that? Talking to voice assistants still feels like trying to use 1998 Dragon Dictate at times.
Can you run your own instance locally or does all your info and data go to their servers? For example, I want an AI assistant I can ask “what’s my schedule today” and have it be able to tell me and even remind me, but not need to open my calendar up to Mycroft or anyone else… is that what Mycroft is about? The reason I’m concerned about this level of separation is I also want an assistant to be able to dive into my files and content of those files so I can ask things like “how much hard drive space is being used by images?” or “can you find a microsoft word file on my file server that talks about the history of implants”… and I don’t want an outside company combing through my data, with ToCs that basically give it “ownership” to do whatever it wants with what it finds in those files…
Yeah, multi-turn dialog (what we call a conversation) is not great on any of the assistants. But I use her quite a lot. like I say ‘goodnight’ to her and all my lights in the house go out and it reminds me if I have no alarm set for some reason. Shes also great to pause the TV when someone calls calls (easier than finding the remote) etc. Basically my house is automated as possible and I use her for exception handling, alarms, reminders etc. All the smart home stuff runs internally on my own hardware.
Sure if you want to spend the time to strip the “phone home” features out of Mycroft. I’m no lawyer but it seems they collect information just like the rest. The difference is they’re vary transparent about it and you get the option of either they own your data or it becomes public domain for everyone.
Really with the way voice assistants are currently that’s just what you have to expect. They’ve come so far over a handful of years because of that data, and if you check out the ones that don’t collect data you’ll notice they’re substantially worse. Maybe in 20 years though your wildest dreams will come true.