console device status does not update

server 1.6.1. pro. windows 10.
when I connect from a new client - a new tablet - it does not appear in list of devices recently connected. it streams OK o that device, so connection exists!
but I cannot force status screen to update. it shows many devices no longer connected but not the new one.
tried stop start server, stop /start service.

also tried: gave the client a static address to make it easy to see in the list - no joy.

UPDATE - this may occor when the device connects via the SERViIGO app, only ?

I rebooted my router - no change - then I tried changing browser and also chaning client to Bubbleupnp, and one/both of those caused my device to show up

I was told by servigo author that this app uses a different api to connect, so is it s bug or a feature that such conenctions do not appear in the list ?
still there are many - no longer conencted, unrecognised devices on my console device list - maybe every smart phone that's been in range for tha last week or so ???

e.g.
These are the devices that have recently been connected to Serviio.

...

 192.168.0.10 Unrecognized device Generic DLNA profile
Edit

 192.168.0.11 Unrecognized device Generic DLNA profile
Edit

 192.168.0.13 Unrecognized device Generic DLNA profile
Edit

 192.168.0.16 Unrecognized device Generic DLNA profile
Edit

 192.168.0.17 Unrecognized device Generic DLNA profile
Edit

 192.168.0.23 Unrecognized device Generic DLNA profile
Edit

 192.168.0.27 Unrecognized device Generic DLNA profile
Edit

 192.168.0.29 Unrecognized device Generic DLNA profile
....

my router's connected devices list does not have most of those !

[zip]

It stores devices that have been connected in past. They do not get removed, as Serviio doesn't know if they are gone forever or just not currently active.

They are only IPs with devices that respond to UPnP search. You could make the list less cluttered if you give your devices static IPs in your router DNS settings.

It stores devices that have been connected in past. They do not get removed, as Serviio doesn't know if they are gone forever or just not currently active.

They are only IPs with devices that respond to UPnP search. You could make the list less cluttered if you give your devices static IPs in your router DNS settings.

ok - that half answers it.
but why can I not get new devices to show , either actual new ones ( not a common need) or ones which have been given a new static address. 9 they no not immediately appear either ? )

I cannot find anyway to force the list to refresh, so I can have a client device on my LAN that is actually streaming a show yet is not shown as a connected device >
I'ts an issue because there's no way to set a device profile until the server lists the device ?

is the " connected vA serviigo" theory relevent or a red herring ?

FYI static addresses do not play nice with windows 10 - they lead to frequent " Error 0x800704cf the network location cannot be reached" errors for local file sharing with other win 10 PCs on LAN, so I have switched to usign reserved IP and 1 week lease times in router. google has many reports like this:
https://www.google.co.uk/search?q=the+n ... 2&ie=UTF-8

[zip]

There is a refresh button on top of the device list, right?

Anyway, these devices are only DLNA devices - so if you're streaming via ServiiGo it won't show up, unless you also used a UPnP/DLNA app to access Serviio. Normally the nonDLNA devices have given profiles by their apps (like MediaBrowser or ServiiGo) so there is no need to change the profiles.

There is a refresh button on top of the device list, right?

Anyway, these devices are only DLNA devices - so if you're streaming via ServiiGo it won't show up, unless you also used a UPnP/DLNA app to access Serviio. Normally the nonDLNA devices have given profiles by their apps (like MediaBrowser or ServiiGo) so there is no need to change the profiles.

1. yes I tried the refresh button, lots , before raising the issue !
2. thanks for confirming the serviigo theory


new question : why do windows PCs not identify themselves to the server. all the WIn 10 PCs on my LAN appear , but as as "unrecognised device" - (compared with my Samsung TVs which do identify themselves ?) is there a windows setting that influences that , or will that change if I run something on the PC ?

[atc98092]

FYI static addresses do not play nice with windows 10 - they lead to frequent " Error 0x800704cf the network location cannot be reached" errors for local file sharing with other win 10 PCs on LAN, so I have switched to usign reserved IP and 1 week lease times in router.

My main server runs Windows 10 with a static IPv4 address with no issues. I think what you are encountering is that Windows is using IPv6 to initially search for the computer, and your IPv6 address isn't static. I think there's a way to tell Windows to use IPv4 first, but haven't really researched it. I did see some of those same network connection errors for a while, and I believe it's IPv6 related. I have a Windows Home Server running as well, and I've installed the DNS service on it to handle my local LAN. I don't have any issues any longer with internal connections any longer.

The changeover to IPv6 will likely continue to cause little hiccups like this until we all learn what settings need to be set where. I know I'm still in the dark quite a bit about it.

FYI static addresses do not play nice with windows 10 - they lead to frequent " Error 0x800704cf the network location cannot be reached" errors for local file sharing with other win 10 PCs on LAN, so I have switched to usign reserved IP and 1 week lease times in router.

My main server runs Windows 10 with a static IPv4 address with no issues. I think what you are encountering is that Windows is using IPv6 to initially search for the computer, and your IPv6 address isn't static..

that is one of several theories, but I tried disbaling IP6 verywhere. Another theory is netbios settings which win 10 gets wrong by default, allegedly, for static IPs. but after months of intermittent frustration, I removed all my static addresses & it had not happened at all since then.
googling that error leads to all sorts of enable this/ disable that... suggestions but the bug appears to predate w10 & there is no single definitive answer. what happened was PC A woudl say it could see PC B but when asked to open a specific shared folder it would throw up the error. Accepting windows offer of running troubleshooting would find no errors but would fix it anyway -until the next time....
anyway we drift off topic...
the error did not affect DLNA streaming, it affected basic file copying / synchronisation between various PCs.