Skip to content
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

Firmware version changing on reboot? #82

Open
cavazosomar opened this issue Dec 30, 2024 · 3 comments
Open

Firmware version changing on reboot? #82

cavazosomar opened this issue Dec 30, 2024 · 3 comments

Comments

@cavazosomar
Copy link

After updating to the latest version (v2024.12.27 currently) I realized that just after finishing the update process a few features don't work such as the relays, vibration, configuration selections, and the device webpage, even the restart button doesn't do anything. After a power reboot the device does come online with everything working however the firmware version appears as v2024.12.19 instead of the version I just uploaded

Right after upload:
Screenshot_20241230_004538
Screenshot_20241230_004805
Screenshot_20241230_004746

After reboot:
hass-tx-ultimate

@edwardtfn
Copy link
Owner

On your device's yaml, please change from TX-Ultimate-Easy-ESPHome_core.yaml to TX-Ultimate-Easy-ESPHome.yaml and flash it again. It should all be back.

@cavazosomar
Copy link
Author

Now the device doesn't require a reboot to start working howeverr I'm still getting the same results, the firmware still reports v2024.12.19 even though it displays v2024.12.27.
I tried changing ESPHome/TX-Ultimate-Easy-ESPHome_core.yaml for TX-Ultimate-Easy-ESPHome.yaml in my yaml file and directly appending - ESPHome/TX-Ultimate-Easy-ESPHome_standard.yaml to my original file (which already included a reference to ESPHome/TX-Ultimate-Easy-ESPHome_core.yaml). Both with the same results

I'm attaching the log from the last firmware update

logs_tx-ultimate-3g_run.txt

timeline where the firmware version is mentioned:
[02:24:22]
[02:25:48]

@arnonh
Copy link
Contributor

arnonh commented Jan 6, 2025

I think it is some sort of fail-safe of the bootloader meaning the v2024.12.27 version doesn't work reliably ,
try testing with the new "revert-to-media-player-as-default" branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants