ETT

There is, and propably will not be, any documentation about Firewall rules (IP plus Ports) required in order the WD cloud connection to work properly ? I noticed connection trials using ports 80, 6xxx (several) and 123 (ntp). HTTPS was not used. I provided the ip for the time setver and WD used it, but WD wanted also to use other time servers in China and in Ukraina. The HTTP was used to several locations on China. Anyway, I dislike the idea of allowing unlimited internet access to the Shellys, which are used control the heating of our house. The WD advertisement needs to be changed to match the functionality ie cloud IS REQUIRED for full usage. With 1 WD one can buy 5 other Shellys, if just a simple relay switch is what one eventually gets from WD without internet. Cloud registration is also required for all Shellys one plans to use with WD, I understood.

I created a Shelly cloud account (and iOs Shelly Smart app) only to test the Shelly WD. I have some 12 Shellys in two locations. I am using NAS/MySQL db plus Shelly scripting to automate and follow my Shellys. Ruuvitags provide measurement to some of my Shellys. Visualization is currently done via MySQL and Grafana. I plan to double the no of Shellys in the future. All this strictly in a separate IoT-LAN, so none is connected to Shelly cloud. I plan to try to create virtual buttons to WD and use webhooks to drive (ON/OFF) some of my Shellys, naturally without cloud. However, this is a bit tedious and limited way to utilize WD. Additionally, the WD firmware updates need to be done via iPhone hot spot.

I created a Shelly cloud account (and iOs Shelly Smart app) only to test the Shelly WD. I have some 12 Shellys in two locations. I am using NAS/MySQL db plus Shelly scripting to automate and follow my Shellys. Ruuvitags provide measurement to some of my Shellys. Visualization is currently done via MySQL and Grafana. I plan to double the no of Shellys in the future. All this strictly in a separate IoT-LAN, so none is connected to Shelly cloud. I plan to try to create virtual buttons to WD and use webhooks to drive (ON/OFF) some of my Shellys, naturally without cloud. However, this is a bit tedious and limited way to utilize WD. Additionally, the WD firmware updates need to be done via iPhone hot spot.

I fully agree. I looked after the best price of WD. None of the shops expressed that cloud is a must. I want to keep my IoT strictly inside my IoT LAN, only NTP-service is allowed for my Shelly devices. Had I known before buying WD that the device does not work without cloud, I would not have bought the WD. I hope that at some day the WD will work without cloud. Now I lost some 130€ because of misleading ad statements.

I want to use all my Shellys without any connection to the internet (or cloud), so a dedicated and isolated LAN only. That does apply to all other Shelly devices I have so far (eg Pro 3EM) . Now Shelly Wall Display seems to be an exception to this philosophy. I managed to update the Wall Display FW to 2.0.0 by sharing an internet connection from my iPhone. However, anything beyond that ie normal use ie adding some of my Shelly devices to the Wall Display does not work without unlimited internet connection and cloud, which most likely is also required for all Shelly devices that are included to the Wall Display. The above principle of operation is in severe conflict with the first ad statement in the Shelly web site (Why to choose Shelly): ”No Cloud required! Control your Shelly devices locally without connecting them to an external cloud or server.” I would not have bought the Wall Display at all if this requirement had been clearly expressed in conjunction with the Shelly Wall Display.

I tested the FW update with Shelly 1PM. The IPv4 of 35.205.173.252 with port 443 enables the FW update successfully. For the Shelly Wall Dsiplay that does not work.

I am disappointed with my Shelly Wall Display. It tries to connect to several sites in China even though I have disabled cloud. I don't like this sort of behavior at all. How do I update the firmware without the device connecting to China ? Is there an IP-address available for such updates (to be added to FW allowed list) ?