Homebridge widget not showing up

[angelflames1337]

Description

The parameter of homebridge not showing up, only the title bar.

It was working all well before. When I clicked the widget it opened the homebridge page just fine.

homepage version

v0.8.13

Installation method

Docker

Configuration

- Homebridge:
        icon: https://cdn.jsdelivr.net/gh/walkxcode/dashboard-icons/png/homebridge.png
        href: http://192.168.1.70:8581
        description: homekit third-party bridge
        widget:
            type: homebridge
            url: http://192.168.1.70:8581
            username: admin
            password:

Container Logs

No response

Browser Logs

No response

Troubleshooting

ping from homepage docker

/app # ping 192.168.1.70
PING 192.168.1.70 (192.168.1.70): 56 data bytes
64 bytes from 192.168.1.70: seq=0 ttl=63 time=0.238 ms
64 bytes from 192.168.1.70: seq=1 ttl=63 time=0.339 ms
64 bytes from 192.168.1.70: seq=2 ttl=63 time=0.387 ms
64 bytes from 192.168.1.70: seq=3 ttl=63 time=0.253 ms
64 bytes from 192.168.1.70: seq=4 ttl=63 time=0.253 ms
^C
--- 192.168.1.70 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.238/0.294/0.387 ms

curl output

/app # curl -L -k http://192.168.1.70:8581

<title>Homebridge</title> <style>@charset "UTF-8";:root{--fa-style-family-classic:"Font Awesome 6 Free";--fa-font-solid:normal 900 1em/1 "Font Awesome 6 Free"}@font-face{font-family:"Font Awesome 6 Free";font-style:normal;font-weight:900;font-display:block;src:url(fa-solid-900.0b0cc8a6df2a4fc7.woff2) format("woff2"),url(fa-solid-900.69d3141ae4b2f721.ttf) format("truetype")}:root{--fa-style-family-classic:"Font Awesome 6 Free";--fa-font-regular:normal 400 1em/1 "Font Awesome 6 Free"}@font-face{font-family:"Font Awesome 6 Free";font-style:normal;font-weight:400;font-display:block;src:url(fa-regular-400.3ccdbd3d093918cb.woff2) format("woff2"),url(fa-regular-400.81482cd4d93fbfd4.ttf) format("truetype")}:root{--fa-style-family-brands:"Font Awesome 6 Brands";--fa-font-brands:normal 400 1em/1 "Font Awesome 6 Brands"}@font-face{font-family:"Font Awesome 6 Brands";font-style:normal;font-weight:400;font-display:block;src:url(fa-brands-400.87587a681474fe69.woff2) format("woff2"),url(fa-brands-400.5d18d427c08f12c3.ttf) format("truetype")}:root{--blue:#007bff;--indigo:#6610f2;--purple:#6f42c1;--pink:#e83e8c;--red:#dc3545;--orange:#fd7e14;--yellow:#ffc107;--green:#28a745;--teal:#20c997;--cyan:#17a2b8;--white:#fff;--gray:#6c757d;--gray-dark:#343a40;--primary:#007bff;--secondary:#6c757d;--success:#28a745;--info:#17a2b8;--warning:#ffc107;--danger:#dc3545;--light:#f8f9fa;--dark:#343a40;--breakpoint-xs:0;--breakpoint-sm:576px;--breakpoint-md:768px;--breakpoint-lg:992px;--breakpoint-xl:1200px;--font-family-sans-serif:-apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, "Noto Sans", "Liberation Sans", sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Noto Color Emoji";--font-family-monospace:SFMono-Regular, Menlo, Monaco, Consolas, "Liberation Mono", "Courier New", monospace}*,*:before,*:after{box-sizing:border-box}html{font-family:sans-serif;line-height:1.15;-webkit-text-size-adjust:100%;-webkit-tap-highlight-color:rgba(0,0,0,0)}body{margin:0;font-family:-apple-system,BlinkMacSystemFont,Segoe UI,Roboto,Helvetica Neue,Arial,Noto Sans,Liberation Sans,sans-serif,"Apple Color Emoji","Segoe UI Emoji",Segoe UI Symbol,"Noto Color Emoji";font-size:1rem;font-weight:400;line-height:1.5;color:#212529;text-align:left;background-color:#fff}@media print{*,*:before,*:after{text-shadow:none!important;box-shadow:none!important}@page{size:a3}body{min-width:992px!important}}body{font-family:Roboto,sans-serif;font-weight:300}html,body{height:100%;-webkit-font-smoothing:subpixel-antialiased}body{background-color:#f4f4f4}.body-top-padding{padding-top:5.5rem}</style> <script src="runtime.0549e309ba4e2c8f.js" type="module" crossorigin="use-credentials"></script><script src="polyfills.985044b7a7399140.js" type="module" crossorigin="use-credentials"></script><script src="scripts.a3c9ccae4e478a7d.js" defer crossorigin="use-credentials"></script><script src="main.7a9f559cced839a8.js" type="module" crossorigin="use-credentials"></script>

[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 that the Homebridge widget on your homepage is not displaying correctly, showing only the title bar and not the expected content. Since you have confirmed that the homepage installation can connect to the Homebridge service via ping and curl commands, the issue does not appear to be network-related.

Given that the widget was working before, and considering the configuration you've provided, there are a few potential causes for this issue:

1. Authentication Issue: The password field in your configuration is empty. If Homebridge requires authentication, ensure that you provide the correct username and password.

2. API Error: The Homebridge API provided by the Config UI X plugin may be returning an error. You can check the API response by accessing the Homebridge API directly through the browser or using a tool like curl.

3. Widget Configuration: Ensure that the widget configuration in your YAML file is correct. According to the documentation, the allowed fields for the Homebridge widget are ["updates", "child_bridges"]. If you have additional fields or incorrect configuration, it may cause the widget to not display properly.

4. Homepage Version: Ensure that you are running the latest version of the homepage. If not, consider updating to the latest version as it may contain bug fixes that resolve your issue.

5. Browser Cache: Sometimes, browser caching can cause issues with loading updated content. Try clearing your browser cache or using an incognito window to see if the issue persists.

6. Homepage Logs: Check the logs of the homepage container for any errors that might indicate what the issue is. You can view the logs by running docker logs homepage in your terminal.

7. Homebridge Plugin Compatibility: Verify that the version of the Config UI X plugin is compatible with your version of Homebridge and that it is properly configured.

If none of these steps resolve the issue, you may want to reach out to the homepage community for further assistance or file a bug report with detailed information about your setup and the steps you've taken to troubleshoot.

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.

[github-actions[bot]]

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.