-
Notifications
You must be signed in to change notification settings - Fork 41
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
Voice PE bricked? #266
Comments
It's running ESPHome, so you can access logs using a USB cable connected to your computer and the ESPHome CLI. |
I have this exact same issue. |
OK, managed to get it working. Follow these steps (from memory):
|
Hey thanks. I fixed it in almost the same way but using the esphome CLI. Your solution would have been faster. However this issue needs to be ironed out for the full release. The average person will not want to use a CLI or esphome. The hardware reset has to work at all times. |
Hi,
This worked just great! In addition to installing the latest firmware on the device the wizzard offered me to start the installation which I did. Now everything is fine. |
Hey all.
I got my Voice PE today and I was trying to set it up using my iPhone and the companion app.
It was discovered using BLE I entered the Wifi credentials and now the ring on the Voice PE is solid white and it seems to reboot (at least thats what I think it does) every 10ish seconds making a slight plop sound (presumably the speakers).
And I cannot connect to the ESPHome Node. I made sure that the IP is correct (its the IP of the Voice PE not HAOS), I even gave it the static IP just to be sure.
The worst part is that I cannot hardware reset it according to the instructions in the documentation. I keep holding and holding the button but the circle never turns red it stays solid white. I held it for a solid 120 seconds just to be sure and nothing happened.
How can I access the logs of this device, is there a way to get some sort of terminal based access? I am running MacOS.
Any help?
The text was updated successfully, but these errors were encountered: