8000 Sensor attributes do not update while sensor value does not change? · Issue #122 · meichthys/uptime_kuma · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Sensor attributes do not update while sensor value does not change? #122

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
edgarmaloverian opened this issue Jan 25, 2025 · 6 comments · Fixed by #128
Closed

Sensor attributes do not update while sensor value does not change? #122

edgarmaloverian opened this issue Jan 25, 2025 · 6 comments · Fixed by #128

Comments

@edgarmaloverian
Copy link

Hi, trying to build network latency graphs, and create helpers like that:
{{ state_attr("sensor.uptimekuma_cloudflare","monitor_response_time")}} where cloudflare is ping check.
what I noticed is that state attribute gets updated only on integration reload or sensor value change, which does not seem sane to me :)

Is it by design, and if yes, is there any way to override it to achieve my goals?
@edgarmaloverian edgarmaloverian changed the title Sensor attributes do not update while sensor binary value does not change? Sensor attributes do not update while sensor value does not change? Jan 25, 2025
@TheRealFalseReality
Copy link

Agreed, wanted the ping to be updated regulalry

@Gatses
Copy link
Gatses commented Mar 26, 2025 •
edited
Loading

I caught the same thing on "Monitor cert days remaining" and "Monitor response time".
It looks like the values are not updated themselves without restarting the integration.

@Gatses
Copy link
8000 Gatses commented Mar 28, 2025

Unfortunately, the data is not updated on its own:

Image
Image

@cryptobench
Copy link
Contributor

@Gatses @edgarmaloverian @TheRealFalseReality I made a fork and did some AI magic and got it working. You can add a custom repo that points to mine here https://github.com/cryptobench/uptime_kuma

@meichthys
Copy link
Owner

@cryptobench
If you don't mind, could you submit a pull reeust?
I'd be glad to look it over and see if it can be merged in.

@Gatses
Copy link
Gatses commented Apr 22, 2025

@Gatses @edgarmaloverian @TheRealFalseReality I made a fork and did some AI magic and got it working. You can add a custom repo that points to mine here https://github.com/cryptobench/uptime_kuma

Now the data is updated independently, thank you!

@meichthys meichthys mentioned this issue May 8, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update attributes over time cryptobench/uptime_kuma
5 participants
@edgarmaloverian @meichthys @Gatses @cryptobench @TheRealFalseReality
0