Pi-Alert / NetAlertX widget

[adm2k]

Description

The widget does not seem to display any values for down alerts - all other values are correct:

I contacted jokob-sk/NetAlertX and was told the following "I'm not sure what api the widget is using. - please contact the developer of the Homepage application as I'm not the author of the plugin."

Can anyone help with this?

homepage version

0.8.13

Installation method

Docker

Configuration

No response

Container Logs

No response

Browser Logs

No response

Troubleshooting

None, not sure how to troubleshoot.

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

---

To troubleshoot the issue with the NetAlertX widget not displaying values for down alerts, you can follow these steps:

1. Check the API Output Directly: Use curl or another tool to directly access the NetAlertX API and see if the down alerts are being reported correctly. This will help determine if the issue is with the NetAlertX application or the widget itself.

2. Review the Widget Configuration: Ensure that the widget configuration in your Homepage setup does not have any errors and matches the allowed fields. According to the documentation, the allowed fields for NetAlertX are ["total", "connected", "new_devices", "down_alerts"].

3. Check for Trailing Slashes: As mentioned in the troubleshooting documentation, ensure that the URL in the widget configuration does not end with a trailing slash, as this can cause errors.

4. Verify Network Connectivity: Make sure that the Homepage installation can connect to the NetAlertX service. You can do this by pinging the service from within the Homepage Docker container.

5. Check Homepage Logs: Look at the logs for the Homepage Docker container to see if there are any error messages that could provide clues about the issue.

6. Browser Developer Tools: Use the network tab in your browser's developer tools to inspect the network requests made by the Homepage widget and the responses it receives.

7. Update Homepage: Ensure that you are running the latest version of Homepage, as there may have been updates or bug fixes related to the widget.

8. Seek Support: If you are unable to resolve the issue, you can seek support from the Homepage community. You can use the 'Ask AI' feature in the documentation, open a GitHub discussion, or check out the #ai-support channel on Discord.

If you need further assistance, please provide more details about your configuration, and any error messages you might be seeing in the container or browser logs.

This comment was generated by Glime.

[adm2k]

In response to the AI bot response, how do I do this? Where is the NetAlertX API?

Check the API Output Directly: Use curl or another tool to directly access the NetAlertX API and see if the down alerts are being reported correctly. This will help determine if the issue is with the NetAlertX application or the widget itself.

[shamoon]

Some important notes here:

1. This has not changed since the widget was added in Added PiAlert widget #1493 a year ago (with the note that they changed their name from pialer), so the only way this broke is if the API changed.
2. The API docs are super skimpy https://github.com/jokob-sk/NetAlertX/blob/main/docs/API.md so I have no idea what its supposed to return because it just returns an array of numbers eg [3,2,0,2,0,0]. Homepage uses the 5th item in that list, unadulterated, so assuming thats really 'down', then its accurate.
3. Instead of curl, in this case you can easily test this in your browser by going to e.g. http://localhost:20222/php/server/devices.php?action=getDevicesTotals

[shamoon]

Ah, I see jokob-sk/NetAlertX#680 (comment)

Next time might as well include a link if you've raised it at the relevant project. It seems homepage is just showing something different than the NetAlertX dashboard, you can open a FR to change that and if it seems to matter to a lot of folks we can change it, but again, been this way since it was added here.

[adm2k]

Well here is the latest on this topic. I took down one device and here is what I see:
[35,27,0,2,1,0] The "1" in position five indicates a "down" which is correct.

The Homepage widget shows "0"

Thoughts?

[adm2k]

Update....
After about 25 minutes this show up, now showing a value in down alerts!

[adm2k]

And yet one more update...

I brought the device I took down back online about 25 minutes ago. As you can see NetAlertX shows a "0" in position 5
[35,27,0,2,0,0]

Homepage still show as down...

I am at a loss, maybe someone with more technical abilities than me can determine what is going on.

Many thanks!

[shamoon]

Again, you can look in your browser network tab and see exactly the data homepage is using, its not doing anything to the number it gets.

[adm2k]

@shamoon

Thanks for the response. Since we all seem to agree the data is correct I guess the question is why there is a large delay in the time that NetAlertx "posts" the "Down" data and when the widget finally displays it (all the overall values seem to update quickly) . It has been up to 30 minutes at time. I guess it's better late than never!

You mentioned looking in the browser Network tab, my knowledge in reviewing this is limited. What am I looking for?

thanks!

[shamoon]

https://developer.chrome.com/docs/devtools/network#open

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details.