I too am having issues with Zigbee devices. I have “Dump Hub logs” as instructed. This was done approximately 10:30 am EST. There are some device routines that either do not execute or have latency issues. I have two hubs, a ST v2 and an Aeotec hub. The devices affected are specific to my Aeotec Hub. Yesterday I had no routine response at times from my Family Room “Third Reality Motion Sensor” and the “Aqara Motion Sensor P1 1” in my Garage. There was no issue with the sensors. When I tested the routines they worked fine. The issue appeared to be cloud related. These sensors are working today. However I am now experiencing the same sort of issue with the routines that use my sensors in my Living Room. Specifically my Tapestry Presence Sensor Z1 1, Tapestry Presence Sensor Z1 2, LR Lamp, LR Lamp2. The routine is to turn the lamps on when presence is detected by either Tapestry sensor. The sensors are detecting presence but the routine does not execute. When testing the routine, it works fine. So again, it appears to be a cloud issue.
I have enabled support…
EDIT: I should add that the reason the routine is relying on the cloud is that the routine’s precondition specifies that it should only execute between the hours of 7:30 am and 11:00 pm. I have an associated routine that turns off the lamps when presence is no longer detected. This routine executes fine. The difference, there is no “Time” condition specified in the routine to turn the lamps OFF. So again, this appears to be a “Cloud” connection issue.
Hi, @Buds_Smart_Home
I moved your post since your description includes Routines, and we need to clarify the following:
Are your devices going offline or unresponsive when you send commands directly to them?
Or, are the routines the one that fail/have a delay but direct commands keep working?
If you only have issues with certain routines, I need their names so I can get their ID to create a report for the engineering team
Also, for failed/delayed executions, we need the following information:
Timestamps on when you tried to execute the routine even if it failed
If it ends up executing, share the timestamp on when this happened (You can also mention 10 minutes later, 20 seconds later, etc.)
The hub logs are helpful to check if the command was received by the hub and the timestamp.
So, since we don’t have information about this yet, we need your help to reproduce the error to collect the information requested and submit the hub logs again.
Also, I tried to enter your account with the email registered here in the forum but got an error saying the access is closed, so, please confirm the email is the one from your ST account, if not, please share it with me over DM.
I’m not sure what you are asking here… What do you mean by “direct commands”? The devices are working. If I edit the routine and tap the test button the routine executes fine, like it should. However the routine does not execute on it’s own. As an example, of presence is detected the routine does not turn the lamps on.
The routine name is “Living Room Lamps Turn ON if Tapestry status INSIDE”
I just went up to my living room and triggered presence on both Tapestry Presence sensor at 4:43 PM EST. Although both sensors detected my presence, the lamps did not turn on. There is no delayed response for this routine. It never executes.
You can probably make this run locally all the time as follows
Create a virtual switch “tapestry_switch”
Create a routine to turn it on at the start of the desired period and another to turn it off at the end of th desired period.
Then create a routine that checks for motion only when tapestry_switch is on. This should always run locally and not depend on cloud.
Since now I got access to your account, I submitted the hub logs which should contain the event at 4:43 PM EST.
Let me analize the other info provided to create the corresponding report. If I have more questions, I’ll let you know.
The Tapestry sensors are correctly responding to presence, and the Third Reality Night Light is reporting an illuminance value of 67 lux. Since the trigger condition is set to activate at or below 200 lux, both presence detection and illuminance readings are confirmed to be working properly. Given this, it appears the issue is related to the time-based component of the automation, which may indicate a communication failure between the hub and the SmartThings cloud.
I wanted to provide an update regarding the issue I reported with Zigbee routines failing to execute on my Aeotec hub. The problem appears to be resolved.
Prior to my last reply, I noticed that the Third Reality Night Light no longer displayed a lux value as it has done previously. I was using Mariano’s Zigbee Light Multifunction Mc driver. I then searched for and found a SmartThings Community post indicating that the Zigbee Switch driver from the Third Realty channel was a suitable alternative (reference link). After switching to the Third Realty driver, the illuminance value returned and I subsequently reported this value to you in my last reply.
I later realized this change may have resolved the issue with my living room routine. I entered my living room to test the routine and discovered that with the lux readings were restored, the routine executes normally again.
In summary, it appears the missing illuminance value prevented the routine from running correctly, rather than a cloud communication issue as initially suspected.