Problem/Motivation

There are several reasons for this:

• Not all log messages are consistent across all add-ons.
• Some messages are unclear to the novice user.

TasmoAdmin doesn't work anymore

TasmoAdmin doesn't work anymore,I can't find a way to solve it
Underneath is the loggin when I start the Addon

[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... 
-----------------------------------------------------------
 Hass.io Add-on: TasmoAdmin v0.5.1
 Centrally manage all your Sonoff-Tasmota devices
 From: Community Hass.io Add-ons
 By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
 armhf / Resin OS 2.3.0+rev1 / HA 0.76.2 / SU 127 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing... 

Problem/Motivation

Can't Autoscan. it fails.

Expected behavior

Auto scan should work

Actual behavior

when running auto scan i get this error:
Recoverable fatal error: Object of class stdClass could not be converted to string in /var/www/tasmoadmin/tasmoadmin/includes/Sonoff.php on line 1000

Steps to reproduce

I am on a clean install of Hass.io 141 with the latest Tasmoadmin 0.6.0 fresh installthough through hassio and with RPI 1b

Proposed changes

Problem/Motivation

TasmoAdmin doesnt work anymore

Expected behavior

Open the web page, but it des not

Actual behavior

returns a "could not read MyConfig.json"

Steps to reproduce

Almost everytime i restart the docker image in hassio, it boots. When i open the UI i get only a "could not read MyConfig.json"

Proposed changes

Nope, tried removing it from hassio e reinstalling, but it alwasy (almost) gives the same error. Some times it works, but very slowly.

Problem/Motivation

(Why the issue was filed)

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Is possible support manage tasmota via MQTT in future ? Thank you

I installed this add-on in hass.io following the instructions and embedded it into Home Assistant, but when I click on it or select the "open web ui" button, it shows me a page where I have to put in a username and password to log in. Can someone help guide me on what to do next, or if I did something wrong and wasn't supposed to see a login page?

Problem/Motivation

Adding device by IP created error message requesting error message be posted

Expected behavior

assist programer troubleshoot

Actual behavior

Autoscan did not find this sonoff device after approx 100 scans. Tried add device with IP and received this error message.
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 SonWEB.
JSON Answer => {"Status":{"Module":1,"FriendlyName":"Sonoff","Topic":"sonoff01","ButtonTopic":"0","Power":1,"PowerOnState":3,"LedState":1,"SaveData":1,"SaveState":1,"ButtonRetain":0,"PowerRetain":0},"StatusPRM":{"Baudrate":115200,"GroupTopic":"sonoffs","OtaUrl":"http://domus1:80/api/arduino/sonoff01.ino.bin","Uptime":"0T00:37:14","Sleep":0,"BootCount":917,"SaveCount":2215,"SaveAddress":"FA000"},"StatusFWR":{"Version":"5.12.0","BuildDateTime":"2018-02-14T21:46:27","Boot":6,"Core":"2_4_0","SDK":"2.1.0(deb1901)"},"StatusLOG":{"SerialLog":2,"WebLog":2,"SysLog":0,"LogHost":"\\192.168.1.156\home\robb\Deskto","LogPort":514,"SSId1":"rowan","SSId2":"rowanotr","TelePeriod":300,"SetOption":"00000009"},"StatusMEM":{"ProgramSize":509,"Free":492,"Heap":19,"ProgramFlashSize":1024,"FlashSize":1024,"FlashMode":3},"StatusNET":{"Hostname":"sonoff01-7958","IPAddress":"192.168.1.50","Gateway":"192.168.1.2","Subnetmask":"255.255.255.0","DNSServer":"192.168.1.2","Mac":"EC:FA:BC:15:1F:16","Webserver":2,"WifiConfig":2},"StatusMQT":{"MqttHost":"192.168.1.14","MqttPort":1883,"MqttClientMask":"sonoffdev1","MqttClient":"sonoffdev1","MqttUser":"ogee","MAX_PACKET_SIZE":1000,"KEEPALIVE":15},"StatusTIM":{"UTC":"Tue Jun 12 18:40:58 2018","Local":"Tue Jun 12 19:40:58 2018","StartDST":"Sun Mar 25 02:00:00 2018","EndDST":"Sun Oct 28 03:00:00 2018","Timezone":1},"StatusSNS":{"Time":"2018-06-12T19:40:58"},"StatusSTS":{"Time":"2018-06-12T19:40:58","Uptime":"0T00:37:14","Vcc":3.465,"POWER":"ON","Wifi":{"AP":1,"SSId":"rowan","RSSI":66,"APMac":"60:38:E0:B2:8B:71"}}}

×

Steps to reproduce

unknown

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

This is a edited copy (sorry, do not know how to link/ref another issue) of a issue I have open over at the Tasmota github page ( arendst/Tasmota#3482 ) and not sure if this is a Tasmota or TasmoAdmin

Wondering if anyone has the issue or just me?

I have banged up a quick test rig with my soldering iron on a plug socket with the POW R2 as the middle man

The POW R2 is showing my soldering iron as drawing a steady 25w

This is all well and good as expected.

Ok, I understand the serial will not work anymore so first issue resolved, well it does but at 4800 :) and yes I know not to connect serial and AC at the same time

Here is the problem I face, I can get to the POW R2 UI over my WiFi as you can see from above and is displaying voltage, current and power etc as expected and can manage that way

The problem I get is that as soon as I set this to a POW R2 from a sonoff basic I can no longer manage in TasmoAdmin in my Homeassistant setup and get the error below, however Tasmoadmin does show the power stats and switch status as per second shot below

Note the unit called sonoffpow-01 is a normal POW and I can manage it fine, The one with the issue is labeled as sonoffpow-02 and I just cannot access the config/edit screens on TasmoAdmin

I am not sure if this maybe an issue with TasmoAdmin not being able to access the POW R2 correctly will be posting on that page and see if I get a response

Problem/Motivation

I have a Wemos D1 mini with 8-18B20 sensors. Using auto detect it doesn't find node.

Expected behavior

I assume but not sure is this related to the format of the message from my Wemos?

Actual behavior

During auto scan doesn't appear. When I try to enter manually I get a huge error dialog and no connection.

Steps to reproduce

Need a Wemos with multiple sensors.

Proposed changes

Looks like the message is not standard when you have multiple sensors. Could be a firm

ware issue.

Problem/Motivation

(Why the issue was filed)

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Hai @frenck

SonWeb has been renamed to TasmoAdmin.
Also the SelfUpdate feature is going to be disabled a little different from your proposal (see TasmoAdmin/TasmoAdmin#105)

Also new releases will be pushed to https://github.com/reloxx13/TasmoAdmin/releases where .tar.gz or .zip can be used to update the hassio addon.

Greets,
Ray

Hello, I'm trying to add my device but I'm getting this error when I get to this screen

and click on search, If I try the autoscan, it shows no devices found, although I have one running.

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 =>

Problem/Motivation

It is hard to find the default information for the login phase on first installation (I found in YouTube video).

Proposed changes> Please add to the installation instructions that the defaults are user: admin, pw: admin

Problem/Motivation

Name doesn't match Hostname if the sonoff device obtains a new IP address

Expected behavior

Name to match Hostname after sonoff devices obtain new DHCP address event though the other fields appear to contain the correct information

Actual behavior

Device keeps the original Name from the first Autoscan

Steps to reproduce

Cycle power on multiple sonoff devices so the DHCP server assigns different IP addresses

Proposed changes

Have the Name match the Hostname after an Autoscan

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

Unable to download updated firmware from github

Expected behavior

Automatic download of firmware from github

Actual behavior

When trying automatic update of firmware I get this errors:

Notice: Undefined property: stdClass::$assets in /var/www/tasmoadmin/tasmoadmin/pages/upload.php on line 174

Warning: Invalid argument supplied for foreach() in /var/www/tasmoadmin/tasmoadmin/pages/upload.php on line 174

Steps to reproduce

Just click on "Update" in device menu.

Warning: strpos(): Offset not contained in string in /var/www/tasmoadmin/tasmoadmin/pages/upload_form.php on line 59

Proposed changes

No idea on how to fix this

Problem/Motivation

I'm using the nginx addon to route from subfolders of my duckdns domain to various services. Overview here

Expected behavior

tasmoadmin be available at https://domain.duckdns.org/tasmo/

Actual behavior

(What actually happened)

Steps to reproduce

1. install nginx addon
2. set domain and enable customize
3. config the nginx in share/nginx_proxy_default.conf

location /tasmo/ {
    proxy_pass https://homeassistant:9541;
    rewrite /tasmo/(.*) /$1 break;

    proxy_set_header Host $host;
    proxy_redirect http:// https://;
    proxy_http_version 1.1;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $connection_upgrade;
}

Proposed changes

I see the nginx config in the addon but I'm not sure of the impact of double nginx routting.

Problem/Motivation

Trying to install Tasmoadmin

Expected behavior

Expected it to install

Actual behavior

Log came back with:
ERROR (SyncWorker_11) [hassio.docker.interface] Can't install hassioaddons/sonweb-armhf:0.6.0 -> 500 Server Error: Internal Server Error ("readlink /var/lib/docker/overlay2: invalid argument").

Steps to reproduce

Enter Home Assistant, Go to Hass.io, Scroll down to Tasmoadmin, click install, loading wheel spins, then red box around install fades in then out.

Proposed changes

Unknown what to do to fix other than the "link" to the install is looking for a file that isn't there or was renamed. I.E. Sonweb ---> Tasmoadmin

Problem/Motivation

Container will not run after updating to 0.6.1

Expected behavior

It to run.

Actual behavior

It dose not run.

Steps to reproduce

Try and run it.

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... 

-----------------------------------------------------------
 Hass.io Add-on: TasmoAdmin v0.6.1

 Centrally manage all your Sonoff-Tasmota devices

 From: Community Hass.io Add-ons
 By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
 amd64 / Ubuntu 18.04.1 LTS / HA 0.87.0b4 / SU 143 / beta
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 

INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing... 
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 11-nginx.sh: executing... 
[cont-init.d] 11-nginx.sh: exited 0.
[cont-init.d] 12-migrate.sh: executing... 
INFO: Migrating data from sonweb to tasmoadmin...
mv: can't rename '/data/sonweb': Directory not empty
[cont-init.d] 12-migrate.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] syncing disks.
[s6-finish] sending all processes the TERM signal.

edit

Fixed it by removing the "sonweb" directory in "hassio/addons/data/a0d7b954_sonweb"

tested on chrome , and safari ,
was working perfect before update
it doesn not open the first screen

error:

Parse error: syntax error, unexpected '' => '' (T_CONSTANT_ENCAPSED_STRING) in /var/www/tasmoadmin/tasmoadmin/includes/Config.php(65) : eval()'d code on line 3

Proposed changes

I want to use a custom url to access sonweb, like https://site.domain.com/sonweb, it this possible ?
In this way I can use the same hassio url.
I tried with Nginx proxy but it fail because on webpage the urls are absolute, for example "/start"

Thank you
Alessandro

404 Error - Page Not Found

JSON Antwoord => {"Status":{"Model":1, "FriendlyName":"Sonoff", "Topic":"pomp", "ButtonTopic":"0", "Subtopic":"POWER", "Power":0, "PowerOnState":3, "LedState":1, "SaveData":1, "SaveState":1, "ButtonRetain":0, "PowerRetain":0}}RESULT = {"StatusPRM":{"Baudrate":115200, "GroupTopic":"sonoffs", "OtaUrl":"http://domus1:80/api/arduino/sonoff.ino.bin", "Uptime":199, "Sleep":0, "BootCount":473, "SaveCount":936}}RESULT = {"StatusFWR":{"Program":"3.2.13", "Boot":6, "SDK":"1.5.3(aec24ac9)"}}RESULT = {"StatusLOG":{"Seriallog":2, "Weblog":2, "Syslog":0, "LogHost":"domus1", "SSId1":"Frank", "SSId2":"indebuurt2", "TelePeriod":300}}RESULT = {"StatusMEM":{"ProgramSize":396, "Free":92, "Heap":12, "SpiffsStart":492, "SpiffsSize":512, "FlashSize":1024, "ProgramFlashSize":1024}}RESULT = {"StatusNET":{"Host":"pomp-1991", "IP":"192.168.1.42", "Gateway":"192.168.1.1", "Subnetmask":"255.255.255.0", "Mac":"EC:FA:BC:8A:67:C7", "Webserver":2, "WifiConfig":3}}RESULT = {"StatusMQT":{"Host":"192.168.1.91", "Port":1883, "ClientMask":"DVES_%06X", "Client":"DVES_8A67C7", "User":"DVES_USER", "MAX_PACKET_SIZE":1000, "KEEPALIVE":15}}RESULT = {"StatusTIM":{"UTC":"Wed Sep 25 18:52:00 2019", "Local":"Wed Sep 25 19:52:00 2019", "StartDST":"Sun Mar 31 02:00:00 2019", "EndDST":"Sun Oct 27 03:00:00 2019", "Timezone":1}}

Any ideas?

Problem/Motivation

When trying to update a tasmotized sonoff frontera my hassio, the device don't update and when trying to checkpoint using browser to reach .bin URL, I recibe permission forbiden messsge

(Why the issue was filed)

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

Tasmoadmin 1.6.0 is in the works, this is a short list with things that can/should/need to be done in the next release of this add-on.

• new option for http/https: TasmoAdmin/TasmoAdmin@7be2b68

• latest release uses self-signed ssl (like the unifi add-on, but maybe just stick to the existing option): TasmoAdmin/TasmoAdmin@b557965

• this update needs a migration: TasmoAdmin/TasmoAdmin@ade5b9b, TasmoAdmin/TasmoAdmin@9d57a3d...

Problem/Motivation

Never mind.. Nothing to look at here.

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

After router reboot/network issues many of the devices will have a new ip address and a require a rescan. This results in duplicate devices requiring deletion.

Actual behavior

Each device must be selected and deleted individually. This can be a slow process if there are many devices on new ip's

Proposed changes

The ability to select multiple devices for deletion would be advantageous.

Problem/Motivation

The closed and locked issue #37 doesn't have a resolution that for users who can't delete that folder remotely.

Could that issue be reopened?

@Adorem commented on Jun 27, 2018, 7:31 AM UTC:

Hi,

I just want to report this issue I already tell in the forum

I get the following error:

INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing…
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 11-nginx.sh: executing…
sed: bad option in substitution expression
[cont-init.d] 11-nginx.sh: exited 1.
[cont-finish.d] executing container finish scripts…
[cont-finish.d] 99-message.sh: executing…

if in the path of “certfile” and or “keyfile” there is /. For example:

  “certfile”: “./fullchain.pem”,
  “keyfile”: “./privkey.pem”,

I notice this because I'm using cerbot/letsencrypt and the files are not located at the root of the /ssl/ directory but in subdirectories /ssl/:

  "certfile": "letsencrypt/live/mydomain/fullchain.pem",
  "keyfile": "letsencrypt/live/mydomain/privkey.pem",

This configuration works fine for example for the node-red addon I'm also using.

Thank you.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

This issue was moved by frenck from hassio-addons/repository/issues/75.

Problem/Motivation

Reuse of past version number

Expected behavior

The version should be greater than 0.7.0

Actual behavior

Add-on shows version 0.4.1

Steps to reproduce

Connect do HA add-on management and it will propose to update to 0.4.1 from 0.7.0

Proposed changes

Tag as new version if possibile

After click on on AutoScan I didn't get "AutoScan scanning..." pop-up window.
But after a while in scan results it found 2 devices ( have only 1 connected during test)

Error:

1st device

2nd device - ok

Problem/Motivation

Looking at the TasmoAdmin code here:
https://github.com/reloxx13/TasmoAdmin/blob/18d4ac6945297fd1b91e6005b3977c8920af823f/tasmoadmin/includes/Sonoff.php#L507
it seems a hostname should be a valid input for the IP address field of a Tasmota device. The generated URL should be valid (http:///cm[...]") and CURL should correctly handle this. However, when using a link-local hostname (e.g. "mytasmodevice.local") with the TasmoAdmin instance running as an hassio addon, the hostname consistently fails to resolve.

I suspect the instance running as an hassio addons fails to resolve (link-local) domain names, hence I'm reporting this for the addon, rather than upstream.

As a cross check, I can access the Tasmota web interface with a browser by using the link-local hostname.

Expected behavior

The user enters a (link-local) hostname in the IP field for a device, and if the hostname is valid, the device is correctly connected to.

Actual behavior

TasmoAdmin reports the "Device not found CURL ERROR => 6: Could not resolve host: "

Proposed changes

I'd verify whether resolving hosts within the hassio addon instance of TasmoAdmin is working, for link-local addresses, and support for it if needbe.

Thank you!

GitHub

reloxx13/TasmoAdmin

TasmoAdmin - Website to manage Sonoff Devices flashed with Tasmota

Problem/Motivation

I cannot specify dns names for my Tasmota devices on my network

Expected behavior

Should be able to use dns or ip address to search for tasmota devices

Actual behavior

can only use IP address

Steps to reproduce

search for a device with dns names, also tried searching from just the container.

$ docker exec -it addon_somehex_sonweb /bin/bash
root@a0d7b954-sonweb:/$ nslookup google.com
nslookup: can't resolve '(null)': Name does not resolve

nslookup: can't resolve 'google.com': Try again
root@a0d7b954-sonweb:/$ nslookup nodemcu_01
nslookup: can't resolve '(null)': Name does not resolve

nslookup: can't resolve 'nodemcu_01': Try again
root@a0d7b954-sonweb:/$ 

Proposed changes

add the ability to specify dns names by either mapping /etc/resolv.conf from the dns hosts or provide it the config.json as section to specify dns

Hi,

Thanks for your work on this addon - it's really useful.

A small feature request - a lot of hassio addons now have a "Show in sidebar" option (next to 'start on boot' etc).

Please could this be added to tasmoadmin?

Thanks,

Ian

Problem/Motivation

Tasmoadmin is stuck on home screen with only "uninstall" and "start".

Expected behavior

Expected it to uninstall completely.

Actual behavior

The same screen comes back on after uninstall, even after HA.restart and Pi reboot.

Steps to reproduce

This was a clean Hassio install on a new RPi3B+ and after I could not login to the web ui, desided to uninstall and reinstall.

Proposed changes

None. Keep up the good work. I've been using it for 3 Months and loving it.

Any schedule on adding Ingress feature to this great add-on?
Thanks for your job!

Hello
is there anyway to autologin when using sidebar integration on home assistant?
thank you

Problem/Motivation

We had a power outage and had to do a fresh Hassos install of HA and Tasmoadmin.
After install the HA works, but the Tasmoadmin web ui wont start.

Expected behavior

to start normally

Actual behavior

When starting tasmotaadmin and clicking on "web ui" getting the error "can not connect"

This is the log after restarting:

[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... 
-----------------------------------------------------------
 Hass.io Add-on: TasmoAdmin v0.5.1
 Centrally manage all your Sonoff-Tasmota devices
 From: Community Hass.io Add-ons
 By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
 armhf / HassOS 1.9 / HA 0.76.2 / SU 127 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing... 
FATAL: The configured certfile is not found
[cont-init.d] 10-requirements.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] syncing disks.
[s6-finish] sending all processes the TERM signal.

Steps to reproduce

Uninstalling and reinstalling happen way to fast and I have a feeling that there is still a bug in the uninstall process.

Proposed changes

Sorry, but I'm a computer HW Eng. and only dangerous in handling SW. Keep up the excellent work. I'm missing my Tasmotaadmin.

Problem/Motivation

WebUI dont works under https
it only works writing https://192.168.2.11:9541/
but it give a warning because it doesn't recognize certificate.

Please help me!

(Why the issue was filed)

Expected behavior

WebUI work

(What you expected to happen)

Actual behavior

WebUI work only under http
actual config
{ "log_level": "debug", "ssl": true, "certfile": "fullchain.pem", "keyfile": "privkey.pem", "ipv6": false }

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

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...

Hass.io Add-on: TasmoAdmin v0.6.1
Centrally manage all your Sonoff-Tasmota devices
From: Community Hass.io Add-ons
By: Franck Nijhof [email protected]

aarch64 / HassOS 2.10 / HA 0.88.2 / SU 145 / stable

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to DEBUG
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing...
DEBUG: Requested API resource: http://hassio/supervisor/ping
DEBUG: API HTTP Response code: 200
DEBUG: API Response: {"result": "ok", "data": {}}
DEBUG: Requested API resource: http://hassio/addons/self/info
DEBUG: API HTTP Response code: 200
DEBUG: API Response: {"result": "ok", "data": {"name": "TasmoAdmin", "slug": "a0d7b954_sonweb", "description": "Centrally manage all your Sonoff-Tasmota devices", "long_description": "# Community Hass.io Add-ons: TasmoAdmin\n\n[![Release][release-shield]][release] ![Project Stage][project-stage-shield] ![Project Maintenance][maintenance-shield]\n\n[![Discord][discord-shield]][discord] [![Community Forum][forum-shield]][forum]\n\n[![Buy me a coffee][buymeacoffee-shield]][buymeacoffee]\n\n[![Support my work on Patreon][patreon-shield]][patreon]\n\nCentrally manage all your Sonoff-Tasmota devices.\n\n## About\n\nTasmoAdmin (formerly known as SonWEB) is an administrative web interface to\nmanage all your Sonoff-Tasmota flashed devices centrally.\nSome of its features:\n\n- Scans your networks and adds your devices automatically\n- See the status off all your devices quick and easy\n- Configure all your devices from a single place\n- Send out firmware updates over the air to one or more your devices at once\n- Can automatically download the latest firmware for you\n\n[Click here for the full documentation][docs]\n\n![TasmoAdmin screenshot][screenshot]\n\n[buymeacoffee-shield]: https://www.buymeacoffee.com/assets/img/guidelines/download-assets-sm-2.svg\n[buymeacoffee]: https://www.buymeacoffee.com/frenck\n[discord-shield]: https://img.shields.io/discord/478094546522079232.svg\n[discord]: https://discord.me/hassioaddons\n[docs]: https://github.com/hassio-addons/addon-tasmoadmin/blob/v0.6.1/README.md\n[forum-shield]: https://img.shields.io/badge/community-forum-brightgreen.svg\n[forum]: https://community.home-assistant.io/t/community-hass-io-add-on-tasmoadmin/54155?u=frenck\n[maintenance-shield]: https://img.shields.io/maintenance/yes/2019.svg\n[patreon-shield]: https://www.frenck.nl/images/patreon.png\n[patreon]: https://www.patreon.com/frenck\n[project-stage-shield]: https://img.shields.io/badge/project%20stage-experimental-yellow.svg\n[release-shield]: https://img.shields.io/badge/version-v0.6.1-blue.svg\n[release]: https://github.com/hassio-addons/addon-tasmoadmin/tree/v0.6.1\n[screenshot]: https://github.com/hassio-addons/addon-tasmoadmin/raw/master/images/screenshot.png", "version": "0.6.1", "auto_update": false, "repository": "a0d7b954", "last_version": "0.6.1", "state": "started", "protected": true, "rating": 5, "boot": "auto", "options": {"log_level": "debug", "ssl": true, "certfile": "fullchain.pem", "keyfile": "privkey.pem", "ipv6": false}, "arch": ["aarch64", "amd64", "armhf", "i386"], "machine": ["intel-nuc", "odroid-c2", "odroid-xu", "orangepi-prime", "qemux86", "qemux86-64", "qemuarm", "qemuarm-64", "raspberrypi", "raspberrypi2", "raspberrypi3", "raspberrypi3-64", "tinker"], "url": "https://github.com/hassio-addons/addon-tasmoadmin", "detached": false, "available": true, "build": false, "network": {"9541/tcp": 9541}, "host_network": false, "host_pid": false, "host_ipc": false, "host_dbus": false, "privileged": [], "full_access": false, "apparmor": "default", "devices": null, "icon": true, "logo": true, "changelog": true, "webui": "https://[HOST]:9541", "stdin": false, "hassio_api": true, "hassio_role": "default", "auth_api": false, "homeassistant_api": false, "gpio": false, "kernel_modules": false, "devicetree": false, "docker_api": false, "audio": false, "audio_input": null, "audio_output": null, "services": [], "discovery": []}}
DEBUG: Filtering response using: .version
DEBUG: Requested API resource: http://hassio/addons/self/info
DEBUG: API HTTP Response code: 200
DEBUG: API Response: {"result": "ok", "data": {"name": "TasmoAdmin", "slug": "a0d7b954_sonweb", "description": "Centrally manage all your Sonoff-Tasmota devices", "long_description": "# Community Hass.io Add-ons: TasmoAdmin\n\n[![Release][release-shield]][release] ![Project Stage][project-stage-shield] ![Project Maintenance][maintenance-shield]\n\n[![Discord][discord-shield]][discord] [![Community Forum][forum-shield]][forum]\n\n[![Buy me a coffee][buymeacoffee-shield]][buymeacoffee]\n\n[![Support my work on Patreon][patreon-shield]][patreon]\n\nCentrally manage all your Sonoff-Tasmota devices.\n\n## About\n\nTasmoAdmin (formerly known as SonWEB) is an administrative web interface to\nmanage all your Sonoff-Tasmota flashed devices centrally.\nSome of its features:\n\n- Scans your networks and adds your devices automatically\n- See the status off all your devices quick and easy\n- Configure all your devices from a single place\n- Send out firmware updates over the air to one or more your devices at once\n- Can automatically download the latest firmware for you\n\n[Click here for the full documentation][docs]\n\n![TasmoAdmin screenshot][screenshot]\n\n[buymeacoffee-shield]: https://www.buymeacoffee.com/assets/img/guidelines/download-assets-sm-2.svg\n[buymeacoffee]: https://www.buymeacoffee.com/frenck\n[discord-shield]: https://img.shields.io/discord/478094546522079232.svg\n[discord]: https://discord.me/hassioaddons\n[docs]: https://github.com/hassio-addons/addon-tasmoadmin/blob/v0.6.1/README.md\n[forum-shield]: https://img.shields.io/badge/community-forum-brightgreen.svg\n[forum]: https://community.home-assistant.io/t/community-hass-io-add-on-tasmoadmin/54155?u=frenck\n[maintenance-shield]: https://img.shields.io/maintenance/yes/2019.svg\n[patreon-shield]: https://www.frenck.nl/images/patreon.png\n[patreon]: https://www.patreon.com/frenck\n[project-stage-shield]: https://img.shields.io/badge/project%20stage-experimental-yellow.svg\n[release-shield]: https://img.shields.io/badge/version-v0.6.1-blue.svg\n[release]: https://github.com/hassio-addons/addon-tasmoadmin/tree/v0.6.1\n[screenshot]: https://github.com/hassio-addons/addon-tasmoadmin/raw/master/images/screenshot.png", "version": "0.6.1", "auto_update": false, "repository": "a0d7b954", "last_version": "0.6.1", "state": "started", "protected": true, "rating": 5, "boot": "auto", "options": {"log_level": "debug", "ssl": true, "certfile": "fullchain.pem", "keyfile": "privkey.pem", "ipv6": false}, "arch": ["aarch64", "amd64", "armhf", "i386"], "machine": ["intel-nuc", "odroid-c2", "odroid-xu", "orangepi-prime", "qemux86", "qemux86-64", "qemuarm", "qemuarm-64", "raspberrypi", "raspberrypi2", "raspberrypi3", "raspberrypi3-64", "tinker"], "url": "https://github.com/hassio-addons/addon-tasmoadmin", "detached": false, "available": true, "build": false, "network": {"9541/tcp": 9541}, "host_network": false, "host_pid": false, "host_ipc": false, "host_dbus": false, "privileged": [], "full_access": false, "apparmor": "default", "devices": null, "icon": true, "logo": true, "changelog": true, "webui": "https://[HOST]:9541", "stdin": false, "hassio_api": true, "hassio_role": "default", "auth_api": false, "homeassistant_api": false, "gpio": false, "kernel_modules": false, "devicetree": false, "docker_api": false, "audio": false, "audio_input": null, "audio_output": null, "services": [], "discovery": []}}
DEBUG: Filtering response using: .last_version
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing...
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 11-nginx.sh: executing...
[cont-init.d] 11-nginx.sh: exited 0.
[cont-init.d] 12-migrate.sh: executing...
[cont-init.d] 12-migrate.sh: exited 0.
[cont-init.d] 13-persistent-data.sh: executing...
DEBUG: Symlinking data directory to persistent storage location...
[cont-init.d] 13-persistent-data.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.`

@frenck there is a problem on the latest version

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing... 
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 11-nginx.sh: executing... 
[cont-init.d] 11-nginx.sh: exited 0.
[cont-init.d] 12-migrate.sh: executing... 
/var/run/s6/etc/cont-init.d/12-migrate.sh: line 10: hass.log.inf: command not found
[cont-init.d] 12-migrate.sh: exited 127.
[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.

First of all great work!

It would be very nice to provide a functionality to execute a command on all / selected devices. For example to change the timezone.

Best regards,
iMarkus

Problem/Motivation

Home Assistant Add in-Unable to connect

Expected behavior

Tasmoadmin should be available when select "open web ui"

Actual behavior

Unable to connect message

Log below:
[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... 
-----------------------------------------------------------
 Hass.io Add-on: TasmoAdmin v0.5.1
 Centrally manage all your Sonoff-Tasmota devices
 From: Community Hass.io Add-ons
 By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
 aarch64 / HassOS 1.9 / HA 0.76.2 / SU 127 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing... 
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 11-nginx.sh: executing... 
[cont-init.d] 11-nginx.sh: exited 0.
[cont-init.d] 12-migrate.sh: executing... 
[cont-init.d] 12-migrate.sh: exited 0.
[cont-init.d] 13-persistent-data.sh: executing... 
[cont-init.d] 13-persistent-data.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

As a convenience for folks that land here while searching how to manually install tasmoadmin without benefit of a hass.io install with addon store / repositories may I suggest we add a short perhaps one liner to point to the solution?

I found out how to install tasmoadmin manually here; I think it would be helpful to add a link to that page in the Install portion of this page
I spent some time searching and forum reading before I found what in retrospect is obvious... (DOH!)

Discussion? I can create a pull request if desired. :-)

Hi Franck,
I'm trying to add your Tasmoadmin in sidebar.
You've already answered that modifying it for ingress is too difficult.
I'm successfully using your "Nginx Proxy Manager" addon to access remotely my Hassio (all, Hassio and addons locally in http, not https), but I'm not able to configure panel_iframe and/or Tasmoadmin to be shown in left window.
Tested both activating and deactivating SSL, no success.
Saw that Tasmoadmin also uses NGINX... may be the cause?

Could you explain how to solve?

Thanks in advance!

https://www.home-assistant.io/blog/2019/04/15/hassio-ingress/

Please :)

Home Assistant

Introducing Hass.io Ingress

Ingress allows Hass.io add-ons to seamlessly integrate their user interface with Home Assistant

Problem/Motivation

I changed the mqtt configuration from non ssl to ssl. After that in the list view only a spinner is shown

Expected behavior

The status values are shown as before

Actual behavior

Spinner is shown. In the Configuration View are also a lot of errors shown on the page that some parameter are not found.

Steps to reproduce

Follwing flags are set when tasmota is compiled:

#define USE_MQTT_TLS
#define USE_MQTT_TLS_CA_CERT

Problem/Motivation

I installed this addon but it doesn't start

Expected behavior

That at least log started ... but nothing at all

Actual behavior

Nothing, I click on start but, after a second, red light and no log

Steps to reproduce

I attach a screenshot

Proposed changes

I tried uninstalling and reinstalling after restarting hassio, but nothing, not even the log.
This is my configuration:
{ "ssl": true, "certfile": "fullchain.pem", "keyfile": "privkey.pem", "log_level": "info" }

Problem/Motivation

when updating the sonoff device it comes with this error

Expected behavior

To update the software to the latest Tasmoa software

Actual behavior

I do get these failures:
[10-51-2018 14:46:55][GLOBAAL] Start update proces
[10-51-2018 14:46:55][ID-1][STAP-1][GLOBAAL] Start Stap 1
[10-51-2018 14:46:55][ID-1][STAP-1][CONTROLEER] Controleer verbinding | PROBEER => 1
[10-51-2018 14:46:56][ID-1][STAP-1][CONTROLEER] FOUT: Apparaat heeft niet gereageerd! | MSG => JSON FOUT => 4: Syntax error
Kopieer de hele foutmelding en plak deze in een nieuwe bevinding op GitHUB. Op de een of andere manier gereageerde de Tasmota Firmware met een onjuiste JSON string, welke verwerkt dient te worden in TasmoAdmin.
JSON Antwoord => Status, Data Size 1, Data 213:46:56 RSL: Group 0, Index 1, Command STATUS, Data 2{"StatusFWR":{"Version":"5.10.0","BuildDateTime":"2017-12-29T11:40:24","Boot":4,"Core":"2_3_0","SDK":"1.5.3(aec24ac9)"}}
[10-51-2018 14:46:56][ID-1][STAP-1][CONTROLEER] Controleer verbinding | PROBEER => 2
[10-51-2018 14:46:56][ID-1][STAP-1][CONTROLEER] FOUT: Apparaat heeft niet gereageerd! | MSG => JSON FOUT => 4: Syntax error
Kopieer de hele foutmelding en plak deze in een nieuwe bevinding op GitHUB. Op de een of andere manier gereageerde de Tasmota Firmware met een onjuiste JSON string, welke verwerkt dient te worden in TasmoAdmin.
JSON Antwoord => Status, Data Size 1, Data 213:46:56 RSL: Group 0, Index 1, Command STATUS, Data 2{"StatusFWR":{"Version":"5.10.0","BuildDateTime":"2017-12-29T11:40:24","Boot":4,"Core":"2_3_0","SDK":"1.5.3(aec24ac9)"}}
[10-51-2018 14:46:56][ID-1][STAP-1][CONTROLEER] Controleer verbinding | PROBEER => 3
[10-51-2018 14:46:56][ID-1][STAP-1][CONTROLEER] FOUT: Apparaat heeft niet gereageerd! | MSG => JSON FOUT => 4: Syntax error
Kopieer de hele foutmelding en plak deze in een nieuwe bevinding op GitHUB. Op de een of andere manier gereageerde de Tasmota Firmware met een onjuiste JSON string, welke verwerkt dient te worden in TasmoAdmin.
JSON Antwoord => Status, Data Size 1, Data 213:46:56 RSL: Group 0, Index 1, Command STATUS, Data 2{"StatusFWR":{"Version":"5.10.0","BuildDateTime":"2017-12-29T11:40:24","Boot":4,"Core":"2_3_0","SDK":"1.5.3(aec24ac9)"}}

Steps to reproduce

First update in second dropdown menu of Tasmoadmin page. Then select automatic update, select the device and update, now this error is coming

Problem/Motivation

error when searching for active devices

Notice: Undefined property: stdClass::$StatusNET in /var/www/sonweb/pages/devices_autoscan.php on line 61

Notice: Trying to get property of non-object in /var/www/sonweb/pages/devices_autoscan.php on line 61

Notice: Undefined offset: 3 in /var/www/sonweb/pages/devices_autoscan.php on line 62

Notice: Undefined property: stdClass::$StatusNET in /var/www/sonweb/pages/devices_autoscan.php on line 61

Notice: Trying to get property of non-object in /var/www/sonweb/pages/devices_autoscan.php on line 61

Notice: Undefined offset: 3 in /var/www/sonweb/pages/devices_autoscan.php on line 62

the first device identified is not a device , and this is the information showed on the ip field :
<br /><b>Notice</b>: Undefined property: stdClass::$StatusNET in <b>/var/www/sonweb/pages/devices_autoscan.php</b> on line <b>233</b><br /><br /><b>Notice</b>: Trying to get property of non-object in <b>/var/www/sonweb/pages/devices_autoscan.php</b> on line <b>233</b><br />

devices are detected correctly , ( not all of them , some are missing from the list) , but as this device #1 cant be deleted , there is no actual way to include the discovered devices .

IMPORTANT NOTICE
If you do not complete the template below it is likely that your issue will not be addressed. When providing information about your issue please be as extensive as possible so that it can be solved by as little as possible responses.

FAILURE TO COMPLETE THE REQUESTED INFORMATION WILL RESULT IN YOUR ISSUE BEING CLOSED

Describe the bug
When using Tasmota 6.1 on a Wemos D1 mini multiple 18B20 sensors the Hassio interface does not recognize the sonoff during auto scan. Also manually adding the device causes error an does not save the address.

Also, make sure these boxes are checked [x] before submitting your issue - Thank you!

• [ x ] Searched the problem in issues and in the wiki
• [ x ] Hardware used : Wemos D1 mini
• Development/Compiler/Upload tools used :
• If a pre-compiled release or development binary was used, which one? :
• You have tried latest release or development binaries? :
• Provide the output of commandstatus 0 :

STATUS 0 OUTPUT HERE - DO NOT DELETE THE MARKERS ABOVE AND BELOW THIS LINE

To Reproduce
Steps to reproduce the behavior:
In Hassio using the admistration UI the Wemos is not recognised.

Expected behavior
A clear and concise description of what you expected to happen.
To identify the usage/device.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
(copied from info screen)

Tasmota Program Version | 6.1.0

ESP Chip Id 1466106
Flash Chip Id 1458400
Flash Size 4096kB
Program Flash Size 4096kB
Program Size 559kB
Free Program Space 444kB
Free Memory 17kB

(copied from the error while manually adding the Wemos D1)

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 => {"Status":{"Module":18,"FriendlyName":["Wemos52"],"Topic":"wemos52","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"SaveData":1,"SaveState":1,"ButtonRetain":0,"PowerRetain":0},"StatusPRM":{"Baudrate":115200,"GroupTopic":"sonoffs","OtaUrl":"http://sonoff.maddox.co.uk/tasmota/sonoff.bin","RestartReason":"Software/System restart","Uptime":"3T03:56:25","StartupUTC":"","Sleep":0,"BootCount":64,"SaveCount":89,"SaveAddress":"FB000"},"StatusFWR":{"Version":"6.1.0","BuildDateTime":"2018-07-06T21:03:23","Boot":31,"Core":"2_3_0","SDK":"1.5.3(aec24ac9)"},"StatusLOG":{"SerialLog":2,"WebLog":2,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["xxxxxx24","xxxxx50"],"TelePeriod":300,"SetOption":["00008009","55818000"]},"StatusMEM":{"ProgramSize":559,"Free":444,"Heap":17,"ProgramFlashSize":4096,"FlashSize":4096,"FlashMode":2,"Features":["00000809","0FDEE794","0C000004","37FFBFCE","00000000"]},"StatusNET":{"Hostname":"xxx24","IPAddress":"192.168.1.52","Gateway":"192.168.1.1","Subnetmask":"255.255.255.0","DNSServer":"192.168.2.27","Mac":"60:01:94:16:5E:FA","Webserver":2,"WifiConfig":3},"StatusMQT":{"MqttHost":"192.168.1.27","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_165EFA","MqttUser":"mqtt15","MqttType":1,"MAX_PACKET_SIZE":1000,"KEEPALIVE":15},"StatusTIM":{"UTC":"Sun Jan 04 03:59:52 1970","Local":"Sun Jan 04 03:59:52 1970","StartDST":"Thu Jan 01 00:00:00 1970","EndDST":"Thu Jan 01 00:00:00 1970","Timezone":1,"Sunrise":"07:43","Sunset":"16:06"},"StatusSNS":{"Time":"1970-01-04T03:59:52","DS18B20-1":{"Id":"0000003EC08A","Temperature":24.1},"DS18B20-2":{"Id":"0000003EDFB2","Temperature":-2.4},"DS18B20-3":{"Id":"03167264A8FF","Temperature":19.4},"DS18B20-4":{"Id":"051671B5E6FF","Temperature":22.8},"DS18B20-5":{"Id":"051671C28DFF","Temperature":22.5},"DS18B20-6":{"Id":"051671C68FFF","Temperature":21.6},"DS18B20-7":{"Id":"051671DDE4FF","Temperature":21.3},"DS18B20-8":{"Id":"0516720A4BFF","Temperature":22.1},"TempUnit": ..,"StatusSTS":{"Time":"1970-01-04T03:59:52","Uptime":"3T03:56:25","Vcc":2.751,"Wifi":{"AP":1,"SSId":"xxxxx24","RSSI":92,"APMac":"00:18:E7:xx:xx:xx"}}}

(Please, remember to close the issue when the problem has been addressed)