I am using with a reverse proxy and it works fine. But remember with iFrame, you have to use https for the iFrame if the site is served by https - you can’t mix and match them.
Tried https also, but now i get ‘hassLocalipaddress’sent an invalid response.
Just found that addon … it is amazing.
ONE question is it save to update from version 6.2.1 with automatic mode?
THANKS
Same for me. Update does not work in spite of the messages show the update was successful. Message form console: 10:58:10 MQT: stat/devicex/UPGRADE = {“Upgrade”:“Failed HTTP error: connection refused”} … And I do not understand why I have to give an OTA URL source when I want to load the binary update - files from my local machine… And it is mandatory to fill in both sources.
Add-on version: 0.11.0
You are running the latest version of this add-on.
System: HassOS 3.13 (armv7 / raspberrypi4)
Home Assistant Core: 0.110.2
Home Assistant Supervisor: 225
Hi, i am fairly new to HA,
I have a fresh install on a RPI 3B+
i had a nightmare getting it to boot up correctly, i was using a very old netgear router as a hub, and the hassos would not start… or at least be accessible via the RPI-IP:8123… I could ping the IP etc , just not access HA.
Anyway, after attaching it via WIFI or LAN directly to my main router/hub all works fine.
i am trying to install TasmoAdmin and Portainer. both these install ok. but do not appear to start up… even after a reboot they do not start. niether of their WebUI load. if i refresh the addons page it shows they are not started.
is a simple way to see their logs (if any)
any help greatly received…
Cheers
Andy
doh!!
thanks… looks like i have a problem with the SSL (which i have not setup… everything is default settings so far,
[cont-init.d] nginx.sh: executing…
[14:37:14] FATAL:
[14:37:14] FATAL: SSL has been enabled using the ‘ssl’ option,
[14:37:14] FATAL: this requires a SSL certificate file which is
[14:37:14] FATAL: configured using the ‘certfile’ option in the
[14:37:14] FATAL: add-on configuration.
[14:37:14] FATAL:
[14:37:14] FATAL: Unfortunately, the file specified in the
[14:37:14] FATAL: ‘certfile’ option does not exists.
[14:37:14] FATAL:
[14:37:14] FATAL: Please ensure the certificate file exists and
[14:37:14] FATAL: is placed in the ‘/ssl/’ directory.
[14:37:14] FATAL:
[14:37:14] FATAL: In case you don’t have SSL yet, consider getting
[14:37:14] FATAL: a SSL certificate or setting the ‘ssl’ option
[14:37:14] FATAL: to ‘false’ in case you are not planning on using
[14:37:14] FATAL: SSL with this add-on.
[14:37:14] FATAL:
[14:37:14] FATAL: Check the add-on manual for more information.
[14:37:14] FATAL:
[cont-init.d] nginx.sh: exited 1.
[cont-finish.d] executing container finish scripts…
[cont-finish.d] 99-message.sh: executing…
everything works great now…
Portainer was failing due to the Protection mode enable. turning this off, all is ok. i will inspect further about turning this on.
Portainer will not start with protection mode enabled.
ok thanks again
Cheers
Andy
Hello, I have 1 tasmota 8.3.1 D1 mini with mqtt. Works very well.
But there is of course 1 thing not working (as always). After restarting hass the device is always “off”. This is the config (3x retain for mqtt is on?) and status as follows. Why is this? It should “retain” it’s status for this switch for my situation.
setoption 19 1 is used… (but only initially).
is allowed to remain silent or praise… 
Have installed TasmoAdmin and did an initial install. TasmoAdmin finds the devices I have enabled (i.e. SetOption19 1). However there is no data; e.g. version, hostname, mqtt and the devices don’t get added to Home Assistant.
Had a look at the TasmoAdmin log and there don’t seem to be any errors. Note: I’m running my own compiled version of Tasmota as I’m connecting to AWS IoT. What am I missing?
Tasmoadmin has nothing to do with devices being added to HA…
Ok so did I get this wrong? The about says that it scans and adds the devices. What does “adding devices” mean in this context?
About
TasmoAdmin (formerly known as SonWEB) is an administrative web interface to manage all your Sonoff-Tasmota flashed devices centrally. Some of its features:
- Scans your networks and adds your devices automatically
- See the status off all your devices quick and easy
- Configure all your devices from a single place
- Send out firmware updates over the air to one or more your devices at once
- Can automatically download the latest firmware for you
It means it adds the devices into the TasmoAdmin interface so you can administrate them.
TasmoAdmin isnt connected to HA and doesnt interface with HA. It simply allows you a simple interface to manage all of your Tasmota devices from one place.
If you want to add the devices to HA you need to have an MQTT broker that’s connected to HA, then configure your Tasmota devices to talk to that MQTT broker.
At that point you can manually configure each device inside HA via MQTT or enable MQTT autodiscovery inside the Tasmota device (which will allow HA to autodiscover them).
Thanks for the clarification. That makes things somewhat clearer.
Re TasmoAdmin I should still see more detail on my devices. As you can see from the screenshot… no data for 2.20 and seems to be looping forever but ok for 2.156. What’s the difference between the two? 2.20 is (successfully) connected to AWS IoT whereas 2.156 is connected to the local mosquitto broker. Could this be made to work with a broker other than a local broker on Home Assistant?
Re adding devices to Home Assistant I setup a local mosquitto broker and Home Assistant listed the Tasmota device (2.156) under devices and corresponding entities. Given MQTT implements a publish/subscribe model it shouldn’t matter where the broker sits right? Even if there was a manual step as opposed to automated discovery this wouldn’t be an issue for a home automation environment given the low rate of adding devices
Hello everyone,
I’m here because i can’t start tasmoadmin,
here’s my log:
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] 01-tasmoadmin: applying…
[fix-attrs.d] 01-tasmoadmin: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] 00-banner.sh: executing…
Add-on: TasmoAdmin
Centrally manage all your Sonoff-Tasmota devicesAdd-on version: 0.13.0
You are running the latest version of this add-on.
System: null (amd64 / intel-nuc)
Home Assistant Core: 0.116.4
Home Assistant Supervisor: 248Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing…
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nginx.sh: executing…
[11:11:12] FATAL:
[11:11:12] FATAL: SSL has been enabled using the ‘ssl’ option,
[11:11:12] FATAL: this requires a SSL certificate file which is
[11:11:12] FATAL: configured using the ‘certfile’ option in the
[11:11:12] FATAL: add-on configuration.
[11:11:12] FATAL:
[11:11:12] FATAL: Unfortunately, the file specified in the
[11:11:12] FATAL: ‘certfile’ option does not exists.
[11:11:12] FATAL:
[11:11:12] FATAL: Please ensure the certificate file exists and
[11:11:12] FATAL: is placed in the ‘/ssl/’ directory.
[11:11:12] FATAL:
[11:11:12] FATAL: In case you don’t have SSL yet, consider getting
[11:11:12] FATAL: a SSL certificate or setting the ‘ssl’ option
[11:11:12] FATAL: to ‘false’ in case you are not planning on using
[11:11:12] FATAL: SSL with this add-on.
[11:11:12] FATAL:
[11:11:12] FATAL: Check the add-on manual for more information.
[11:11:12] FATAL:
[cont-init.d] nginx.sh: exited 1.
[cont-finish.d] executing container finish scripts…
[cont-finish.d] 99-message.sh: executing…Oops! Something went wrong.We are so sorry, but something went terribly wrong when
starting or running this add-on.Be sure to check the log above, line by line, for hints.
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
I’ve already tried to change the ssl to “false” inside the add-on and i got:
TypeError: Cannot read property ‘value’ of null
And i tried to edit it manually and it didn’t do anything, when i reboot the config file goes default.
(sorry if i’m not very clear english is not my native language)
I hope someone could help me.
Here is my config if it can help for that addon. Make sure you have the port configured as well
ssl: false
certfile: fullchain.pem
keyfile: privkey.pem
Hello! I’ve been using TasmoAdmin for months now, but I cannot access it though Home Assistant since yesterday.
It started asking me to log in. When I enter the correct credentials nothing happens, I am returned to the login page (I tried incorrect credentials and then I get a warning saying “Login data incorrect”). I tried uninstalling the plugin and installing it again. Still, the same issue persists. The log doesn’t contain any errors.
If I try accessing it directly (hassio:9541 in my case) the login then works and I can use the admin.
Any insights why would it not want to work through hassio GUI?
1 Like