Skip to main content

Travel Routers Part 7 - HooToo Tripmate Original

The first of the 2 HooToo travel routers arrived today and at first glance it looks similar to the RavPower. The front has a button with a quick battery level indicator and a WiFi/active indicator.

HooToo Tripmate Original
Battery - 6000mAH (quick press the power button to see power level) While the documentation calls it an "external battery" it seems to also power the router.
Ports - mini USB for charging the battery, USB port for charging other devices and flash drives, RJ45 ethernet port.
Modes - Access Point, bridge, file server
GUI - web admin, smartphone app
Default SSID - Tripmate-XXXX
Default password - 11111111
Default IP Address - 10.10.10.254
Default uid/pwd - admin/(no password)
Manual: link

** The only difference between the HooToo HT-TM01 is the SD Cardslot, the size of the device, the theme of the web interface. I originally thought that the web interface theme was different, however, it's not.  In fact the GUI is exactly the same as the RavPower. The one difference is that (a) the WiFi LED colors are inverted from the RavPower and several of the pages are returning server 501 errors. Looking at the download page I see that the version numbers are also identical.

After doing a little research I was able to determine that the support phone number is identical between the two companies(ravpower, hootoo).

UPDATE: Correction; the webui has a different theme. It turns out that my browser was caching too much from the original router. Clearly the admin tool did not set the TTL or cache aging correctly. Well, they are the same device but for the SD card. I'm going to assume that they are the same under the covers.

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…