OpenWRT Widget - cpuLoad not correctly formatted #3306
Replies: 4 comments
-
Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course! Thanks for using Homepage! ❤️ To display the CPU load from the OpenWRT widget correctly, you should divide the integer values you're getting by 65536.0 and then round the result to two decimal places. This conversion is necessary because the load averages provided by OpenWRT are in a fixed-point format that needs to be converted to a floating-point format to be understood as the familiar load averages. If you need further assistance on how to implement this change in the widget or if you have any other questions, please let me know! This comment was generated by Glime. |
Beta Was this translation helpful? Give feedback.
-
Fixed it here #3576 |
Beta Was this translation helpful? Give feedback.
-
This discussion has been automatically closed due to lack of community support. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
-
This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
-
Description
Should be a simple fix, the current CPU Load from the OpenWRT widget is displayed as an Integer.
However, according to docs here:
https://openwrt.org/docs/techref/ubus
Other
No response
Beta Was this translation helpful? Give feedback.
All reactions