wdhille Posted January 23, 2021 Posted January 23, 2021 I've been chasing down issues with my Z-Wave locks. It's been horrible. It was suggested I look at the error logs, which I hadn't done previously. For some reason, my ISY error log has the IP address of my Pixel phone popping up. So, I took the phone off DHCP and assigned a static IP address to it. IT still follows it... Mind you the ISY and Wi-Fi are on VLAN isolated subnets, which might be why I see this error. But.... More importantly, I have disabled (force stop) Agave, and this is a new ISY I'm using. Other than Chinese hackers, anyone have any ideas? This is with a static IP address I put in this morning at 7:30 AM. This error does not show up unless my phone is using Wi-Fi. xmlns:u= Sat 2021/01/23 04:18:38 PM System -170001 [HTTP:0-31-5] 192.168.10.137:53027->80 Sat 2021/01/23 04:18:38 PM System -170001 [HTTP:0-31]: POST[1]-->/services Sat 2021/01/23 04:18:38 PM System -170001 <s:Envelope><s:Body><u:GetSystemStatus This is yesterday with a DHCP address assigned by the Firewall/Router. xmlns:u= Fri 2021/01/22 06:45:06 PM System -170001 [HTTP:0-27-5] 192.168.10.27:52606->80 Fri 2021/01/22 06:45:06 PM System -170001 [HTTP:0-27]: POST[1]-->/services Fri 2021/01/22 06:45:06 PM System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u=
Michel Kohanim Posted January 24, 2021 Posted January 24, 2021 @wdhille, I already responded to your ticket. For your reference: If you open the Event Viewer and change the Level to 3, then ISY logs the source address/port and the local ISY Port. This is specifically there so that you can see whether or not anyone is hacking you. In your case, no one is. It’s your phone/mobile app talking to ISY. With kind regards, Michel
Recommended Posts