- in abhängigkeit des verwendeten Leitungsquerschnittes
Schade 
Das Wird bei mir wohl nicht gehen. Da ich am betroffenen LS 16mm² je Ader habe und ich das eigentlich nicht auch am Shelly 3em anlegen wollte (ist der Shelly 3em dafür überhaupt ausgelegt ?). Mal schauen, ob ich noch Platz habe für zwei zus. LS.
Ja das siehst du richtig, wie in den Anschlussschemen.
besten Dank!
Ich würde mich gern hier anschließen.
Dachte erst, dass ich mich einfach an die Sicherung der drei Phasen (L1 - L3) anklemmen kann. Nun sehe ich das aber so (lt. Bild im Lexikon), dass ich ne eigene 3-Phasen-Sicherung brauche, welche ihre Versorgung von der 3-Phasen-Sicherung der betroffenen drei Phasen bekommt.
Sprich je Shelly 3em eine eigene Sicherung (entweder über eine Phase, wenn einzelne Phasen gemessen werden soll oder als Sicherungsblock, wenn es um Drehstrom / 3-phasig geht). Habe ich das richtig verstanden?
Danke euch und schönes WE!
Grüße!
Kurze Frage in die Runde: Könnte ich mit dem Uni diesen IR-Sensor nutzen? Oder einem Äquivalent ... Evtl. gibt es etwas auf Laserbasis? Bin iMo auf der Suche nach so etwas.
Danke Euch!
P.S.: bin mit dem UNI auf komplett neuen wegen unterwegs und daher technisch nicht sattelfest.
Unfortunately I have no Idea in terms of Hassio
I am facing the exact same problem. I am running my Shellys (21 2.5) with the latest FirmWare und als have the newest App installed. But I still lose connections every day.
Issue: I open the Shelly App and using it. After a few seconds most of the devices are not reachable. Even if I opened the same roller shutter seconds ago - it´s gone. Same problem with relays.
@ifr Are you using a MESH-WLAN?
As you already mentioned before: the Shellys are not really offline or disconnected. No issues, if I try to connect via web interface.
Sind die Dimmer per MQTT angebunden?
@bocsitomcsi I was forced to deactivate "Post status subscribes" and "To give private values at startup".
Pic in GER:
pasted-from-clipboard.png
After these changes were made everything looks good. The shelly seem to react on these initial states.
Enter the device ip in your browser und use the web interface ^^. You can set up a weekly schedule.
You should open a new Ticket at Alterco and/or maybe open a new Thread in this forum because the topic discussed here does not match with your issue.
Have you made your schedule in the App or via web interface?
btw.: I would not compare those two things (kingart vs shelly). Not only because of the certificate... possibility and build is also different.
Ok... Maybe I found a hint to the solution. I recently checked all settings again (shelly and mqtt in ioBroker). From my point of view there is an unfortunate condition.
In ioBroker there is a setting for the mqttBroker
[Blockierte Grafik: https://ticket.shelly.support/file.php?key=vuecna3f59cgip6eegm0np2mouzujgbs&expires=1592611200&signature=ef0ade1c598f27e4be3db3dae73b3942fda16337&id=13409]
(copy from my ioBroker) [Blockierte Grafik: https://ticket.shelly.support/file.php?key=n_e0gn02jfjobqu5gpvujbb_rsom9cua&expires=1592611200&signature=6307fc6dff196e18069771256a6945aed229ac6f&id=13412]
(copy from ioBroker.net - settings)
So... On each reconnect the server "publish" the last known state to the connected client. If there is an unknown or false state, the roller shutter is reacting on the and changes its position. So if the setting I mentioned above is set to "true" I can reproduce the strange behavior of the roller shutter. Is the setting set to "false" (shown in the pic) I cant reproduce the strange behavior while I start/stop or restart the mqtt instance of the ioBroker. By now I am testing wheter the problem remain while reconnect to WLAN after loosing connection. My assumption is that its also gone.
jpedro: Are you using ioBroker with mqtt?
Background: I recently try to inspect the problem. What I figured out is, that I can stop my instance of the mqtt adapter in ioBroker. After starting the instance again I was looking at the LOG. I can see, that the mqttServer was subscribing the different shellys AND some of them are closing directly after the subscribe event. Strange thing: only some of them are closing - not all. But the hard fact is, that I can reproduce that behavior.
Greetz!
Hey @ all!
It is my first post, too. So ... HELLO! 
@jpedro: I have a WIFI6 (AX) Mesh with ASUS routers (4 of them - all connected over ethernet). Unfortunately some of my 21 Shelly 2.5 behave equal. I also forced some of them to disconnect from the WIFI and - GOTCHA! Few seconds (1 -2 sec) after loosing connection and reconnect the Shelly closes to 0% and remain at this position.
I am very intereseted in any solution. Thanks for open up a ticket
Greetz from Germany!
