lerobot-record

[qinglin-ai]

When validating with the lerobot-record command, I encountered "INFO 2025-11-06 09:47:59 t_record.py:336 No policy or teleoperator provided, skipping action generation. This is likely to happen when resetting the environment without a teleop device. The robot won't be at its rest position at the start of the next episode."

[hachimada]

@qinglin-ai

I think you need to specify --teleop.type, --teleop.port, and --teleop.id. Without these options, I saw the same error. Once you include them, you should be able to reset the robot’s position with teleop robot after running the policy.

For example:

lerobot-record \
--robot.type=so101_follower \
--robot.port=/dev/ttyACM1 \
--robot.id=so101_follower_arm 
--robot.cameras="{ front: {type: opencv, index_or_path: /dev/video2, width: 640, height: 480, fps: 30}}" \
--display_data=true \
--dataset.repo_id=${HF_USER}/eval_xxx\
--dataset.single_task="xxx" \
--policy.path=${HF_USER}/xxx \
--teleop.type=so101_leader \
--teleop.id=so101_leader_arm 
--teleop.port=/dev/ttyACM0

[qinglin-ai]

@qinglin-ai

I think you need to specify --teleop.type, --teleop.port, and --teleop.id.我认为你需要指定 --teleop.type 、 --teleop.port 和 --teleop.id 。 Without these options, I saw the same error.如果没有这些选项，我看到了同样的错误。 Once you include them, you should be able to reset the robot’s position with teleop robot after running the policy.一旦你包含它们，你应该能够在运行策略后用 teleop robot 重置机器人的位置。

For example:  例如：

lerobot-record
--robot.type=so101_follower
--robot.port=/dev/ttyACM1
--robot.id=so101_follower_arm --robot.cameras="{ front: {type: opencv, index_or_path: /dev/video2, width: 640, height: 480, fps: 30}}"
--display_data=true
--dataset.repo_id=${HF_USER}/eval_xxx
--dataset.single_task="xxx"
--policy.path=${HF_USER}/xxx
--teleop.type=so101_leader
--teleop.id=so101_leader_arm --teleop.port=/dev/ttyACM0

Thank you for your suggestion

[Yyl-Sylmi]

May be you can try pressing the right arrow key.