Unable to add to HomeKit

[vascott1]

Current Situation

Just got a NAS that supports docker. It is UGreen. I installed the container and it is working well. My old homebridge pi is powered off. I restored a backup of that to this version. From the Web UI I can control all of my devices. After removing the old bridge from HomeKit I am trying to add the new one and consistently get "Accessory Not Found"

I am new to Docker so am not sure what I would need to submit here for help. Sorry about that. I can say I took defaults all the way through and am set to Bridge for networking. When I go the Web UI for homebridge, I am using the "external" IP of the NAS. Same as I use for shares, etc and port is 46693.

I am sure this is something simple so forgive the docker newbie question.

Thanks!

Docker Config

I am not sure how to find this information.

Logs

No response

Host Operating System

UGreen NAS running UGOS (it's new)

Host Architecture

x86_64 / amd64

[NorthernMan54]

Do you have this flag set ? https://github.com/homebridge/docker-homebridge?tab=readme-ov-file#compatibility

[vascott1]

The solution was to put the container in “host” mode and not “bridge” I did that through the gui but might be the same thing. Got it working and it is great

Thanks :)

On Jun 19, 2024 at 10:30 AM, <Northern Man @.***)> wrote:

Do you have this flag set ? https://github.com/homebridge/docker-homebridge?tab=readme-ov-file#compatibility

— Reply to this email directly, view it on GitHub (https://github.com/homebridge/docker-homebridge/issues/566#issuecomment-2178859552), or unsubscribe (https://github.com/notifications/unsubscribe-auth/ALLAX23OYERDBD472LPVRSTZIGIW5AVCNFSM6AAAAABJQPZ2RCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZYHA2TSNJVGI). You are receiving this because you authored the thread.Message ID: @.***>

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been closed as no further activity has occurred.