No state update, stuck on loading

[macf0x]

Related to #375 (comment)

I'm using a LilyGO ttgo-t-eth-poe. When configured for Ethernet I'm assuming it's not returning expected data and the status remains on loading.

Using the status URL (http://taspoe/cm?cmnd=status0) it returns this Json
https://tasmota.github.io/docs/Commands/#management

Are you able cater for Tasmota Ethernet device status?

{"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":" ","RestartReason":"Vbat power on reset","Uptime":"87T15:29:29","StartupUTC":"2021-09-07T11:39:02","Sleep":50,"CfgHolder":4617,"BootCount":33,"BCResetTime":"2021-06-01T14:35:21","SaveCount":37}}

{"StatusFWR":{"Version":"9.4.0.4(ethernet)","BuildDateTime":"2021-05-29T09:40:06","Core":"1_0_6","SDK":"v3.3.5-1-g85c43024c","CpuFrequency":80,"Hardware":"ESP32-D0WDQ6","CR":"361/699"}}

{"StatusNET":{"Hostname":"Letterbox-6744_eth","IPAddress":"192.168.x.x","Gateway":"192.168.x.x","Subnetmask":"255.255.255.0","DNSServer":"192.168.x.x","Mac":"xx:xx:xx:xx:xx:x","Webserver":2,"WifiConfig":0,"WifiPower":17.0}}

{"StatusSNS":{"Time":"2021-12-04T04:11:22","Switch1":"OFF","Switch2":"OFF","ESP32":{"Temperature":53.3},"TempUnit":"C"}}

[inverse]

We should be able to cater - Just need to check for the existence of StatusSTS.Wifi and assume ethernet if not.

Code needs to be reworked as there is a lot of duplication for this logic.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[macf0x]

Still an issue, with the current Tasmota releases.

Given the increasing popularity of the Ethernet (PoE) variants, I'm surprised there isn't more interest in this issue.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[macf0x]

Still an issue, with the current Tasmota releases.

[snuguru-maestro]

It's not related to a tasmota version specifically, but to the way the uptime calculation is done. the uptime variable is never initialised and the whole script just fails and skips everything else afterwards.
I don't know how to fix it, but I found a VERY ugly workaround (and I'm probably really close to the source of the issue).

How I did it:
after I spun-up the latest docker image, I connected to the container (with docker exec -it bash) and added let uptime = ""; between the following lines in /var/www/tasmoadmin/resources/js/devices.min.js (I just searched for the first instance of "uptime" with vi and worked my way up a little)
Of course this will not survive once the container is gone, but it seems to work (though you wont see the uptime but you have everything else).

let m = void 0 !== t.StatusPRM.StartupDateTimeUtc ? t.StatusPRM.StartupDateTimeUtc : void 0 !== t.StatusPRM.StartupUTC ? t.StatusPRM.StartupUTC : "";
let uptime = "";
if ("" !== m) {

I am a complete dud when it comes to js, but I'm sure @inverse or someone with a bit more .js in their blood could have a look and maybe patch it properly. I will have a closer look maybe I can find a real fix, but in the mean time for all those who have this issue there is a workaround.