Error with https get request

execution

#1

I have been using the AT_Presence Webcore/Smartthings/ActionTiles setup for nearly a year. Webcore backup bin code h6fo. Recently starting receiving the following error for the https get requests which stores the data on my server.

Error executing external web request: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

I can manually enter the URL successfully and update the database. I have seperate pistons for my 4 family members, each has the error. I do not believe this is a piston code error, but a webcore functionality error. My host is hostgator, and my HTTPS cert is up to date. Thanks for any incite!


#2

Do you want to post the piston screen shot and logs?


#3

Error:

+0ms ╔Received event [Home].test = 1584301051159 with a delay of 2ms
+104ms ║RunTime Analysis CS > 25ms > PS > 41ms > PE > 38ms > CE
+107ms ║Runtime (42373 bytes) successfully initialized in 41ms (v0.3.110.20191009) (106ms)
+108ms ║╔Execution stage started
+358ms ║║Comparison (string) Home is_any_of (string) Home, ACE, Middle School, Elementary 2, LCMR, Grandma and Pops, Library, Farm Market, Stone Harbor = true (2ms)
+360ms ║║Condition #32 evaluated true (246ms)
+367ms ║║Comparison (string) Home is_not (string) Away = true (1ms)
+369ms ║║Condition #52 evaluated true (8ms)
+370ms ║║Condition group #30 evaluated true (state did not change) (257ms)
+372ms ║║Cancelling statement #9’s schedules…
+380ms ║║Executed virtual command setVariable (3ms)
+388ms ║║Executed virtual command setVariable (3ms)
+405ms ║║Sending external web request to: REMOVED
+552ms ║║Error executing external web request: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
+553ms ║║Executed virtual command httpRequest (158ms)
+557ms ║║Cancelling statement #35’s schedules…
+559ms ║╚Execution stage complete. (451ms)
+628ms ╚Event processed successfully (628ms)

#4

I invited you to the beta tester group in this forum because there are fairly significant changes to web requests in the next release and on the new code I did not receive the same error attempting to hit that URL. Feel free to give it a try; there are instructions in the latest post in the ST Beta category. It would be great to have more testing.


#5

Awesome, will do thanks for the invite.


#6

In addition to the webcore fix you are testing, You likely could simplify this somewhat by use presence sensor changes as the trigger (vs conditions as the trigger). This should remove the perception of duplicates if a timer fires vs. the trigger changes.

You also have the option on your wait block to make TCP disabled…

Others may have more thoughts on this…


#7

Thanks for the code advice @E_Sch, I’ll give it a try, much appreciated.