@mfalkvidd it's working, but i think in not pro way - why ? you need create separate channel for communicastion ( for security point it's ok ) but if you have many nodes and you want exchange some informasion insite network it't will be not working you need some integrasion ex domoticz, hassio etc bo some think chane in other node. Maybe you add this option to change node_id in mqtt gatway ?

@mfalkvidd
MY_MQTT_CLIENT_ID was rewrite for other device

so if I good understand, the best options is use dedicated channel for communication

ex:
arduino00:
MY_MQTT_PUBLISH_TOPIC_PREFIX=mysensors-in00
MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "mysensors-out00
domoticz for ex:
new: mysensor gateway mqtt with TOPIC : mysensors-${in/out}00

arduino01
the same action but change 00->01

@mfalkvidd
why node ID need to be 0 ? I want to have a few node ( different localization ) and all arduino node should be have unical node_id but only sketch name can by unical.

I'm using MY_GATEWAY_MQTT_CLIENT

Hi,
Can someone help with moving from dynamic cfg ( mysensor discovery ) to static mqtt cover cfg

mysensors:
    gateways:
      - device: 'mqtt'
        topic_in_prefix: 'mysensors-in'
        topic_out_prefix: 'mysensors-out'
        persistence_file: '/opt/homeassistant/mysensors.json'
    optimistic: false
    persistence: true
    retain: true
    version: '2.3'

cover.yaml:

  - platform: mqtt
    name: "${cover.name}"
    command_topic: "mysensors-in/${nodeid}/${cover.id}/1/0/3"
    state_topic: "mysensors-in/${nodeid}/${cover.id}/1/0/3"
    qos: 0
    retain: true
    position_open: 100
    position_closed: 0

mysensors.json

{
    "0": {
        "sensor_id": 0,
        "children": {
            "1": {
                "id": 1,
                "type": 5,
                "description": "",
                "values": {
                    "30": "1",
                    "3": "0",
                    "31": "1"
                }
            },```
...

how should look currect
command_topic
state_topic
set_position_topic
position_topic