Asus OnHub special features

[jedboy]

I saw OnHub mentioned in another thread.

TP-LINK TGR1900 (Google OnHub)

Pretty cheap on Amazon. It is old, from 2015
I got OpenWrt installed.

I'm wondering if anyone has used any of the unique hardware features in OpenWrt?
Like
Zigby
Bluetooth
Proximity detector
Speaker
Light sensor

[frollic]

@jedboy

Zigby
Bluetooth
Proximity detector
Speaker
Light senso

are all/any of those supported by Linux ?

[slh]

In the absence on documented information, e.g. on its device page on the wiki, you'll be the first to find out (which may include driver development/ mainlining).

[jedboy]

@frollic factory firmware is based on ChromeOS so supported by Linux in a sense, not aware of any available docs or drivers though

@slh I thought that might be the case. Might be to big of a hill for 8 yr old device

[goofball]

Is this thread specific to the ASUS version? I'm using a TP Link OnHub and i'm most interested in implementing radio2, combo 2.4+5ghz with slow speed meant for scanning.

Speaker probably not so hard. I would like to get the speaker working on mine with mpd. It's already used at the bootup process.

Bluetooth/Zigbee were not used in the Google provided OS so i don't know how much these features actually can work if at all.

[jedboy]

Share info on Asus or TP Link. They seem to be mostly the same.
Proximity sensor may only be on asus

[jedboy]

This topic is already covered on another topic. I added a post there.

Onhub TP-LINK TGR1900 future support?

I was in search of using special onhub features. I gleaned some answers from this thread. They shall be shared below. I'm using the Asus version. The speaker works. It is mentioned aboved You can test the speaker like this: opkg update opkg install mpg123 wget https://freetestdata.com/wp-content/uploads/2021/09/Free_Test_Data_100KB_MP3.mp3 -O /tmp/test.mp3 mpg123 /tmp/test.mp3 One post mentions getting onhub working as a blutooth speaker Zigbee is also mentioned in that post, no specifi…

Can someone close this topic?
@goofball @psherman

[slh]

I'd rather suggest to keep this thread open.

Why, the other thread is more about getting OpenWrt on the onhub. That part has been done (technically that thread could now be closed, but I'll leave it open for some kind of user support as well), all you would 'typically' expect from an OpenWrt router should be working with that.

In this thread, you've been asking about something rather specific, namely supporting features available in the hardware which are quite different from what one would usually expect from an OpenWrt supported device, so why not keep discussions about those in this thread?

• zigbee
  cool feature, very welcome addition, but I don't really see that to become part of the default images - so something for opkg install kmod-xxx <insert some kind of zigbee manager here>
• bluetooth
  while this should be technically rather simple to support (in the sense of getting hcitool scan to work), OpenWrt by itself doesn't know what to do with bluetooth, so it would need quite a lot of additional packages and configurations, so probably also a case for opkg install bluez … (kmod might be included)
• proximity detector
  not really anything I'd expect OpenWrt to do anything sensible about, but at the same time it's probably going to be a single small kmod, outputting its detected distances via sysfs(?), so adding this by default might no be harmful, but neither very helpful either (I might err on including it by default, otherwise opkg install kmod-xxx)
• speaker
  again, a cool features, but a rather large (albeit hopefully easy) addition, which is not very useful without quite a bit of configuration (configuring content sources, some kind of playback control), something that sounds like a job for opkg install ... again.
• light sensor
  I'd look at this in similar way as the proximity sensor, probably a small kmod, outputting its values to sysfs, probably worth including, how to act on its output would be a different question

All of these features are nice and doable (if one can find and integrate the drivers, ideally for mainline as well), but few of them would be very useful for the default images shipping as they are, as neither are really router specific (in the light of a typical off-the-mill router running OpenWrt), require relatively large additions and quite a bit of configuration and new luci-apps. I would suggest to start approaching this with a wiki page (chapter on the existing device page), describing a sensible setup for these features - once that is done (maybe even a community build adding these), the question of integrating the findings can be revisited for OpenWrt's default images, but right now, it's probably too early for that.

As far as the necessary development for any of the 'special features' named above goes, this thread is probably the best location.

Disclaimer: I'm not an OpenWrt developer, not speaking for the project - the above is my opinion only. This is only answering to your request to close this thread (right now) in favour of the more generic device support one - but I can be convinced either way.

[jedboy]

Thanks for the sage advice. There is some chatter on the other thread, so will follow through with that for now. Then, maybe get back to this one.

[ryanrsrs]

Oh, is this the new OnHub thread? I just posted in the other one.

Anyway, I just bought one of these and I like fixing up device tree issues.