-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Unable to OTA devices, latest HA, latest Tasmoadmin, HAOS install. #291
Comments
The check that's being done is the backend is checking if it can access the firmware that the given URL to ensure that things are downloaded/accessible. I'm guessing the firmware is not accessible on the URL provided? |
This was posted a few days ago. I am seeing the same problem. *** Nevermind, problem was PEBCAK. I had the TasmoAdmin update address as my Unraid server IP FFS!!! |
Ok, so I installed TasmoAdmin on my Unraid server as a docker container and it will OTA properly. I can run it there, but I really want my HA server to handle all the duties of my automated home. I have updated everything including the latest TasmoAdmin and the latest version of HA. This stinks of TasmoAdmin not having correct file system permissions in HA. Add-on version: 0.24.3 TasmoAdmin startup on HA with debug enabled, says symlink completed... where would that reside? s6-rc: info: service base-addon-banner successfully started |
i'm seeing the very same problems on my side. "Minimal Firmware is not accessible on the server at http://10.0.0.126:9541/data/firmwares/tasmota-minimal.bin.gz
logs are not very usefull..... (seems that only the startup of the module gets logged) is this update-service working for anybody running the Home Assistant Operating System? |
Very strange - I'm running the addon from the edge repository and not experiencing any issues.
|
well, this is sort of strange.... but something trivial as deinstalling and reinstalling the addon did solve the problems in my case. Device 5 |
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
Problem/Motivation
Cannot OTA my devices, appears that the files are never download to my HA server.
Expected behavior
I would expect the OTA to work, it does work from the devices looking to github for the firmware.
Actual behavior
Steps to reproduce
When filling out the update form and either picking automatic or supplying my own files via browse I end up in the same situation.
Proposed changes
The text was updated successfully, but these errors were encountered: