This is just a patch release, so no update to docker images.
To update, look for status change (can take upto an hour, or immediate after a restart).
Click Settings, expand Tools, and find Update now and select the update then click Save.
Thank you! That did the trickâŚand thank you again for creating the extension.
Good to know - thanks
Hi Adam,
I sent you the logs this week end. Tell me if you want more details 
Thanks
The thing that stands out from the logs as that I see no sign of the virtual docker networks, just a single ethernet interface. This means either is either running natively on your NAS (and docker isnt installed at all), or that the network mode in the docker container is not set to âhostâ which it must be.
I do not have a synology NAS, so I cannot give you exact instructions to navigate its UI to enable host network mode.
I expect you need to select the advanced settings view, then select the network tab, then somewhere in there you should find setting for the network mode. It needs to be set to âhostâ.
Synlogy docker information: https://www.synology.com/en-us/knowledgebase/DSM/help/Docker/docker_container
It doesnât look much different to the QNAP docker UI, so I expect this can be fixed by just changing the settings on the container and restarting it.
Once this is done, I suggest updating to the latest version.
Adam
Thank you for this, great extension! I love that I can control Roon and my Nu-Vista as one Activity.
Hello,
I hope someone can help me. I installed the extension a couple of months ago with the docker image on my Ubuntu 18.04 server. It never worked flawlessly for a extended period for me. It seemed that updating the docker image was the problem but I am not sure.
Now I canât get the extension to show up in Roon anymore. The container is running but the extension is not showing up in Roon. Restarting and reinstall in docker doesnât help anymore.
Anyone an idea?
Thanks in advance.
Joost
Which version are you running? Also are you able to extract and send me logs? (Ill PM you my email address). Also which docker version?
To extract logs, using chrome or safari (not MS edge) enter the url http://xxx.xxx.xxx.xxx:9080/logs where xxx.xxx.xxx.xxx is the IP address of the host runnign the extension and that shoudl download a zip file.
Hello Adam,
Thanks for your reply. Appeared not to be a problem with you extension.
Because the url you mentioned didnât work I started looking at the logs in docker and found an error with my network. Has something to do with setting up ipv6 I think. Did some tinkering and it is working again, but I am not that confident that it will stay that way with ipv6.
Thank you for your work on this great extension!
Cheers,
Joost
The extension actively avoids sending over IPv6 for the simple reason that I donât think Harmony supports IPv6 or at least Iâm sure its discover mechanism certainly does not.
I normally run this on my QNAP NAS which I think is running some older 17.x version of docker. OTOH I have also run it alot on my Raspbery PI with 18.x versions of docker without problem. I have never needed to fiddle with any settings in docker - just a default install of it.
Anyway - great to hear you have it working 
Hi everyone,
I have installed Deep Harmony on my Synology NAS using docker. Installation went fine, Roon found the extension without problems, but Deep Harmony can not find my Harmony Companion - status is âAwaiting HarmonyâŚâ. Iâve tried to restart my Harmony Companion, but that doesnât solve the problem.
Any suggestions how to solve this problem, will be very much appreciated!
Best regards, Jochem
Hi,
For the first time I stumbled upon the problem (with the extension) I canât resolve by myself.
I believe this is a known issue when upgrading from an old version.
Try pulling a new docker image using:
docker run --detach --restart unless-stopped --network host khazul/roon-extension-deep-harmony
Ah, now you have two images running. What do you get if you enter docker container ls and âdocker image lsâ?
The former lists registered containers, the latter lists pulled images (from which runnable containers are created).
I would remove both and pull it again.
this is what I get:
sp1976@xUbuntu-serwer:~$ sudo docker container ls
[sudo] hasĹo uĹźytkownika sp1976:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
fe10868885c4 khazul/roon-extension-deep-harmony â/usr/src/app/run.shâ 22 minutes ago Up 22 minutes dazzling_kare
8290f777cf9c khazul/roon-extension-deep-harmony â/usr/src/app/run.shâ 26 minutes ago Up 26 minutes quirky_euclid
2b5f6683fb0c khazul/roon-extension-deep-harmony â/usr/src/app/run.shâ 46 hours ago Up 46 hours jolly_visvesvaraya
f247d307f0f4 khazul/roon-extension-deep-harmony â/usr/src/app/run.shâ 46 hours ago Up 46 hours festive_davinci
39f1e3653077 khazul/roon-extension-deep-harmony â/usr/src/app/run.shâ 9 months ago Up 46 hours hardcore_hawking
sp1976@xUbuntu-serwer:~$ sudo docker image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
khazul/roon-extension-deep-harmony latest 3eb29a1844d5 13 months ago 115MB
hello-world latest 4ab4c602aa5e 13 months ago 1.84kB
sp1976@xUbuntu-serwer:~$
EDIT: Ok, I stopped and removed all containers than ran the:
Now I have the latest version 
Adam helped me resolve the same issue a few months ago, glad to be able to pass along the info and help you
@Larry_Post thank you so much.
Hello I feel a bit dim but can someone point me to instructions once its up and running?
IN other words I have it running and it sees my hub and I have ticked vsarious things for my activities
Now what? Whats supposed to happen?
Does your Harmony remote pause/play, skip/ff and skipback/rw work to control Roon?
