Unifi Controller - "Subsystem status unknown"

[Wxam]

Description

Dear reader,

I need a little help with the Unifi Controller, I've setup the unifi controller and added it into the services.yaml and the widgets.yaml

services.yaml

• Unifi Controller:
  description: Unifi building the future of IT
  icon: si-ubiquiti-#0559C9
  widget:
  type: unifi
  url: https://192.168.174.246:8443
  username: [e-mailadres]
  password: [Password]
  site: [site]
  server: localdocker
  container: unifi-controller

widgets.yaml

• unifi_console:
  url: https://192.168.174.246:8443
  username: [e-mailadres]
  password: [Password]
  site: [site]

I've already tried recreating the Unifi-Controller and I've rebooted the Homepage

homepage version

v.0.8.13

Installation method

Docker

Configuration

No response

Container Logs

No response

Browser Logs

No response

Troubleshooting

tried recreating the Unifi-Controller and I've rebooted the Homepage controller

[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 seems you have set up the Unifi Controller widget in both the services.yaml and widgets.yaml files for your Homepage installation. However, you are experiencing issues with it not functioning correctly.

Here are a few troubleshooting steps you can take:

1. Check URL and Port: Ensure that the URL and port in your configuration are correct. The default port for Unifi Controller is usually 8443, but it's important to verify that this is the port your Unifi Controller is configured to use.

2. Credentials: Double-check that the username and password are correct. Since you've mentioned using an email address as the username, ensure that this is indeed a valid username for the Unifi Controller and not just for the Ubiquiti account.

3. Site Parameter: Verify that the site parameter is correctly specified. If you're unsure of the site name, you can usually find it in the Unifi Controller web interface under the settings section.

4. API Error: If you are receiving an "API Error," it could be due to incorrect credentials or issues with the Unifi Controller API. Ensure that the account you're using has API access enabled.

5. Clear Cache: As mentioned in the documentation, if you enter incorrect credentials and receive an "API Error," you may need to recreate the container to clear the cache. Since you've already tried recreating the Unifi-Controller and rebooting the Homepage, ensure that the cache is indeed cleared.

6. HTTPS and SSL Certificate: If you are using https in the URL, ensure that the SSL certificate on the Unifi Controller is valid and trusted by the system where Homepage is running. If it's a self-signed certificate, you might need to add an exception or use http for testing purposes.

7. Firewall and Network Access: Make sure that the Docker container running Homepage has network access to the Unifi Controller. If they are on different networks or if there's a firewall in between, you may need to adjust the settings to allow communication.

8. Logs: Check the container logs for any error messages that could give you more information about what's going wrong. Since you did not provide any logs, it's difficult to diagnose the exact issue without them.

9. Documentation and Support: Review the documentation for any additional configuration steps or known issues. You can also seek help from the Homepage community or support channels.

If you continue to face issues, please provide more detailed error messages or logs, as they can be crucial in diagnosing the problem.

Remember to replace any sensitive information such as passwords or personal email addresses with placeholders when sharing your configuration for troubleshooting.

This comment was generated by Glime.

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.