Glances plugin not working anymore since Glances changed their API

[stecydube]

Description

Glances plugin changed their API and calls result in an error:

Something went wrong: TypeError: S.find is not a function

homepage version

v0.8.13

Installation method

Docker

Configuration

- Network Usage:
      widget:
        type: glances
        url: https://glances.example.com
        metric: network:eth0

Container Logs

2024-05-14T13:09:05.373700342Z [2024-05-14T13:09:05.357Z] error: HTTP Error 404 calling https://glances.example.com/api/3/cpu
2024-05-14T13:09:05.439610141Z [2024-05-14T13:09:05.439Z] error: HTTP Error 404 calling https://glances.example.com/api/3/quicklook
2024-05-14T13:09:05.460195292Z [2024-05-14T13:09:05.459Z] error: HTTP Error 404 calling https://glances.example.com/api/3/network

Browser Logs

No response

Troubleshooting

None

[glime-ai[bot]]

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! ❤️

---

Based on the information provided, it appears that the Glances widget integration is not functioning correctly due to a recent update to the Glances API. The error messages in the container logs indicate that HTTP 404 errors are occurring when the Homepage application is attempting to call the Glances API endpoints.

To resolve this issue, you should first ensure that the Glances service is running and accessible at the URL specified in your configuration. If Glances has been updated to a new major version (such as from v3 to v4), the API endpoints may have changed, which would require updating the widget configuration to match the new API paths.

Here are some steps you can take to troubleshoot and potentially resolve the issue:

1. Verify that the Glances service is running and that you can access it directly via its URL.
2. Check the Glances documentation for any changes to the API endpoints and update your widget configuration accordingly.
3. Ensure that the version field in your widget configuration is set to the correct version of Glances that you are running. If you are running Glances v4 or higher, you need to specify version: 4 in your configuration.
4. If the API endpoints have indeed changed with the new version of Glances, you may need to wait for an update to the Homepage application that supports the new API paths, or you may need to modify the source code yourself if you have the capability.

If you have verified that the Glances service is running correctly and the issue persists, you may want to open an issue on the Homepage GitHub repository or join the discussion there to seek further assistance from the developers or the community.

This comment was generated by Glime.

[stecydube]

In response to the AI bot:

1. Service is running
2. Nothing to change in config
3. no such thing as a "version" config entry for that widget
4. 😐

[brhahlen]

It should become:

- Network Usage:
      widget:
        type: glances
        version: 4
        url: https://glances.example.com
        metric: network:eth0

It's also in the example here, but only in the first one

[shamoon]

3. no such thing as a "version" config entry for that widget

Please search : #3462 #3196, and read the manual: https://gethomepage.dev/latest/widgets/services/glances/

[stecydube]

Thank you.

I did a search and somehow I did get nothing. Odd.

Added the version string, saved and even had the container restarted and it still produced the error about v3...
Turned out the "save" didn't happen when editing from my synology UI. Did it from the terminal and now it works. 🤪