cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Palazzo13
Contributor
1,024 Views
Message 211 of 1,166

Re: Whole Home WiFi firmware update v1.02.04 build10

I went about 10 days without any discs removing themselves from the network (it happened twice in quick sucession at that time) but have had to restart the network today as connection speeds were dropping, and like other users report, devices keep dropping and reconnecting to the discs, even when they're not being moved.

The performance seems to have degraded gradually over the 10 day period. 

0 Ratings
Reply
MrX911
Contributor
1,011 Views
Message 212 of 1,166

Re: Whole Home WiFi firmware update v1.02.04 build10

Don’t know why this would make a difference as I have no interfering devices but devices have always been on channel 44 (auto) since new but after my latest factory reset system would not stay stable. Deciding to change channel to 48 and been fine for 18 hours!
0 Ratings
Reply
spiderlane
Contributor
1,003 Views
Message 213 of 1,166

Re: Whole Home WiFi firmware update v1.02.04 build10

I feel for those who are suffering problems and it's really interesting to see the difference experiences. Just to add mine…

Before the firmware update I had to disable steering because the system was useless with certain devices (namely my Macbook Pro and my Nest cameras). The new firmware initially improved things for those devices but I was still getting disconnects regularly for the Nest cameras.

However what's  odd is that after a few days the system settled down and I have not had a single Nest camera disconnection since then. The system has been totally rock solid for all devices apart from one instance where one of the discs went red and I had to restart it several times to get the service back. Interestingly this is the only disc with Wi-Fi backhaul as all the others are now connected by ethernet. 

It's odd how my experience (gone from very unstable to very stable)  is the polar opposite to so many on here

Cheers

Mark 

0 Ratings
Reply
richard42
Contributor
991 Views
Message 214 of 1,166

Re: Whole Home WiFi firmware update v1.02.04 build10

