-
Autor
I am about replacing a bus system cabled to 13 cover untits with Shelly Dual Cover PM. While I have setup loads of various Shelly devices (Wifi driven) in the past the initial network setup seems to be a problem.
Initially I left the new devices as is and access those via direct Wifi AP on 192.168.33.1 to setup Wifi client, upgrade the firmware from 0.9.9 to 1.1.0 and trying to add those afterwards with their network IP addresses using the Shelly App.
What I experienced was that the AP mode worked, setting up the Wifi client mode (DHCP and set the IP as fixed using the LAN router interface) worked.
After that running the firmware worked but took around 15mins+ to succeed. Then using their IP addresses the UI was NOT accessible anymore and I had a network outage.
Same adding the PMs to the Shelly App!?
Wifi signal/logo on the LCD screed was grenn but Cloud logo either didn't turn green or took 30mins!?
So the setup for a single Pro Cover PM took around 30-45mins and the network connectivity was still unreliable.
The used Wifi/LAN router was a T-Systems Speedport and in the router interface the Shelly IP were listed and so discovered but for one out of 6 Shelly devices the logo was NOT a Wifi logo but a LAN/Ethernet logo in the router UI!?
That started to cause a lot of headache for me and so I decided to turn off Ethernet using the Shellie's LCD screen.
After doing that the Wifi connection + Cloud connection worked straight away and took totally 30s to reboot and connect.
This leads me to an assumption that the Shelly Pro Cover PM don't properly work if both, Wifi+Ethernet, is enabled. One has to know about this as it seems that either the firmware or the hardware networking ports are causing network issues. I do not believe that this is a problem of my internet router but I haven't tried another router so far.
Does anyone have similiar issues with the Shelly Pro (Cover) PMs having both networking ports enabled? Is this something which has been addressed so far and Shelly is aware about?
if it comes enabled by default and one has to disable it manually before it properly works that it's not recommended to have both network ports enabled by factory defaults 
