I also re-pair one device for test and also no luck. I really don’t know what else I can do. Very frustrating.
On smartthings controling of devicse works as before.
So you have two home automation platforms controlling the same devices?
No, before Homey I used Smartthings. When I switched to Homey I deleted all routines on Smartthings and left all devices linked to Smartthings. Today I remembered that I can test controlling of devices also on smartthings.
That’s what I call being controlled by two home automation platforms. Are you sure that’s not causing your issues?
Yes I’m sure that this is not a problem. I removed connection between Smartthings and Shelly and no luck.
Had an app crash today as well. Homey Cloud. Not possible to generate diagnostic report after the crash, but I did one after reinstallation of the Shelly app.
fcbb5c91-127e-49e4-9a98-6842ce5d662a
The crash was likely on v3.22.7
Now I’m on v3.22.8, hopefully fixes the crashes 
Thanks for your work with the Shelly app!
Let me give you a more detailed explanation on how this works including an analysis from my point of view.
When the app starts it will open up a websocket connection between Homey and Shelly Cloud. This websocket connection is used to both receive status updates as well as send commands. The connection is opened based on OAuth2 authentication with the Shelly cloud credentials of the user. It can happen that the connection breaks but there is a reconnect mechanism in place. Unfortunately this reconnect mechanism does not work as there is a bug in the OAuth2 module from Athom when trying to refresh the token on restoring the connection. But this lis irrelevant for your problem as you say you receive status updates in Homey.
So it seems you dont have issues with the credentials or establishing a connection. According to you the only issue you are having is that the commands you send are not executed on the device.This could mean two things. The code for sending the command is messed up and the command is not being send or somewhere after sending the command it’s not being properly handled.
This part of the code for sending commands hasnt changed for months, I tested it myself earlier today, there are no other users reporting this and you never mentioned any errors on the flowcards (although you never confirmed my questions about this either). This pretty much rules the code out as a possible cause. That means it’s somewhere further down the line which is out of my control.
It sounds like there is something wrong in the communication between Homey and Shelly Cloud or more likely in the handling of the commands in Shelly Cloud. It’s strange this only seems to affect you though. I’m aware the is a whole range of Shelly Cloud servers so it could be you are just unlucky with your assigned server. Either way, I can not help you with this (and this is exactly why I wouldn’t recommend using cloud services to anyone that is serious about home automation.)
2 Likes
I understand that is hard to find a problem for that. But something changed definitely because yesterday around 16:00 I noticed that my smart house became completely dum. I don’t know if this is because of the app update, Homey update or Shelly cloud update.
Is possible to get a experimental version with reverted changes from 3 day ago?
The only recent change is the removal of old and deprecated cloud drivers and a change in the reconnect mechanism. But as you say you receive status updates and have repaired devices this can not be the issue.
As far as I know the only way to run different versions of Homey Cloud is by setting up a development environment.
I’ve read through the first post multiple times, but I cannot add a Shelly 1 to homey. Always the timeout.
Works fine in the Shelly app. There are no updates.
Factory reset Shelly.
Restarted homey
Restarted app
Removed device everywhere
Nothing…
After I re-add it to the Shelly app and cloud, there is no firmware update available.
Cannot add to homey.
Reboot shelly
Reboot homey
No change.
Manually adding device also give the timeout.
I don’t understand what I am doing wrong.
Am I just that stupid or?
Any help is appreciated.
3fdb174e-669b-4c03-95cc-24bb6dffdd44
Sending diagnostic reports for this kind of issue is pointless as it will just show that the requests made to the device fails what we already know.
Sound like a network configuration issue where the Shelly 1 is not in the same LAN as Homey. There are actually other networking errors in the log as well for devices with the following IP addresses:
- 192.168.5.167
- 192.168.5.80
- 192.168.5.125
If you have multiple access points try pairing when both Homey and the device are using the same access point. If that works you know where to start.
Thank you for your time. I was just trying to be as complete as possible.
It’s just very strange that it all worked just fine for years. Homey is 192.168.5.130.
.125 is the device I want to find in Homey (and works fine via Shelly App or cloud)
.167 is not a ip on my network (at this time)
.80 is not an ip on my network (at this time)
I will try to find a solution in the area you pointed out.
Thank you for your effort.
Edit: for some reason I now get passed the “white screen”… but I get a nicely formatted error message;
that something went wrong and that I most likely do not have the right firmware etc.
Back to rebooting both devices again.
I have added a Shelly 2 Dimmer module to my hall light and I have this to come on at dusk and dim to 27%. The light will then go off around 11pm or wherever I manually switch it off.
All ok so far.
When my wife want to switch the light on she wants it to be a maximum brightness, 100% however when it’s switched on via the light switch (momentary) and the light is off, it comes on at 27% and need to be manually dimmed up.
Is there a flow that I can use to set the brightness to 100% when manually switched on. I know this seems obvious but when I created a flow like
When - input 1 turned on
And -
Then - Dim to 100%
The light goes to 100% the instantly turns off.
I can’t figure it out.
I have a homey pro 2019 running 10.0.2 and the app is 3.22.8 thanks
The current firmware of the Homey Pro 2019 is 10.0.2. Don’t know if that is a problem.
Could you test two things.
- Add a 1 second delay in the then action before the dim to 100%;
- Dim to 99% instead of 100%
Let me know.
This works in as much that the light stays on when I add in a 1s delay
However when I press again to switch off it keeps coming back on.
Changing dim to 99% does the same.
Weird. Why are you using the input 1 turned on as trigger instead of the turned on / off trigger cards? What is the result using this as trigger card?
I don’t know what is wrong today but I can’t even do a diagnostic report. Is possible that this is somehow connected with the controlling of all Shelly devices that I still have?
