Loading...
Modbus TCP Relay · Modbus TCP I/O
This module is intended for Modbus TCP relay and digital input devices that expose:
The module now provides:
This module should work well with Waveshare devices that present:
5021That includes the common Waveshare Ethernet/PoE relay family where the device behaves like a standard Modbus TCP relay controller rather than needing a vendor-specific API.
Searching for Waveshare in Companion should also surface this module.
These defaults should work for common Waveshare relay boards:
50210808If your device uses different Modbus addressing, adjust the start addresses and counts to match its register map.
Testing against a Waveshare unit on this system showed that Read Coils responded correctly at coil start address 0, but timed out for offsets such as 1, 2, 7, 8, 16, and higher.
For Waveshare boards like this one, you should keep:
Coil (Relay) start address: 0If changing the coil offset causes timeouts instead of a Modbus exception, that usually indicates the device only responds on the base coil map starting at 0.
Use these settings as a starting point:
192.168.x.x502108false500Recommended Companion usage:
Toggle coil (relay) 1 to Toggle coil (relay) 8 presetsAll coils (relays) on and All coils (relays) off presets for master controlCoil (relay) is on feedback on custom buttons if you want state indicationPulse coil (relay) action if the output should behave momentarilyUse these settings as a starting point:
192.168.x.x502108true08250Recommended Companion usage:
Digital input is active feedback to show input state on buttons$(instance:input_1) and $(instance:input1_status) in labels or triggersThis module does not assume Waveshare-specific toggle commands. For compatibility with generic Modbus devices, toggle actions are implemented by reading the current state and then writing the inverse state.
Generic
CommunityGeneric
CommunityGeneric
CommunityGeneric
Community