Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Acurite 00275RM (#74) stay NA on versions higher than 0.19b #52

Open
mihasik22 opened this issue Jun 6, 2023 · 2 comments
Open

Acurite 00275RM (#74) stay NA on versions higher than 0.19b #52

mihasik22 opened this issue Jun 6, 2023 · 2 comments

Comments

@mihasik22
Copy link

After updating to any version higher than 0.19b both outdoor sensors acurite 00275RM (code 74) become unavaliable.
Data from sensors transmitted to mqtt but the home assistant considers that these devices do not exist.
I try almost everything but none happened - only works on version 0.19b and below.

Versions logs look different, but in detailed research i saw only one difference in payload: 0.19 reports rssi with 6 digits precision, and newest versions only 5.

Old version log:
Received message: rtl_433/events : {"time": "2023-06-06 17:17:22+1000", "protocol": 74, "model": "Acurite-00275rm", "subtype": 2, "id": 8468, "battery_ok": 1, "temperature_C": 33.2, "humidity": 30, "temperature_1_C": 25.0, "mic": "CRC", "mod": "ASK", "freq": 433.97594, "rssi": -0.196003, "snr": 18.48466, "noise": -18.6807}

New version log:
DEBUG:Received Device Data from SDR and sent to MQTT: rtl_433/events : {"time": "2023-06-06 14:10:57+1000", "protocol": 74, "model": "Acurite-00275rm", "subtype": 2, "id": 8468, "battery_ok": 1, "temperature_C": 37.7, "humidity": 30, "temperature_1_C": 23.8, "mic": "CRC", "mod": "ASK", "freq": 433.92842, "rssi": -8.39855, "snr": 16.93324, "noise": -25.3318}

If you need any additional information to find the error, I am ready to provide it.

@mihasik22
Copy link
Author

In addition: these sensors are also identified as channel 0 instead of A. Chanell A for these devices is fixed and I can't test them on another channel. I think that this issue may have the same reasons as #53

@thejeffreystone
Copy link
Owner

Yeah this one should be fixed. I hope. Its been. while since I dedicated any time to this add-on...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants