on 08-02-2011 10h06
the latest version of the HH FW is 184.108.40.206.83.8.48
However I am on .45, and the system has been powered on since last Tuesday (a week)
Normally it wouldn't bother me, but I've experienced 2 apparent crashes of the HH3 in the last 24 hours (looks like a complete reboot - ethernet and wifi connectivity lost, ssid disappears, returns after <2 min, no net connection, that returns another 30s or so later)
So there may be an instability bug here -- hence keen to ensure I'm running the latest firmware first before investigating further.
on 09-02-2011 8h02
I noticed the hub rebooted again last night. The log isn't especially interesting just showing
|06:48:15, 09 Feb.||Host 00:0e:8e:24:c3:7b connected to SSID 'planetf1e' at 162 Mbps|
|06:48:12, 09 Feb.||( 32.420000) Ethernet is down after 0 minutes uptime|
|06:48:09, 09 Feb.||( 29.350000) Server URL: https://pbthdm.bt.motive.com; Connecting as user: ACS username|
|06:48:09, 09 Feb.||( 29.060000) Initializing transaction for event code 1 BOOT|
|06:48:07, 09 Feb.||( 27.290000) Ethernet is up|
|06:47:53, 09 Feb.||( 13.170000) Booting firmware 220.127.116.11.83.8.45 (Type A)|
|06:03:46, 09 Feb.||Host 00:0e:8e:24:c3:7b connected to SSID 'planetf1e' at 144 Mbps|
|05:58:45, 09 Feb.||Host 00:0e:8e:24:c3:7b connected to SSID 'planetf1e' at 117 Mbps|
|05:53:43, 09 Feb.||Host 00:0e:8e:24:c3:7b connected to SSID 'planetf1e' at 130 Mbps|
|05:48:45, 09 Feb.||Host 00:0e:8e:24:c3:7b connected to SSID 'planetf1e' at 144 Mbps|
|05:47:40, 09 Feb.||(82831.930000) Time synchronized with server 18.104.22.168|
|05:47:40, 09 Feb.||(82831.910000) Requesting time from server 22.214.171.124|
|05:43:46, 09 Feb.||Host 00:0e:8e:24:c3:7b connected to SSID 'planetf1e' at 117 Mbps|
So why the reboot at 0648 -- this is a similar time to yesterday, but also around the time the first client would connect...
on 10-02-2011 8h11
Interesting -- exactly the same today, making it, I think - 3 days on the run.
The "reboot" is happening around the same time each day -- so could be scheduled rather than a crash.
Anyone else seeing this?
on 10-02-2011 11h40
Im on the same firmware as you mate.
Had the router running for 24hrs, and so far no problems.
Is there a way to do a forced update does anybody know?
on 10-02-2011 15h10
I've had an email response from the forum mods and asked the same question - either "pull" by me or "push" from tech support
For the first few days I had no reboots. Then the last 3 days I have. One thought I had is that it was a failed update - but I think first step is to get to what BT document as the "current" firmware (unless that info is wrong), then worry about remaining problems.
Even with these issues it's a dream compared to the HH2...
on 10-02-2011 15h23
Does sound a bit like a failed update given that it is the same time each day.
on 10-02-2011 17h45
I'll need to go on and check mine also, I had been getting an intermittant issue were it would say an ethernet cable is unplugged (PS3) but would correct itself within seconds, annoying when it happens in the middle of a movie I'm streaming.
on 10-02-2011 18h54
It may be something you have already tried, but have you performed a hard reset? Even if the sync drops on the hub, this won't necessarily force a firmware upgrade.
I've found that the firmware is only upgraded once a full reset is completed and before any synchronisation takes place.
Just an idea...
on 11-02-2011 7h41
Not certain if the hub booted again last night, but I think so:
|06:49:15, 11 Feb.||( 32.040000) Auto channel selection (reason 'Power up') is complete. Selected channel: 6, noise data: 1-(-114) 2-(-113) 3-(-112) 4-(-116) 5-(-113) 6-(-114) 7-(-111) 8-(-115) 9-(-115) 10-(-111) 11-(-120) 12-(-121) 13-(-121).|
I can't be certain as I was up a little later, and the log is swamped by wireless log events (speed changes) - not that useful! So this is the earliest one I can reasonably see
Funnily enough this is the same time -- 06:49 again, or close enough...
still on .45
May wait to see if I hear back soon, otherwise as mentioned above it may be worth a hard reset (which shouldn't be needed of course)