Home Assistant Community Add-on: TasmoAdmin

I came across this addon, and it seems interesting, since my tasmota devices are increasing, and know keeping track of them by IP/MAC.
Only configured the Tasmota devices within home Assisstant, so having all together sounds great.

But I’m not able to get it working so far…

My HASS is accessible via DuckDNS and also having the MQTT broker addon configured.

I left the TasmoAdmin config as it was, with SSL on true (also tried it on false btw).

Am I overseeing something here?

I could not get it to work with duckdns but it does work via https://myipaddress:9541

1 Like

Thanks! Well got it working now, changing to http:// and set SSL to false.

But is there a way to get it configured from HASS itself?
When I click on the icon in the left bar, nothing happens.

Got this config in config.yaml:

panel_iframe:
  tasmoadmin:
    title: TasmoAdmin
    icon: mdi:chip
    url: http://my.local.HASS.IP:9541

Only manage to get it working when I type the adress mentioned above in a webbrowser manually.

I got mine working by adding a port forwarding rule on my router. Similar to what I needed to do to get 8123 working. I added another tcp rule, 9541 as both internal and external port and my ip address for my hassio as the internal ip address.

1 Like

Thanks! That did the job!

Only forwarded TCP 9541 to my internal IP of the Home Assisstant host.
Then “open web ui” in Supervisor was working, but it was refering to my duckdns:9541 adress.

The icon in the left still gave a blank screen when pressed. So no responce there. Changed SSL to true again and changed the adress of it (http://mylocal-ip:9541) in config.yaml to https://myduckdns:9541.

That worked for me! :+1: :smiley:

Edit:
Love it! All my Tasmota devices adjustable and controlable in one overview! :partying_face:

Don’t know if more people had this issue when using Tasmoadmin with DuckDNS, but I’m not able to get my devices upgraded, whatever I try…

  • I’ve tried to update automatically and select the lite version.
  • I’ve tried it manually with my local IP selected.
  • I’ve tried it manually with my DuckDNS adress selected.
  • I’ve tried it manually with my DuckDNS adress and “OTA use SSL” selected.

Annyone encountered the same problems?

Isn’t the OTA server the Tasmota server?

Uncheck OTA use SSL. Remove all references to .bin files from Firmware boxes. Hit Automatic

Thanks for the help!

But this is what I’ve tried the verry first time, leaving the .bin and the OTA fields blank and hit “Automatic”. But this was also not verry succesfull…

What about now? If you successfully update devices?

No, this is unfortunatelly not working for me.

Also only having the oppertunity to upload the lite version (which seems to be the smallest in the automatic option).
Only having 408kB free as program space on my devices. And the lite version is already 473KB. So I asume it also gives an upload problem?
The minimal version should fit with its 378KB if I’m correct?

On OTA Server IP use your internal IP address: 10.0.0.xxx of your HA. It’s work for me

1 Like

Thanks a lot for your effort Vlad, really appreciate it. But the local IP of my HASS host was the first thing I tried. Unfortunatelly not working :frowning:

Just update all by hand, which was verry time assuming :frowning:

Sorry for the absence…
Problem solved it was a conflict between 2 install of tasmoadmin one in my unraid app docker and the other in hass supervisor

Worked well for a time, but now won’t start with the error:

“403 Client Error: Forbidden (“endpoint with name addon_a0d7b954_sonweb already exists in network hassio”)”

Jim

Same problem here. Workaround until more replies or solution (on a local network): login directly, open settings, disable “Activate login” and save.

Excellent utility @Frenk!
Zero issues on first try, first install. Thanks once again for your time and effort, Happy Holidays.

did you get something i am the same

thank you anyway

No, didn’t looked after it annymore. Just left it as it is for a while now.

Hey @frenck , Great Job but one question.
Your Documentation doesn’t mention anything about a registration.
What am I registering for, what’s it used for, is it just internal to my HA instance or is it a Web Registration?