OneCreek

Yes! And with the older version of OSS I had/have the issue https://github.com/Akylas/OSS-DocumentScanner/issues/99. Don't know if it's related.

Ok thanks for the feedback. I didn't have the need for nextcloud yet and preferred the slimmer sftpgo. If I can help analyze or send new logs please let me...

I finally got it working! :) But too much changes on my and app side to reproduce I guess...

I'm sorry, I don't exacly know how to get this response... I assume browser developer debug menu? and then?

I assume the response is: ``` StatusPRM: {Baudrate: 4800, SerialConfig: "8E1", GroupTopic: "tasmotas",…},…} StatusFWR: {Version: "14.6.0(release-tasmota)", BuildDateTime: "2025.04.16 11:21:41", Boot: 31, Core: "2_7_8",…} StatusLOG: {SerialLog: 0, WebLog: 2, MqttLog: 0,...

It might be important, that there are 4 "devices" listed, that is actually 1 device as a power socket with multiple switches.  and showing as 

and some also show:  actually at the moment I cannot even reproduce https://github.com/TasmoAdmin/TasmoAdmin/issues/1370#issuecomment-2855826581 Update: thats Firefox, compared to the other one being Edge

I get this in Edge under actions?doAjax**All** as well 

apparently I broke my Tasmota Device when editing the config via TasmotaAdmin. Reset and Restore of settings after "faulty edit" restored also the problem. reflashing the latest tasmota firmware also...

> Showing single devices as two switches should be fine. e.g. with me for a two socket device it's like I know. Also worked/works for me. > Ouch that sounds...