I’ve tried 2 different browsers, I fill out all the fields, the code dictated by my speaker and the NEXT button in lower right hand side is always greyed out!
I don’t understand, tried redoing it 20 times, changing values, nothing works, button stays grey and does nothing when I click on it.
I’m having the same issue. I believe it’s a server-side issue with getting the list of currently registered devices. Whenever I change the name of the device in the form, a GET request is sent to https://account.mycroft.ai/api/devices which returns a HTTP-500 error.
Edit: Something you can do for now is enable the “Next”-button using inspect element, then hitting enter with your cursor in the room field. That should at least complete the pairing process, although you can’t manage anything in the web UI afterwards because the device does not show up.
This is unfortunately my first time attempting to use and setup mycroft, and this issue is something I am also running into. Installed on linux but unable to pair as the web UI won’t let me continue. Isn’t this exactly the reason we self host these things? So this won’t be an issue? And yet my self host bugs me to pair every command and I can’t even do it.
Edit: the other user notted a workaround that I was trying for an hour or so, until I figuered out you have to inspect element on the next button, delete anyhting on that line connected to “disabled” and replace “Disabled=true” to “enabled=true”. Successfully connected
Hi all, thanks for flagging this. The server errors have now been fixed, so please let us know if you are still experiencing any issues.
The outage was caused by a 3rd party API failure. We will be conducting a post-incident review to look at what we can learn from this, including how we can better detect and respond to issues like this in the future.
I’m also running into the issue…unlucky time to discover Mycroft, I guess. I tried the “edit HTML attributes” trick before I got here, but it still fails because the POST request is missing data from two voice-related config fields that simply aren’t showing up on the page. I tried disabling all local and network-wide adblocking, and using different browsers, but no dice.
…and I see @bubulescu has just pinpointed the same issue.
I went as far as trying to modify the XHR body directly inside Firefox’s dev console, but ended up with a 500 error instead of a 400 error. Hopefully this is fixed soon…I’ve got a VM running Mycroft just waiting to pair!