[Bug]: Saving MQTT config via web interface on Heltec v3 doesn't work

[Calimerorulez]

Category

Other

Hardware

Heltec V3

Firmware Version

2.3.1

Description

Trying to save MQTT config via web interface doesn't work.

Relevant log output

Console output Chrome:

index-nsbd6Oaw.js:84 Uncaught (in promise) TypeError: o.toBinary is not a function
    at zg (index-nsbd6Oaw.js:84:14940)
    at Vg (index-nsbd6Oaw.js:84:14228)
    at Object.writeMessage (index-nsbd6Oaw.js:84:11921)
    at i.toBinary (index-nsbd6Oaw.js:83:29735)
    at zg (index-nsbd6Oaw.js:84:14940)
    at Vg (index-nsbd6Oaw.js:84:14228)
    at Object.writeMessage (index-nsbd6Oaw.js:84:11921)
    at i.toBinary (index-nsbd6Oaw.js:83:29735)
    at zg (index-nsbd6Oaw.js:84:14940)
    at Vg (index-nsbd6Oaw.js:84:14228)

[yaleman]

I'm getting the same issue on T-Beam 2.3.6.7a3570a Beta ..

[kdkd]

I can confirm the same problem. I think commit 6113924 broke it. Rolling it back allows me to enable MQTT now.

[Obliterous]

I can confirm this is still broken with latest version as of June 19th.

[Hunter275]

@Obliterous What firmware are you on and are you using https://client.meshtastic.org ?

[Obliterous]

@Obliterous What firmware are you on and are you using https://client.meshtastic.org ?

2.3.10.d19607b

Yes.

[Hunter275]

@Obliterous Can you update to 2.3.11 and lmk if this bug persists, I cannot replicate it on 2.3.11

[Obliterous]

2.3.11.2740a56 Beta installed, still unable to save mqtt config. if I change & save any other setting for any other module, it will save those changes again without retaining MQTT changes.

[Obliterous]

update: it always triggers a save of SERIAL settings, even if others have been changed. Changes to MQTT settings are not retained.

[Obliterous]

Additional; after updating to 2.3.11.2740a56, I am no longer able to connect via BT.

EDIT; NVM, I'm an idiot here. had wifi enabled.

[dmanierre]

I'm also facing the same issue, I tried with 2.3.11 and 2.3.12 I was just trying to toggle the Enable slider on the MQTT tab and save but can't get the changes to stick. I'm also using https://client.meshtastic.org/

[Hunter275]

The issue is in the toBinary() call when preparing to send the moduleConfig to the device. I believe it is failing due to the model for MQTT config being incorrect.

Working on a fix.

[Hunter275]

I can confirm the same problem. I think commit 6113924 broke it. Rolling it back allows me to enable MQTT now.

6113924

[Hunter275]

@dmanierre @Obliterous @kdkd @yaleman @Calimerorulez

Can you please try this build: https://web-asz33wey0-meshtastic.vercel.app/

[MidlifeRenaissanceMan]

Seems to have worked on a V3 433MHz board running a5a37cd using an old Chrome Version 103.0.5060.53 (Official Build) (64-bit) on CentOS7. I seem to have some other problems, but I'll try it on a few different V3 units I have.

edit: USB Serial connect

[Hunter275]

@MidlifeRenaissanceMan other problems?

[MidlifeRenaissanceMan]

As I suspected. Antenna issues. Not software