Yes, very likely. You should report this to Athom. Looks like an issue with their cloud infrastructure.
I used the input 1 as I wanted the light to be dimmed to 100% when I switched it on using the momentary switch.
I have since changed that to âturned onâ and thatâs worked, not sure why that wouldnât work for input 1.
Thanks for your help
Me again and my problem with controlling Shelly devices from the Homey cloud.
Iâm also now in contact with Shellyâs support team, Iâm still waiting response from the Homey support team.
In the meantime, I created a completely new account on Homey Cloud and tried it with a clean setup (adding some devices just for test), and also did not work.
Could you be so kind and create an experimental build from version 3.22.4 just for testing purposes? 
The error is from Homey Cloud. Allterco Robotics wont be able to help you and creating a new account on the Shelly Cloud might not make a difference as well.
I assume you understand I canât push a version to the test channel that reverts back to a couple of versions. There are users actually using that as their production installation. It would affect a lot of people for the benefits of only one.
If you can create a developer environment you could load this version yourself from GitHub.
Iâm on Homey Cloud and with Shelly app with version v3.22.8.
I have a question on the new reconnect behaviour.
The Shelly app today triggered the card âCloud connection errorâ.
When I saw that had happened I was curious to evaluate if the connection had been re-established, but apparently not. At least not a few minutes later.
I did a log if there is something to look into.
ebfb5a20-7db9-4d3b-a9a0-c6835bfa5956
After re-installing the Shelly app connection was not re-established.
After a second attempt to re-install the Shelly app it crashed.
Did a third attempt but connection is not re-established. It has not happened to me before that I can not re-establish cennecton between Shelly and Homey Cloud with a re-installation of the Shelly app.
Currently Iâm stuck
Hereâs another log from the state Iâm in after all this
2799906f-586b-4308-8e3e-b8394397efbe
Do you receive updates from your Shelly devices into Homey?
Did you try with âTry to repairâ option?
No and No
Have never needed to repair earlier, a bit unattractive if you have many devices 
Currently I have lost the connection and I am not able to restore it - has not happend to me before
Just try with one device no need to try with all of them.
Can test later today with an extra Shelly Plug that I havnât installed yet
I donât know where the problem is. I just want to come to the conclusion and that in the end this problem is solved.
After a couple of back and forth with Homey support I get this message:
Hi Boris,
Thank you for your reply.
You can check the settings in the Shelly app on your phone. There must be a problem in the Shelly app.
What you also can try, is to delete the Shelly account and create a new one and leave all the settings default.This isnât a Homey issue. If you canât get it solved, maybe you can contact the developer of the Shelly app: [APP][Pro&Cloud] Shelly
I wish you a great day!
Best Regards,Daphne
Athom Support
So again nothing, just circling around from one person to another.
I assume you understand I canât push a version to the test channel that reverts back to a couple of versions. There are users actually using that as their production installation. It would affect a lot of people for the benefits of only one.
I didnât know that experimental versions automatically affect other users as well. I was under the impression that the new version is installed on the userâs Homeys when is released publicly.
I didnât expect anything else from the wonderful support of Athom. Did you send them the screenshots of the errors as posted here before. They are obviously connection errors somewhere in the cloud infrastructure from Athom.
Unfortunately users always point to the app and Athom support does but have the knowledge to actually assess the issue.
But just to make sure itâs not the app Iâll revert the changes made to the reconnect mechanism and will deploy it to test. That should not affect any other users. Perhaps the extended timeout before reconnecting is not playing nice with Homey Cloud. But if it does but make a difference there is nothing more I can do for you guys. You will have to get 2nd level support (a could engineer) to look at it.
Thank you. 
Yes, I sent them screenshots. I ended up on my own generating a diagnostic report for them from my Homey Cloud instance so they could check for connectivity issues between these two clouds. After that I just got a reply that their developers were informed about this problem and that was it.
Sorry, but I have to intervene here. Please do not blame our awesome support guys, they are doing fantastic work under the workload they have. Yes there is a very complex issue on our side that has been ongoing for too long now, we immediately admit that. There is a fix for this problem that is almost ready to be released. But⌠that is not the problem that we are seeing now. Version 3.22.8 has a bug in it which causes the Shelly app to crash on our cloud environment. The developer gets a crash report of this and can fix this. We can not fix this new issue, but we can, and will, fix the connectivity issue.
I added a new device (Shelly Plug S) to the Shelly system, and after that also to the Homey Cloud setup.
The new device is however unresponsive to power switching I do in the Homey app, nor does it read its cureent state from the Shelly Cloud.
It appears I have no connection anymore between Homey Cloud and the Shelly Cloud, and this is sticky also after multiple re-installations of the Shelly app.
The only reports that are send to me are manually submitted by users and contain either no information at all or logging about the known issue regarding the reconnect mechanism. I just checked the developer portal and I do see about a 100 reports (of 4000 cloud users) indicating the app crashing but with no useful information as well. No idea why this has not been emailed to me.
But Iâll believe your word for it and will revert the code. The changes where made only because of this ongoing known connection issue. If Athom will be fixing the underlying issue there is no need to try and work around that anyway.
1 Like
Then you have the same problem as me. Device updates work normally but you cannot control them.
Happend to me earlier today for the first time, and I had then been on v.3.22.8 for some days without any problems at all.
I think it started with that the Shell-condition âCloud connection errorâ was triggered, I think that is a new one from the recent releases, but not sure. I know this becauseI have a flow that notifies me when Shellyâs âCloud cennection errorâ gets trigged. After that I can not get it fucntional again, not even after re-installations of the Shelly app.
Hello everyone, I have a couple of Xiaomi plant detectors that work with Bluetooth, but my Homey is too far away for the signal to reach. I was wondering if the Bluetooth gateway recently released by Shelly would amplify the signal and work for connecting my plant sensor, or does it only work with Shelly products?
Thank you.
Thatâs exactly what Iâm thinking as well. Seems to only happen when a user experiences a cloud disconnected and the trigger card is supposed to trigger. I might have actually found the bug but Iâll revert the complete code just to make sure (making this card do nothing). I still cant explain why this would make devices uncontrollable even after a restart of the app though.
Although the BLE gateway is probably able to pick up the advertisements from the plant sensor there is no automated way to update those devices in Homey as the Shelly app has not permission to update devices from other apps.
