Jump to content
🌟 NEW Shelly Products Reveal Video! 🌟 NEUE Shelly-Produkte-Enthüllungsvideo! 🌟 ×
NOTICE / HINWEIS: iOS 18 Update and Today Widgets ×

Not connected to cloud


Cor

Recommended Posts

hello all,

 

I have a Shelly Plug S, all setup and I used to controll this device via MQTT, device is working fine with local web controll.

Now I want to controll the device via the shelly app , or https://control.shelly.cloud/

The device is there , but it is shown as offline.

Cloud controll is on (MQTT deactivated) , latest firmware , rebooted , but it still shows as offline in the app , and on the controll.shelly.cloud.

2024-08-1313_49_22-456019830@desktop-lgtmcrb-RemoteDesktop-RustDesk.jpg.2018797ace270e5fef01ce5a2418f627.jpg

 

Anything I can do without resetting the device?

 

Thanks, 

Cor

 

Link to comment
Share on other sites

Hmm odd there can only be a few things that would stop the cloud connection. 

Network settings and default gateway is incorrect. 
Firewall settings blocking connection 
 

I would look at the debug log on the device to confirm that there are no errors from the device side 

from the looks of that screen show that does not look like the latest firmware. 

can you confirm what firmware you have installed and also check on your cloud settings that its connected to a cloud server 

Link to comment
Share on other sites

Posted (edited)

@Heinz : thanks for helping!

 

Firmware:

2024-08-1314_22_35-456019830@desktop-lgtmcrb-RemoteDesktop-RustDesk.jpg.3f22ee7e73262b7e79ac46f17ab2b8ea.jpg

 

Network settings:

I have checked with another )newer device , which is both connected to cloud and mqtt  , and the settings for network are the same ( excepts for the Ip adress).

2024-08-1314_25_24-456019830@desktop-lgtmcrb-RemoteDesktop-RustDesk.jpg.e7c9fbc052f5f7d39150fb515c742454.jpg

 

Quote

Firewall settings blocking connection

, that I don't really know. But since other (newer) devices are working fine with the app and cloud , I expect this not to be a problem.

 

debug: Does this help?

