Does anyone else have an LG Oled 2017 TV model they can successfully connect to the BT Whole Home Wi-Fi with? My Tv just wil not connect to the WHW whatever I try, however it will connect to a separate individual Nighthawk Wi-Fi extender that I have.
I have what is essentially the same but non- OLED SUHD 2017 SJ800V model. It connects instantly and is a great rock solid connection.
Follwing the reset advice, unfortunately the same problem occurred after 4 days, where one of my discs in the app was again pink. I also confirm that no steering had been turned off.
To re-cap, with v1.02.05 build 01, I had no problems after turning "off" Legacy Steering, but after build 10, it does not make any difference whether this setting is on or off, which is quite frustrating having found a work around, ie the system will only stay up for around 4 days.
I've sent the log files to BT so will see what the feedback is.
I never did get any response from BT on this which is a shame
I therefore tried switch off "All" steering. Since I did this stability has once again returned. The steering side does seem to be causing some challenges getting it to work!
At least for now I have another work around
Yes - Airprint has stopped working for me, too.
Thanks both, I can report that although stability has increased I still get the printer dropping off and the thermostat showing no response, during this time I can still access the web interface of the printer and manage the thermostat via the Honeywell app its just the Homekit/Airprint which stops working.
I will try turning off all steering and see if it improves things further.
@mikew88 @Sircoynie With all steering disabled do devices still switch to another disc themselves, i.e. moving with iPhone/iPad from upstairs to downstairs, in my environment a device could still 'see' multiple discs but the one in the front room would be a far stronger signal than upstairs or kitchen.
There is a known issue with Airprint/some other network discovery protocols which will be fixed in a future firmware update. I expect this may be causing the issues you're currently seeing. Check back on the forum for details of the update when it is released.