Rvh91

I'm having a similar issue, but for me it does not report a zero value, but a small non-zero value instead. For different sensors I was using a template to...

Could you check if you always get exactly zero? Or just that it seems zero due to the scale of the graphs?

So if you access the internal wifi directly. I think you have a minimum requirement for the firmware version, but also a maximum. I recall that i read somewhere that...

I have the same issue. Running a reolink E1 pro. updated to 2022.12.0 and the binairy sensor for the motion detection shows up as unavailable.

until this is resolved, has anyone found a workaround?

I think I've tracked the issue to originate from [commit 4239923ea2e4dc8872b4eafc95127f68eb03b411](https://github.com/home-assistant/core/pull/83006). That is the only thing that has changed between 2022.11.5 and was merged in in 2022.12.0. @bdraco could you...

This looks great! it is exactly what i meant! I'll have to play around with the code you shared a bit to understand the syntax a bit better, but great...

Been playing around with the statistics, speeds up the rendering significantly! thanks for the suggestion. It seems however as if the 'auto' period setting doesn't really use 100 data points...

Thanks! I have noticed it working now. I'm a bit confused now by the documentation however. related to this block in the readme: ``` type: custom:plotly-graph entities: - entity: sensor.temperature...

> In that case you can just say: `period: auto` which sets that exact default Yes that was what I was using, I just wanted to understand what was happening....