Hello,
I recently got a couple of Waveshare Modbus POE ETH Relay (C) and tried, in different times, either to add one of them in configuration.yaml like the following example, or by installing the integration found at GitHub - icecoldfire/HomeAssistant-Waveshare-Relay: This is a custom integration for Home Assistant to control the Waveshare Modbus POE ETH Relay Board. It allows you to control relay channels and configure flash intervals directly from Home Assistant. after doing the required changes with VirCom accordingly.
homeassistant:
modbus:
- name: ws-relay-1
type: rtuovertcp
host: wsrelay1.iot.internal
port: 4196
timeout: 9
switches:
- name: WS1-CH1
slave: 1
address: 0
write_type: coil
- name: WS1-CH2
slave: 1
address: 1
write_type: coil
- name: WS1-CH3
slave: 1
address: 2
write_type: coil
- name: WS1-CH4
slave: 1
address: 3
write_type: coil
- name: WS1-CH5
slave: 1
address: 4
write_type: coil
- name: WS1-CH6
slave: 1
address: 5
write_type: coil
- name: WS1-CH7
slave: 1
address: 6
write_type: coil
- name: WS1-CH8
slave: 1
address: 7
write_type: coil
binary_sensors:
- name: WS1-DI1
slave: 1
address: 0
input_type: discrete_input
scan_interval: 1
- name: WS1-DI2
slave: 1
address: 1
input_type: discrete_input
scan_interval: 1
- name: WS1-DI3
slave: 1
address: 2
input_type: discrete_input
scan_interval: 1
- name: WS1-DI4
slave: 1
address: 3
input_type: discrete_input
scan_interval: 1
- name: WS1-DI5
slave: 1
address: 4
input_type: discrete_input
scan_interval: 1
- name: WS1-DI6
slave: 1
address: 5
input_type: discrete_input
scan_interval: 1
- name: WS1-DI7
slave: 1
address: 6
input_type: discrete_input
scan_interval: 1
- name: WS1-DI8
slave: 1
address: 7
input_type: discrete_input
scan_interval: 1
I’m getting different results when it comes to automations: in the first scenario, lights connected to WS1-CH1 will not turn immediatly but only after WS1-DI1 is pulled high for about 1.5s. Changing to a lower scan_interval causes this to stop working at all.
When using the integration, I can control channels and intervals directly from it, and see that timers are responding as buttons connected to DI are pressed, but if I create an automation and select, for example, timer 1 value change as condition and switch 1 toggle as action, nothing happens at all on button press.
Is this setup known to be broken/unreliable?
Is what I’m reading here agreeable?
Just to clarify, I’m running HAOS on Proxmox and the momentary switches used for testing this waveshare module are from btcino.