#Do I have a $60 brick?

1 messages · Page 1 of 1 (latest)

deft hollow
#

After a long time sitting on the shelf waiting for some free time to dive into Home Assistant Voice PE, I can't get past step 3 in the Getting Started instructions.

I did a factory reset and got BT connected, then it refused my WiFi credentials.

Another factory reset and I can't even get back to the initial "Do you want to connect"? screen.

Even AI is down to guessing. Most recently telling me to delete the core container.

Do I have a $60 brick?

dusk blaze
deft hollow
# dusk blaze is the wifi network your trying to connect to a 2.4 ghz network?

Yes. I have over 100 WiFi and Ethernet devices on my Home Assistant. The ssid I used is for my 2.4GHz network.

I did try to install the latest PE firmware following the instructions in "Reinstalling the firmware on Home Assistant Voice Preview Edition from bootloader mode", which sounded promising, but that resulted in a strange error: "Installation failed- Your ESP8266 board is not supported". ESP8266 ???

dusk blaze
deft hollow
dusk blaze
deft hollow
#

Also, my Home Assistant host PC does not have Bluetooth.

dusk blaze
deft hollow
dusk blaze
#

i don't recommend that you build the firmware yourself from yaml. you should keep to the stock firmware unless you want/need to customise the firmware.

deft hollow
#

After the flash, the HAvPE just rebooted and went into BT pairing.

dusk blaze
#

you plug into your pc and you run the web tool on your pc browser the same as you did with the flash tool

#

it connects in the same way using the usb serial connection

deft hollow
dusk blaze
#

give me a moment and ill grab my spare vpe and go through process to check i am not missing something.

deft hollow
#

PROGRESS! One simple step- restart the HAvPE and then I was able to set up my WiFi credentials.

dusk blaze
#

yes, that is what i was expecting

#

once its on your wifi network your home assistant install should detect it and you can set it up.

#

the bluetooth improve is ONLY for wifi cred setting. as you had trouble doing that we are setting it via USB instead but the next step in either case is setup once its detected on the network.

#

saves me flashing my dev/debug vpe back to stock 😛

deft hollow
#

Thanks for the assist.
More progress. ESPHome detected the HAvPE and when installed, the ESPHome compier went to work compiling
hundreds of modules, and a couple of dozen warnings. Finally uploading the compiled binary. The device log looks good. And "Hey Nabu, what time is it" replied with the correct time.
Now the learning begins.

dusk blaze
#

why are you using the compiler? what customisations are you making to the firmware?

#

unless you are cusomising the firmware then you absolutly do not need to compile anything and do not even need the "builder tool" installed

deft hollow
#

I didn't intend to, I just clicked on "Submit" from the ESPHome dialog.

dusk blaze
#

are you talking about the integration OR the addon?

deft hollow
#

Neither. ESPHome detected the HAvPE and asked if I wanted to add it.

dusk blaze
#

when you say "ESPHome" that can mean multiple things.

deft hollow
#

ESPHome Builder, Discovered devices.

dusk blaze
#

given you said compiling it would seem that you are talking about the "ESPHome Builder" addon

#

there is no need to "take control" of the device in the builder tool

#

it should have popped up as a device on home assistant without that

#

the only reason to take control of it is that you want to customise the firmware in some way. if you are not planning on doing that then you should not have it added in the builder tool and should leave it as stock.

#

if it works for you now then that is fine but if you have any issues the first thing you are gunna be asked to do is flash back to stock.

deft hollow
#

Too late. I did "Take Control", but nonetheless the device appears to be working. But the device does not present at configuration - devices. It does present in configuration - Voice Assistants - 1 Assist Device.

dusk blaze
#

yeah, I am not saying that it wont work by taking control.
however you are downloading and compiling the current dev firmware instead of using the released "stable"
this can cause random issues from time to time and if you EVER have ANY problem. then flashing back to stock stable is going to be one of the first things.

unless you have a reason to run custom built firmware then you should not run non-stock firmware.

#

if its working that is fine and great but its just a bit of a warning.

#

if you want to go back to stock then you should remove from the builder tool and then plug into pc and use the firmware flasher tool to flash over usb again. then dont "take control" and just use it.
its entirely up to you but just a heads up.

deft hollow
#

I do appreciate your help. I think that the crux of my problem is that my Home Assistant host computer does not have Bluetooth and the "Getting Started" instructions doesn't address this directly. I do have a Bluetooth proxy on my desk but all I have ever used it for is a couple of thermometers.

WHY require BLE? Every ESP32 WiFi device uses a default AP for WiFi setup - except Voice PE?