RogerThat currently works on Linux/Mac Intel and Windows. Mac M1 is not currently supported. It has been tested on Mac Intel and Ubuntu 18.04, 20.04, 22.04.
RogerThat is a standalone python web server designed to receive TradingView alerts (or similar) and forward them to Hummingbot.
TradingView is a widely used market market tracker that allows users to create, share and use custom strategies but is quite limited in how it can be "plugged in" or connected to other services. It does however allow the creation of "Alerts" which can send data to a Webhook (requires a public-facing URL).
RogerThat facilitates the collection and forwarding of these TradingView Alerts to Hummingbot via the MQTT Bridge module, which listens to RogerThat via subscribed MQTT topics.
Whilst RogerThat's purpose is to bridge TradingView and Hummingbot, it can work as a gateway / bridge between any service that sends data via Webhooks (to a public URL) and serve / route them to multiple Hummingbot instances or connected MQTT clients.
BTC address
bc1qpq4djuxgxsk0zrkg9y2rye8fyz7e0mjx64gzq0
Install Docker Engine.
General Steps
Install Docker Engine (Headless servers)
Debian/Ubuntu Steps
First, you need to make sure your system is up-to-date. Do this by running the following commands:
sudo apt-get update && sudo apt-get upgradeNext, uninstall any existing versions:
sudo apt-get remove docker docker-engine docker.io containerd runcNext, install some necessary packages that Docker needs:
sudo apt-get install apt-transport-https ca-certificates curl software-properties-common gnupgAdd the GPG key for Docker's official repository to your system:
sudo install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/debian/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
sudo chmod a+r /etc/apt/keyrings/docker.gpgAdd Docker's repository to your APT sources:
echo \
"deb [arch="$(dpkg --print-architecture)" signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian \
"$(. /etc/os-release && echo "$VERSION_CODENAME")" stable" | \
sudo tee /etc/apt/sources.list.d/docker.list > /dev/nullUpdate the package database with Docker packages from the newly added repo:
sudo apt-get updateNow you can install Docker:
sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-pluginDocker should now be installed, the daemon started, and the process should run on boot. You can verify this by checking the service's status:
sudo systemctl status dockerUse this command to create the Docker group if it doesn't exist:
sudo groupadd dockerUse this command to add the current user to the Docker group:
sudo usermod -aG docker $USERThis command will make the changes effective without having to log out and log back in:
newgrp dockerDownload and extract this whole repository.
Linux/Mac
wget https://github.com/TheHolyRoger/RogerThat/archive/refs/heads/master.zip
unzip master.zipChange directory:
cd RogerThat-masterError - Failed to create tables you can resolve it by following these steps. Press Ctrl + C to exit the program, and then start it again. This should help resolve the issue.
scripts directory
Windows
Manually download and extract the repository zip file.
Open up Windows CMD and switch directory to the extracted zip folder.
scripts directory
Then run the following commands to launch the docker image:
Linux/Mac
./scripts/start_docker.shWindows
Use git bash only for git commands, do not run RogerThat scripts from git bash as they will not work.
scripts\start_docker.batLinux/Mac
./scripts/start_docker.shOR as daemon (in background):
./scripts/start_docker.sh -dWindows
scripts\start_docker.batOR as daemon (in background):
scripts\start_docker.bat -dUpon successful launch, navigating to http://localhost/ (or your public domain) in your browser will show a 404 not found page.
Press ctrl+c if running interactively, or run the following command to stop RogerThat:
docker compose stopEdit the configuration files in ./configs as needed.
Localhost, Non-Docker Broker
If running a MQTT broker locally (not docker) you should be able to use localhost as your mqtt_host:
...
mqtt_host: localhost
...Localhost, Docker Desktop based Broker
Running a MQTT broker via Docker Desktop (not advised) you should be able to use host.docker.internal as your mqtt_host:
...
mqtt_host: host.docker.internal
...Localhost, Docker Engine based Broker
Use the setup command as below to automagically find your EMQX hostname and update compose and config files:
Linux/Mac
scripts/setup_config.sh --setup-emqx-docker-hostnameWindows
scripts\setup_config.bat --setup-emqx-docker-hostnameManual Steps if script fails
Running a MQTT broker via Docker in a Linux box on the same host (e.g. the default hummingbot EMQX setup) you'll need to add rogerthat to the same docker network.
To find the name of the docker network run the command:
docker network lsYou should see something like:
e872661fddcc hummingbot_broker_emqx-bridge bridge local
The network name in this example is hummingbot_broker_emqx-bridge.
Edit the docker-compose.yml file in the root directory.
Add the emqx network to the network list at the bottom like this:
...
networks:
rogerthat-bridge:
driver: bridge
hummingbot_broker_emqx-bridge:
external: true
Add the emqx network to the rogerthat service like this:
...
entrypoint: ["/home/rogerthat/docker_compose_entrypoint.sh"]
networks:
- rogerthat-bridge
- hummingbot_broker_emqx-bridge
...Now run the following command to find the hostname of your MQTT broker replacing hummingbot_broker_emqx-bridge as needed:
docker network inspect hummingbot_broker_emqx-bridgeYou will see the hostname of the MQTT broker in the output like this:
"Containers":
{
"eb1d17a525cb06a863d10f227cdf7edcd713371fe3f699921360b7b23c512c78":
{
"Name": "hummingbot_broker-emqx1-1",
"EndpointID": "8d8c81332a0284e76246bf0bb19d25987e255d9cf9c43cdeed7df9f5ea436cde",
"MacAddress": "02:42:ac:13:00:02",
"IPv4Address": "172.19.0.2/16",
"IPv6Address": ""
}
}Where hummingbot_broker-emqx1-1 is the hostname of the MQTT broker in this example.
You can then edit your configs/gateway_mqtt.yml file and add the service name e.g. hummingbot_broker-emqx1-1 as your mqtt_host:
...
mqtt_host: hummingbot_broker-emqx1-1
...For certain special tasks, you can use the config setup script via docker by running the following commands:
Linux/Mac
scripts/setup_config.sh --helpscripts/setup_config.sh.
Windows
scripts\setup_config.bat --helpscripts\setup_config.bat.
Expand ...
Since TradingView requires a publicly accessible URL for webhook alerts, you'll need to use your own domain name, or your public IP address.
You'll also need to open up (and forward) port 80 (or 443 if using HTTPS) in your firewall/router to the machine running RogerThat.
It is recommended to use Cloudflare proxied with HTTPS to mask your IP address.
Expand ...
Change the hostname to listen on for the public TradingView webhook with the following commands:
(Do not use a full URL here, the hostname is the part of the URL after https:// and before any other slashes)
Linux/Mac
scripts/setup_config.sh --hostname yourhostname.com
scripts/setup_config.sh --hostname 1.2.3.4Windows
scripts\setup_config.bat --hostname yourhostname.com
scripts\setup_config.bat --hostname 1.2.3.4If using your own domain name, it is recommended to use a long and not obvious subdomain as the hostname eg: thereisnotraderhere.mydomain.com.
Expand ...
It is recommended to use Cloudflare to proxy and mask your IP address in production since public access must be exposed.
You can use services like DNS-o-matic with your home dynamic IP to keep it updated and proxied with Cloudflare.
Expand ...
Services you can use for dynamic DNS with a non-static public IP address are:
- DNS-O-matic (Recommended, with Cloudflare)
- No-IP
- Afraid
- Duck DNS
- Dynu
Expand ...
To setup (LetsEncrypt run the following commands.
Linux/Mac
scripts/generate_cert_letsencrypt.shWindows
scripts/generate_cert_letsencrypt.batOr run the following command to generate a self-signed key pair:
Linux/Mac
scripts/generate_cert_self_signed.shWindows
scripts\generate_cert_self_signed.batAfter enabling HTTPS you can now forward port 443, close port 80 and start RogerThat.
Set up your TradingView alert URL like this:
http://<public-ip-or-domain-name>/api/tv_webhook/?api_key=<tradingview-apikey>Where <public-ip-or-domain-name> is your domain name or public IP address and <tradingview-apikey> is the generated api key found in web_server.yml under api_allowed_keys_tv.
Alerts must be formatted as JSON, the only required parameter is topic.
The topic key must be present in the JSON data to be accepted.
Example alert data:
Adjusting the Bid and Ask Spreads
{
"topic": "hbot/hummingbot_instance_1/command_shortcuts",
"params": [
["spreads", "1", "1"]
]
}Simple Start command
{
"topic": "hbot/hummingbot_instance_1/start",
"log_level": "DEBUG"
}Simple Stop command
{
"topic": "hbot/hummingbot_instance_1/stop",
"skip_order_cancellation": false
}Advanced alert with all fields using Pine variables
{
"topic": "hbot/hummingbot_instance_1/external/events/my_event",
"type": "external_event",
"timestamp": "{{timenow}}",
"sequence": "{{timenow}}",
"data": {
"exchange": "{{exchange}}",
"symbol": "{{ticker}}",
"interval": "{{interval}}",
"price": "{{close}}",
"volume": "{{volume}}",
"position": "{{strategy.market_position}}",
"inventory": "{{strategy.order.comment}}"
}
}Connect the Hummingbot MQTT Bridge and RogerThat to the same MQTT Broker.
Example Config ...
Use something like the following config to connect RogerThat to Hummingbot via the MQTT Bridge.
This config is found inside your main hummingbot folder then conf\conf_client.yml
# Remote commands
mqtt_bridge:
mqtt_host: localhost
mqtt_port: 1883
mqtt_autostart: true
Expand ...
Command shortcuts can be defined in Hummingbot's conf_global.yml, for more information see here: https://docs.hummingbot.io/operation/config-files/#create-command-shortcuts
Test Connection ...
To test basic connection, use any MQTT client and connect to the same broker as RogerThat, then subscribe to the rogerthat/# topic.
There is also a small python script in the examples/ folder which can be used to mimic a TradingView alert. You'll then see the MQTT message if you subscribe to your chosen topic.
