I read this entire thread and I’m having exactly the same problems.
I noticed that most of them happened after updating the app. And I don’t know if it’s related to the new firmware 15 of the station recently. With the update 14 of the hubs, most of the problems were temporary. Before everything was normal.
I have many wifi products (local and cloud), matter, zigbee and thread. Most of them are zigbee products via matter tuya bridge.
The problems are in smartthings, because via homekit also via matter, the devices work normally. Today I have:
Aetoec Hub and Smartthings Station (in a group) - Zigbee devices and some Matter
Smartthings V3 Hub - Matter devices, Wifi (local) and Matter over Wifi
Hub TV QLED 2025 Matter and Zigbee (only on the network)
Hub TV The Frame 2023 only Matter (some Matter devices over Wifi)
The Aeotec hub has Softlimit, but that was recently, I believe that due to the inclusion of the station, if it is better to remove the station from the group, I can do it easily.
I think it is going back and forth, because when it restarted, I also saw “ok” but when I replied to you, it was in “softlimit”. Let’s see how your hub behaves but that would be a different error.
The status changing in the app and automations triggered when they’re not supposed to?
Is it also for all the device types and not only hub connected?
Does it happen for all the capabilities of the devices?
If you do, please share the following info:
Which OS are you using?
If it’s iOS as well, follow these steps:
First:
Enable the creation of additional logs in the app:
In the ST app, go to “menu” > “settings”.
At the bottom of that page, you’ll find a section called “Troubleshooting”. Please, enable the option that says “Create Additional SmartThings Log”.
Restart the app
Then:
Replicate the issue while recording the screen. Since we’ll see the timestamp in the video we only need to know your timezone so we can track the events in the Cloud logs, please
In the app menu, go to “contact us”
Then, tap on “Error reports”
On the opened page, tap 10 times on the title/label “What is the error about?” or until the prompt to create a log appears.
Click on “ok” and wait for the process to finish. Then, save the generated file in the place you prefer and share it with us in the same email you sent to build@smartthings.com
Sorry for not replying earlier. I created a report for the engineering team since I could see that:
It appears you’ve recently changed the configuration, correct? I only saw if “Fan” is OFF and “DR1” is ON, then turn “DR1” OFF
And something curious is that the property that identifies something as a precondition, which is called “trigger” should have been set to “Never” but it’s configured as “Always”. When this happens, both conditions can trigger the event.
I recently updated a Routine to have one precondition, and the trigger was assigned properly. So, I’m wondering if this is only due to the trigger value. Could you create another Routine setting the precondition as well to see if it gets assigned correctly, please?
Is it happening with all your routines?
Yes, I changed it, trying to see if I could find a work around — I couldn’t. Have restored it to its previous configuration.
Ok, sure… but that doesn’t really speak to why, ~1/2 of the time, the event doesn’t trigger when both conditions are true (as in the recording I sent).
Done. I crested very similar routine called “DR2 Turn Off.” It behaves exactly like the routine in the recording.
And yes, this is happening with every routine and every device.
So it seems pretty clearly to be caused / related to the device status flipping I’ve been pointing to. Is there any progress in figuring out what’s causing that?
Or per @orangebucket earlier, is there any way you could try connecting me to a different server(s)?
Just to jump in, someone else has been seeing a similar issue with the API intermingling correct current attribute statuses with incorrect ones time stamped thirty minutes or so previously (*). If their testing/reporting methodology was correct it would appear that both the correct and outdated statuses were being seen on each of the servers in the pool.
(*) I am unclear if the incorrect ones correspond with a previous attribute change.
I also note that I wasn’t aware of issues with Rules at the time of my earlier speculation.
It’s been over a week now and everything is still broken!!
Is there any chance that this will get resolved in the foreseeable future or are you just telling me to abandon the platform because this is really becoming untenable…
Hi, @jghoffer. Sorry for the delay.
As I mentioned before, I created a report for the engineering team. This behavior is strange and needs further investigation, which the team is already doing.
For now, I would like to check if the same happens when instead of using a condition as “precondition” you add both conditions and then select the option “When all conditions below are met”, this is just a test to see if there’s an alternative.
I appreciate you created a report… any sense of how long it might be before that report turns into any sort of action?
Please forgive my obvious frustration, but like I’ve been trying to emphasize for a week now, this error of yours has completely wrecked the functioning of our house!
We collected useful data from the other case that was similar to yours. The engineering team made a change that should solve the issue, can you check if your case was solved as well, please?