So far so good as far as the Blink system is concerned and no dropouts on that side. Its picking up activity fine and I live viewed the postman this morning after the alert.. and just this minute next doors cat kindly triggered it whilst walking up to my front door and sniffing the step
The TPlink is warm this morning as its now stood on end, centre top its like putting your hand on a radiator which is cooling down. But yesterday I'd left it laid on its front for a short while after I swapped the cable from LAN1>LAN4 and it was blisteringly hot. Even the desk where it had been laid down on was uncomfortably hot to touch.
I spent ages last night putting devices back on, thats a PITA. I did ~16 individual devices and switches.
My NAS is still running from a static IP attached to the Zyxel and the Hive System (9) is also still using a reserved IP.
I still need to do several plugs and a few things I don't use so often such as the printer, so about another 10 to go............
However I'm struggling to get my TV, the downstairs firestick and the sound plate connected as none of them can pick up a signal from the TPlink All these 3 are in a notorious blackspot which has always been problematic. I even wrote about it in the
Zyxel review "This location was a previous wi-fi dead spot and Id previously had to install CAT5 to get a decent stream to the TV. The VMG8324 totally negates the previous need for a run of ethernet cable." Unfortunately I ripped out the cable about 4 years ago after having new carpet laid. Another trip to the loft is in order to get a long length of CAT5 to temp move the TPlink a bit nearer to try setting it up, but that will have to be for another day.
I'm not really happy with the existing set up and I've got the TPlink in space where I really wanted to keep the Show, purely because I was trying to give some devices best chance of getting a signal. Wireless penetration on the VMG8324 is definitely much better, even if it doesn't have ac.
I'm wondering if there's something wrong with the Zyxel,
Also beginning to wonder - especially after trying to set up the TPlink. I could see there may be as low as 5 active devices listed in arp but it just wouldn't release an IP address to anything new attempting to connect. As I mentioned in previous post, its only recently its been struggling and not always switching on porch light when asked.. and the most annoying thing not giving an IP to my phone when I walk in. Last month I exceeded by data use for the first time ever and once aware I could see that it wasn't giving an IP to my phone and I was continuing to use data when I thought I was on wifi.. and refused to connect until I rebooted the router. Nail in the coffin is the fact the Blink system needs at least 3 IPs to be able to function properly. 9 times out of 10 it was failing to allocate an IP address to the camera once it detected movement. More often than not the way I knew someone was at the door was because the Show and an echo dot would announce "I'm having problems connecting to the Internet". The Zyxel was obviously attempting to release their IPs but then wouldn't give them back either to cam nor the device(s) it took them from.
That said there is definitely a limit and it is small (<16). This limit affects not just the Zyxels and I suspect it may be related to a specific wireless chipset. You can ignore what the GUI says (32) because it definitely will not. I am not sure where the restriction is but Bob Pullen gives a clue in respect of another router
They have however confirmed that the platform configuration is limited to 16 devices on the Wi-Fi interface. This limitation is not at the DHCP layer.
The 16 is still being disputed and several saying its less than that. If you search around then this problem is something beginning to rear its head only over about the past year or so as more people get smart home systems. I read a post on a forum somewhere where someone had said they had in the past written software for wifi devices and it was a limitation of some of the cheaper wifi chipsets. btw he also said something about it not needing much memory or CPU which was something 7LM recently queried. If I find that post again I shall link to it.