You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firmware Versions tested: Room Server / Companion Radio
OS: Ubuntu Linux (using Screen/Web-Serial)
The Issues
I am currently setting up a mesh network and facing several hurdles regarding the "Room Server" firmware compared to the "Companion" firmware.
WiFi Configuration on Room Server:
I am unable to set WiFi credentials on the Room Server firmware via the Serial Console. Commands like set wifi.ssid or wifi set result in "Unknown command".
Is WiFi configuration supported via CLI in the Room Server build?
Is there a way to trigger a Captive Portal (AP Mode) via hardware buttons?
Does the Room Server require WiFi credentials to be hardcoded during the flashing process (NVS), or is there a runtime configuration method?
Role Clarification (Room Server vs. Companion):
Does the Room Server act as a transparent repeater by default?
Why does the Room Server not show up in the Node List (0 hops) of a Companion device, even when in close range? Is it "silent" by design?
Does the Room Server support the "Store & Forward" feature for offline participants, or is it strictly a web-interface/MQTT bridge?
Connectivity:
Despite flashing with SSID/Password provided in the web flasher, the device does not consistently connect to a standard 2.4GHz WPA2 network.
Are there specific logs I can enable to debug the WiFi handshake?
Is there a specific "Save" command required beyond the initial flash to persist WiFi settings?
Sending Data via Room Server:
Is it possible to actively send messages/data directly from the Room Server (e.g., via the web interface)?
My goal is to avoid running two devices in parallel at home (one Room Server for the infrastructure/repeating and one Companion/Client just for sending). Can the Room Server handle both tasks simultaneously?
Goal
I want to use the Room Server as a permanent backbone/repeater that allows users to sync missed messages, while also using it to send messages myself. Any guidance on the correct CLI commands or flashing procedure for WiFi would be greatly appreciated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Body:
Device & Environment
Hardware: Heltec V3 / V4 (ESP32-S3)
Firmware Versions tested: Room Server / Companion Radio
OS: Ubuntu Linux (using Screen/Web-Serial)
The Issues
I am currently setting up a mesh network and facing several hurdles regarding the "Room Server" firmware compared to the "Companion" firmware.
I am unable to set WiFi credentials on the Room Server firmware via the Serial Console. Commands like set wifi.ssid or wifi set result in "Unknown command".
Is WiFi configuration supported via CLI in the Room Server build?
Is there a way to trigger a Captive Portal (AP Mode) via hardware buttons?
Does the Room Server require WiFi credentials to be hardcoded during the flashing process (NVS), or is there a runtime configuration method?
Does the Room Server act as a transparent repeater by default?
Why does the Room Server not show up in the Node List (0 hops) of a Companion device, even when in close range? Is it "silent" by design?
Does the Room Server support the "Store & Forward" feature for offline participants, or is it strictly a web-interface/MQTT bridge?
Despite flashing with SSID/Password provided in the web flasher, the device does not consistently connect to a standard 2.4GHz WPA2 network.
Are there specific logs I can enable to debug the WiFi handshake?
Is there a specific "Save" command required beyond the initial flash to persist WiFi settings?
Is it possible to actively send messages/data directly from the Room Server (e.g., via the web interface)?
My goal is to avoid running two devices in parallel at home (one Room Server for the infrastructure/repeating and one Companion/Client just for sending). Can the Room Server handle both tasks simultaneously?
Goal
I want to use the Room Server as a permanent backbone/repeater that allows users to sync missed messages, while also using it to send messages myself. Any guidance on the correct CLI commands or flashing procedure for WiFi would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions