Question About Firmware 25.5.2 Upgrade on PE Devices

[calm vault]

I have two PEs. A few days ago, I manually upgraded one of them from firmware version 4.0 to the 25.5.2 preview version.
The other PE is still running the official 4.0 release.

Yesterday, I saw that version 25.5.2 was officially released, but for some reason, neither of my PEs has received an upgrade notification.

Should I manually upgrade to version 25.5.2, or just wait for the update notification?

Also, will the PE that I manually upgraded to the 25.5.2 preview version still receive the official release notification?

[split atlas]

not sure what you mean by "4.0", the VPE hasn't had a firmware release with that version number that I am aware of?

or do you mean "25.4.0"?

so just looked it up and whilst the latest is 25.5.2 now its only just changed from pre-release to release. and whilst "released" its not get been deployed.

you can see that the current version in the version check is 24.4.0 HERE
and the installer tool still has it flagged as pre-release here

I think we are waiting for THIS to be approved before it fully rolls out.

you should get the update notification soon, I would give it some time tbh unless you really want to get it manually.

ah... they may also be waiting for the ESPHome release later this week. and release them alongside each other

[calm vault]

Yes, I was referring to version 25.4.0. Currently, one of my PEs is on 25.4.0, and the other one I manually upgraded to the 25.5.2 preview version using this link:
https://esphome.github.io/home-assistant-voice-pe/

I would like to ask: after the official release of version 25.5.2, will the PE that I manually flashed with the 25.5.2 preview also receive the official update?

Thank you in advance for your help!

[split atlas]

i think it will be the same binary anyway, but if its not then yes it should get a notification too

assuming you have the firmware entity enabled in HA and the VPE's can access the internet in any case 🙂

[calm vault]

I believe the firmware entity is enabled, and the device is connected to the internet.

[split atlas]

then yes you should be fine

[calm vault]

A few days ago, I wanted to try the wake word sensitivity feature, so I eagerly flashed the preview version.

[split atlas]

fair enough

how did it go?

[calm vault]

So once the official version is released, I hope to switch to it as well. 😄 I always like to stay up to date.

The wake word sensitivity adjustment is a great feature. As a non-native English speaker, I set it to “highly sensitive,” and the wake success rate has improved significantly.

[split atlas]

thats great, do you get any more false positives because of it though?

[calm vault]

During the days I’ve been using the preview version, I’ve only experienced one false wake-up. It was triggered by music playing in my study room. Other than that, I haven’t had any false positives.

[split atlas]

thats cool, ill probably play with the new settings when it gets deployed

[calm vault]

The situation is already very good. Compared to having a very low wake-up rate, this is the best state I’ve experienced so far. However, for my family members who are non-native English speakers, it is still somewhat difficult to trigger the wake word.

[split atlas]

even as a native speaker, i have trouble with some wake words and had to change the way i was them slightly

the WW models will get updated and get better as time goes on

[calm vault]

Yes, that’s right. The pronunciation and tone of the wake word “okaynabu” can affect the wake-up success rate.

I hope it will get even better in the future.

[split atlas]

mine just popped

[calm vault]

I received it too. One of my PE devices, which was on firmware 25.4.0, got the update notification. I updated it, and it’s working fine now.
However, the PE that I had manually flashed with the 25.5.2 preview didn’t receive the update.
What’s strange is that the preview version seems to be missing one of the disabled sensors for some reason.
I reset the PE that I had previously flashed with the 25.5.2 preview version, but even after reconnecting, it’s still missing that sensor.

[split atlas]

the pre-release and the rolled out version are the same binary

[calm vault]

I’m just a bit confused as to why one of the sensors seems to be missing — maybe I overlooked something?
Thanks again for your help so far!

[split atlas]

you could try deleting and readding device to HA, and/or reinstalling firmware but honestly i am going to struggle with screenshots unless they are in English

[calm vault]

I’ve already tried removing the device from Home Assistant and adding it back, and I’ve also reinstalled the firmware. However, this sensor is still missing. The sensor that’s missing is a disabled entity named something like: binary_sensor.home_assistant_voice_0911e3_assist_in_progress (Voice Assistant in Progress).

[split atlas]

i am pretty sure that, that sensor is disabled by default. its not something that needs to be active

[fallen sinew]

That sensor is disabled now, it's replaced by sensor "assistant state".