Repository navigation
Replies: 2 comments 1 reply
|
I just installed and noticed this as well. |
1 reply
|
Thank you so much for this report: clear, precise, and with the exact lines. It made the fix quick. The gateway tile now shows the real subnet and counts every device in it, and Home Assistant clients on the same network are grouped as one. It will be in the next release. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
On a network wider than a /24, the dashboard shows the wrong subnet and wrong usage counts. The scanner itself handles the wider network correctly (
netutil.get_local_network()reads the real prefix andscan/arpplan.pyrotates through the /24 blocks), but two display paths hardcode /24.Environment
10.20.2.50/22(netmask 255.255.252.0), gateway10.20.0.1What I see
10.20.0.are counted. Devices on 10.20.1.x–10.20.3.x are left out, including the Home Assistant host itself.Cause
vedetta/app/frontend/ha/js/net-rotator.js,gatewayTile()(L97–102): the subnet is built from the gateway IP's first three octets plus.0/24.SUBNET_HOSTS = 254(L8) is a constant. Theusedfilter is a string-prefix match on the first three octets.vedetta/app/ha/passive_view.py,_net()(L99): each client's network is derived asip + "/24". The docstring notes that the VLAN isn't in the data.Suggested fix
The backend already knows the real CIDR (
get_local_network()→ e.g.10.20.0.0/22). Expose it from/api/ha/networksor/api/ha/summary, and have the frontend use it for:num_addresses - 2),_net()could use the same CIDR for addresses that fall inside the local network, and keep the /24 fallback only for addresses outside it.Expected
Gateway tile shows
10.20.0.0/22, about 1022 usable hosts, and counts every device in that range. Clients in the /22 are grouped as one network.(Addresses above are placeholders; the real network has the same shape.)
All reactions