Closed jonwaland closed 3 weeks ago
Hi @jonwaland ,
I have the same issue, but I don't think that's something that can be fixed in the app. Maybe I'm wrong, but that's probably how Google implemented some of their discovery mechanism.
Not sure though. The thing is however I only consume the output from the scanners, so if e.g. ARPSCAN reports an address then that address gets stored.
I'll keep this open for a bit - Let's see if someone has an idea.
You can bock the IP if you want:
https://github.com/jokob-sk/NetAlertX/blob/main/docs/NOTIFICATIONS.md
Let me know what you think.
Thanks, j
TBH, I didn't think it was the app - its very much an ARP-SCAN and Google Home Hub interaction. Google device should not be responding on the broadcast address.
So what I want to do is just ignore IP Address changes for this device - it has a static IP - I still want to know if it is offline. What's the best way to do this?
You should be able to achieve this by unselecting "Alert All Events" and selecting "Alert Down". Let me know how to make the documentation clearer so it's more obvious in the descriptions and this article: https://github.com/jokob-sk/NetAlertX/blob/main/docs/NOTIFICATIONS.md
Let me know what you think.
Thanks, j
Ahh - I got that I can disable most of the notifications, I was also wondering about being able to block the actual events.
The notifications page is fine.
Is there an existing issue for this?
Current Behavior
Google Home hub keeps "appearing" to flip IP address, despite being statically allocated.
It seems ARP-SCAN thinks the device is on 192.168.1.255 - the broadcast address!
Expected Behavior
device doesn't get allocated .255 address
Steps To Reproduce
add a google home hub to the network. Set static IP. wait.
app.conf
docker-compose.yml
What branch are you running?
Production
app.log
log.txt
Debug enabled