fhoekstra

I'm getting this same error on Tensorflow 0.8.0 (on Ubuntu) @foolyc Should adding the name also be necessary for tensorflow 0.8 ? As @cbfinn says it was tested for v0.5-0.8...

**EDIT: I was wrong, the 0.5.0 version of the API wrapper library does not remove Glances v2 support yet.** Glances does not seem to have any form of extended support:...

I haven't been able to test locally so far as I am developing in VSCode DevContainer and haven't been able to expose my GPU to the DevContainer yet.

EDIT: never mind, found that HA uses syrupy and found [the syrupy docs](https://github.com/tophat/syrupy?tab=readme-ov-file#basic-usage) @engrbm87 This is almost done. ~~I have completed local testing but am struggling to add the GPU...

Thanks @joostlek , just did that. Wasn't that hard to find that syrupy is the library we use, would a PR for the docs with mentioning syrupy and snapshots be...

@joostlek You're right, I dropped a commit somewhere. I did generate them now, but they look wrong: a few sensors don't have the GPU part of the entity ID it...

I did, but nothing happened. Maybe I messed up the `translation_key`s (I copied them from existing sensors as much as possible). EDIT: Temperature and fan speed look good, but the...

I think it's all good now, added some new custom translation keys for processor and memory usage with the `{sensor_label}` template so the GPU name is inserted there and the...

Shall I replace the (double) underscores with spaces? Or do you think "processor" does not fit here?

In f041750 , I put in a proposal for removing the `GPU_0__` prefix if only a single GPU is present on a host. @engrbm87 , let me know what you...