Where in the menus I can see how the WIIF works and if it has errors to see what makes it better or what the issue and also for ETH to know if the cable causing issues. Tplink routers shows that
Is -93 dBm and Higher is better ? -94 dBm or lower -92 dBm? How can I make it better?
View attachment 70995
Is this good on the WIFI network ?
Is this good also? -26 dBm is better than -25 dBm or -27 dBm? How can I make it better? no matter what I do it stays the same
Sometimes this specific device get stuck on 1 / 5 Mbps for some reason and doesn't change anymore. it takes a long time for it to happen so I can't test it with each setting. It's a WIFI LED camera that capture the TV screen and shows colors behind Ambision Pro. I always have issues with this device. when first it's connected to the network it shows 2ms-5ms and then after 5-6 of that it suddenly going randomly 50-350 and it always has timeout totally random. and sometimes it can be 2ms for a whole day. I can't understand what actually make this happen, it's power cable? when I touch it's power cable it can time out somehow, but I tried like 4 power adapters so I can't understand how all of them will cause issues.
View attachment 70993
Could it be the antenna's direction that fixes this issue?
This kinda what happens it can sometimes be a lot worse
View attachment 70998
This is kinda when it's fine not perfect
View attachment 70997
You said that 192.168.50.8 is a wifi camera? Here's why you are seeing this. Are you also getting stutters when viewing the live feed on the camera? If so, here's why that will likely not improve much. No matter your efforts.
The jitter you are seeing on ping is normal. It's caused mostly by the interference from neighboring networks on the 2.4ghz band. I get it on my Wifi camera which is on the 5ghz band, which for me is also congested (utilization around 50% when network is idle.)
Code:
Pinging bike-watch [10.10.10.25] with 32 bytes of data:
Reply from 10.10.10.25: bytes=32 time=94ms TTL=64
Reply from 10.10.10.25: bytes=32 time=8ms TTL=64
Reply from 10.10.10.25: bytes=32 time=110ms TTL=64
Reply from 10.10.10.25: bytes=32 time=15ms TTL=64
Reply from 10.10.10.25: bytes=32 time=5ms TTL=64
Reply from 10.10.10.25: bytes=32 time=43ms TTL=64
Reply from 10.10.10.25: bytes=32 time=4ms TTL=64
Reply from 10.10.10.25: bytes=32 time=78ms TTL=64
Reply from 10.10.10.25: bytes=32 time=5ms TTL=64
Reply from 10.10.10.25: bytes=32 time=94ms TTL=64
Reply from 10.10.10.25: bytes=32 time=8ms TTL=64
Reply from 10.10.10.25: bytes=32 time=114ms TTL=64
Reply from 10.10.10.25: bytes=32 time=5ms TTL=64
Reply from 10.10.10.25: bytes=32 time=33ms TTL=64
Reply from 10.10.10.25: bytes=32 time=7ms TTL=64
Reply from 10.10.10.25: bytes=32 time=59ms TTL=64
Reply from 10.10.10.25: bytes=32 time=4ms TTL=64
Reply from 10.10.10.25: bytes=32 time=77ms TTL=64
Reply from 10.10.10.25: bytes=32 time=14ms TTL=64
Reply from 10.10.10.25: bytes=32 time=107ms TTL=64
Reply from 10.10.10.25: bytes=32 time=5ms TTL=64
Reply from 10.10.10.25: bytes=32 time=21ms TTL=64
Reply from 10.10.10.25: bytes=32 time=7ms TTL=64
Reply from 10.10.10.25: bytes=32 time=40ms TTL=64
Reply from 10.10.10.25: bytes=32 time=5ms TTL=64
Ping statistics for 10.10.10.25:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 114ms, Average = 38ms
The signal of your camera to the router is already great. The issue is the overpopulated 2.4ghz band.
If the screenshot you shared was taken during low or no network utilization then that means the underlying utilization of ~20% means you will likely see only ~80% of the connection speeds IRL. That 20% utilization is actually pretty good for that 2.4ghz band. Where I am, I have never found a 2.4ghz channel that was less than 60% utilization at idle. I live in a congested area, and no longer use this band as a matter of preference.
Here's the rub in use-case and what probably got you looking into this:
The screenshot shows a 24/65 connection speed on Wifi n, with an excellent signal indicating a good proximity to your router, with those being expected connection speeds for Wifi n devices with 1x1 antenna configurations and 20mhz channel width. (Expected from most budget wifi cameras).
But, assuming your camera is 1080p, it needs at a minimum 5mps, preferably 10.
Your 24/65 connection is Rx/Tx from the router's point of view, meaning the router's connection to your camera's UL is 25mbits. but really only 80% of that because of the underlying channel utilization. So, mathematically only 20mbits. But, real-world speeds are going to be only 60 - 70% of computational values due to overhead, etc. So real world upload streaming speeds from your wifi camera at this connection speed are going to be roughly 12mbits.
That might seem adequate for uploading a 1080p stream, but it's a tight margin. Then you have to factor in the retransmits and packet loss from the channel interference. This is why any live view stream might seem jittery and unstable.
There is very little you can do about the underlying issues with the old 2.4ghz band except to invest in a camera that works on the 5ghz band. Even as my example shows, my camera is on a crowded 5ghz band, but the link speeds are much higher to compensate. Even though it's jittery there is more than enough bandwidth to support the 2k stream on my camera.
Thank god we have the 6ghz band now:
Code:
Pinging 10.10.10.130 with 32 bytes of data:
Reply from 10.10.10.130: bytes=32 time=6ms TTL=64
Reply from 10.10.10.130: bytes=32 time=6ms TTL=64
Reply from 10.10.10.130: bytes=32 time=6ms TTL=64
Reply from 10.10.10.130: bytes=32 time=6ms TTL=64
Reply from 10.10.10.130: bytes=32 time=7ms TTL=64
Reply from 10.10.10.130: bytes=32 time=6ms TTL=64
Reply from 10.10.10.130: bytes=32 time=6ms TTL=64
Reply from 10.10.10.130: bytes=32 time=6ms TTL=64
Reply from 10.10.10.130: bytes=32 time=6ms TTL=64
Reply from 10.10.10.130: bytes=32 time=6ms TTL=64
Reply from 10.10.10.130: bytes=32 time=6ms TTL=64
Reply from 10.10.10.130: bytes=32 time=8ms TTL=64
Reply from 10.10.10.130: bytes=32 time=6ms TTL=64
Reply from 10.10.10.130: bytes=32 time=7ms TTL=64
Reply from 10.10.10.130: bytes=32 time=6ms TTL=64
Reply from 10.10.10.130: bytes=32 time=9ms TTL=64
Reply from 10.10.10.130: bytes=32 time=6ms TTL=64
Reply from 10.10.10.130: bytes=32 time=6ms TTL=64
Reply from 10.10.10.130: bytes=32 time=7ms TTL=64
Reply from 10.10.10.130: bytes=32 time=6ms TTL=64
Ping statistics for 10.10.10.130:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 9ms, Average = 6ms
That's from a device on my network on the 6ghz band.
In summary: the connection to your camera is great in terms of router placement. The underlying channel utilization is already pretty low for your 2.4ghz band. The n network connection speeds are as expected for devices using a 1x1 antenna configuration. The issues are from fundamental bottlenecks from the Wifi n standard and 2.4ghz band.
I hope this helps. Cheers.
