rstrouse
Wind sensor low battery not communicated to HA, but radio logs show event is received and seen by espsomfy.
Describe you new feature you'd like
When the wind sensor detects wind, it successfully communicates the binary sensor on in HA. Subsequently, when the wind sensor sees the wind stop, it successfully communicates binary sensor off in ha. Later on when a battery low event is sent via RTS the wind sensor sends another wind off event identical to the previous one, the only difference is this wind off event was not preceded by wind on. This process repeats approximately every 20 minutes. The wind sensor sends another wind off event. These are all seen in the radio logs. So basically the only way to differentiate in the radio logs between an actual wind event and a low battery event is that the actual wind event shows wind on, followed by wind off, meaning just a pair of two events, whereas the low battery event repeats every 20 minutes. Just the wind off event, and then 20 minutes later wind off, and 20 minutes later wind off.
When we look at this on the HA side the only things we see is the initial pair of wind on, wind off. We never see in the HA side anything for the low battery, meaning the wind off repeating every 20 minutes never appears there. It's missing entirely.
I think what's happening here on the firmware side is that it knows the binary sensor state was already off so when it sees the wind off event it thinks oh there's nothing that needs to change so we don't need to transmit this to HA.
In the radio logs the code column is 1 for wind detected, then 0 for no wind. But for low battery the code column is always 0.
I would like a method where ha can detect low battery. This could be derived easily if each of the states for the binary sensor was resent every 20 minutes when it sets it to zero again even though it's already zero. I tried using developer tools on ha to set the binary sensor to unknown. However, when the zero code was received over RTS, it stayed unknown on the ha side.
This is showing code number 1 for wind detected (Time 22:00) followed by code 0 for wind no longer detected. (Time 22:01)
This is showing the 20-minute Time Gap between consecutive low battery events. Time= 23:38-23:58