Beiträge von LubomirH

  • schedule vs. power outage

    Hi,

    I need the Shelly PLUS 1PM to switch on our dehumidifier every Friday at lunch time and switch off at midnight between Sunday and Monday.

    I have configured the schedules the following way:

    Fri 12:00 Switch ON

    Fri 23:59 Switch OFF

    Sat 00:00 Switch ON

    Sat 23:59 Switch OFF

    Sun 00:00 Switch ON

    Sun 23:59 Switch OFF

    It works, but whenever there is a power outage after any of the Switch ON schedule, it will not switch on immediately after power restoration, but first with the next Switch ON schedule.

    Is there any setting which will make the relay switch on even after a power outage?

    I know I can minimize the time the dehumidifier will be off by adding a bunch of Switch ON schedules during the day, but I hope there is just some setting I am missing.


    thanks for help!

    Lubomir

  • Devices in different vlans - how to add them to Shelly app?

    I came here while trying to find an official statement about the ports the Shelly devices are using to connect to the Shelly cloud.

    I was able to add the Shelly2.5 device to the Shelly app in two steps, first while being connected to the Shelly own AP and later while being on the same IOT WLAN/VLAN via the menu/discovered devices. After successful addition the app seems to use the HTTP port to connect to the device.

    But it didn't want to connect to the cloud until I have opened some additional ports to my standard IOT rules (UDP53-DNS; TCP80-HTTP and TCP443-HTTPS).

    Below is the full list as I have it now.

    I had to open UDP123 (ntp) und TCP6011 + TCP6021. One can change to local time server via settings later.

    IOT-shelly-FWrules.JPG

    Note: The DNS is not visible on this screenshot, it is way up on the list.

    Below is a communication I could see after Shelly2.5 restart.

    I have ignored the UDP5353 (multicast DNS) und UDP5683 (multicast CoAP) for now. You can read about the latter here https://github.com/alexryd/homebr…P-and-multicast

    IOT-shelly-Communication.JPG


    have fun ;)

    LH

  • Cloud Ports

    +1 für eine eindeutige answer from Shelly welche Ports sollen freigeschaltet werden so da steht nichts in Wege zum Shelly cloud.

    Zu den DNS (UDP53) und standardmäßige HTTP (TCP80, TCP443) die ich bestand aus meine IOT VLAN geöffnet hatte, habe ich auch noch UDP123 (ntp) und TCP6011 + TCP6021 gesehen und gleich auch geöffnet.

    So sieht es bei mir jetzt und shelly ist in clouds ;)

    IOT-shelly-FWrules.JPG

    bemerkung: DNS ist wesentlich oben auf der FW rule liste

    Das hier ist eine Liste der Kommunikation die ich könnte nach Shelly2.5 restart sehen.

    Ich habe UDP5353 (multicast DNS) und UDP5683 (multicast CoAP) ignoriert, mindestens für diese Augenblick. Hier kann man lesen darüber https://github.com/alexryd/homebr…P-and-multicast

    IOT-shelly-Communication.JPG


    MfG

    LH