Hi everyone, I’m excited to share a new project: Device Pulse, a custom integration that helps you monitor network-connected devices (IP-based) and get full visibility and control over their online/offline status.
A visual timeline card that shows when each monitored device went offline or came back online — great for spotting connectivity patterns or intermittent issues over time.
A table view that shows all monitored devices with live status, last response time, ping failures, etc. Offers filtering and sorting, handy for quickly scanning network health — especially useful if you monitor many devices.
Thank you for sharing. This is a really useful project.
It’s excellent.
One question, since I installed I have noticed my H.A backup sizes are increasing considerably. I’m uncertain if it is linked but if it is, can I limit the database use of this integration ?
Thank you !
Regarding your issue, I don’t think it is related, unless you have a very large number of devices under monitoring, you have configured a very fast ping interval (e.g. every 10 seconds), and you have enabled secondary sensors, such as those related to ping response time. With some additional information, it would be possible to understand it better.
Well presented and easy to set up - thank you. I’m not getting anything on the timeline card, however. Installed through HACS - do I need to do anything else to get it going or does something actually have to go offline?
this project/solution is great.
I have installed it and it`s really nice!
Ihave installed via HACS Device Pulse and the Timeline Card (not the Table Card-not needed by me).
What makes me wondering:
Even that most devices were detected, some additionally added manually by me, these devices are not shown-even if they are online.
Is there a reason why?
Thank you in advance and have a nice day.
Thank you for your kind words and for appreciating the project.
Regarding your question: the Timeline Card is designed to display events only. This means it shows devices when there is a state change (for example, from offline to online or vice versa). If a device has remained continuously online since the initial configuration, no event is generated, and therefore it does not appear in the timeline.
@pdn Thank you for this great integration! Do you know what the default ping timeout response is before a ping would fail and the byte size packet of the ping that is being sent each time? I am getting some ping failures with the integration, but when I ping the same device from a Windows machine, I am not. I think Windows defaults to a ping timeout of 4000ms and byte size packet of 32.
Do you know what the default ping timeout response is before a ping would fail and the byte size packet of the ping that is being sent each time?
Hi @zakrzep, and thank you for appreciating the project.
The integration under the hood uses the ping integration provided by Home Assistant, which has a fixed timeout of 1 second. I have no info about the packet size, but it is probably the same.
@pdn Yes, That was my problem. I had it configured for 3 pings, every 10 seconds and I was getting failures. When I was comparing the pings in Windows, I did not see that because it defaults to 4000 ms. I have since changed to 30 seconds between pings. Not sure if you could add another option for timeout ms? I also need to find out why some devices take so long to respond!
Changing the interval to 30 seconds doesn’t really help. The real issue is that some devices take too long to respond, so the request times out anyway.
Unfortunately, the timeout value is hardcoded in the original ping integration, and I don’t have a way to expose it as a configurable parameter.
That said, for a future version, I’m already planning to remove the dependency on the ping integration, which would allow me to manage the timeout setting as well.
Feel free to open an issue in the repository so we can keep track of the problem.
What Device Pulse does
UI: Timeline & Table cards for visibility
