iotreboot / tasui Goto Github PK

In light of the SetOption73 that has occurred, it would be handy if the front page of the tool detailed what version of tasmota is supported. Make it obvious to the user the tool it written for Tasmota 8.3.0 or 7.1.1 or 6.3 or 5.10 (random numbers). Sometimes tools are updated quickly and that cool, but if a tool falls behind the main development of the actual firmware, problems like Option73 can arise and users should be able to use the tool with confidence if their version is supported.

request: add the supported tasmota firmware version on the main page

Not an issue but could not think of anywhere else to put thiis. I cloned TasUI to try an install on my RPi3 as exposing the local network to an external site does seem somewhat dangerous?

Sadly the install LOOKS like it wants ARCH Linux and hence the install failed on a Raspberry Pi 3 with Raspbian.

Thoughts?

Tasui looks great. Discovered all my devices except 2 .
Both use the serial connection on gpio1/3 and read the values of a PZEM power monitoring device.
Is this related to the fact that serial is used ? Both upgraded to tasmota 8.1.0 and option73 on.

any chance of implementing persistent storage(at least for docker container)? I'd help but i'm not good in react.

As noted below, SetOption73 1 decouples buttons and the corresponding relays will not be triggered:
arendst/Tasmota#8177

Doing a device discovery disabled all my light switches.

i have a few active tasmota devices in my network that are not being discovered by the javascript client. accessible by MQTT, web and by Alexa discovery. But the JS client never finds it. Configured as a W-DEXI module.

Is there a setting needed to ensure it is discoverable?

Should read "Pulsetime" not Pusletime

TasUI seems to have problems working inside an Iframe. When using the tasUI addon within Homeassistant, and then adding:

panel_iframe:
tasui:
title: TasUI
icon: mdi:lightbulb-on
url: http://myhomeassistantdomain.com:8013/

the tasui dosnt load. the ui loads fine when accessing the ip and port directly

how do I use this this as non of my devices show up

LOVE the product by the way.

When first firing up TasUI, the Start/End IP address do not match the local subnet.

e.g in my case:

• Local subnet: 10.1.1.0/24

• TasUI start/end IP: 192.168.10.1 - 192.168.10.254

Is that fixable?

TasUI has realy helped me alot.

I have some ifan and noticed their is no control for them yet.
Power and light slider work perfectly and would like to know if fan is on the list of todo.

@meingraham : Please get in touch with @effelle

would be excellent to have also a view on power consumption, either as own view or added to the status view with

• Energy Total
• Energy Yesterday
• Energy Today
• Current

eventually also a sum below the list for the consumption values is useful

Ref# https://tasmota.github.io/docs/Commands/#power-monitoring

Message: [FATAL tini (7)] exec docker-entrypoint.sh failed: Exec format error

I'm running a pretty standard default Hass.io install on RaspberryPi 4.

Hello!
Nice coding! looking forward for new features!

Right now I would like to point out that on mobile phone the ui is not very friendly, it is to wide, even on my old desktop with 1366px wide screen. I am not very good at coding, so here are some ideas:

• move the side menu on top of the page, instead / on top of the dark blue "TasUi" header
• move the status icon next to the device name
• if posibile, add sensors output on Status view page ; for example, i have a DHT11 on one of my devices

Here is a visual idea

A device with Tasmota version 6.5.0 is discovered
but Devices with Tasmota version 7.1.0, 7.1.1 or 7.1.2 are not discovered

Tasmota firmware 8.5.0 devices will show up in TasUI, but the DETAILS and the SETTINGS screens will not load for these updated firmware devices. Clicking on either of these causes a blank webpage to appear and clicking BACK in the browser also renders a blank page. A manual REFRESH of the webpage is required to regain access to the TasUI page.