Yes: scroll back just a few posts.
1 Like
I use the Shelly-app for Homey in the cloud. Version 3.22.8.
When I press a shelly button, on any shelly device, the button visually turns on but in the shelly cloud the botton remains off. After some time the button visual goes out.
When I turn on the button in the shelly cloud, the shelly app from homey responds.
What is going on?
Youâre right, at first I thought Websocket was only used for real-time events. Looks like itâs really a problem on Shellyâs side. And also more and more users are affected.
When you send a Command Request do you get a Command Response? If there was an error message there that could be helped.
Not yet. What do you use Homey cloud or Homey Pro?
I see the same issue. The command direction is not working.
That would help indeed but there is none.
What do you mean with that? No Command Response received or no error message in Command Response?
Both. Allterco Robotics is looking into it as we speak.
1 Like
@Boris_Fers @Johan_Nilsson @Super_Grover
Together with Allterco Robotics we have looked into the issue. Short summary, the issue is identified and I just published a release to the test channel (3.23.2) which fixes this and is now pending approval by Athom.
Longer version, Allterco Robotics switched from numeral deviceIdâs to strings with the introduction of the Shelly BLU devices. They forgot to tell me and to update the API documentation which still references to a number. There was probably a âcompatibilityâ layer active that kept this API afloat âfor the transition periodâ but this was removed two days ago.
4 Likes
so we are down again, im sick of this, this time i wrote to Homey before you.
Lovely response, really motivating for the time I put into this.
Read the messages above your constructive criticism. Not being able to control devices was caused by undocumented and uncommunicated changes to the Shelly Cloud API. Out of my hands. The other issue where the connection breaks and is not restored is a known issue in a module by Athom. Out of my hands as well.
Ok, I did break something where the app would crash if the connection goes down but also fixed that straigth away. Mea Culpa. That is now pending approval by Athom for some two days now. Out of my control.
So good thing you contacted Homey directly. 
2 Likes
Definitely more than two days ago 
Tested version 3.23.2 and is working now 
I have updated and can confirm after just a short test that it works.
Thanks @Phuturist for your work!!!
What is your thinking about the reconnect stuff?
I think your intention was very good and encourage your to keep it for some more testing
Nothing has changed concerning the reconnect issue. I did leave a longer grace periode of missed ping-pongs (checks if the connection is alive) in the code before attempting to reconnect but the underlying issue is still present. Itâs just an unfortunate incident where this issue with the Shelly Cloud API pops up right around the time I tried to workaround the reconnect issue and users and Athom start to point to me as the developer. Itâs taken another big chunk out of my free time to find the cause.
But about the reconnect issue, if you read along in this thread you have read the message of someone from Athom support telling that they are on it and expect the have it fixed any time soon. Thatâs all the information I have. This is an open issue from me with Athom for about a year now. I actually had to remind, escalate it and make users report this themself to get Athomâs attention. I think I have done enough to get this sorted now.
My personal opinion, donât use cloud services for Home Automation unless you really have to.
hope its ok to ask.
But last time I reinstalled the shelly app 100 times and the only thing that helped me was to uninstall and install again, and then search all my devices, which is not so funny, cause all flows need to be fixed afterwards.
Do you think thatâs where I am again, cause i reinstalled many times yesterday, with no success.
/t
I donât even try to think to do this. 
Wait for a new version or install the test version and it should work.
Have you removed the connection loss trigger?
One suggestion, can you add support for Shelly:Online event?
Based on this event, it would be possible to know when the device lost connection to Shelly cloud.
Yes, as per your request I reverted all the changes made to the cloud connection including this triggercard (which actually introduced the bug that made the app crash when the connection went down).
Feel free to submit a feature request. For now I need to take care of other stuff which I havent been able to do because of this.
Hello,
Since switching to the Shelly Cloud, my Shelly devices can no longer be accessed. The flows donât work. However, the measured values are displayed. Is this a known problem or is there a solution? I have already deleted all deices and added new ones.
Best regards
Ulf
Wait for a new version or install the test version.
