ok. That is how mine is partitioned too. Will try it out now. Thank you!
1 Like
It looks like applying the snapshot sysupgrade wiped the configuration when updated via the WebUI on one of the initial TP Link builds. It's on a spare unit, and I did a backup beforehand, so I can just restore that but is there something I missed that would allow the configuration to persist across the sysupgrade?
Early versions of my patches had a different, incompatible storage layout to what was eventually committed to openwrt. So it's expected to have a one time loss of configuration if you were using the early image. But that shouldn't happen on future upgrades.
1 Like
I'm sure the answer is no, but is there any chance that we would be able to make use of the Zigbee radio in the OnHub? Are there any drivers for the Silicon Labs EM3581?
could someone share the dmesg log ?
bootlogs in toh page is still empty
Hey everyone, not sure if this is really the right place to post this but I threw together some scripts for some basic RGB effects.
Thanks to bnorris and anyone else who helped make this a supported device.
1 Like
Thanks. This comment let me flash succesfully on some Asus Onhubs. Asus code also shows as Green once loaded.
1 Like
First off I want to thank the devs who have taken the time to bring OpenWrt to the TP-Link OnHub. I've been waiting for this for a few years and forgot to check back on the progress until last week when I needed to set up another AP.
I do need some help though, because I'm having trouble after loosing access, likely due to a mistake in configuration. I went ahead and went back to factory with the USB recovery image, but now when I put the OpenWRT factory.bin on the router and issue the command to write it to internal storage it seems to work, and boots up with the multicolor LEDs at the top, but I can't get an ip address on the lan port (or wan port...) once I've rebooted and removed the USB drive. Currently I'm just booted to the USB stick which isn't an issue since its plugged into a UPS and won't restart in case of a brownout or something, but I'd prefer to get it working on internal storage again.
edit*
Oh, I forgot to ask about the three wireless interfaces. Does anyone know the capabilities of each? Is it possible to combine the two 5ghz to do 80mhz+80mhz for more bandwidth over wireless, or is that a stupid question? 
The AP is FAR from any others and centrally located around 15ft from devices that i'd like to see a bit more bandwidth on wireless. Just got gigabit symmetrical last week, so in the process of optimizing for that.
edit2**
Just finished discovering the same thing. Max I've seen on a speed test is 200mbps with the same behavior you noticed on core0.
Having same issue on an Asus OnHub.
As a separate question, There is a comment from Franco Castillo on a youtube Video from Vantech on 802.11s setup that seems to indicate the -ct drivers are only for Wave2 for 802.11s. Any truth in this? Wasn't able to reinstall any of the ath10k firmwares after removal.
OpenWRT - 802.11s Mesh WiFi Network - YouTube
[ @Justin L ] It doesn't work because that chipset is Wave-1 and the CT driver doesn't support 802.11s on those chipsets. Only with Wave-2 as
I'm having the same issue as @landerslanding and @Bndwdthseekr that I can boot from USB drive on my TP-Link Onhub. However when I write the image to emmc and reboot it starts OpenWrt as indicated by the multicoloured led ring but never establishes a link on the wired lan port. Not sure what is going on since the same file works fine from USB?
I can see that the freshly flashed firmware is trying to establish a link but it fails and then keeps re-trying and failing over and over again. I've tested a direct connection, via a 100mbit switch and with a fixed ip in the 192.168.1.x range but none of these options make a difference.
After doing a factory restore I tried another thing. Boot from USB, write the firmware to emmc followed directly by a sysupgrade. Unfortunately that doesn't make a difference either.
If anybody has an older build still available on their PC could they share it somewhere?
Thanks in advance.
Okay so for me, the first time worked. I was able to restart it several times, move it to the desired location, and all was good. I only discovered this issue after I lost access and didn't have the time to open it (still haven't) to get to the serial interface and reset it that way, but instead restored and repeated the original process.
edit**
Oh yeah, I lost access because I was stupid and applied settings in the wrong order.... so nothing to do with openwrt
When I install my USB drive and try to recover image to factory reset my Onhub, but I think Onhub doesn't recognize my USB.
My USB is USB 3.0 with 16GB, does the USB 3.0 matters on Onhub?
My factory reset USB drive was also a USB3.0 16GB drive and it worked fine. Just takes a long time in general.
When I connect USB to Onhub, it just showed blinking red LED light and doing nothing.
Also USB didn't blinking that was not busy.
See msg 116 above by dadogroove "Note that Recovery mode does not appear to work with all USB drives (for example, some newer USB 3.0 flash drives). If the device appears not to be accepting your USB drive, try swapping for a different one."
OK I managed to reflash mine successfully after being locked out and resetting a few times. What I ended up doing is as follows:
- Factory reset using the google chrome created 'special' USB stick
- Boot OpenWrt from a USB stick
- SSH into OpenWrt and dd the whole /dev/mmcblock0 with zeros (this will take a while)
- SCP the factory image to /tmp on the Onhub
- write the factory image to /dev/mmcblock0 using blocksize of 1M (bs=1M)
- reboot with the USB stick removed
Now my OnHub boots OK and gives me a connection on the lan port as expected. I'm not sure why I had issues before but I guess there could be some leftover data on emmc when we write the image. Hope this helps others who are locked out after messing up their config.
Thanks to the developers for all their effort. This is still a great piece of hardware and now even better with OpenWrt.
3 Likes
I think also devloper mode is same. I tried to install OpenWrt in developer mode with same USB, but it seems to not boot with USB and goes to only breathing purple light.
Are you experiencing intermittent internet on the mesh? My onhub also seems to be heating up more than usual after I installed the latest snapshot
The device page doesn't make it clear but it does take some time after the RGB ring lights up before the network is active. I never timed it but it seems like it takes around 20-30 seconds. Not sure if this helps anyone. Also not sure if a static IP is required but I always set it manually anyway.