RFXTRX Integration implausibe and sporadically jumps of rain sensor TFA 30.3233

[irimitenkan]

The problem

I'm using the rain sensor TFA 30.3233. Every about more or less 7-10 days, sometimes only some hours later, I get implausible jumps of the rain counter, it jumps up to 2000+ and ~2minutes later then back to old value. This has impact to my rain rate, too: it shows the mm/h in the last 24hours and and it crashes my rain per month statistic based on this rate.

I also own a TFA reciever for same rain sensor, there is nothing unusual and (without these sporadically jumps of the integration) the measured values of both are identical.

I guess this is caused by the TFA sensor itself and these implausible jumps are filtered by original TFA receiver and the integration has to consider this as well ?

Please see attached screenshots. Counter yesterday evening and today morning: .

Zoomed:

Rate of counter example:

What version of Home Assistant Core has the issue?

core-2024.2.5

What was the last working version of Home Assistant Core?

unknown

What type of installation are you running?

Home Assistant Container

Integration causing the issue

RFXTRX

Link to integration documentation on our website

https://www.home-assistant.io/integrations/rfxtrx/

Diagnostics information

please see screenhots in problem descriptions

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @danielhiversen, @elupus, @robbie1221, mind taking a look at this issue as it has been labeled with an integration (rfxtrx) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `rfxtrx` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign rfxtrx` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

rfxtrx documentation rfxtrx source _{^{(message by IssueLinks)}}

[elupus]

I checked our source. I can't see any explanation for this behaviour in the source.

Did you see this firmware release: http://blog.rfxcom.com/?p=334 not sure what firmware you are running.

[irimitenkan]

Did you see this firmware release: http://blog.rfxcom.com/?p=334 not sure what firmware you are running.

Yes, I'm using latest firmware release. About 2 weeks ago I enabled the debug logging and yesterday the strange jump occurred again (during sunny weather) and now the debug trace is available. Seems to be a device (firmware?) problem. Rain total value sequence 145, 405, 145:

2024-04-29 14:30:06.673 DEBUG (Thread-4 (_connect)) [RFXtrx] Recv: 0x0a 0x52 0x0d 0x78 0x42 0x01 0x00 0xa3 0x0a 0x02 0x79
2024-04-29 14:30:06.677 DEBUG (MainThread) [homeassistant.components.rfxtrx] Receive RFXCOM event: {'packet_type': 82, 'sub_type': 13, 'type_string': 'Alecto WS1700', 'id_string': '42:01', 'data': '0a520d78420100a30a0279', 'values': {'Temperature': 16.3, 'Humidity': 10, 'Humidity status': 'normal', 'Humidity status numeric': 2, 'Battery numeric': 9, 'Rssi numeric': 7}}
2024-04-29 14:30:09.042 DEBUG (Thread-4 (_connect)) [RFXtrx] Recv: 0x0b 0x55 0x09 0x79 0x5a 0x7b 0x00 0x00 0x00 0x02 0x3e 0x70
2024-04-29 14:30:09.046 DEBUG (MainThread) [homeassistant.components.rfxtrx] Receive RFXCOM event: {'packet_type': 85, 'sub_type': 9, 'type_string': 'TFA 30.3233.01', 'id_string': '5a:7b', 'data': '0b5509795a7b000000023e70', 'values': {'Rain rate': None, 'Rain total': 145.796, 'Battery numeric': 0, 'Rssi numeric': 7}}
2024-04-29 14:30:09.047 DEBUG (MainThread) [homeassistant.components.rfxtrx.sensor] Sensor update (Device ID: 5a:7b Class: RFXtrxDevice Sub: 9)
2024-04-29 14:30:09.049 DEBUG (MainThread) [homeassistant.components.rfxtrx.sensor] Sensor update (Device ID: 5a:7b Class: RFXtrxDevice Sub: 9)
2024-04-29 14:30:09.050 DEBUG (MainThread) [homeassistant.components.rfxtrx.sensor] Sensor update (Device ID: 5a:7b Class: RFXtrxDevice Sub: 9)
2024-04-29 14:30:09.055 DEBUG (MainThread) [homeassistant.components.rfxtrx.sensor] Sensor update (Device ID: 5a:7b Class: RFXtrxDevice Sub: 9)
2024-04-29 14:30:09.139 DEBUG (Thread-4 (_connect)) [RFXtrx] Recv: 0x0b 0x55 0x09 0x7a 0x5a 0x7b 0x00 0x00 0x00 0x06 0x3e 0x70
2024-04-29 14:30:09.143 DEBUG (MainThread) [homeassistant.components.rfxtrx] Receive RFXCOM event: {'packet_type': 85, 'sub_type': 9, 'type_string': 'TFA 30.3233.01', 'id_string': '5a:7b', 'data': '0b55097a5a7b000000063e70', 'values': {'Rain rate': None, 'Rain total': 405.892, 'Battery numeric': 0, 'Rssi numeric': 7}}
2024-04-29 14:30:09.144 DEBUG (MainThread) [homeassistant.components.rfxtrx.sensor] Sensor update (Device ID: 5a:7b Class: RFXtrxDevice Sub: 9)
2024-04-29 14:30:09.146 DEBUG (MainThread) [homeassistant.components.rfxtrx.sensor] Sensor update (Device ID: 5a:7b Class: RFXtrxDevice Sub: 9)
2024-04-29 14:30:09.146 DEBUG (MainThread) [homeassistant.components.rfxtrx.sensor] Sensor update (Device ID: 5a:7b Class: RFXtrxDevice Sub: 9)
2024-04-29 14:30:09.147 DEBUG (MainThread) [homeassistant.components.rfxtrx.sensor] Sensor update (Device ID: 5a:7b Class: RFXtrxDevice Sub: 9)
[...]
2024-04-29 14:30:54.044 DEBUG (Thread-4 (_connect)) [RFXtrx] Recv: 0x0b 0x55 0x09 0x83 0x5a 0x7b 0x00 0x00 0x00 0x02 0x3e 0x70
2024-04-29 14:30:54.049 DEBUG (MainThread) [homeassistant.components.rfxtrx] Receive RFXCOM event: {'packet_type': 85, 'sub_type': 9, 'type_string': 'TFA 30.3233.01', 'id_string': '5a:7b', 'data': '0b5509835a7b000000023e70', 'values': {'Rain rate': None, 'Rain total': 145.796, 'Battery numeric': 0, 'Rssi numeric': 7}}

[elupus]

Yup. You could try and report it to rfxcom.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.