ChriD / Raumserver

Raumserver - A HTTP Request Server to control the RF-Multiroom System
32 stars 11 forks source link

Some UPNP devices say 'bye bye' only to come back again later #10

Closed ChriD closed 7 years ago

ChriD commented 8 years ago

Some UPNP devices say 'bye bye' only to come back again later. (They are not turned off) May be a problem in the UPNP-Stack or may be a problem on the UPNP Device itself

2016.04.28 18:43:13.763 DEBUG:    Refreshing UPNP device list [Raumkernel::Manager::UPNPManager::refreshDeviceListThread]
2016.04.28 18:43:18.768 DEBUG:    Refreshing UPNP device list [Raumkernel::Manager::UPNPManager::refreshDeviceListThread]
2016.04.28 18:43:22.343 DEBUG:    UPNP Device found: Universal Media Server(f880d5ef-c6ed-47c2-a1e1-5acd82b9eae1) [Raumkernel::Manager::UPNPManager::onDeviceFound]
2016.04.28 18:43:22.348 DEBUG:    Adding device 'Universal Media Server' to manager [Raumkernel::Manager::DeviceManager::addDevice]
2016.04.28 18:43:22.351 DEBUG:    Try to create device from device XML [Raumkernel::Devices::DeviceCreator::createDeviceFromDeviceXML]
2016.04.28 18:43:22.354 DEBUG:    Media Server device created (uuid:f880d5ef-c6ed-47c2-a1e1-5acd82b9eae1) [Raumkernel::Devices::DeviceCreator::createDeviceFromDeviceXML]
2016.04.28 18:43:22.359 DEBUG:    Create ContentDirectory-Proxy for media server uuid:f880d5ef-c6ed-47c2-a1e1-5acd82b9eae1 [Raumkernel::Devices::MediaServer::createProxies]
2016.04.28 18:43:22.366 DEBUG:    Create ConnectionManager-Proxy for media server uuid:f880d5ef-c6ed-47c2-a1e1-5acd82b9eae1 [Raumkernel::Devices::MediaServer::createProxies]
2016.04.28 18:43:22.373 DEBUG:    Media Server 'Universal Media Server' is now useable! [Raumkernel::Manager::DeviceManager::addDevice]
2016.04.28 18:43:23.772 DEBUG:    Refreshing UPNP device list [Raumkernel::Manager::UPNPManager::refreshDeviceListThread]
2016.04.28 18:43:28.777 DEBUG:    Refreshing UPNP device list [Raumkernel::Manager::UPNPManager::refreshDeviceListThread]
2016.04.28 18:43:33.781 DEBUG:    Refreshing UPNP device list [Raumkernel::Manager::UPNPManager::refreshDeviceListThread]
2016.04.28 18:43:38.785 DEBUG:    Refreshing UPNP device list [Raumkernel::Manager::UPNPManager::refreshDeviceListThread]
2016.04.28 18:43:42.784 DEBUG:    UPNP Device lost: Universal Media Server(f880d5ef-c6ed-47c2-a1e1-5acd82b9eae1) [Raumkernel::Manager::UPNPManager::onDeviceLost]
2016.04.28 18:43:42.789 DEBUG:    Removing device 'Universal Media Server' from manager [Raumkernel::Manager::DeviceManager::removeDevice]
2016.04.28 18:43:42.793 DEBUG:    UPNP device 'Universal Media Server' removed [Raumkernel::Manager::DeviceManager::removeDevice]
2016.04.28 18:43:42.797 DEBUG:    Media Server 'Universal Media Server' removed [Raumkernel::Manager::DeviceManager::removeDevice]
2016.04.28 18:43:43.789 DEBUG:    Refreshing UPNP device list [Raumkernel::Manager::UPNPManager::refreshDeviceListThread]
2016.04.28 18:43:48.794 DEBUG:    Refreshing UPNP device list [Raumkernel::Manager::UPNPManager::refreshDeviceListThread]
ChriD commented 8 years ago

i've updated the OhNet UPNP Stack to a recent version. We will see if this will do better...

ChriD commented 8 years ago

It seems that upgrading the upnp stack does not solve this problem Some user reported this problem when using a firefwall which blocks some udp ports. I have to investigate if this could be a problem.

ChriD commented 8 years ago

No update for this issue. On my system it works fine. I have to wait for other results from other users

ChriD commented 7 years ago

Closed due there where no further complains about this issue