Beiträge von iamheretohelp

    Hello, hello! It is Dimitar Stanishev here from the Shelly Support team. We would like to provide you with more explanation of the new feature, which our Plus and Pro series will have. It is "Shelly Script" and below you can find more information.

    Developing a solution that uses complex logic or inter-component interactions that are asynchronous in time requires flexibility that can not easily be provided by constantly complicating the underlying OS of the device. As with any other software system, the "user space" software solution(s) are better suited to implement logic that is specific to the use case and can be developed by the end-user.

    The natural solution to the complexity of users' "job to be done" is to distribute the computational load of the solution building process. We here just can't be that smart to come up with all the right formulas. So we empower our users to create solutions by deploying scripts on Shelly devices (second generation). Actually, we don't know of any other device that offers that at the moment.

    Now you can have even more of the _creative autonomy_, which has been one of the main success product themes of our products. We don't want to tell you how to solve the problem, we don't want you to use a third-party integration, we don't want you to buy a hub.

    ## What is a "Shelly script"?

    A script is a program, written in a subset of JavaScript, which is a tried and proven technology - Mongoose OS, the same stack that we have the rest of our devices built on. The secret sauce is the exposure of the RPC APIs to the script. And the extra needed functionality - HTTP.GET (soon POST), Timers for scheduling, the ability to use the local web interface of the device to upload, edit and manage running scripts.

    We will publish links to the documentation and repository with examples in the coming days.

    Thank you for your feedback, Ratfink ! For sure, you have bought them from one of the dealers or directly from the manufacturer - https://shop.shelly.cloud/. Please tell me with more details from whom you have bought them, so we can find what can be the reason. Once after that, I will investigate and give you a solution.

    It is extremely difficult to communicate with Dimitar. Sometimes he answers, sometimes he doesn't. He has created a ticket in their internal system, telling the developers to fix it. But this was weeks ago...

    It is quite obvious that this is rather low priority for him and even lower priority for the developers. Their internal communication is a mess and I'm not even sure the developers actually are willing to fix this problem because the info I received from shelly-support months ago was that the developers say that the delay is intentional, necessary and can't be removed (see above). Dimitar has neither confirmed nor denied this but says that shelly support get their info either from him or from or from their own testing. So he seems to be implying that the support people don't communicate directly with the developers at all. I've asked for clarification on this but received no reply.

    And even if he'd confirm that, we'd only know that support is making stuff up, but we'd still not know whether support is actually fixing this. I have pointed out to Dimitar multiple times over the last months that this is an easy fix if it is true that the delay is baked into the firmware. But Dimitar has ignored the question and neither confirmed or denied what is causing the delay.

    In a nutshell: we are basically in the same spot as in April and I advise anyone who wants to see a solution to the shelly dimmer 2 delay problem: open support tickets with shelly support until we see some solutions.

    Thank you for your honest opinion! As I said in the personal chat with you, a lot of people are trying to reach me and I am not able to answer all of them in the respective manner of time. Your problem is planned to be fixed in 1.11 when it is officially released.

    damn...

    So I just created a new ticket. My wife is killing me. I have installed over 20 dimmer2 in our house...

    Give me your ticket number, so I can check if the problem is the same or it is something else.

    The delay occurred due to Easter in Bulgaria. I will text it here as well, please excuse me for the delay. As I promised over a personal message, today, I will review everything with our hardware team.

    I have not heard back from iamheretohelp since almost three weeks. By now I am starting to consider this behaviour as rude. As busy as he may be, there is always time to write a quick note that you haven't forgotten about the issue and will get back. But he is just silent, despite multiple reminders I sent.

    No, you are not. You are ignoring tophee.

    Now, a message to everyone. When there is a such situation, everyone can open an official ticket with us here - https://shelly.cloud/support/

    tophee, it will be great if you share with me the ticket number, so I can investigate what exactly happened and check the whole communication. After that, I will be able to advise with more details. If you found a way to reach me directly, I will be really thankful, so we can investigate why this is happening exactly. I have some proposals. Also, I would like to point that all the relays ( Shelly 1, Shelly 1PM, Shelly 2.5, Shelly 1L and etc. ) are not the same as Shelly Dimmer 2 ( the device is internally built with MOSFET transistors ). Although, I assume that the device should act in the same from the switch and from the cloud.

    Hello everyone! It is Dimitar Stanishev from the Shelly support team here. About the problem, which @orkus has. @Olsche informed me about it. @orkus , I have checked and I see that the device was on 1.9.6dimmer2 firmware. I need answers on a couple of topics:
    - What was the wiring? With neutral or not?
    - What was connected to O? Were there any transformer or LED driver? If yes, what it was? What were the bulbs after it?
    - What calibration has been used for this Shelly Dimmer 2?