Hello, a small follow up - maybe this causes the problem? This shows the discovery of a specific upnp device, which is then refined. What makes me wonder is the proposed location which is wrong: Location: http://169.254.5.186:4009/gen-desc.xml If you look at the 2nd message which delivers me the event the ip address of the host is correct: HOST: 192.168.0.9
debug 20080801 08:08:51 bid#102 - at.smarthome.fhzupnprefiningdriver.FHZRefiningDriverImpl[FHZRefiningDriver match method called for DEVICE_CATEGORY: UPnP] info 20080801 08:08:51 bid#94 - [56;org.osgi.service.upnp.UPnPDevice] ServiceEvent REGISTERED debug 20080801 08:08:51 bid#102 - at.smarthome.fhzupnprefiningdriver.FHZRefiningDriverImpl[Matched device: uuid:AT-SM-FHZ1-dimmablelight1 of model type FHZDimmableLight] debug 20080801 08:08:51 bid#94 - [Importer] searching for UPnPEventListener debug 20080801 08:08:51 bid#102 - at.smarthome.fhzupnprefiningdriver.FHZRefiningDriverImpl[FHZRefiningDriver attach method called for DEVICE_CATEGORY: UPnP] info 20080801 08:08:51 bid#102 - at.smarthome.fhzupnprefiningdriver.FHZRefiningDriverImpl[Attaching to device with UDN: uuid:AT-SM-FHZ1-dimmablelight1 of model type FHZDimmableLight] debug 20080801 08:08:51 bid#102 - at.smarthome.fhzupnprefiningdriver.FHZRefiningDriverImpl[at.smarthome.fhzupn prefiningdriver 1.0 creating new DimmableLight Device] debug 20080801 08:08:51 bid#94 - [Importer] deviceSearchResponseReceived debug 20080801 08:08:51 bid#94 - ================REQUEST===================== HTTP/1.1 200 OK Content-Type: text/html; charset="utf-8" Server: Linux/2.6.20-17-generic UPnP/1.0 CyberDomo/1.8 Content-Length: 0 Cache-Control: max-age=1800 EXT: Date: Fri, 01 Aug 2008 08:05:56 GMT ST: upnp:rootdevice USN: uuid:AT-SM-FHZ1-S20_Switch4::upnp:rootdevice Location: http://169.254.5.186:4009/gen-desc.xml MYNAME: FHZDimmingSwitch -------------------------------------------- debug 20080801 08:08:51 bid#94 - Event::org.osgi.framework.ServiceEvent[source={org.osgi.service.upnp.UPnPEve ntListener}={upnp.filter=(UPnP.device.UDN=uuid:AT-SM-FHZ1-dimmablelight1), service.id=57}] debug 20080801 08:08:52 bid#94 - [Importer] httpRequestRecieved event debug 20080801 08:08:52 bid#94 - ================REQUEST===================== NOTIFY /evetSub HTTP/1.0 Content-Type: text/xml; charset="utf-8" HOST: 192.168.0.9 NT: upnp:event NTS: upnp:propchange SID: uuid:5cca-a11b-f11d-e0c2 SEQ: 0 Content-Length: 165 Connection: close <?xml version="1.0" encoding="utf-8"?> <propertyset xmlns:e="urn:schemas-upnp-org:event-1-0"> <property> <Status>off</Status> </property> </propertyset> -------------------------------------------- Kind regards, Daniel Felsing -----Ursprüngliche Nachricht----- Von: Daniel Felsing [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 01. August 2008 08:03 An: users@felix.apache.org Cc: 'Francesco Furfari'; 'Stefano "Kismet" Lenzi' Betreff: UPnP Basedriver 0.8.0 from felix - Devices get lost after a certain period of time...(basedriver locks up) Hello all, I already published that in another post but since it is a new topic / problem i summarise my architecture. I have 2 hosts A and B. Both are running UPnP Basedriver to access the upnp network. Host A acts as a upnp bridge to export X10 like devices (Switches, Motionsensors, Lights etc.) into the upnp network. Right now 19 devices get exported. I'm using the helper class UPnPEventNotifier there. Host B acts as a central server which imports and refines those devices (using a refining driver) using the base driver. The refined devices use UPnPSubscriber to subscribe to UPnP Events and get status updates of the devices. Host A and B are connected through a gigabit switch, so no wireless or anything other in between. After a random time - say 30-50 minutes - it often occur that devices just unregister and disappear. I refer to the topic of the domoware site since the guy there had a similiar problem and maybe mr lenzi and mr furfari can remember that: https://sourceforge.net/forum/forum.php?thread_id=1871253 <https://sourceforge.net/forum/forum.php?thread_id=1871253&forum_id=406095> &forum_id=406095 ok - the other guy was using devices that were not exported by the upnp basedriver.i'm only using devices that get exported by upnp base driver from felix. That's the difference. I tried the solution explained there to use the DriverController.search method to propagate msearches for all devices every 10 minutes. After 3 hours of operation doing that the basedriver on Host A (the bridge) begin to lockup. The devices all disappear and i get continous error messages by Cyberdomo saying "Too many files open". So to summarise my problem: a) The renewal of devices without m-search using the base-driver on both ends doesn't seem to work properly, since after some time devices disappear. (however all is working fine for some time) b) After doing m-searches the basedriver is getting unstable saying "too many files open" I really need help. Kind regards, Daniel Felsing --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
