still having the same issues. to refine the description, it appears routines are firing, but commands usually don’t make it to the devices. for example, when someone arrives home, sometimes location updates properly and the ‘name is home’ alert is received, indicating the routine fires, but the device actions such as unlocking door and turning on lights doesn’t happen
Hi, @jmcclellan
The engineering team made some changes to help with the situation.
Since you’re still seeing some inconsistencies, we need to investigate what’s going on. So please provide the following:
- Try to trigger one of these routines again and let us know its name
- Let us know the behavior observed. For example, it announced “x” was home and nothing else happened, or “only x command was sent”, or, commands weren’t received until 5 minutes later.
Include date and times of when you performed these tests to find the corresponding events in the logs - Then submit the hub logs as follows:
- In the Advanced Users app, enter the “Hubs” section
- Enter the corresponding Hub and click on “Dump Hub logs”
- Confirm the process by clicking on “Dump Hub logs” again in the pop-up.
- You’ll get a green box at the top confirming the Hub logs were requested.
Thanks. to be clear, the behaviour doesn’t seem to have changed at all - physical device control is intermittently non-function or severely delayed.
at 2:09pm today one of the presence detections worked, “, At Home” routine executed. the VPS device was turned on, the “ is home” notification was sent to phones, but none of the physical devices performed their actions.
also still cannot control physical devices through the app, and devices are randomly going offline/online
dumping logs now
just now, another “, at home” routine fired when someone else arrived home. the VPS switched on, notification received, physical devices did not respond. dumping logs again
the Front Door Lock actually locked at 4:57, ~3 minutes after I issued the command in the app, despite the error shown
What manufacturer and model is the lock?
It is a Schlage BE469 z-wave
This is just an example though, I’m seeing the same behaviour on a variety of other devices too like lights, sensors etc, it’s basically everything
Hi @nayelyz
I’m seeing a similar inconsistent behavior after update to v61.6
I have 5 Shelly Switches, with their Input States wired to an Open/Close Contact Sensor.
When the Contact Sensor Opens or Closes, I can see it’s Input Status in the Shelly App instantly.
However, the Input State in the SmartThings Device Card only updates intermittently/randomly. If I pull down/refresh the Device Card, the Input State updates to the current state.
It was rock-solid for at least the past two years until this firmware update.
I’ve Power-Cycled my entire network several times, including the SmartThings v2 Hub (with batteries removed :).
Shelly Plus1 Switches with their latest firmware; Fixed IP’s; Edge Driver is TAustin Driver Tests Alt Channel, Shelly Gen2/3 Device Driver V1.8
I had tried changing the Edge Driver and toggling back, but it didn’t help.
Any thoughts on other things to try? Is there another Shelly Gen2/3 Edge Driver you’re aware of?
I’m having the same issues, my V3 is a mess…
Hi, @JohnRichard
Just to clarify, you mentioned seeing the status in both the Shelly app and SmartThings of the same device. Does this mean that you’re using bridged devices?
Please open support access to your account and the name of some of these Shelly devices so we can take a look at their details.
- Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM
- Enable support access to your account:
- Go to the SmartThings Web (my.smartthings.com)
- Log in to your Samsung Account
- Select Menu (⋮) and choose Settings
- Toggle on Account Data Access
- Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.
See more information about this access here: https://support.smartthings.com/hc/en-us/articles/36170233944852-Enabling-Account-Data-Access-for-Support
Hi @nayelyz
I’m not using the Shelly to SmartThings Integration. I use the TAustin Edge Drivers in SmartThings, Scan for nearby devices, it finds them, so it has direct control from SmartThings. But when I click a SmartThings Device Card or if I click a device in the Shelly App, I can typically see it responding in both apps at the same time. Hope that makes sense 
Yes, email is the same. I turned on Access.
I’m going to DM you which Hub and Devices I see it happening with most often.
Thank you!
Hi, @JohnRichard
Thank you for the information. Checking your devices, I can see this is a LAN integration; this means it doesn’t support driver changes. Do they continue working randomly or not at all?
We’ve seen in the past that this type of device enters a weird state when a driver change is performed.
Can you replicate the issue and follow these steps to get the proper logs, please?
- Select one of the devices and trigger an event (you need to let us know which action you performed so we can compare what we see in the logs)
- Take note of the date and time and share it with us
- Check if the event is reflected after a while or if not at all and let us know what you observed. (If the event had a delay, share the timestamp on when it happened)
- Then, submit the hub logs so the events get uploaded to the server and the team can check them later:
- In the Advanced Users app, enter the “Hubs” section
- Enter the corresponding Hub and click on “Dump Hub logs”
- Confirm the process by clicking on “Dump Hub logs” again in the pop-up.
- You’ll get a green box at the top confirming the Hub logs were requested.
I already created a report for this but we need fresh logs for the investigation.
Yes, they are accessed from SmartThings by using TAustin’s Shelly Edge Drivers. They have Static IP’s and good signals.
Yes, I had tried it as a troubleshooting step, but found out quickly that it does not allow a driver change.
They continue to work through SmartThings. Pressing their On/Off Button typically provokes the desired/immediate action (i.e. opening the gate), but randomly (and frequently) do not report back their Input State (wired to an Open/Close Contact).
But to be clear, their Input States are reported/seen immediately in the Shelly App, and in the Shelly WebGUI (connected directly to the Shelly Switch via LAN IP)
As well, this behaviour just started after v61.6. Prior to that, there were no delays in the SmartThings App, nor a need to refresh the Device Card.
Absolutely!
Device: “Main Gate Switch” (used as example, but 4 other Switches behave the same way).
08:05:51am Trigger: Pressing SmartThings Switch Toggles/On Off (history is recorded in Shelly App)
Note State Shown in MySmartThingsAdvanced as “False”, while in Shelly WebGUI as “ON”
In Android/SmartThings App, pull down/refresh Device Card, then its State is updated in both the SmartThings App and MySmartThingsAdvanced shows State as “True”
Done… Got the “Green Box”
Please let me know if you have any other questions or thoughts!
Thanks!!!
Hi @nayelyz
I’ve done further troubleshooting on my end and can’t seem to pin this issue down on any of my Routers or Devices.
Any idea if the team has been able to investigate it further?
Thanks
I just asked them if they have seen anything about this.