Sonoff RF bridge with Sonofflan fluctuating between "on" and "unavailable"

Third party integrations
1

Anyone know why this is happening?

image
image632Ɨ1116 53.6 KB

2

Seems about an hour unavailable, and then available again. Did you try to use the bridge when ā€˜unavailableā€™, it might be that it passes the 433Mhz signals through.

3

For the most part it always passes the signal when triggered but the problem is that from time to time itā€™ll get ā€œghost triggersā€ which makes it unusableā€¦

This google geminiā€™s 2 cents:
Hello! Thanks for providing the image, it gives a clear picture of the issue.

The sporadic triggering of your automations is almost certainly due to the Sonoff RFBridge becoming sporadically unavailable and then turning on, as shown repeatedly in your Home Assistant log.

This behavior, where the device rapidly cycles through unavailable and then turned on, is a well-known issue with the Sonoff LAN integration (especially when dealing with RF Bridges) and is often an indication of underlying connection or state management problems.

Here is a breakdown of what is happening and how to fix it:

:mag: The Root Cause

The log entries show a pattern of the RFBridge433 entity state changing from some state (presumably on or off) to unavailable and then almost immediately to turned on.

  1. became unavailable: This happens when Home Assistant briefly loses communication with the RF Bridge. This is often caused by:
  • Brief Wi-Fi drops.
  • The Sonoff LAN integration performing a refresh/reconnect to the eWeLink cloud.
  • Network latency between the device and your Home Assistant server.
  1. turned on: When the device reconnects, the integration might initialize its state to a default value, or a state change event is incorrectly generated. If your automation uses a simple State Trigger for the RF Bridge entity, like ā€œwhen RFBridge433 is turned on,ā€ this spurious turned on event will trigger your automation.

This rapid state cycling is why your automations are firing frequently, but only sometimes an actual RF command is received (when a real trigger occurs, which is masked by these connection events).

It goes on to suggest a way to write the automations yaml in a way that wont get falsely triggered by these fluctuations which I am currently testing (so far so good) but Iā€™m not super keen on having to resort to workarounds so I thought Iā€™d ask if anyone knows whatā€™s going on with this.

4

Canā€™t really help. All my Sonoff Rf Bridges are flashed with OpenMqttGateway.

1 Like