No version for distro humble. Known supported distros are highlighted in the buttons above.
No version for distro iron. Known supported distros are highlighted in the buttons above.
No version for distro rolling. Known supported distros are highlighted in the buttons above.
No version for distro noetic. Known supported distros are highlighted in the buttons above.
No version for distro ardent. Known supported distros are highlighted in the buttons above.
No version for distro bouncy. Known supported distros are highlighted in the buttons above.
No version for distro crystal. Known supported distros are highlighted in the buttons above.
No version for distro eloquent. Known supported distros are highlighted in the buttons above.
No version for distro dashing. Known supported distros are highlighted in the buttons above.
No version for distro galactic. Known supported distros are highlighted in the buttons above.
No version for distro foxy. Known supported distros are highlighted in the buttons above.
No version for distro lunar. Known supported distros are highlighted in the buttons above.
No version for distro jade. Known supported distros are highlighted in the buttons above.
No version for distro indigo. Known supported distros are highlighted in the buttons above.
No version for distro hydro. Known supported distros are highlighted in the buttons above.

telegram_ros package from telegram_ros repo

telegram_ros

Package Summary

Tags No category tags.
Version 0.0.0
License MIT
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/tue-robotics/telegram_ros.git
VCS Type git
VCS Version master
Last Updated 2023-09-06
Dev Status MAINTAINED
CI status Continuous Integration
Released UNRELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

The telegram_ros package

Additional Links

No additional links.

Maintainers

  • Rein Appeldoorn

Authors

No additional authors.

telegram_ros

CI Lint

Bridges between a Telegram conversation and ROS.

Only a single Telegram user can send and receive text, images and locations to/from the ROS bridge. A user must send the /start command to start a conversation. A new user can then /start as well and take over. Once connected, a user can type /stop to disconnect

Currently, there is no authentication (Issue #6)

Installation (from source)

Go to the src directory of your catkin workspace and clone the package from github:

git clone https://github.com/tue-robotics/telegram_ros.git

Install the required dependencies:

rosdep install --from-path -y -i telegram_ros

Compile your workspace

catkin build # or catkin_make (make sure to refresh your workspace env afterwards)

Create a bot

If you don't have a bot yet, chat to BotFather in Telegram to create one. You can provide a name for your bot and you will receive the API token.

Run

rosrun telegram_ros telegram_ros_bridge _token:="YourToken:FromBotFather"

rosparam set /telegram_ros_bridge/whitelist '[1, 2]'  # For the chat IDs that should be allowed

ROS API

Topics

Output

Input

Parameters

  • ~token (string): Telegram BOT API token
  • ~caption_as_frame_id (bool): Whether to put the caption of the image in the frame_id (default: False)
  • ~whitelist (bool or list): False when everyone can use the bot or a list of telegram user IDs that are allowed to talk with the bot (default: False)
CHANGELOG
No CHANGELOG found.

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

Deps Name
1 message_generation
1 message_runtime
1 catkin
1 cv_bridge
0 python3-telegram-bot
1 rospy
0 python-sphinx-autoapi-pip
0 python-sphinx-rtd-theme-pip
2 sensor_msgs
2 std_msgs

System Dependencies

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged telegram_ros at Robotics Stack Exchange

No version for distro melodic. Known supported distros are highlighted in the buttons above.