Beiträge von tgessendorfer

tgessendorfer

Hello,

I have 7 Shelly Shelly Pro Dual Cover/Shutter PM which control 13 shutters so the last Shelly has no shutter connection at all.

I want to create a single group with all shutters inside and control them via switch or button all at once.

What would be the best approach to achieve this?

Could I connect a switch to the last free channel of my Shelly Pro Dual Cover/Shutter PM and control the group from this switch?

Any recommendation and/or real world experience would be appreciated.

No SmartHome solution existing so only Shelly in Wifi via App currently but a switch would be great...

tgessendorfer

Zitat von thgoebel

It is not recommended to enable both WLAN and LAN in the same network. For what purpose should it be useful?

Smart answer 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

tgessendorfer

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?

tgessendorfer

I have a couple of Shelly Dimmer 2, all setup same way with multiple momentary switches turning on/off 4 LEDs in a single room but one has strange issues that when I turn on the light on any of the 3 switches the light immediately turns off?

This is strangely not always the case and works 60% of the time and always works with the Shelly App.

In the history I can just see a "turn off" and in the Debug log I can't really figure out why it turns of.

Any ideas? Trying firmware 1.140 and previous one...

Debug log attached with the button press turn on and off procedure.

Code

314328147:1704410844227029 mgos_sys_config.c:323   Saved to conf9.json
314373925 cloud_aes.c:592         Sending 2389 bytes
314377892 314384687 cloud_aes.c:576         free mem: 31044 / 28680, buf len: 2400, buf size: 2414
314395179 cloud_aes.c:406         Bytes written: 1420 bytes remaining: 980
314402362 stmuart.c:248           enqueuing command 10
314406884 stmuart.c:351           uart_send: 204 16 0 bytes
314411974 mgos_mongoose.c:66      New heap free LWM: 28552
314422385 dimmer_proto.c:192      error[0] pulses[7] power[0.00] dchi[0] status[8001] debug[0(0 0)]
314453416 mgos_http_server.c:180  0x3fff2a44 HTTP connection from 192.168.0.172:37444
314478940 mgos_mongoose.c:66      New heap free LWM: 27936
314487704 cloud_aes.c:406         Bytes written: 980 bytes remaining: 0
314537558 cloud_aes.c:592         Sending 31 bytes
314541592 314547010 cloud_aes.c:576         free mem: 36040 / 27936, buf len: 32, buf size: 46
314554115 cloud_aes.c:406         Bytes written: 32 bytes remaining: 0
314599504 json.c:428              RAM: 49672 total, 34880 free
314605644 cloud_aes.c:592         Sending 1191 bytes
314609609 314615680 cloud_aes.c:576         free mem: 34824 / 27936, buf len: 1200, buf size: 1214
314620647 cloud_common.c:1612     Stop status keep alive timer
314641207 cloud_aes.c:406         Bytes written: 1200 bytes remaining: 0
314766548 cloud_common.c:1173     Cmd: status
314771141 cloud_common.c:144      Confirmed status serial 51
314775495 cloud_common.c:1176     Cloud clear status timer
314782441 cloud_aes.c:592         Sending 31 bytes
314786417 314791835 cloud_aes.c:576         free mem: 36032 / 27936, buf len: 32, buf size: 46
314798944 cloud_aes.c:406         Bytes written: 32 bytes remaining: 0
316350599 stmuart.c:248           enqueuing command 10
316356265 stmuart.c:351           uart_send: 205 16 0 bytes
316371747 dimmer_proto.c:192      error[0] pulses[8] power[0.00] dchi[0] status[8001] debug[0(0 0)]
316796781 mgos_http_server.c:180  0x3fff2a44 HTTP connection from 192.168.0.172:45096
316814298 json.c:428              RAM: 49672 total, 34740 free
317075480 dimmer_buttons.c:281    BUTTON0: state[1]
317080520 dimmer_buttons.c:156    # Start dimming timer: 0
317239848 dimmer_buttons.c:281    BUTTON0: state[0]
317245741 dimmer_actions.c:116    SHORTPUSH[0]
317250662 dimmer_buttons.c:144    # Stop dimming timer: 0
317465876 json.c:428              RAM: 49672 total, 35708 free
317472060 cloud_aes.c:592         Sending 1192 bytes
317476046 317482153 cloud_aes.c:576         free mem: 35652 / 27936, buf len: 1200, buf size: 1214
317488217 cloud_common.c:1612     Stop status keep alive timer
317497487 cloud_aes.c:406         Bytes written: 1200 bytes remaining: 0
317544252 cloud_common.c:1173     Cmd: status
317549944 cloud_common.c:144      Confirmed status serial 52
317554297 cloud_common.c:1176     Cloud clear status timer
317560156 cloud_aes.c:592         Sending 31 bytes
317564140 317569569 cloud_aes.c:576         free mem: 36652 / 27936, buf len: 32, buf size: 46
317577749 cloud_aes.c:406         Bytes written: 32 bytes remaining: 0
317656107 stmuart.c:248           enqueuing command 03
317660681 stmuart.c:351           uart_send: 206 3 6 bytes
317669886 dimmer_proto.c:47       STU: Got answer from command: 03
317715965 dimmer_buttons.c:281    BUTTON0: state[1]
317721020 dimmer_buttons.c:156    # Start dimming timer: 0
317801894 dimmer_buttons.c:281    BUTTON0: state[0]
317806692 dimmer_actions.c:116    SHORTPUSH[0]
317811727 dimmer_buttons.c:144    # Stop dimming timer: 0
318028238 json.c:428              RAM: 49672 total, 35672 free
318034424 cloud_aes.c:592         Sending 1191 bytes
318038437 318044539 cloud_aes.c:576         free mem: 35616 / 27936, buf len: 1200, buf size: 1214
318050617 cloud_common.c:1612     Stop status keep alive timer
318058207 cloud_aes.c:406         Bytes written: 1200 bytes remaining: 0
318101687 cloud_common.c:1173     Cmd: status
318106300 cloud_common.c:144      Confirmed status serial 53
318111746 cloud_common.c:1176     Cloud clear status timer
318117638 cloud_aes.c:592         Sending 31 bytes
318121661 318127125 cloud_aes.c:576         free mem: 36488 / 27936, buf len: 32, buf size: 46
318134371 cloud_aes.c:406         Bytes written: 32 bytes remaining: 0
318218333 stmuart.c:248           enqueuing command 03
318222937 stmuart.c:351           uart_send: 207 3 6 bytes
318233346 dimmer_proto.c:47       STU: Got answer from command: 03
318350654 stmuart.c:248           enqueuing command 10
318356356 stmuart.c:351           uart_send: 208 16 0 bytes
318366678 dimmer_proto.c:192      error[0] pulses[122] power[0.00] dchi[0] status[8001] debug[0(0 0)]
318440884 json.c:428              RAM: 49672 total, 35708 free
318447103 cloud_aes.c:592         Sending 1192 bytes
318452210 318458323 cloud_aes.c:576         free mem: 35652 / 27936, buf len: 1200, buf size: 1214
318463341 cloud_common.c:1612     Stop status keep alive timer
318471254 cloud_aes.c:406         Bytes written: 1200 bytes remaining: 0
318526947 cloud_common.c:1173     Cmd: status
318531583 cloud_common.c:144      Confirmed status serial 54
318535972 cloud_common.c:1176     Cloud clear status timer
318541859 cloud_aes.c:592         Sending 31 bytes
318545873 318552430 cloud_aes.c:576         free mem: 36652 / 27936, buf len: 32, buf size: 46
318559574 cloud_aes.c:406         Bytes written: 32 bytes remaining: 0
320350821 stmuart.c:248           enqueuing command 10
320355456 stmuart.c:351           uart_send: 209 16 0 bytes
320366918 dimmer_proto.c:192      error[0] pulses[8] power[0.00] dchi[0] status[8001] debug[0(0 0)]
320593211 mgos_http_server.c:180  0x3fff2774 HTTP connection from 192.168.0.172:45100
320760969 mgos_http_server.c:180  0x3fff2a44 HTTP connection from 192.168.0.172:45106
322268080 json.c:428              RAM: 49672 total, 34664 free
322351038 stmuart.c:248           enqueuing command 10
322355679 stmuart.c:351           uart_send: 210 16 0 bytes
322365733 dimmer_proto.c:192      error[0] pulses[8] power[0.00] dchi[0] status[8001] debug[0(0 0)]

