Fix null client when using MDNS.#981
Conversation
|
Same, I will dig deeper into this after work today. |
|
Thanks, I got quick on pushing this, I see the issue and I'll push the update shortly. |
|
This nailed it, tks Am recommending that this get merged into the current development branch |
|
Tks |
|
@h2zero Finally got some time today to validate this further and look at the MQTT Discovery messages in the log fragment I shared and the various topics, they are missing the gateway name. |
|
At least the crash is solved 😄. The gateway name is an odd issue, changes were made to this area, I'm not sure why this would happen though. I'll do some work on it, thanks for the report. |
|
Agreed on the crash |
|
@NorthernMan54 I believe I have resolved the missing gateway name, could you test this branch https://github.com/h2zero/OpenMQTTGateway/tree/bugfix/gateway-name ? If it works for you I will PR it asap. |
|
Just updated my test device, and am getting this, which is great ;-) |
|
Thanks, I will PR it now. |
When using MDNS the client was not initialized prior to the call to connect. This ensures initialization before the call.