Members thgoebel Posted July 2 Members Share Posted July 2 A Shelly pro 2PM I repaired today (screw of blue terminal was jammed) shows a strange behaviour: The device cannot be added to the cloud because the check mark ‚enable cloud‘ (WebUI) isn’t permanently saved. At first sight, the check mark seems to be set. But after refreshing the Website, check mark shows the status ‚disabled‘ again. Diagnostics: Firmware is 1.3.3. Any hints? Quote Link to comment Share on other sites More sharing options...
Heinz Posted July 3 Share Posted July 3 can you send the Logs as well as the device logs as well as device data? Just did a test on the same device with the same firmware wanted to see if there is something here. diagnostics-shelly-pro2pm-debug-log.txtdiagnostics-shelly-pro2pm-data.txt Quote Link to comment Share on other sites More sharing options...
Members thgoebel Posted July 3 Author Members Share Posted July 3 Thanks, Heinz, for your support! Attached both files. Did try to enable cloud and saved diagnostics log. diagnostics-shelly-pro2pm-data.txtdiagnostics-shelly-pro2pm-debug-log.txt Quote Link to comment Share on other sites More sharing options...
Heinz Posted July 3 Share Posted July 3 just a few questions did you restart the Pro device when you updated the device. and then are you using the main connection on wifi or lan ? as your wifi signal is below the required usage Quote Link to comment Share on other sites More sharing options...
Members thgoebel Posted July 3 Author Members Share Posted July 3 (edited) Restart was executed before diagnostics were downloaded. WLAN connection was used. LAN connection not tested with this device yet. WLAN in my laboratory is intended a bad one. Weak WLAN reception of Shelly devices shall be recognised better with this environment. „Unusable“ doesn’t exist with a RSSI of more than -85dB… Other devices with weak RSSI can be added flawlessly to the cloud! (My hope was a developer would drop some words about this issue… Unfortunately, I didn’t find an appropriate thread in the QA section. Und das ist auch der Grund, weshalb ich Englisch gewählt habe.) Edited July 3 by thgoebel Quote Link to comment Share on other sites More sharing options...
Heinz Posted July 3 Share Posted July 3 @supportadmin is this a common bug ? Quote Link to comment Share on other sites More sharing options...
Members thgoebel Posted July 3 Author Members Share Posted July 3 LAN connection was tested some minutes ago: Same behaviour (as expected)! Quote Link to comment Share on other sites More sharing options...
Heinz Posted July 3 Share Posted July 3 last thing i could think about it on that network your device is connected to is there a firewall blocking anything ? Quote Link to comment Share on other sites More sharing options...
Heinz Posted July 3 Share Posted July 3 other wise the only thing i could think of is that it must be the shelly pro device. maybe some bug on the firmware on the device or firmware issue in general. Quote Link to comment Share on other sites More sharing options...
Members thgoebel Posted July 3 Author Members Share Posted July 3 15 minutes ago, Heinz said: last thing i could think about it on that network your device is connected to is there a firewall blocking anything ? Other Shelly devices (quite a lot during the repair and test process) are flawlessly to be added to the cloud. I add EVERY repaired Shelly to my cloud to check for some forgotten membership to another clients cloud. 17 minutes ago, Heinz said: maybe some bug on the firmware on the device or firmware issue in general. This is my assumption too… Quote Link to comment Share on other sites More sharing options...
Todor Tsvetkov Posted July 4 Share Posted July 4 On 7/3/2024 at 2:58 PM, thgoebel said: Thanks, Heinz, for your support! Attached both files. Did try to enable cloud and saved diagnostics log. diagnostics-shelly-pro2pm-data.txt 6.35 kB · 6 downloads diagnostics-shelly-pro2pm-debug-log.txt 3.25 kB · 4 downloads This device is not coming with correct provisioning data. Problem in the manufacturing process. It's a rare occasion, it is already addressed internal. The device requires replacement. 1 Quote Link to comment Share on other sites More sharing options...
Members thgoebel Posted July 4 Author Members Share Posted July 4 Thanks, Todor, for the clarification! I suppose the device is usable without cloud connection? Anyway, this was my observation… Quote Link to comment Share on other sites More sharing options...
Heinz Posted July 5 Share Posted July 5 locally yes the device should work just with out remote control Quote Link to comment Share on other sites More sharing options...
Members thgoebel Posted July 5 Author Members Share Posted July 5 (edited) Will check it for unrestricted functionality of rpc calls. Otherwise, the device shall serve as dispenser for spare parts. Unfortunately, spare parts - particularly for ‚pro’ devices - aren’t available yet. Edited July 5 by thgoebel Quote Link to comment Share on other sites More sharing options...
felix946 Posted August 14 Share Posted August 14 On 4.7.2024 at 14:23, Todor Tsvetkov said: This device is not coming with correct provisioning data. Problem in the manufacturing process. It's a rare occasion, it is already addressed internal. The device requires replacement. I only did a factory reset and was then able to reactivate the cloud connection. Quote Link to comment Share on other sites More sharing options...
Members thgoebel Posted August 14 Author Members Share Posted August 14 Factory reset didn’t help to solve the issue. But the device is fully functional via rpc commands. Thus, the missing cloud is not really crucial. 1 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.