Alles anzeigen

tgessendorfer

Es gibt wohl jetzt die Firmware Version 2.2.1 für den Shelly Motion (2) wo ich 3 Stück mit riesen Problemen upgegradet hatte.

Ich habe ein Update auf einem Motion 2 gemacht und die Verbindungsprobleme scheinen behoben:

tgessendorfer

Same here... installed in a single electric plug my Shelly Plus 1PM measures 270V while attaching a Duspol device shows 246V and this makes the Shelly disabling the relay...

Firmware 20230308-091612/0.14.1-g22a4cb7

tgessendorfer

Done

Der Inhalt kann nicht angezeigt werden, da Sie keine Berechtigung haben, diesen Inhalt zu sehen.

tgessendorfer

Hello,

can anyone let me know how I can replace a Eltako s12-100 with 3 Momentary Switches connected to it using 1 cable with a Shelly Dimmer 2 and how to wire correctly?

Attaching a picture from my setup (both N cables will be bridged and connected with a single cable to the Shelly btw.)

I was thinking the right way would be as follows but would appreciate some confirmation please:

input L Phase 230V (upper left brown cable) of Eltako goes into L of Shelly Dimmer 2
input +A1 (upper right brown cable for Momentary Switches press) goes into I1 of Shelly Dimmer 2
bulbs output (lower left grey cable) goes into O output of Shelly Dimmer 2
N cables (left right two blue cables) goes (bridged with a Wago) into N of Shelly Dimmer 2

Externer Inhalt lh3.googleusercontent.com

Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.

Beiträge von tgessendorfer

Shelly Pro Dual Cover/Shutter PM - How to control multiple with single button

SHELLY PRO DUAL COVER PM FW1.1.0 Wifi network issues with Ethernet/LAN being enabled on the device

SHELLY PRO DUAL COVER PM FW1.1.0 Wifi network issues with Ethernet/LAN being enabled on the device

Shelly Dimmer 2 with momentary switch turn on and immediately off?

Downgradelink Motion2 zu v2.1.8 bei Problemen mit aktueller Firmware v.2.2.0

shelly plus 1pm voltage reading not accurate

Replacing Eltako s12-100-230 connected to 3 Momentary Switches with Shelly Dimmer 2

Replacing Eltako s12-100-230 connected to 3 Momentary Switches with Shelly Dimmer 2