Unable to OTA devices, latest HA, latest Tasmoadmin, HAOS install. about addon-tasmoadmin HOT 9 CLOSED

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?

from addon-tasmoadmin.

This was posted a few days ago. I am seeing the same problem.

TasmoAdmin/TasmoAdmin#810

*** Nevermind, problem was PEBCAK. I had the TasmoAdmin update address as my Unraid server IP FFS!!!

from addon-tasmoadmin.

I still have not been able to get this working...
With BE and FE checks disabled, I get the following...

Looks good, that is the version I would expect. When I attempt and upgrade I get the following log...

I have been unable to find the downloaded file on my HA machine... If I try the OTA URL in my browser I am greeted with a 403. So either it is not really downloading the files or the permissions are not right.

from addon-tasmoadmin.

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
You are running the latest version of this add-on.
System: Home Assistant OS 10.1 (amd64 / generic-x86-64)
Home Assistant Core: 2023.5.3
Home Assistant Supervisor: 2023.04.1

TasmoAdmin startup on HA with debug enabled, says symlink completed... where would that reside?

s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
Log level is set to DEBUG
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-tasmoadmin: starting
s6-rc: info: service init-nginx: starting
[16:32:57] DEBUG: Symlinking data directory to persistent storage location...
s6-rc: info: service init-tasmoadmin successfully started
s6-rc: info: service php-fpm: starting
s6-rc: info: service php-fpm successfully started
[16:32:58] INFO: Starting PHP-FPM server...
s6-rc: info: service init-nginx successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
[16:32:58] INFO: Starting NGINX server...
s6-rc: info: service legacy-services successfully started

from addon-tasmoadmin.

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
Please check the OTA IP address and port are correct
Full Firmware is not accessible on the server at http://10.0.0.126:9541/data/firmwares/tasmota.bin.gz
Please check the OTA IP address and port are correct"

wget http://10.0.0.126:9541/data/firmwares/tasmota-minimal.bin.gz
--2023-05-26 09:06:30--  http://10.0.0.126:9541/data/firmwares/tasmota-minimal.bin.gz
Connecting to 10.0.0.126:9541... connected.
HTTP request sent, awaiting response... 403 Forbidden
2023-05-26 09:06:30 ERROR 403: Forbidden.

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?

from addon-tasmoadmin.

Very strange - I'm running the addon from the edge repository and not experiencing any issues.

malachi@pulsar ~ $ curl -I http://192.168.1.100:9541/data/firmwares/tasmota-minimal.bin.gz
HTTP/1.1 200 OK
Server: nginx/1.24.0
Date: Fri, 26 May 2023 21:06:27 GMT
Content-Type: application/octet-stream
Content-Length: 265930
Last-Modified: Fri, 26 May 2023 21:05:57 GMT
Connection: keep-alive
ETag: "64711f35-40eca"
Access-Control-Allow-Origin: *
Accept-Ranges: bytes

malachi@pulsar ~ $ curl -I http://192.168.1.100:9541/data/firmwares/tasmota.bin.gz
HTTP/1.1 200 OK
Server: nginx/1.24.0
Date: Fri, 26 May 2023 21:06:37 GMT
Content-Type: application/octet-stream
Content-Length: 453911
Last-Modified: Fri, 26 May 2023 21:05:57 GMT
Connection: keep-alive
ETag: "64711f35-6ed17"
Access-Control-Allow-Origin: *
Accept-Ranges: bytes

from addon-tasmoadmin.

well, this is sort of strange.... but something trivial as deinstalling and reinstalling the addon did solve the problems in my case.
if you have not done so allready, you could give it a try....

Device 5
[2023-06-24T20:28:11.061Z] Starte Update Prozess
[2023-06-24T20:28:11.061Z] Attempting upgrade to version 12.5.0
[2023-06-24T20:28:11.061Z] Checking version...
[2023-06-24T20:28:11.201Z] Current version is 12.1.1(tasmota)
[2023-06-24T20:28:11.201Z] OTA Url => http://10.0.0.126:9541/data/firmwares/tasmota.bin.gz
[2023-06-24T20:28:11.286Z] Starte Module update...
[2023-06-24T20:28:11.367Z] Sleeping for 10s...
[2023-06-24T20:28:21.368Z] Update gestartet
[2023-06-24T20:28:21.368Z] Checking version...
[2023-06-24T20:28:21.424Z] Failed to fetch trying again... attempts left 9 sleeping for 10s...
[2023-06-24T20:28:31.426Z] Checking version...
...
[2023-06-24T20:29:46.534Z] Version is 12.5.0(tasmota)
[2023-06-24T20:29:46.534Z] Device upgrade successful

from addon-tasmoadmin.

For me I had SSL enabled on the addon, which blocks the http:// and opens it on https://

If i wget https://<my_domainname_or_IP>:9541/data/firmwares/tasmota-sensors.bin.gz --no-check-certificate I could download it

disabling ssl on the HA addon fixes it

from addon-tasmoadmin.

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

from addon-tasmoadmin.