Relay seemingly not pulling MQTT messages?

[Serafeline]

Using relay commands as described in README.md.

Agents on device A are visible on device B, and vice-versa according to hcom TUI. Both devices show hcom relay status as being connected and up to date, with both devices present.
When sending a message to a remote agent as, say, lase:BABA, the message is pushed correctly, as per hcom TUI, and the command returns no errors; but the remote agent device never shows any sign of life coming from the other device on the relay within its TUI or agent.
When attempting to send a message via TUI to a remote agent, the TUI shows an error stating that the agent does not exist. I also noticed that within the TUI, remote agents are shown in the format lase:BABA:F0F0, which does not work for sending messages via CLI.

Would appreciate if anyone else could repro. Thanks.

P.S. This is an amazing tool and I hope it stays active. :)

[aannoo]

should be fixed in 0.7.21

[Serafeline]

Will confirm shortly

[Serafeline]

Still having the same issue on my end after updating to v0.7.21 I'm afraid.

What I've noticed is that when joining a relay, all devices become visible, but the devices already on the relay can't see any newly joined devices. Tested both ways and this seemed to be the case. Further, if the hcom relay connect tokengoeshere command is sent again from the relay host, it can then see the newly joined devices/agents, but the other device seems never receives any sent messages (though they report as sending successfully on the host, no sign of interaction can be seen on the client), and attempting to list messages from the host on the client device states the the device is no longer connected but was last seem around the same time I reissued the connect command on said host.