mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
How to monitor one device with multiple ip adresses #3477
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#3477
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @m4rtini2 on GitHub (Jul 13, 2024).
⚠️ Please verify that this question has NOT been raised before.
🛡️ Security Policy
📝 Describe your problem
Hello,
i can not make dhcp assign the same ip adress to different mac adresses of one device so to monitor such devices i have created a monitor for every device / interface. But this way i have long list with the same device once active and once not active most of the time. It is very seldom the lan and wlan interface are connected at the same time.
Is there a way to monitor a device with multiple interfaces like lan,wlan,bluetooth with one monitor?
Something like: Monitor Type: ping / Friendly Name: mediaplayer / Hostname: lan ip, wlan ip, bluetooth ip / fail if no response from any ip after x tries
I found the following posts, but none of them adresses my issue.
Is there a solution to this problem or is it planed?
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.13
💻 Operating System and Arch
debian 12
🌐 Browser
firefox
🖥️ Deployment Environment
Uptime kuma running in a lxc container on proxmox. Installed with the acording proxmox helper script.
@kaystrobach commented on GitHub (Aug 6, 2024):
Group them, once one in the group is down, the group is considered down.
@m4rtini2 commented on GitHub (Aug 27, 2024):
This is not a working solution. If one interface in this device group is down the whole group is shown as not accessible. Even if the device is still connected and working. So the group should display 'up'. With this configuration i have to open the group to see it is up. Also can't find an option to change that behaviour so i assume uptime kuma can't be used for this scenario.
Are there plans to add this feature?
@apio-sys commented on GitHub (Aug 27, 2024):
Your device could have a single resolvable name regardless of it's current IP address and as such you can consider it UP if you can ping your hostname no?
@m4rtini2 commented on GitHub (Aug 28, 2024):
That would work if you could get dhcp entries into dns automaticly but i am using pihole and it does not support this. One ip gets the correct name but the other ips get 'unknown'. I could manualy enter all the static dhcp records into the dns records but this is not maintainable with many devices.
Uptime kuma is just not the right tool for this scenario yet.
Thank you for your help.
@apio-sys commented on GitHub (Aug 28, 2024):
Indeed, UK is probably not the tool that you are looking for in your specific environment. @CommanderStorm I think you can close this issue here for now.
@DerJochen commented on GitHub (Dec 11, 2025):
I ran into the same problem with my laptop (LAN and WIFI). To solve it I created a group for the laptop with an inverted signal. Then I added both interfaces (also inverted) to the group.
This way, when all interfaces are down, they show green and the group turns it to red. If at least one interface is up, it shows as red. This would normally turn the group red, but inverted it now shows the laptop as "up".