Add RAK4631 PoE + Ethernet companion support (W5100S/RAK13800) 🤖🤖#2679
Open
1sthandy wants to merge 1 commit into
Open
Add RAK4631 PoE + Ethernet companion support (W5100S/RAK13800) 🤖🤖#26791sthandy wants to merge 1 commit into
1sthandy wants to merge 1 commit into
Conversation
1sthandy
force-pushed
the
feature/rak4631-poe-ethernet-companion
branch
from
322fc9d to
57a9988
Compare
Adds support for running a RAK4631 over PoE using the RAK13800 (W5100S)
Ethernet module on a RAK19018 base, in two roles:
- PoE repeater: powers up reliably on the RAK19018 (Silvertel) converter.
The cold-start path is shortened and CPU sleep is disabled, because
dropping below the converter's hold current makes it fold back and
reset. Boot-voltage protection is bypassed when battery-less on PoE.
- Ethernet companion: exposes the MeshCore companion protocol as a TCP
server (default port 5000) over the W5100S, so Home Assistant connects
to the device's IP. Uses a static IP to avoid blocking DHCP at cold
start. W5100S PHY bring-up is deferred out of setup() into loop() to
avoid collapsing the marginal PoE supply during the cold-start window.
New files:
- src/helpers/SerialEthernetInterface.{cpp,h}: TCP transport for the
companion serial frame protocol.
- variants/rak4631/W5100SPoE.{cpp,h}: W5100S power/reset + init helper.
New platformio envs:
- RAK_4631_repeater_poe (+ _debug)
- RAK_4631_companion_radio_eth
All additions are guarded by WITH_W5100S_POE / WITH_ETHERNET_COMPANION,
so existing RAK4631 builds are unaffected.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1sthandy
force-pushed
the
feature/rak4631-poe-ethernet-companion
branch
from
57a9988 to
e513038
Compare
|
Is this duplicating the work in #1983 ? I believe these are both targeting the same hardware, no? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds support for running a RAK4631 over PoE using the RAK13800 (W5100S) Ethernet module on a RAK19018 base, in two roles:
RAK_4631_repeater_poe,+_debug): boots reliably on the RAK19018 (Silvertel) converter. The cold-start path is shortened and CPU sleep is disabled, because dropping below the converter's hold current makes it fold back and reset. Boot-voltage protection is bypassed when battery-less on PoE.RAK_4631_companion_radio_eth): exposes the MeshCore companion protocol as a TCP server (default port 5000) over the W5100S, so Home Assistant connects directly to the device's IP. Uses a static IP to avoid blocking DHCP at cold start. W5100S PHY bring-up is deferred out ofsetup()intoloop()to avoid collapsing the marginal PoE supply during the cold-start window.New files
src/helpers/SerialEthernetInterface.{cpp,h}— TCP transport for the companion serial-frame protocol.variants/rak4631/W5100SPoE.{cpp,h}— W5100S power/reset + init helper.New PlatformIO envs
RAK_4631_repeater_poe(+RAK_4631_repeater_poe_debug)RAK_4631_companion_radio_ethSafety / impact
All additions are guarded by
WITH_W5100S_POE/WITH_ETHERNET_COMPANION, so existing RAK4631 builds are unaffected.Testing
Tested on real hardware (RAK4631 + RAK13800 + RAK19018):