Smart life routing problem

[legacy1]

Smart devices by Smart life App can not be controlled over VM network 

C:\tracetcp_v1.0.3>tracert 34.251.67.249

Tracing route to ec2-34-251-67-249.eu-west-1.compute.amazonaws.com [34.251.67.249]
over a maximum of 30 hops:

1 8 ms 6 ms 8 ms 10.112.32.133
2 10 ms 10 ms 8 ms basl-core-2b-ae63-650.network.virginmedia.net [80.1.81.185]
3 * * * Request timed out.
4 13 ms 13 ms 13 ms nrth-ic-3-ae0-0.network.virginmedia.net [62.253.174.78]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

[legacy1]

Ok some somewhat interesting I hardcore the firewall for my  Smart devices where I did not include TCP port 8886 so now its using that but still with the UDP 21120 from these Smart devices so looks like it starts off as TCP then tries UDP which seem to be down so it fails back to TCP... 

[Tudor]

A trace route to both IP address and URL give up after 6 hops on my non-VM ISP connection. 

[legacy1]

Looking at it again the UDP is from smart meter I guess it just send data one way so smart devices are by TCP