No Topic Visible if running micro ros agent on Humble, but these are visible if the agent is running on Foxy

Nobody has claimed this yet.

## No Topic Visible if running micro ros agent on Humble, but these are visible if the agent is running on Foxy

- Hardware description: Linux and ESP32
- RTOS: -
- Installation type: micro_ros_setup
- Version or commit hash: Humble

#### Steps to reproduce the issue
I have followed the tutorial from the links below:
https://micro.ros.org/docs/tutorials/core/first_application_linux/
https://micro.ros.org/docs/tutorials/core/teensy_with_arduino/

The issue is, if I run the micro ros agent on ROS Humble (both serial or udp), I don't see any topics and nodes related. But in -v6 I am able to see the data is publishing.

The thing is, I am able to subscribe it through node. But I am not able to see the topic list in the terminal.

I have tried unset ROS_DOMAIN_ID, set the same ROS_DOMAIN_ID, set the same RMW_IMPLEMENTATION, unset the RMW_IMPLEMENTATION. But nothing works.

Then I tried to use foxy to run micro ros agent (using docker ros-foxy), I am able to see the topic list on Humble. And I also able to echo it. as you can see the picture below


#### Expected behavior
I should be able to see the topic list, while the micro ros agent runs in the Humble.

#### Actual behavior
Unable to see the topic list, while the micro ros aget runs in the Humble.

#### Additional information
This is my env, even if I didn't set the same ROS_DOMAIN_ID, and didn't set the RMW_IMPLEMENTATION, if I run the agent on Foxy, it still work and detected on Humble 

Start by reproducing the issue with the micro-ROS Agent on ROS 2 Humble and compare its -v6 output with the Foxy Docker setup, using both serial and UDP as described. Check the ROS_DOMAIN_ID and RMW_IMPLEMENTATION variations from the report. Done means topics and nodes are discoverable and can be echoed when the agent runs on Humble.

Written by the indexing model from the issue text.