[SOLVED] Hass traffic to Microsoft? What's it for?

1

Hi,

I recently noticed some traffic from my hass instance to Microsoft and was wondering what it is. I’m very concerned for my technology privacy and freedom in the digital world and don’t entirely trust Microsoft.

Here’s the traffic I’m curious about.

-->  netstat -an |grep 443 |grep EST
tcp        0      0 192.168.1.2:51502       40.71.237.168:443       ESTABLISHED
tcp        0      0 192.168.1.2:47174       40.71.237.172:443       ESTABLISHED

-->   lsof -i TCP:443
COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
hass    13426   ha   14u  inet 689995      0t0  TCP myhomeassistant:47174->40.71.237.172:https (ESTABLISHED)
hass    13426   ha   20u  inet 698589      0t0  TCP myhomeassistant:51502->40.71.237.168:https (ESTABLISHED)

A whois lookup on both 40.71.237.168 & 40.71.237.172 show they belong to Microsoft Corporation but nslookups on them both fail with this:

-->  nslookup 40.71.237.172
** server can't find 172.237.71.40.in-addr.arpa: NXDOMAIN
-->  nslookup 40.71.237.168
** server can't find 172.237.71.40.in-addr.arpa: NXDOMAIN

I can open a webpage to the addresses on port 443 but they both say this:

{
    "ReturnCode": "-99",
    "ErrorMessage": "please contact customer care, supportID: xxxxxxxxxxxxxxxxxxxx",
    "CorrelationId": ""
}
2

Are you using any cloud based integrations?
Do you have any custom components or addons installed?

Edit:
Looks like devices.myq-cloud.com resolves to that IP, and it is probably on Azure, which is why MS owns it

1 Like
3

Thanks Richie, you’re spot on! I am in fact using MyQ (grumbles at MyQ under his breath). How did you resolve the IP 40.71.237.172 to devices-east.myq-cloud.com? I tried the reverse lookup for 40.71.237.17 but it just came back with this:

** server can’t find 172.237.71.40.in-addr.arpa: NXDOMAIN"

Thanks for the insight.

4

dumb luck, I also use MyQ but do not have it integrated into HA, since I am using my security system instead to trigger a relay to activate the openers

1 Like