DAVe3283

@dshokouhi this is not fixed on the latest HA core release for me

> I think you first need to wait for the app to re-register the sensors after updating HA core and then on the next restart it should work. I will...

You need to add a filter on the output sensors to avoid the insane update speed in 2024.2.0. ~~I recommend also pulling in my fix for the energy sensor until...

IMO a better solution to this due to other side effects (e.g. https://github.com/esphome/issues/issues/5501#issuecomment-1957720730) is to revert to the old behavior. I submitted #6265 to do that, and you can use...

That is odd, as it works for most of us. You could try putting it in quotes: ```yaml external_components: - source: "github://pr#6261" components: [ cse7766 ] ``` Here is my...

If the proposed rollback works for you, leave a comment or thumbs up on the PR (esphome/esphome#6265) so the maintainers know it works right and people want it.

Since 2024.2.2, this has worked as expected for me without changing any UART settings. Just remove the single `update_interval` and apply a `throttle` or `throttle_average` filter to each of the...

@gzcwnk the documentation has been updated with an example: https://esphome.io/components/sensor/cse7766 Basically just replace your cse7766 section with the example one, and it should work again. You could also go download...

Updated ESPHome to 2023.2.0, no change. Rebooted VM, still no change. Disabled SSL in ESPHome addon and rebooted VM, still no change. Every time Home Assistant starts up, it has...

Updating 2023.2.4 → 2023.2.5 with the ESPHome add-on running got the update notifications working again. This appears to be an issue with how Home Assistant handles (or rather doesn't) the...