3200879869:1723552182939750 mgos_sys_config.c:323   Saved to conf9.json
3200944423 cloud_aes.c:592         Sending 1853 bytes
3200949191 
3200957850 cloud_aes.c:576         free mem: 34864 / 33048, buf len: 1856, buf size: 1870
3200973828 cloud_aes.c:406         Bytes written: 1420 bytes remaining: 436
3200982723 mgos_mongoose.c:66      New heap free LWM: 32920
3201022712 mgos_http_server.c:180  0x3fff1ee4 HTTP connection from 192.168.68.20:60817
3201060573 cloud_aes.c:406         Bytes written: 436 bytes remaining: 0
3201104780 cloud_aes.c:592         Sending 31 bytes
3201109550 
3201116008 cloud_aes.c:576         free mem: 38012 / 32920, buf len: 32, buf size: 46
3201124821 cloud_aes.c:406         Bytes written: 32 bytes remaining: 0
3201176378 json.c:428              RAM: 52056 total, 39672 free
3201185389 cloud_aes.c:592         Sending 958 bytes
3201190150 
3201197618 cloud_aes.c:576         free mem: 39600 / 32920, buf len: 960, buf size: 974
3201203568 cloud_common.c:1612     Stop status keep alive timer
3201219043 cloud_aes.c:406         Bytes written: 960 bytes remaining: 0
3201280623 cloud_common.c:1173     Cmd: status
3201285988 cloud_common.c:144      Confirmed status serial 72
3201291202 cloud_common.c:1176     Cloud clear status timer
3201299563 cloud_aes.c:592         Sending 31 bytes
3201304329 
3201310814 cloud_aes.c:576         free mem: 40532 / 32920, buf len: 32, buf size: 46
3201319723 cloud_aes.c:406         Bytes written: 32 bytes remaining: 0
3201874087 mgos_http_server.c:180  0x3fff1ee4 HTTP connection from 192.168.68.20:60818
3201896567 json.c:428              RAM: 52056 total, 38980 free
3206868260 mgos_http_server.c:180  0x3fff2074 HTTP connection from 192.168.68.20:60828
3206889789 json.c:428              RAM: 52056 total, 38792 free
3211864597 mgos_http_server.c:180  0x3fff2074 HTTP connection from 192.168.68.20:60830
3211886109 json.c:428              RAM: 52056 total, 38792 free
3213852667 mgos_http_server.c:180  0x3fff2074 HTTP connection from 192.168.68.20:60832
3213871063 mgos_system.c:58        Rebooting in 200 ms
3214027266 esp_main.c:138          SDK: state: 5 -> 0 (0)
3214033358 esp_main.c:138          SDK: rm 0
3214038988 esp_main.c:138          SDK: pm close 7
3214048753 mgos_wifi.c:70          WiFi STA: Disconnected, reason: 8
3214056046 esp_main.c:138          SDK: sleep enable,type: 2
3214063138 mgos_net.c:84           WiFi STA: disconnected
3214069204 shelly.c:312            WiFi status=1313166336; mode=1
3214077475 coiot.c:491             Coap listener 0x3ffef80c is closed!
3214084217 coiot.c:616             coap_connect, WIFI status=1313166336 mode=1
29900649:1723552226198476 mgos_sys_config.c:323   Saved to conf9.json
29931661 mgos_mongoose.c:66      New heap free LWM: 36056
29965482 cloud_aes.c:592         Sending 1853 bytes
29970261 
29978924 cloud_aes.c:576         free mem: 36144 / 34320, buf len: 1856, buf size: 1870
29989226 mgos_http_server.c:180  0x3fff2024 HTTP connection from 192.168.68.20:60855
30010102 json.c:428              RAM: 52056 total, 34680 free
30024108 cloud_aes.c:406         Bytes written: 1420 bytes remaining: 436
30030163 mgos_mongoose.c:66      New heap free LWM: 33208
30068589 mgos_http_server.c:180  0x3fff189c HTTP connection from 192.168.68.20:60856
30105730 cloud_aes.c:406         Bytes written: 436 bytes remaining: 0
30147468 cloud_aes.c:592         Sending 31 bytes
30152255 
30158713 cloud_aes.c:576         free mem: 38192 / 33208, buf len: 32, buf size: 46
30167476 cloud_aes.c:406         Bytes written: 32 bytes remaining: 0
30198554 json.c:428              RAM: 52056 total, 39864 free
30206348 cloud_aes.c:592         Sending 967 bytes
30211092 
30218589 cloud_aes.c:576         free mem: 39768 / 33208, buf len: 976, buf size: 990
30225770 cloud_common.c:1612     Stop status keep alive timer
30249366 cloud_aes.c:406         Bytes written: 976 bytes remaining: 0
30289354 cloud_common.c:1173     Cmd: status
30294703 cloud_common.c:144      Confirmed status serial 4
30301129 cloud_common.c:1176     Cloud clear status timer
30308229 cloud_aes.c:592         Sending 31 bytes
30312979 
30319441 cloud_aes.c:576         free mem: 40736 / 33208, buf len: 32, buf size: 46
30328070 cloud_aes.c:406         Bytes written: 32 bytes remaining: 0
30375298 cloud_common.c:1185     Cmd: fw_info
30384168 shelly_update.c:350     no new firmware available...
30389521 shelly_update.c:311     cancel scheduled ota check
30395135 shelly_update.c:319     fwinfo check in 86400 seconds
30402106 cloud_common.c:1374     fwinfo: 0 20230913-113421/v1.14.0-gcb84623 http://firmware.shelly.cloud/gen1/SHPLG-S.zip
30409678 cloud_aes.c:592         Sending 31 bytes
30414438 
30420879 cloud_aes.c:576         free mem: 40372 / 33208, buf len: 32, buf size: 46
30430772 cloud_aes.c:406         Bytes written: 32 bytes remaining: 0
34977806 mgos_http_server.c:180  0x3fff1f9c HTTP connection from 192.168.68.20:60860
34999257 json.c:428              RAM: 52056 total, 38964 free
36096287 mgos_http_server.c:180  0x3fff1f9c HTTP connection from 192.168.68.20:60861

 

 

Cloud, it says it is connected.

2024-08-1314_34_32-456019830@desktop-lgtmcrb-RemoteDesktop-RustDesk.thumb.jpg.7e2ac177df16ee966768d080dd90e227.jpg2024-08-1314_34_43-456019830@desktop-lgtmcrb-RemoteDesktop-RustDesk.jpg.2e6c3231c8a3cf744f3f3c5a80c7f27c.jpg

 

Thanks, 

Cor

 

Edited by Cor
updated with cloud info
Link to comment
Share on other sites

Hi. 

I can't see the internal IP address of your network so I can't see if there is an issue or not 😄 ( its generally no major risk to showing your internal IP address but never share your public IP, as long as your internal IP is not pointing outside its not a major risk 🙂 )

what you can try is to make the DNS and the gateway the same IP address this should be the IP address of your network Default gateway. 

What I sometimes do with networks before I set a static IP address in a complex network is see that the device is working when getting an IP address from the DHCP server. Does the Device still say offline when you set the device to get the automatic IP address? 

If it stays offline when getting the IP address from the DHCP server ( Router ), there is a block. But I don't think by the sounds of it that you have any firewall to block devices. 

Try that and let me know 



 

Link to comment
Share on other sites

On 17.8.2024 at 12:53, Cor said:

@Heinz , just at home. And with removing and adding the device in the app  it is working now.

 

Many thanks for your help, 

Cor

I have the same problem. May I ask how you removed and readded the Device without loosing the configuration?

I have three devices and want to get sure to minimize the workload.

thanks 

 

 

Link to comment
Share on other sites

In some cases re-adding it into the network would resync. But sometimes like the case above it did not. 

I would log in to the device via the WebUI and reconnect the device to the network. 

when you delete the device linked to scenes from the app and re-add it with the same name and in the same room, it should relink the device to the scenes. I have not tested what it does with the local actions, but that should be stored on the device's memory. This is only removed with you do a factory reset. 

hope this helps 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Erstelle neue...