Puck Not Holding LAN Connection

[Pompey+Lad]

Update: I reset network on the puck then connected WiFi, router dhcp issued ip address ending 162. 

Inserted the ethernet cable.

Went into standby & then home.

Puck connects without blue screen nonsense.

In network settings puck is using ethernet address ending 166.

It seems that puck first looks for wifi, loads settings up then selects ethernet as a preference over wifi.

Weird, but solves the problem.

[Spasmcasm]

I've basically given up with it TBH. The puck user experience isn't anything like I thought it would be. 
When we first got it up and running it seemed ok, but then we started getting the latency and freezing issues as I've previously sought help with. All the well meaning advice given on here was tried and even hours (and I mean hours,) of calls to customer service still can't get the puck to pick up a wired LAN connection to the booster from turn on. Without going back into it all, we can't hardwire the puck to the router because of the house layout. We can't run cables, so sky gave us 2 x boosters as the wifi in each room falters so the wifi connection between the puck and router isn't stable.
We'll see out the the remainder of our sky contract and probably go to Virgin. We've already been assured by them that the entry point for the house cable will be where we want it (not where Open reaches contractor said we had to have it, hence the issues above) so the cabling issue will be resolved.
We don't find the interface or user experience to be anything like as intuitive as the old Q box. Still, each to their own!!

[Jporch316]

---

@Spasmcasm wrote:

I've basically given up with it TBH. The puck user experience isn't anything like I thought it would be. 
When we first got it up and running it seemed ok, but then we started getting the latency and freezing issues as I've previously sought help with. All the well meaning advice given on here was tried and even hours (and I mean hours,) of calls to customer service still can't get the puck to pick up a wired LAN connection to the booster from turn on. Without going back into it all, we can't hardwire the puck to the router because of the house layout. We can't run cables, so sky gave us 2 x boosters as the wifi in each room falters so the wifi connection between the puck and router isn't stable.
We'll see out the the remainder of our sky contract and probably go to Virgin. We've already been assured by them that the entry point for the house cable will be where we want it (not where Open reaches contractor said we had to have it, hence the issues above) so the cabling issue will be resolved.
We don't find the interface or user experience to be anything like as intuitive as the old Q box. Still, each to their own!!

---

Boosters are not the answer for sky stream ..... you'd be much better off getting a decent wifi mesh system which create a stable and much larger wifi zone. All a booster does is take an already weak signal and attempt to grab it and move it on ..... 

[Anonymous]

Seconded @Jporch316

I use an Eero mesh and can get UHD working flawlessly in a conservatory, with a brick wall between the puck and the router. On EE's standard router I can barely get signal in there. 

A modern mesh network with well placed points does wonders. 

[Jporch316]

I use to use the original Google mesh system - worked great for me. Since swapping to VM I use their own mesh pod system which does the job .....

[Me123321123]

This is the type of behaviour I have seen and am currently experimenting with four reserved IP ranges for my two sky devices (one each for WiFi and Ethernet.). I've seen it hold a strange named connection to the network and get itself in such a mess that a factory reset is the only way out.  I'm testing as well with the power saving options disabled as well.  

From what I've seen and read the network firmware is not good on these boxes and any setup which hasn't got a direct connection into the router from the puck has the potential to cause issues.

A