@ RockhopperJ how have you got on? Did BT get back to you after looking at your logs?
Still going strong here 24 days uptime now with not a single reboot + 8 days (powercut) since changing the line lease to infinite, i may regret saying this but I've purchased some second hand premium discs as they seem pretty stable here now. 🤔 I've even added one of them wireless BH disc without any issues or without causing any reboots or issues at all surprisingly.
Yes - @MurrayB and I have been swapping messages all week… But in all honesty, we’re no further forward sadly. Just to share steps taken in case it helps others:
Just to add, both salve WHP discs have WiFi connected backhauling as I cannot route Ethernet to those devices. I never 'restore' the WHP discs from a backup to avoid re-introducing issues.
The solution in discussion with MurrayB at present.
My premium boxes have gone back to BT for a refund after 9 months of BETA testing. Wish you all luck in getting the issues resolved - Foz, looks like you may have a fix for BT to work on - they should send you some sort of freebie 🙂
What I meant by 9 was
Sadly, and after several hours in to the early hours, I could not achieve any stability, but concluded I didn’t have a rogue device. I also checked everything worked fine when test connecting directly to the ASUS router (via wifi) instead (powering off the WHP discs and re-enabling the 2.4/5GHz service on the router etc..). The only reason I use the WHP discs is that my home layout typically the BT master socket installed in the porch/front of house) which means my router/modem aren’t located optimally for a decent wifi service throughout and certainly not good enough to support working from home without repeaters or powerline devices due to where our office’s are located in the property.
My house is quite old with a few electrical rings (due to extensions / new wiring etc.) so power line extenders did work and where awfully slow in comparison to the WHP discs when they work 😳
Seems odd to me that BT can not see the problem in the logs, if they requested your router log and compared the two times when disc reboot or you have the issues they should see the problem/cause.
Open logs in notepad++ and search "reboot" or/and "Reboot caused by detection of second master not reachable via ism" without the "
It will show as a system message. i suspect the firmware will be issuing the reboot command and not a random crash due to bad coding.
I did hunt for this line myself buy never found it… At present as 832C became unusable, I’ve since reverted back 822C so have completely lost any historic data. I’m getting about 3-4 hours before the primary re-boots causing the slaves to go red for a few minutes. Strangely the disc all report continues uptime now, where as previously when this happened the clocks would reset particularly on the primary…. Anyway… I’m waiting for Murray’s solution to arrive 🤞!
You shouldn't need any historic data if the discs are still randomly rebooting, the reboots will show in the logs regardless of why its rebooting, any reboots are easy to spot because the date defaults to 2013-01-01 until time is updated via internet when connection is established, so prior to the change in date what do you see as the last message on master disc log?