Shelly ProDualCoverPMs not operating reliably

  • Hello everyone,

    I am the happy user of many shelly devices throughout my home and have now installed a total of three Shelly ProDualCoverPMs.

    My problem with my new 3x ProDualCoverPM is that they only work in about 95% of the cases.

    In about 1 in every 15 or 1 in 20 attempts to open or close my covers, the Shellys do not close or open the covers but after 2 seconds simply report that the cover is now open or closed (depending on the direction where the error occurred). I am experiencing these same issues with all my 3 installed units. I have stood near the ProDualCoverPMs while testing this and have discovered that whenever the error occurs, I do not hear the "click" of the relay of the Shelly. It seems that the Shelly is not providing power to the motor in these cases and then after 2 seconds simply reports that the job is done and the cover is now open or closed.

    Setup:

    • Shelly is directly hooked up to the individual motor of the cover without intermediate components
    • The cover motor consumes about 100W when operating and when done quickly falls to 2W for a second and then 0W
    • Shelly is fully calibrated using the web-interface

    Example error that occurs 1 in 15-20 attempts:

    • Cover (1) connected to one ProDualCoverPM is currently closed.
    • I press on "open" for cover(1) using the web-interface.
    • The debug console shows that the command is received.
    • There is *no* audible click that Shelly operates the relay that provides power to the motor.
    • 2 seconds later, Shelly reports the job to be done and the cover now to be fully open.

    (see full debug log below)

    What I have already tried:

    • I have turned off the eco mode.
    • I have checked that the Shellys have perfect wifi reception.
    • I have updated to the latest stable firmware (20231106-160215/1.0.8-gdba0ee3).
    • I have updated to the latest beta firmware (20231114-185915/1.1.0-beta2-g4fbfafd)
    • I have configured the Idle power threshold to values between 2W and 7W
    • I have disabled obstacle detection

    I greatly appreciate any pointer / help in this matter! This is vital to me as I have to open my covers before any rain approaches. At this time, I cannot reliably command my covers to open when that happens.

    Device: Shelly ProDualCoverPM

    Stable firmware: 20231106-160215/1.0.8-gdba0ee3

    Beta firmware: 20231114-185915/1.1.0-beta2-g4fbfafd

    Example of an unsuccessful attempt (also included in full log below):

    [script][/script]

    [script]{ [/script]

    [script]"ts": 1700690661.086, [/script]

    [script]"level": 2, [/script]

    [script]"data": "shelly_notification:163 Status change of cover:1: {\"id\":1,\"last_direction\":\"open\",\"move_started_at\":1700690661.06,\"move_timeout\":50.00,\"source\":\"WS_in\",\"state\":\"opening\"}" [/script]

    [script]}, [/script]

    [script]{ [/script]

    [script]"ts": 1700690663.84, [/script]

    [script]"level": 2, [/script]

    [script]"data": "shelly_notification:163 Status change of cover:1: {\"id\":1,\"apower\":0,\"current\":0,\"current_pos\":100,\"move_started_at\":null,\"move_timeout\":null,\"pf\":0,\"source\":\"limit_switch\",\"state\":\"open\"}" [/script]

    [script]},[/script]

    [script][/script]

    Full device log showing successful and unsuccessful attempts:

    diagnostics-shelly-produalcoverpm-debug-log-4.txt

    3 Mal editiert, zuletzt von redpine (23. November 2023 um 00:39)

  • redpine 23. November 2023 um 00:24

    Hat den Titel des Themas von „Shelly“ zu „Shelly ProDualCoverPMs not operating reliably“ geändert.
  • I have written a small script that remedies the situation while this is unsolved. The script listens for open/close operations that are unusually fast (e.g. below 4 seconds) and if it detects this, sends another open/close command. If the unusually fast command was in fact normal, e.g. because the covers were barely open/closed and thus the operation really only took below 4 seconds to complete than calling the additional open/close command should not have any impact.

    I have tested the script with my setup and it seems to fix the situation at least temporarily for me as a hot fix.

    If anyone else comes across this issue, here is my code that I used to fix this:

    2 Mal editiert, zuletzt von redpine (23. November 2023 um 14:04)