just installed the new version, and it doesn t work for me :/
1 / still damn boring deps like dprovider ... (i hate native modules)
2 / the server start normally with all my config but it s not detected when i scan the network
description is ok on 192.168.2.145.. what can i check to know why the server is not detected ? (since i don t need a ssdpServer i now use the new "renderer-finder" module as client to scan the network so i can remove this damn node-ssdp and it work s very well)
i had to change the ST parameter to ssdp:all... renderer-finder only server mediaRenderer by default, so now it s detected but still not working (my fault ...)
ola olivier
just installed the new version, and it doesn t work for me :/
1 / still damn boring deps like dprovider ... (i hate native modules) 2 / the server start normally with all my config but it s not detected when i scan the network
is it normal :
ssdpServer: SsdpServer_adInterval: 10000_adLoopInterval: Timeout_events: Object_location: "http://192.168.2.145:4747/DeviceDescription.xml"_logger: Logger_maxListeners: undefined_socketBound: true_ssdpIp: "239.255.255.250"_ssdpPort: 1900_ssdpServerHost: "239.255.255.250:1900"_ssdpSig: "node.js/1.2.0 UPnP/1.1 node-ssdp/2.2.1"_ssdpTtl: 1_started: true_ttl: 1800_udn: "uuid:e0bf7adf-7429-4a8a-961f-0a99f17e9f99"_unicastHost: "0.0.0.0"
description is ok on 192.168.2.145.. what can i check to know why the server is not detected ? (since i don t need a ssdpServer i now use the new "renderer-finder" module as client to scan the network so i can remove this damn node-ssdp and it work s very well)
an idear ?