Skip to content

rethink-setup provisioning fixes for RTK_RTL8711am module - #131

Open
BluSyn wants to merge 1 commit into
anszom:masterfrom
BluSyn:pr/softap-tls-setup
Open

rethink-setup provisioning fixes for RTK_RTL8711am module#131
BluSyn wants to merge 1 commit into
anszom:masterfrom
BluSyn:pr/softap-tls-setup

Conversation

@BluSyn

@BluSyn BluSyn commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

May be hard to merge this since it touches important setup paths, but hoping it's useful for someone else.

This resolved 2 specific issues:

  • rethink-setup.ts would succeed to provision device, but device doesn't fully join wifi after completion (this took lots of debugging to resolve, this PR adds lots of extra debugging output during setup as a result).
  • After joining wifi, fails to connect to rethink due to weak TLS cipher support (legacy hardware or firmware)

Devices this resolved in testing:

  • LG FV1413H2BA (front load washer)
  • LG RVSX238MC (two-door fridge)

Both devices have RTK_RTL8711am modules, so likely hardware related. Combined these 2 fixes into one PR since they are likely related to same hardware support.

Specific changes:

  • Improves rethink-setup setApInfo with a two-pass scan refine (frequency / security), multiprofile and legacy bssid fields, credential length logging, and delayed releaseDev. (delayed releaseDev is most likely the change that actually fixed the problem)

  • Allow CBC-SHA cipher suites (SECLEVEL=0, min TLS 1.0) on device HTTPS/MQTTS listeners so older CLIP clients can complete /route request. (Note: nginx reverse proxies need the same ciphers if used to terminate 443)

Improve rethink-setup setApInfo with a two-pass scan refine (frequency /
security), multiprofile and legacy bssid fields, credential length
logging, and delayed releaseDev so picky RTK_RTL8711am firmwares join
home Wi-Fi. Allow CBC-SHA cipher suites (SECLEVEL=0, min TLS 1.0) on
device HTTPS/MQTTS listeners so older CLIP clients can complete /route
when terminating TLS on Node.

Note: nginx reverse proxies need the same ciphers if they terminate 443.
@anszom

anszom commented Aug 20, 2026

Copy link
Copy Markdown
Owner

Thank you for the PR. I've just returned from vacation and I'm slowly working through the PR & issue backlog. I'd appreciate your patience :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants