Ok thank you
Cant tell for all the other brands but the default implementation for relay devices, including the current Shelly Wave devices, are using the SWITCH_BINARY class that doesnt support button events.
@Johan_Nilsson @Boris_Fers I pushed a change to the test channel which reverts most of the changes made to the reconnect mechanism on Homey Cloud. This should at least solve any app crashes. Not sure if it solves connection issues (devices not responding to commands) though. Could you test it by installing this test version.
Thanks for your efforts!
I updated to v3.33.0.
I still donât get Homey Cloud to communicate with my Shelly devices.
Somehow I have gotten mine to a bad state where re-installation doesnât restore the problems.
Are you getting no updates at all or only not able to control devices?
And could you send a diagnostic report, just to confirm there are no errors.
Both ways I think.
- Switching a device (on/off) in Homey Could has no effect on the device or its status in Shelly
- Switching a device (on/off) in Shelly doesnât change its status in Homey. In this case however the device follows commands from Shelly.
Could you test version 3.23.1 which is currently in test.
No difference to 3.23.0
Could you send another diagnostic report?
Hereâs a new diagnostic
02276be5-4de1-42a1-a75d-271323d6966a
Yeah, nothing in that log. So much for the theory that my previous edits concerning the reconnect mechanism are causing these connection issues. At least in your case it does not seem to matter. Iâd like to hear for @Boris_Fers as well though.
But as mentioned earlier I assumed reverting these edits would only resolve any app crashes that could happen when the connection actually broke. But I just can not imagine these edits having impact on not being able to establish a connection at all on app restart. The edits I did where only related to a working connection going down.
There is not much more I can do right now. If the issue persists for more users but there are no crash reports in my developer console and my own test results with Homey Cloud dont give any issues I would not know where to look.
I removed Shelly app and all devices.
After that I reinstalled Shelly app v3.22.8 and added a few devices.
50% better 
Homey Cloud now reflects correct status of my Shelly devices, but I can still not control Shelly devices from Homey Cloud
Same as before.
I donât know how you get the access and refresh tokens and how you store them, but maybe thatâs where the problem lies. Today, when I created a new Homey cloud account, I had this problem from the start, so the reconnect mechanism definitely wasnât triggered then, definitely not. However, the initial connection was established, that is, the first access and refresh token was obtained. However, since we existing users still had a valid access token when the app was updated, this error started to appear when the reconnect happened.
I will try with a completely new Homey account and then we will see if this assumption is true or not.
Thank you for the information.
So if I want to use the buttons for more then a mere switch on/off I will have to use another device.
It is not good, but I can live with it.
@Johan_Nilsson @Boris_Fers and any other Homey Cloud user really âŚ
I have made progress in identifying the source of the recent issue with Homey Cloud. My initial tests with my own test Homey Cloud where fine on every latest versions of the app. But just now I noticed Iâm running into the same issue as described here with the symptoms that there is a cloud connection and devices updates are coming in but controlling the devices isnt possible. So something other than the app has recently changed.
So I tested this with a couple of older versions of the app, back to version 3.21.7 of about a month ago. I wanted to make sure that this behavior is indeed caused by something outside the app. All the older versions of the app show exactly the same behavior now. This definitely rules out that any of the recent update to the app are related to this issue and itâs caused by something outside the app. Itâs also not an issue with the token as there is a working cloud connection on app (re)start which is established based on the same OAuth2 token.
I just noticed that Shelly is doing a migration of my.shelly.cloud to control.shelly.cloud in the upcoming days. My guess is that they have broken something in the Cloud Control API or made changes without telling me. I have asked them about this. There is not much more to do other than to wait.
I am waiting for a response from their support. Otherwise even a completely new installation doesnât work, just tested.
Just for test get your authorisation cloud key from your shelly account and try with this token if it works.if they are rolling out this migration then access token from old API will definitely not work on new API.
Itâs not that simple. The current connection is based on OAuth2 authentication. You cant just simply replace the token. And the current implementation still works in establishing a connection. But it seems Allterco Robotics unintentionally broke permissions (or intentional and forgot to tell me upfront).
I assume you are using websocket to receive device updates. Probably the rest API for sending commands.
As mentioned a couple of times the app is using the websocket connection for both sending and receiving. What currently is broken is this:
Since yesterday my three Shelly Plug S devices stopped listening to commands from homey. Tried everything, connection reset through maintenance dialog in homey, fw upgrade, reboot, reinstallation of Shelly app (as suggested).
The devices are visible in homey and their shown status is accurate but I cannot control them from homey, only from the Shelly app.
Anyone an idea how to fix it? Athom only replies (within a day!) That it is a known issue. Yeah. I know(n).
