Events not firing? (Mostly motion detection)


#1

1) Give a description of the problem
For the last several days, i’m having issues with events not firing. Most commonly it’s Motion == Inactive. SmartThings displays my motion sensors as “No Motion” and reports them switching to inactive in “Recently”, but the piston is not picking up that event, and therefore my lights never turn off. This issue is intermittent, but is occurs fairly regularly throughout the day (4-5 times a day in both bathrooms). Is there a current known issue on either the WC or ST side, or a workaround?

EDIT: More info - i caught the error in the ST live log, it’s pasted below. Does anyone know how to resolve this? Seems like it may be a connectivity issue on the Samsung side (surprise surprise), but not 100% sure.

85213610-8a28-4465-9bee-d8731530bb33 8:33:42 PM: error org.springframework.jdbc.UncategorizedSQLException: Hibernate operation: could not execute query; uncategorized SQLException for SQL [select this_.id as id54_0_, this_.version as version54_0_, this_.date_created as date3_54_0_, this_.`key` as key4_54_0_, this_.type as type54_0_, this_.value as value54_0_ from server_config this_ where this_.`key`=?]; SQL state [null]; error code [0]; [SimpleAsyncTaskExecutor-75] Timeout: Pool empty. Unable to fetch a connection in 30 seconds, none available[size:50; busy:0; idle:0; lastwait:30000].; nested exception is org.apache.tomcat.jdbc.pool.PoolExhaustedException: [SimpleAsyncTaskExecutor-75] Timeout: Pool empty. Unable to fetch a connection in 30 seconds, none available[size:50; busy:0; idle:0; lastwait:30000]. @line 1141 (processSchedules) 85213610-8a28-4465-9bee-d8731530bb33 8:33:12 PM: info ║ Setting up scheduled job for Mon, Oct 29 2018 @ 8:34:11 PM PDT (in 59.964s), with 4 more jobs pending 85213610-8a28-4465-9bee-d8731530bb33 8:33:12 PM: trace ║╔ Execution stage complete. (113ms) 85213610-8a28-4465-9bee-d8731530bb33 8:33:11 PM: trace ║╚ Execution stage started 85213610-8a28-4465-9bee-d8731530bb33 8:33:11 PM: trace ║ Runtime (58311 bytes) successfully initialized in 63ms (v0.3.108.20180906) (146ms) 85213610-8a28-4465-9bee-d8731530bb33 8:33:11 PM: info ╚ Received event [Bathroom Motion].motion = inactive with a delay of 547ms 85213610-8a28-4465-9bee-d8731530bb33 8:33:09 PM: error org.springframework.jdbc.UncategorizedSQLException: Hibernate operation: could not execute query; uncategorized SQLException for SQL [select this_.id as id56_0_, this_.version as version56_0_, this_.date_created as date3_56_0_, this_.`key` as key4_56_0_, this_.type as type56_0_, this_.value as value56_0_ from server_config this_ where this_.`key`=?]; SQL state [null]; error code [0]; [SimpleAsyncTaskExecutor-117] Timeout: Pool empty. Unable to fetch a connection in 30 seconds, none available[size:50; busy:3; idle:0; lastwait:30000].; nested exception is org.apache.tomcat.jdbc.pool.PoolExhaustedException: [SimpleAsyncTaskExecutor-117] Timeout: Pool empty. Unable to fetch a connection in 30 seconds, none available[size:50; busy:3; idle:0; lastwait:30000]. @line 1141 (processSchedules)

Below is a green snapshot of the piston, it’s been working fine for about 6 months without issue. Below that is a log snippet, you’ll see that there’s no event with motion changing to inactive - the ST app reported the motion sensor changing to No Motion at 11:05am, but there’s no corresponding event in the log.

10/29/2018, 11:07:08 AM +304ms
+1ms	╔Received event [Home].time = 1540836429640 with a delay of -1336ms
+319ms	║Runtime (58298 bytes) successfully initialized in 155ms (v0.3.108.20180906) (316ms)
+320ms	║╔Execution stage started
+454ms	║╚Execution stage complete. (134ms)
+457ms	╚Event processed successfully (456ms)
10/29/2018, 11:04:08 AM +111ms
+1ms	╔Received event [Bathroom Door].contact = open with a delay of 1046ms
+235ms	║Runtime (58300 bytes) successfully initialized in 135ms (v0.3.108.20180906) (232ms)
+236ms	║╔Execution stage started
+273ms	║║Executed virtual command setVariable (4ms)
+280ms	║║Executed virtual command setVariable (3ms)
+287ms	║║Executed virtual command setVariable (3ms)
+1269ms	║║Executed [Bathroom Light].on (974ms)
+1446ms	║║Executed [Bathroom Light].setLevel (154ms)
+1568ms	║║Executed virtual command setVariable (4ms)
+1575ms	║║Executed virtual command setVariable (3ms)
+1583ms	║║Executed virtual command setVariable (3ms)
+1598ms	║║-----====>>> POOPED: false
+1599ms	║║Executed virtual command log (2ms)
+1607ms	║║Executed virtual command setVariable (3ms)
+1614ms	║║Executed virtual command setVariable (3ms)
+1627ms	║║warnDelay: 900
+1628ms	║║Executed virtual command log (2ms)
+1640ms	║║offDelay: 1200
+1642ms	║║Executed virtual command log (1ms)
+1646ms	║╚Execution stage complete. (1410ms)
+1648ms	║Setting up scheduled job for Mon, Oct 29 2018 @ 11:07:09 AM PDT (in 179.882s)
+1659ms	╚Event processed successfully (1659ms)```

Webcore Missing Motion.inactive Messages
#2

@RobinWinbourne Do you possibly have any insights?


#3

Did you ever get a response it resolve this issue? I too am experiencing it.


#4

I just created another thread about this same issue and was directed here. Hopefully we can figure out if there is some common cause. My system was working fine for months until a few weeks ago. Now it is almost unusable. I’ve paused most of my pistons to avoid my electric bill going through the roof.


#5

See

And


#6

Are you and @ajstack22 both on na04-useast2?

When I submitted a ticket, they told me to try the forums :-(. Here I am.


#7

Post your experiences on the SmartThings forum I linked. They are reading that topic.


#8

I am on na04-useast2


#9

My friend is on USEast1 and doesn’t have these issues.


#10

Nope, don’t think there is much that can be done - It’s an issue that appears to be on the ST servers.

I finally had my last straw the day after xmas last week, when something caused ST to re-trigger a presence event that had already fired about 2 hours earlier, which in turn opened my garage door at 11pm. Between that and half my lights or fans frequently not turning off when they were supposed to, i finally had enough.

I’ve spent the last 3 days or so migrating over to Hubitat. It’s solid. Definitely an adjustment moving to Rule Machine from WebCore, but it’s at least reliable.


#11

I must admit, I have been thinking the same thing. You would think ST could issue a statement regarding these issues. I’m also surprised WC is not pressing the issue with ST, my apologies if they are, but please SOMEONE tell us what’s going on. As a software developer I have had several holidays ruined over the years because the company I worked for realized pissing off customers is bad business.