-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Difficulty entering HA credentials #92
Comments
We have a setup guide here, but I agree that it is somewhat hidden at the moment. In the future, I'll implement the setup tutorial right into the app.
I'm not really following what you mean by that.
That's definitely something I should support soon. Even though I don't have a keyboard to test this with, I should try to implement it anyways.
Haven't heard of that yet. Will look into if it makes sense to add this way of setting it up too. I think the best way would be to host a QR code generator on our website which you could then scan with the headset to have a seamless setup, but for that Meta needs to implement a QR Code scanner first. Also thank you very much for the feedback! |
Oh haha, I just noticed that yesterday too, thanks for the report! |
Actually I couldn't access the guide when I was initially setting it up. I think your website was down briefly, so just tried different methods to enter the server info.
Sometimes virtual keyboards (like on phones) have additional layers of characters you can switch between. I couldn't find a colon on your virtual keyboard so I tried holding shift and other keys in case the character was hidden on another layer.
Happy to test it if you end up adding that. Since getting a Quest 3 I've found passthrough + physical keyboard really practical, especially for MR apps coming from web or desktop.
Yeah, the SideQuest app has a text box you can push to the connected HMD. It beats using a virtual keyboard to enter 20 random characters to log into something on the headset and you use a password manager. This possibly enters text using the same method as a Bluetooth keyboard, so enabling one may enable the other.
Nice thinking. That would definitely be the ideal solution 🤞
|
As a new Immersive Home user on Quest 3, I tried to enter my Home Assistant URL with 3 different methods before realising it could only be filled by pasting text copied from another app on the headset:
I finally managed to enter the URL using these steps:
I understand that the token is far too long to enter by hand, but a complete keyboard and handling keystrokes/pasting from input devices and SideQuest would reduce the barrier of entry.
Also, nice work on kicking off a great open-source project. I'm interested in seeing where this goes.
The text was updated successfully, but these errors were encountered: