-
Notifications
You must be signed in to change notification settings - Fork 103
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
Support last-updated for unchanging sensor values #93
Comments
Good thought! My sensors all update fairly frequently with different values. Can you check to see if rtl_433 is sending the value to mqtt? My first guess is we may want to set |
I just ran into this same situation with a humidity sensor. It was raining outside and relative humidity was at 100% for an extended period (several hours). I confirmed that the MQTT messages were being published but the I confirmed on the Home Assistant Discord that setting My plan at the moment is to manually configure those MQTT sensors in Home Assistant. It's worth noting this is reproducible with lots of different sensors whose value doesn't change for several hours - e.g. UV index sensor overnight, fridge / freezer temperature sensor, rainfall sensor, etc. |
There's open discussions about this at merbanan/rtl_433#2102 and home-assistant/home-assistant.io#23900. |
Looking into this, I still need to get a better understanding of updated, changed, availability… first comment, it seems like force update for all 433 auto discovered devices is a pretty blunt control. Does this wind up generating state updates in hass / recorder every time a message is received? |
Yes, that's exactly the issue. It's suggested here that removing @Gonioul , it turns out that "Last updated" doesn't actually mean what it looks like in the UI. I've filed a discussion in the Home Assistant front-end repository at home-assistant/frontend#13687. To solve the original case of "The only way to know the entity is not dead is to look for the utc value of the device.", I think we'd need to write something that marks an entity as unavailable if a given period of time has passed. |
Ah! We can expose expire-after perhaps: https://github.com/merbanan/rtl_433/blob/master/examples/rtl_433_mqtt_hass.py#L747 |
Registering my interest in this! |
Hi,
Looks like the last-updated value of the entity isn't updated if the sensor value doesn't change (temperature for example).
The only way to know the entity is not dead is to look for the utc value of the device.
Regards,
The text was updated successfully, but these errors were encountered: