HomeGenie Forum
General Category => Troubleshooting and Support => Topic started by: mp@etlsolutions.com on May 11, 2015, 12:32:22 PM
-
Hi HG Forum, I was wondering if anyone could help please?
I have HomeGenie successfully running on a Raspberry Pi 2, the Pi is also running minidlna on UDP:1900.
Even though I have not enabled the UPnP functionality of HG it is still starting three instances of the mono process all bound to 0.0.0.0:1900 which obviously conflicts with minidlna.
I did try the UPnP functionality of HG but it didn't work and kept starting multiple mono processes bound to 1900 (and other TCP ports) and kept adding more and more processes.
So until the UPnP is 'stable' I will have to stick with minidlna.
Any help/thoughts anyone as to how I stop HG from binding to UDP:1900?
Kind regards
Martin
-
HG by default use UPnP to announce itself as a discoverable service. It also provide the hg homepage url that can be so discovered and accessed from any UPnP/DLNA browser client.
Currently, the only way to disable this is by commenting the following like of code:
https://github.com/genielabs/HomeGenie/blob/master/HomeGenie/Service/HomeGenieService.cs#L222
Cheers,
g.
-
Perhaps a trick could be starting the minidlna application before HG.
Cheers,
g.
-
Hi Gene, thanks for the advice. I did start minidlna first and then HomeGenie afterwards but it still binds three mono processes to the same UDP:1900 port as minidlna is running on.
So I'd have to download the whole source and compile it myself for the change you suggest to work?
Thanks again
Martin