#Tasmotaadmin doesn't appear to work after changing HA IP.

1 messages · Page 1 of 1 (latest)

rocky rose
#

I recently changed my router, and had to setupa new subnet for my devices. I want to add them to my IoT vlan, but I'm not able to get TasmotaAdmin to load after changing the IP. Any ideas on what I need to do to get it to load in HA again ? It does load if I open the WebUI on it's own, just not using HA anymore.

rocky rose
#

Has anyone tried doing this ?

idle tiger
#

What does the log of the TasmoADmin app say?

rocky rose
#

Nothing, just says that it's running.

rocky rose
# idle tiger What does the log of the TasmoADmin app say?

Here is what I see..

-----------------------------------------------------------
 Add-on: TasmoAdmin
 Centrally manage all your Sonoff-Tasmota devices
-----------------------------------------------------------
 Add-on version: 0.33.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 17.1  (amd64 / generic-x86-64)
 Home Assistant Core: 2026.2.2
 Home Assistant Supervisor: 2026.02.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
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
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
s6-rc: info: service init-tasmoadmin successfully started
s6-rc: info: service php-fpm: starting
s6-rc: info: service php-fpm successfully started
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
[19:30:11] INFO: Starting PHP-FPM server...
s6-rc: info: service legacy-services successfully started
[19:30:11] INFO: Starting NGINX server...
#

So I just noticed that the page is showing the old IP still..

#

Nothing is "configured" to use that IP..

#

Here is debug level logging..

-----------------------------------------------------------
 Add-on: TasmoAdmin
 Centrally manage all your Sonoff-Tasmota devices
-----------------------------------------------------------
 Add-on version: 0.33.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 17.1  (amd64 / generic-x86-64)
 Home Assistant Core: 2026.2.2
 Home Assistant Supervisor: 2026.02.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
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
[19:54:11] 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
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
[19:54:11] INFO: Starting PHP-FPM server...
s6-rc: info: service legacy-services successfully started
[19:54:12] INFO: Starting NGINX server...
rocky rose
#

Holy crap! I think I just fix it..

#

I did!!!!

#

I had to click on the edit button, and change the IP it was trying to connect to there..