#hey folks, has anyone managed to get a
1 messages ยท Page 1 of 1 (latest)
You don't stick dashboards on devices, they always live in HA
if you're trying to display HA's UI then that device needs a working modern browser
well...
https://www.youtube.com/watch?v=XvGmGBApVNc
i mean, what i REALLY want to do is be able to tell the mycroft, "hey neon, turn on the livingroom light", and it will do that through its link to HA. in this case, the HA client provided natively in Neon appears to be designed to interact with the HA server and display widgets.
do you know something about it?
Never heard of the Neon before your posts
#voice-assistants-archived may be able to help with the voice assistant side
yeah, i might try there. i just figured if i could see the client connection working as expected, the voice part wouldn't be too much more effort
but maybe i have it backwards lol
anyway, thanks for responding
Well, they're completely unrelated things
Displaying HA's UI is just about a web browser
Voice assistant is a whole different world
you may be right, though regarding the web browser part, i was thinking the whole purpose of using a longterm api key was to access/consume HA via API, meaning the display may or may not be a web browser, it could just be whatever interface is native to the platform, rendering the data etc
so i was thinking the voice assist part would be leveraging the same api?
Well, the voice assistant will use the API (looking at their docs)
For the display though, HA's UI is only accessible with a browser
that's what i mean, i don't think it's rendering from HA's UI
If showing anything from HA on the Mycroft needs a key then that's not going to be using HA's UI
However, the docs on that are ... zero
yup
Good work Mycroft ๐
hence why i came here, 8 hours of googling later lol
shot in the dark
next is... i dunno... hacking?
๐ช
I'd reach out to the Mycroft devs and ask them for help
They should know how their product works
yeah, i think that's actually the next step