For exemple:
(I started to read a bit of the codebase, but i had other issues meanwhile)
To what i can see in this class, calling the constructor with a stream implies that you should not call ConnectAsync later.
IMO it should be at least document, or better, the constructor should be a Factory Method.
MqttTcpChannel constructors have different behavior.(I started to read a bit of the codebase, but i had other issues meanwhile)
To what i can see in this class, calling the constructor with a stream implies that you should not call ConnectAsync later.
IMO it should be at least document, or better, the constructor should be a Factory Method.
@paolofulgoni We wan't to use our own logger https://github.com/Invenietis/CK-ActivityMonitor
One of my coworker will do extensive optimisations with the Spans
We don't want to support net461 or UWP, we only need netcore.
One of my coworker will do extensive optimisations with the Spans
We don't want to support net461 or UWP, we only need netcore.
Hi @chkr1011!
I'd like to integrate the MQTTnet Client library to a project.
Is there a best practice for how to handle reconnects?
All I found is this example:
I'd like to integrate the MQTTnet Client library to a project.
Is there a best practice for how to handle reconnects?
All I found is this example:
mqttClient.UseDisconnectedHandler(async e =>
{
Console.WriteLine("### DISCONNECTED FROM SERVER ###");
await Task.Delay(TimeSpan.FromSeconds(5));
try
{
await mqttClient.ConnectAsync(options, CancellationToken.None); // Since 3.0.5 with CancellationToken
}
catch
{
Console.WriteLine("### RECONNECTING FAILED ###");
}
});
I’m trying to send publish messages with QoS1 I’m seeing quite a bit of latency. So I’m trying to establish if there is something wrong in my code or is it because MQTTnet is always waiting for a PubAck before publishing the next item? I’m assuming that the message ordering guarantees come into play, however should that apply only on a per topic basis? Thanks.
Hi, I have been playing with the mqtt API. I have a mosquitto server. I was using standard MQTTnet and followed the examples. I switched to ManagedMqttClient because it diconnected every second. That didn't help. Stil disconnecting. Have any body experienced the same issues?
Hi everyone, I'm making some experiments with Blazor and MQTTnet and created a project for fun
https://github.com/paolofulgoni/MQTTrace
I must say that my main purpose is to learn Blazor a little bit.
If anyone is interested, help is welcome!
Beware: the project is really incomplete!!!
https://github.com/paolofulgoni/MQTTrace
I must say that my main purpose is to learn Blazor a little bit.
If anyone is interested, help is welcome!
Beware: the project is really incomplete!!!
@FrankenApps Take a look at https://github.com/chkr1011/MQTTnet/wiki/Examples, please. There you can find some of my examples that contain authentication.
@mrNo0b You can set the following options:
public string ClientId { get; set; } = Guid.NewGuid().ToString("N");
public bool CleanSession { get; set; } = true;
public IMqttClientCredentials Credentials { get; set; }
public IMqttExtendedAuthenticationExchangeHandler ExtendedAuthenticationExchangeHandler { get; set; }
public MqttProtocolVersion ProtocolVersion { get; set; } = MqttProtocolVersion.V311;
public IMqttClientChannelOptions ChannelOptions { get; set; }
public TimeSpan CommunicationTimeout { get; set; } = TimeSpan.FromSeconds(10);
public TimeSpan KeepAlivePeriod { get; set; } = TimeSpan.FromSeconds(15);
public MqttApplicationMessage WillMessage { get; set; }
public uint? WillDelayInterval { get; set; }
public string AuthenticationMethod { get; set; }
public byte[] AuthenticationData { get; set; }
public uint? MaximumPacketSize { get; set; }
public ushort? ReceiveMaximum { get; set; }
public bool? RequestProblemInformation { get; set; }
public bool? RequestResponseInformation { get; set; }
public uint? SessionExpiryInterval { get; set; }
public ushort? TopicAliasMaximum { get; set; }
public List<MqttUserProperty> UserProperties { get; set; }So, I would say no, that's not possible.
Well, I used this
serverOptions = new MqttServerOptionsBuilder()
.WithDefaultEndpoint()
.WithDefaultEndpointPort(mqttServer.Port)
.WithConnectionValidator(c =>
{
foreach (MqttUser user in mqttServer.Users)
{
if (user.Username == c.Username && user.Password == c.Password)
{
c.ReasonCode = MqttConnectReasonCode.Success;
return;
}
}
c.ReasonCode = MqttConnectReasonCode.BadUserNameOrPassword;
})
.WithSubscriptionInterceptor(c =>
{
c.AcceptSubscription = true;
})
.WithApplicationMessageInterceptor(c =>
{
c.AcceptPublish = true;
})
.Build();and it seems to work for me...
However I honestly do not know if it is secure in any way, but it is fine for my use case.
https://github.com/FrankenApps/MqttDebugger
Made a little Cross-Platform GUI in case anyone is interested. It still lacks a lot of features, but it could basically be viewed as a replacement of Arduino's Serial Monitor via MQTT.
Made a little Cross-Platform GUI in case anyone is interested. It still lacks a lot of features, but it could basically be viewed as a replacement of Arduino's Serial Monitor via MQTT.
Hi everyone, I'm using MqttNet in core 3.1 mvc and connect over 1000 clients and each publish around 200bytes of 7 messages every second. In MVC web, I'm using paho javascript to subscribe some topic and there was delay over and over. At first there is only 2/3 seconds and later go up to several minutes. Is there any way to set up the mqtt broker to send subscriber the last message and dump the old messages. I'd tested WithMaxPendingMessagesPerClient(3) and seem not working at all.
Hi i got docker compose with mosquitto broker, mosquitto exporter connected to grafana , prometheus. When i run docker compose up i can see by default one client is connected and some sample data is displayed in dashboard for mosquitto clients. Usually for two or three clients i login to docker mosquitto broker container and do mosquitto_subscribe to the topic manually. How to subscribe to multiple 100 clients in docker mosquitto broker. All my hubs/ clients are already publishing to the topic and mosqitto broker. If i dont subscribe to the data i dont have data in mosquittodb?. Usually a nodejs or other services consumes the topics. But as of now i dont have the setup i am looking for monitoring side. Any suggestions.
I'm able to successfully subscribe and receive messages, but publishing is only possible immediately after the connection is established.
If i attempt to send a message a few seconds later, i'm getting a success result, but the message is never actuallypublished.
I am however able to keep receiving messages...
The exact same setup works flawlessly from a console app.
If i attempt to send a message a few seconds later, i'm getting a success result, but the message is never actuallypublished.
I am however able to keep receiving messages...
The exact same setup works flawlessly from a console app.
I use MQTTnet to do a MQTT Server, I want to Listen for heartbeats
How can I do it?
？？
Hi, I have what I hope is a simple question. I have a bug that can be explained by the library calling into the various interceptors multiple times in parallel. I always supposed that the interceptors return
Task and library awaits for them to finish before going on processing connections and messages, but it does not seem to be case. So, how is this supposed to work? Can, for example, the connection validator be called a second time while still validating a previous connection?
(obviously my interceptors are async and make use of await)