Home Assistant Community Add-on: TasmoAdmin

Installation Home Assistant OS
,
63

Thank you! An update is coming pretty soon! (Including the rename to TasmoAdmin)

2 Likes
64

Hi
Can anyone help me with setting up a Sonoff in HA? I am new to HA after realising that I made a fatal error buying a SmartThings hub.
I didn’t name all of my Sonoff’s with different project names when I flashed them with Tasmota, but I have since used SonWEB to change the friendly name and the host name and the Tasmota web page to change the MQTT topic all to the same name - HallLights.
I have set up Mosquitto MQTT and added the script in the configuration.yaml file, I can see the switch on the overview page, but it won’t turn them on. Could anyone tell me where I’ve gone wrong?

14
141134×1448 263 KB

65

Try checking your Mosquitto logs to check whether your devices are actually connecting.

Also, try setting a username and password in your Mosquitto settings, and then setting the the same details in each device. It looks as though there is a password set in each device - but you haven’t set one in Mosquitto.

Eg.
mqtt:
broker: core-mosquitto
username: something
password: something

66

Thanks Lee,
I’ve added the password and that’s not worked, this is the log;
starting version 3.2.2
1529228117: mosquitto version 1.4.12 (build date 2017-06-01 13:03:48+0000) starting
1529228117: Config loaded from /etc/mosquitto.conf.
1529228117: Opening ipv4 listen socket on port 1883.
1529228117: Opening ipv6 listen socket on port 1883.
1529228117: Warning: Mosquitto should not be run as root/administrator.
1529228120: New connection from 172.30.32.1 on port 1883.
1529228121: Socket error on client , disconnecting.
1529228121: New connection from 172.30.32.1 on port 1883.
1529228121: New client connected from 172.30.32.1 as 3626eb9c-cab8-4448-8f9a-816d2bdc4fa6 (c1, k60).
1529228148: Client 3626eb9c-cab8-4448-8f9a-816d2bdc4fa6 disconnected.
1529228166: New connection from 172.30.32.1 on port 1883.
1529228166: New client connected from 172.30.32.1 as 1d8b894e-3554-4eeb-9e84-3cd91f66be86 (c1, k60).
1529228417: Client 1d8b894e-3554-4eeb-9e84-3cd91f66be86 disconnected.
1529228435: New connection from 172.30.32.1 on port 1883.
1529228435: New client connected from 172.30.32.1 as 8b60291d-3c6c-4877-aa1e-0d02f575b658 (c1, k60, u’DVES_USER’).

67

On the tasmota page the host should be the IP address of your pi

1 Like
68

Thanks!! that’s fixed it. Appreciate your help!

69

Having a problem getting it to work in panel_iframe

I copied the iframe section from the install but I just get a blank page with sonweb in the top corner.

I have tried using http, https my duckdns address and local ip address and with and without :9541 but get ether the blank screen or broken link image.

addon is great and working through the web ui link

70

Have you forwarded the port on your router?

71

Port forwarding is set to forward port 9541 to the ip address of my pi with hassio installed.

Set up port forwarding in the same way for hassio to port 8123 and mqttserver on 1883 and both these work ok.

72

What are the iFrame settings?

73

These are the settings I am trying

panel_iframe:
  sonweb:
    title: SonWEB
    icon: mdi:lightbulb-on
    url: https://xxxxxxxxxx.duckdns.org:9541
74

Please be sure to check your browser console, it will definitely show you what’s wrong.

75

Feels like this should be obvious but where is the browser console

76

In most browsers (e.g. Chrome) this can be opened by pressing F12.

77

Offtopic

Please DO NOT forward port 1883 of MQTT, this is the unsecured port (without SSL).

/ End off-topic.

2 Likes
78

here is the console report does this help to give me a reason as it means nothing to me

[Deprecation] Styling master document from stylesheets defined in HTML Imports is deprecated. Please refer to https://goo.gl/EGXzpw for possible migration paths.
static/icons/favicon.ico:1 Failed to load resource: net::ERR_CONNECTION_REFUSED
27core-28b81466033e83fc2478e2db92d668d6.js:1 WebSocket xxxxxxxxx.duckdns.org:8123/api/websocket?latest’ failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
n @ core-28b81466033e83fc2478e2db92d668d6.js:1
The FetchEvent for “https://xxxxxxxxx.duckdns.org:8123/sonweb” resulted in a network error response: the promise was rejected.
service_worker.js:279 Uncaught (in promise) Error: Both cache and network failed: “TypeError: Failed to execute ‘fetch’ on ‘ServiceWorkerGlobalScope’: ‘only-if-cached’ can be set only with ‘same-origin’ mode”, “No result returned”
at u (service_worker.js:279)
at f (service_worker.js:279)

79

Further info

If I go directly in my browser to

http://xxxxxxxxxxx.duckdns.org:9541

I get to the login page but if I use http in the configuration.yaml the browser console state mixed request can’t use https and http.

If I then change configuration.yaml to https iget the above error and also putting

https://xxxxxxxxxxx.duckdns.org:9541

In the browser does not get me to the login page

Any ideas?

80

if you can go to http://duckdns then you don’t have SSL installed.

81

:tada: Release v0.2.0

This release renames SonWEB to TasmoAdmin.
It follows the upstream project rename, which has recently been done.

This version upgrade TasmoAdmin to v1.1.0, which contains a lot of fixes and new features!

Enjoy! :construction_worker_man:

Full Changelog

Fixed

  • Corrected Docker images names
  • Fixes upstream changed webroot location
  • Fixes incorrect data directory

Changed

  • Rebranding to TasmoAdmin
  • Rewrites GitLab CI
  • Upgrades base image to v1.4.2
  • Upgrades git to 2.15.2-r0
  • Upgrades TasmoAdmin to v1.1.0

Removed

  • Removes patch, since it is no longer needed
82

I’m getting a 502 bad gateway error. I am using Caddy and I changed my sonweb to tasmoadmin and changed the iFrame etc… caddy seems to be issuing the ssl certificates…