Hundreds of Devices & No Clear Button

[jhb50]

Visiting my daughters home, and Serviio now shows devices 192.168.1.2 thru 192.168.1.184 in console with generic profile. Reset button does nothing and only choice seems to be to do 180+ separate deletes to clear them. How does one reset the device list?

See attached console and device Spy shots

[zip]

You have to do it one by one. Refresh would get a new state, but only the devices that can be found by the UPnP Search method (and can be identified by their UUID). For other devices we just create a new renderer in the table when the IP address changes.

[jhb50]

You have to do it one by one. Refresh would get a new state, but only the devices that can be found by the UPnP Search method (and can be identified by their UUID). For other devices we just create a new renderer in the table when the IP address changes.

Sorry but I do not understand. There are only a few real devices as device spy shows, so how can Serviio generate renderers for all these hundreds of non existant devices.

What I think may have happened is that every time a device connects to your network it is given a different ip address. Then as that device accesses the Serviio server the list grows and grows.

Perhaps using static ip addresses for the devices on your network will work best.

EDIT: I forgot to mention, I would remove all ip addresses on that list and start over again after static ip addresses have been assigned.

[jhb50]

No, I don't think that is correct. DHCP assigns an address and thats it. It would not try another. This problem does not occur on my home router nor has anyone else reported this problem.

No, I don't think that is correct. DHCP assigns an address and thats it. It would not try another. This problem does not occur on my home router nor has anyone else reported this problem.

Not exactly, DHCP may use static, dynamic, or automatic allocation. Static may be preferred for private home/office networks since connected devices will usually always be the same. Where dynamic would be implemented in a public network such as a coffee shop to ensure ip addresses are available for the next set of users.

[jhb50]

every time a device connects to your network it is given a different ip address. Then as that device accesses the Serviio server the list grows and grows.

That statement is incorrect. Once the device is given an address, it will be reused the next time. The list does not grow and grow. Hence you suggestion that this is the cause is also incorrect.

[will]

every time a device connects to your network it is given a different ip address. Then as that device accesses the Serviio server the list grows and grows.

That statement is incorrect. Once the device is given an address, it will be reused the next time. The list does not grow and grow. Hence you suggestion that this is the cause is also incorrect.

Actually he is correct, DHCP can give a different address every time a device connects or renews its lease, if that's how it's been setup. If you spend a few days in a house with a router that isn't set to reuse address / use the same for a device, you could easily see lots of 'different' devices (as in different IP, not different MAC address) after a while.

To solve your problem, you could wipe out your device list using the API.

[npuser]

thats very interesting. I would investigate why router/dhcp server is not reusing previous ip address if the IP lease periods has not expired yet. Unless the dhcp server lease time setting set to expire rather quick. Still, even if frequency of lease expiry is the case here dhcp by design should re-assign previous ip address with new lease expiry datetime stamp. In your case dhcp server for a some reason thinks previous ip is still in use by other devices (mac) and assigns whole new ip rather than reassign it back to same mac address. I bet you only see 5 Devices in router "view dhcp clients" list section but with different IP address immediately after the IP lease time expires. The dhcp usually self cleans the dhcp clients list but serviio does not hence the polluted device list.

Only suggestion, if the lease time is set to too short, increase it to at-least 5 days or so unless it is a business environment where you have a lot of frequent visitors and have potential to run out of ip addresses in a dhcp scope.

Does NOT address your query "how to clear devices?" but just trying to get our heads together to figure out what may be happening....

NPuser

[jhb50]

I appreciate all the feedback.

I have come to the conclusion that all these addresses must have been created when attached to one of the hotspot routers I connected to while travelling across the country. When I clear them now they do not reappear so the problem is not at this location.

I'll put together a REST command to clear everything. Thanks Will.