Same issue here even from a file
I managed to progress by putting ota.tasmota.com/ as the OTA server (Iād read it needed to be the HA IP).
Despite it then changing the firmware locations for OTA on all devices the upgrades failed on all of them.
This is because it appends data/firmwares/ to the address, which is incorrect and in-configurable.
Looks like the addon is out of date from where Tasmota is stored.
The correct addition should be tasmota/release/ to make Tasmota ESP8266 Binaries
I read yesterday that if you use a .gz firmware instead of bin it doesnāt try and d/l minimal and should work,
Sadly nope. So Iām just doing 1 at a time via web browser
I do have a login loop, when i use tab from HA supervised installation, in anonymous sesion I can login. I have tried deleting TASMO_SESSION cookie, but Iām still stuck in login loop.
Iām having the same issue, updates used to work for me but now they donāt. Iāve gone through and manually updated all my devices with
which works and I only have 8 devices so not too troublesome. Would be good to get the string changed or be able to edit it to point to the correct repository.
I could be wrong but it looks like TasmoAdmin does actually download the latest files?
Forgot to say that Iām not getting error that I can find relating to this in any logs.
Iām having the same issue, I donāt allow my IoT devices to get to the internet and Iād rather not update them all manually.
Try pointing your devices to the correct path on your HA OTA location rather than internet OTA, BUT make sure the path is tasmota/release rather than data/firmwares.
I only noticed @mkjustuk 's post when on my last device update but it appeared to work for me.
Please ignore my last post, Iāve just tried to update using that info and it does not work! Not sure what I did when I last updated I thought it worked but obviously not.
For anyone else having this issue, hereās the solution,
https://github.com/hassio-addons/addon-tasmoadmin/issues/272
Iām not sure how I managed to get my config into this state, but I made sure all check boxes were unchecked and the updates no longer fail.
In tasmota admin I have several sockets that are flashed with the current Tasmota firmware 12.4.0.
If I now execute the command āWebserver 1ā, the WebUI is changed over correctly. If I then execute āWebserver 2ā, I receive an error and the socket is no longer correctly accessible. If the socket is disconnected from the power supply and then reconnected, the socket is accessible again.
Here is the error message:
Edit device
Device not found
JSON ERROR => 4: Syntax error
Please copy the whole error message and copy it in a new issue on GitHub. Somehow the Tasmota Firmware answered a wrong formatted JSON string which needs to get adjusted in TasmoAdmin.
JSON Answer =>
Warning: Undefined array key ādevice_idā in /var/www/tasmoadmin/tasmoadmin/pages/device_action.php on line 13
Fatal error: Uncaught TypeError: TasmoAdmin\DeviceRepository::getDeviceById(): Argument #1 ($id) must be of type string, null given, called in /var/www/tasmoadmin/tasmoadmin/src/Sonoff.php on line 318 and defined in /var/www/tasmoadmin/tasmoadmin/src/DeviceRepository.php:66 Stack trace: #0 /var/www/tasmoadmin/tasmoadmin/src/Sonoff.php(318): TasmoAdmin\DeviceRepository->getDeviceById() #1 /var/www/tasmoadmin/tasmoadmin/pages/device_action.php(13): TasmoAdmin\Sonoff->getDeviceById() #2 /var/www/tasmoadmin/tasmoadmin/index.php(55): include_once(āā¦ā) #3 {main} thrown in /var/www/tasmoadmin/tasmoadmin/src/DeviceRepository.php on line 66
For some reason Portainer always shows TasmoAdmin as either starting or unhealthy. Never did this before the last update
1 Like
I have the same āunhealthyā warning in my portainer (Home Assistan), any solution?
Running 2.15.1 at the moment as a test (previous 2.17.1)
only solution I have found is to ignore it. Itās still working.
In my environment, Tasmota devices are getting new IPs all the time. I have over 50 and do not have DHCP reserversations configured. Therefore TA is always getting out of sync. I cannot find a way of easily refreshing everything thatās out there without deleting all entries first which one must do manually one by one. In my case thatās over 100 entries to delete first. Is there a better way? Something obvious I have missed? Thanks!
1 Like
Why not assigning a fixed ip-address to your individual Tasmota devices?
Open the console and type:
savedata 1
ipaddress1 xxx.xxx.xxx.xxx
savedata 0
Dynamic gives a lot of other flexibility. My devices are mostly light switches and get reset all the time. Dynamic generally works out better. It would be good if TA could be configured to refresh itās inventory on demand. Autoscan doesnāt seem to remove old entries. It will add the same one again if the IP changed.
I use DHCP address reservations in my DHCP server. This causes the address to be the same but still ādynamicā.
Hi, I have a few sonoff miniās with firmware 6.7.1. Can you please help me with upgrade instructions using Tasmoadmin? I understand I have to do each incremental upgrades as below.
v7.2.0 v8.5.1 v9.1 Current release.
I downloaded both the minimal and the final versions for all these. When I tried to browse to the two bin files for v7.2.0 in the tasmoadmin upgrade screen, I see the below error.
Minimal Firmware is not accessible on the server at http://127.0.0.1:9541/data/firmwares/tasmota-minimal.bin
Please check the OTA IP address and port are correct
Full Firmware is not accessible on the server at http://127.0.0.1:9541/data/firmwares/tasmota.bin
Please check the OTA IP address and port are correct
Where exactly do I need to place the firmware files in homeassistant and how to do this? Also I am using https. How do I set the localhost to https.
Just added this to home assistant today. Previously they were mapped to my Smartthings, but werenāt being used. I see that if I turn on the switch, in a few seconds, it turns off automatically. Not sure whaāts going on.