Contact Details

domusonline

Checklist

• I am able to reproduce the bug with the latest version.

• I have updated to the latest Alpha firmware, and am able to reproduce the bug. Many issues are fixed quickly in alpha before the general beta release.

• I made sure that there are no existing OPEN or CLOSED issues which I could contribute my information to.

• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.

• This issue contains only one bug.

• I have read and understood the Contribution Guidelines.

• I agree to follow this project's Code of Conduct

• I actually read this list, and should be taken seriously.

Affected app version

v2.7.14-open.3 (29320672)

Affected Android version

Android 16

Affected phone model

Samsung A34 5G

Affected node model

XIAO KIT nRF

Affected node firmware version

2.7.22

Steps to reproduce the bug

1. Got to "MQTT" module configuration
2. Set the module to active and to use client proxy
3. Test the connection -> It will work stating server accepted credentials
4. Go to "Lora" configuration and deactivate TX (to force MQTT only comms)
5. Try to send a message -> It will fail
6. Check the MQTT module configuration again... there will be errors at the top

Actual behavior

There will be errors.

Expected behavior

The connection should succeed as with previous versions ([v2.7.14-open.1 (29320633) worked)

Screenshots/Screen recordings

See above

Relevant log output

Additional information

[v2.7.14-open.1 (29320633) worked. I believe open.2 didn't (will eventually test). Open.3 definitely doesn't work.
I'm trying to see if I can captur "adb" logs... not sure if I have it or will have to install something... Need some time.