Emil Tin
Emil Tin
Hi, did you get a chance to look into this?
Than you for looking into it. I think emqt needs to replace alias with the correct topic? I don't feel it makes sense to push the responsibility for handling aliases...
Emqtt can already correctly replace topic aliases with the full topic, so the mechanism is there. It just stops working after a reconnect. I hope this can be fixed in...
Yes, I'm using emqtt for for publisher and subscriber, and EMQT as the broker. * emqtt 1.11.0 (https://github.com/emqx/emqtt.git) (rebar3) locked at c815a18 > strange, I don't see emqtt has this...
I can handle topic aliases with this little helper (Elixir code): ```elixir defmodule MyApp.AliasCache do def new, do: %{} def handle(alias_cache, publish) do case publish do %{topic: "", properties: %{"Topic-Alias":...
> You called publish API more times(with only Topic-alias set) I'm never publishing with only topic alias set.
OK, I will do that. Perhaps I can create a reduced code example. Thank you!
I asked in the emqx repo: https://github.com/emqx/emqx/discussions/12929
I assume --reconnect refers to the CLI tool? I'm using emqtt as a library. Does it work the same when using the reconnect option? If I understand you correctly, emqtt...
Thank you for the reply, very helpful. If I implement buffering myself, I will need to know when a message has been delivered. You mention callbacks, but I don't see...