None of mine are connected via ethernet (not practical for me and there's more than sufficient bandwidth over Wi-Fi for my use cases).  I have the first disc plugged into the router (BT Smart Hub with Wi-Fi disabled) and the rest of the discs are scattered around to give full coverage, the walls are very thick here, so it's the perfect place for a mesh solution.

I was pleasantly surprised with the reliability when I first setup the kit, having had problems in the past with BT hardware.  So I quickly increased the number of discs to 6 for even better coverage and everything has been working flawlessly for months up until the current firmware update.  Nothing else has changed on the network.

abattle
Contributor
985 Views
Message 215 of 1,166

Re: Whole Home WiFi firmware update v1.02.04 build10

On the old firmware, my 5GHz channel was automatically set to 36. Since the firmware upgrade the 5GHz is now automatically set at 44. Still no problems.

Given that for good connections the discs use the 5GHz band to communicate with eachother, and seeing as the problems on here seem to be centered around communication issues between discs hence the dropouts, I would manually set the 5GHz channel at 36, then 40 and so on until the system stabilises.

You need to access the web login to alter the 5GHz channel.

Andrew

0 Ratings
Reply
richard42
Contributor
963 Views
Message 216 of 1,166

Re: Whole Home WiFi firmware update v1.02.04 build10


@abattlewrote:

On the old firmware, my 5GHz channel was automatically set to 36. Since the firmware upgrade the 5GHz is now automatically set at 44. Still no problems.

Given that for good connections the discs use the 5GHz band to communicate with eachother, and seeing as the problems on here seem to be centered around communication issues between discs hence the dropouts, I would manually set the 5GHz channel at 36, then 40 and so on until the system stabilises.

You need to access the web login to alter the 5GHz channel.


It's a plug and play solution, there shouldn't be any need for people to alter their settings, especially as in my case they were working fine prior to the current firmware update.   In any case, according to my Wi-Fi network scanner, the discs here are currently using channel 36 for 5Ghz and channel 6 for 2.4Ghz.  I have never altered any settings, so these are presumably the channels that the discs are currently using based upon minimising congestion, not that congestion should cause the issues that have been described on this thread anyway.

The issue I experienced yesterday seemed to stem from walking from one room to another with the laptop and resulted in my phone and laptop being unable to connect to the Wi-Fi at all, in any location.  I had to turn off all of the discs manually and turn them back on again, as the app was obviously also temporarily inoperable.

0 Ratings
Reply
abattle
Contributor
956 Views
Message 217 of 1,166

Re: Whole Home WiFi firmware update v1.02.04 build10


@richard42wrote:

@abattlewrote:

On the old firmware, my 5GHz channel was automatically set to 36. Since the firmware upgrade the 5GHz is now automatically set at 44. Still no problems.

Given that for good connections the discs use the 5GHz band to communicate with eachother, and seeing as the problems on here seem to be centered around communication issues between discs hence the dropouts, I would manually set the 5GHz channel at 36, then 40 and so on until the system stabilises.

You need to access the web login to alter the 5GHz channel.


It's a plug and play solution, there shouldn't be any need for people to alter their settings, especially as in my case they were working fine prior to the current firmware update.   In any case, according to my Wi-Fi network scanner, the discs here are currently using channel 36 for 5Ghz and channel 6 for 2.4Ghz.  I have never altered any settings, so these are presumably the channels that the discs are currently using based upon minimising congestion, not that congestion should cause the issues that have been described on this thread anyway.

The issue I experienced yesterday seemed to stem from walking from one room to another with the laptop and resulted in my phone and laptop being unable to connect to the Wi-Fi at all, in any location.  I had to turn off all of the discs manually and turn them back on again, as the app was obviously also temporarily inoperable.


I agree, no tinkering should be required. That said, if I were in your position I would change the 5GHz just to see if that works. The next update, going by past experience, is 2-3 months away.

0 Ratings
Reply
richard42
Contributor
905 Views
Message 218 of 1,166

Re: Whole Home WiFi firmware update v1.02.04 build10

The BT Whole Home Wi-Fi has crashed again, in less than 24 hours.  Wi-Fi latency went sky-high, Wi-Fi calling vanished on iOS, Internet inaccessible, that's just on devices already connected.  New devices were unable to join the Wi-Fi at all.  All discs showed blue lights, app obviously completely unusable.  Here's a ping of a LAN address from my laptop when it occured:

PING 192.168.1.254 (192.168.1.254): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 192.168.1.254: icmp_seq=1 ttl=64 time=34.797 ms
64 bytes from 192.168.1.254: icmp_seq=2 ttl=64 time=34.561 ms
64 bytes from 192.168.1.254: icmp_seq=3 ttl=64 time=898.814 ms
64 bytes from 192.168.1.254: icmp_seq=4 ttl=64 time=793.180 ms
Request timeout for icmp_seq 5
64 bytes from 192.168.1.254: icmp_seq=5 ttl=64 time=1042.671 ms
64 bytes from 192.168.1.254: icmp_seq=6 ttl=64 time=1066.630 ms
64 bytes from 192.168.1.254: icmp_seq=7 ttl=64 time=1058.323 ms
64 bytes from 192.168.1.254: icmp_seq=8 ttl=64 time=643.524 ms
64 bytes from 192.168.1.254: icmp_seq=9 ttl=64 time=1013.754 ms

As before, the only solution was to run around turning off all 6 discs on both floors.  Then to repeat, turning all 6 discs back on again.  Once they had rebooted, the network was fine again, for now at least. 

PING 192.168.1.254 (192.168.1.254): 56 data bytes
64 bytes from 192.168.1.254: icmp_seq=0 ttl=64 time=3.054 ms
64 bytes from 192.168.1.254: icmp_seq=1 ttl=64 time=3.241 ms
64 bytes from 192.168.1.254: icmp_seq=2 ttl=64 time=3.529 ms
64 bytes from 192.168.1.254: icmp_seq=3 ttl=64 time=3.201 ms
64 bytes from 192.168.1.254: icmp_seq=4 ttl=64 time=3.578 ms
64 bytes from 192.168.1.254: icmp_seq=5 ttl=64 time=3.106 ms
64 bytes from 192.168.1.254: icmp_seq=6 ttl=64 time=3.165 ms
^C

Furthermore there's nothing in the logs around the time this happened, I have checked.

I maintain that this is a serious firmware issue and needs addressing URGENTLY.  I strongly object to BT releasing a firmware update that renders hardware purchased in good faith no longer fit for purpose.  The lack of response is frustrating to say the least, as is the time wasted.  I am not prepared to wait 2-3 months for BT or their supplier to fix this problem.

0 Ratings
Reply
Steve59
Aspiring Expert
880 Views
Message 219 of 1,166

Re: Whole Home WiFi firmware update v1.02.04 build10

Just wondering how long people get up time after a physical reboot of all the discs as my general experience is it "seems" to stay up for a good few days after a reboot

So if i can get it to last a week for example, I may plan in a maintenance reboot, ie a timed restart from the mains to reset everything

Not ideal but would rather a planned loss off connection once a week than random ones, as I have found using the "restart" in the app to be flakey with further dropouts until discs have been rebooted

Currently been up 1 day 17 hours since forced reboot.

Thoughts ?

0 Ratings
Reply
richard42
Contributor
865 Views
Message 220 of 1,166

Re: Whole Home WiFi firmware update v1.02.04 build10


@Steve59wrote:

Just wondering how long people get up time after a physical reboot of all the discs as my general experience is it "seems" to stay up for a good few days after a reboot

 

Thoughts ?


For me, it's less than 24 hours, on average.  I doubt it's time-related, it could be a memory leak in the firmware in which case it may be triggered by the number of packets or quantity of data transmitted over the network.  Without seeing the code, it's anybody's guess.  Only the developers can sort this mess out.

0 Ratings
Reply