xnd Posted April 26 Share Posted April 26 (edited) sorry for duplicate post, I just found this section fits better this scripting issue. Feel free to delete my previous post here under: Home > Devices > Shelly Plus (Gen2) devices > Shelly Plus Plug S : With latest firmware: "fw_id": "20240425-141453/1.3.0-ga3fdd3d", "ver": "1.3.0", Diagnostic data included below. See: Also with such version of the code: print('start'); function main() { var i = 0; while (i < 12) { i = i + 1; console.log(i); } print('end'); } Timer.set(2000, false, main); output: Also reproducible on other devices (Shelly Plus 1PM, Shelly Pro 4PM) ----- also the same issue was reported earlier: diagnostics-shelly-plusplugs-data.txt diagnostics-shelly-plusplugs-debug-log.txt Edited April 26 by xnd Quote Link to comment Share on other sites More sharing options...
xnd Posted April 29 Author Share Posted April 29 issue still present Quote Link to comment Share on other sites More sharing options...
xnd Posted May 2 Author Share Posted May 2 (edited) ... also reproducible in latest stable fw: 20240425-141825/1.3.0-ga3fdd3d on all my devices: Plus Plug S, Pro 3EM, Pro 4PM Edited May 2 by xnd Quote Link to comment Share on other sites More sharing options...
Emiel Posted May 2 Share Posted May 2 I can confirm this on the Pro3. Annoying if you try to debug a (parsed) array. Quote Link to comment Share on other sites More sharing options...
PiZ Posted May 2 Share Posted May 2 Same here with Pro EM-50 Quote Link to comment Share on other sites More sharing options...
xnd Posted May 2 Author Share Posted May 2 (edited) also reproducible in firmware 1.3.1 on my following devices: - Shelly Plus 1PM: 20240430-105751/1.3.1-gd8534ee - Shelly Pro 3EM: 20240430-105803/1.3.1-gd8534ee Edited May 2 by xnd Quote Link to comment Share on other sites More sharing options...
xnd Posted May 2 Author Share Posted May 2 here is reply on Facebook: https://www.facebook.com/groups/ShellyIoTCommunitySupport/posts/7235208039911831/?comment_id=7243276419104993&reply_comment_id=7244620915637210 Quote Link to comment Share on other sites More sharing options...
Emiel Posted May 3 Share Posted May 3 To be honest, it is not true that it is an known issue IMHO. As I replied on Facebook, the issue is new (I upgraded last week when testing the script unfortunately), I didn't notice before. Before all prints came out. Now only the first few prints and the last few come out. There should at least be an option to flush your prints (as in wait for them, not throw them to /dev/null ), otherwise it's quite useless. But, as stated, it is an introduced bug, and I assume it should be fixable. Quote Link to comment Share on other sites More sharing options...
FritzFratz Posted May 22 Share Posted May 22 I have the same problem with Plus1PM und Plus2PM. It is not possible to test anything, because it is logging absolutely nothing. A I do not know the names of the events, I can not continue without Log-Output... Plus1PM 20240430-105751/1.3.1-gd8534ee (here it worked for a short time, I think I made an FW-Update than...) Plus2PM 20240522-112837/1.3.2-g34c651b I just started programming shelly´s - but it ended very soon 😞 Quote Link to comment Share on other sites More sharing options...
Administrators Sebastian U. Posted May 23 Administrators Share Posted May 23 Do you have auth enabled? If yes disable authentification and restart your Shelly device. Now you should get debug logs again. You can reenable auth but after an reboot there won‘t be any debug output. Quote Link to comment Share on other sites More sharing options...
xnd Posted May 29 Author Share Posted May 29 no, auth is disabled Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.