Hack attempt?

💬 Lounge
1

Checking logs this morning...
Is this a hacking attempt? I have no cloud connection.
sys:12022-07-16 04:13:27.102 Received cloud request for App 5 that does not exist, path: /device/15 from 54.162.122.170

sys:12022-07-16 04:13:27.099 Received cloud request for App 5 that does not exist, path: /device/61 from 54.91.60.175

sys:12022-07-16 04:13:27.089 Received cloud request for App 5 that does not exist, path: /device/62 from 54.242.91.101

sys:12022-07-16 04:11:04.578 Received cloud request for App 5 that does not exist, path: /device/62 from 44.200.166.132

sys:12022-07-16 04:11:04.577 Received cloud request for App 5 that does not exist, path: /device/15 from 18.207.132.125

sys:12022-07-16 04:11:04.577 Received cloud request for App 5 that does not exist, path: /device/61 from 52.90.164.57

sys:12022-07-16 04:11:04.577 Received cloud request for App 5 that does not exist, path: /device/18 from 52.23.218.34

sys:12022-07-15 23:21:28.063 Received cloud request for App 5 that does not exist, path: /device/62 from 34.231.225.45

sys:12022-07-15 22:17:25.953 Received cloud request for App 5 that does not exist, path: /device/18 from 3.235.84.49

sys:12022-07-15 22:17:25.447 Received cloud request for App 5 that does not exist, path: /device/18 from 3.235.84.49

3

You likely had attempted to link your hub to a cloud service (that includes the Hubitat mobile app) and since then you removed the app, but didn't remove the IP address of your hub from the service, and the service is trying to communicate with the app that has since been removed. Identifying what service that might be, and removing the hub's IP will stop the errors.

4 Likes
4

Guessing from the device/## that App 5 may have been MakerApi…

2 Likes
5

I have never attempted to connect to the cloud. I've never wanted to.
Alexa maybe?
How do I identify App5?

6

something its also a webhook notifications but its definitely an integration.

1 Like
8

Did you install any built in integrations (like the alexa skill) and remove it?

2 Likes
9

MakerApi not installed.

10

Yes, lost Alexa Skill somehow and had to reinstall.
Actually, lost Hubitat Skill in Alexa somehow and had to reinstall.

1 Like
11

Likely that. Delete hubitat skill on alexa and the alexa skill on hubitat.... (btw Alexa is cloud based which is why it's sending you connection errors) Once done confirm on alexa that anything related to hubitat is gone. Reset everything back up. You should be good after that. I would also recommend that you set a DHCP reservation for both hubitat and your alexa speakers. This will ensure they always see eachother where they expect to see eachother.

I would also recommend Echo Speaks be installed on Hubitat so you can use the speakers for announcements.

7 Likes
12

Oooo o think I had this issue with Alexa a long time ago.

I suggest first removing the Alexa skill from you amazon account side and reinstalling it and relinking it.

1 Like
13

Thanks Rick.

I've tried to install Echo speaks, but must have skipped a step because it won't login.

I dropped it after a couple of attempts.

14

Make sure all popup blocking is disabled. Took me a few attempts too. You can post in the echo speaks v4 thread for help on that too

2 Likes