Actions vs. Status queries in the Shelly couplings

1. offizieller Beitrag
    • Offizieller Beitrag

    Based on your questions:


    Since firmware 1.5.0, the Shelly have the Actions, with the help of which you can send when switching-state-change http requests.


    This can also be used to update the switching status of a CUxD device for Shelly. :)


    But:

    I'll point out that the Shelly sends the command only once (per switching operation). If this command does not arrive at the homematic center or if it is not processed there as expected, then a possible inconsistency of the switching state results at least until the next switching operation! :(


    Here I clearly see my published solution with the cyclical update at an advantage! ;)


    Who wants to test it anyway:


    State OFF => OUTPUT SWITCHED OFF URL

    Code
    http://<IP der CCU>:8181/x.exe?Antwort=dom.GetObject("CUxD.<CUxD-Geräteadresse:Kanal>.SET_STATE").State(0)

    Status ON => OUTPUT SWITCHED ON URL

    Code
    http://<IP der CCU>:8181/x.exe?Antwort=dom.GetObject("CUxD.<CUxD-Geräteadresse:Kanal>.SET_STATE").State(1)

    (The commands only cause the status to be set without executing any commands.)


    Have fun with it.:)

    • Offizieller Beitrag

    (This enty is in the original german Thread entry no. #8. I do not translate the whole discussion, sorry for this.)

    Info to all working with Homematic:

    After a "stress test", I can see that the switching status update via Actions works well.


    What is bothering me personally is that there is still no way to control if the command does not arrive in the homematic.


    :/ So maybe the combination is the "Golden Way":

    • Actions for Immediate Delivery
    • cycl. query for safe update (in longer intervals)

    I will test it with my "new" Shelly2.5 in this way.