https://github.com/prometheus-community/windows_exporter

Than you can see it in netdata: https://www.netdata.cloud/windows-monitoring/

Or in Grafana: https://grafana.com/grafana/

I didn’t meant the addon container just a regular container. If you don’t use HAOS, then don’t use their containers, use these instead:

• https://hub.docker.com/r/linuxserver/code-server
• https://hub.docker.com/r/linuxserver/bookstack

Yeah, that’s what you put in a compose file, and you shouldn’t care about anything else, port mappings can be read from the Dockerfile if it’s not documented, and if the container was built correctly you shouldn’t care about config files.

I never met a container with 0 documentation. You can read the Doockerfile at least, it’s not magic.

I mean, I can understand why someone want to use HAOS and neber deal with such things, but if someone can set up HA in a container, the second and third container from there is not an unbelivably big step.

{{ state_attr('timer.dining_study_clear', 'duration') }}

Search for the name of the addon on docker hub and write your compose. Addons are just other containers.

Wow, it’s strange. I don’t have a yellow but installed countless m.2 and pcie devices in countless computers, and never seen such a limitation. Ram and cpu compatibility lists are a thing on mobo websites, but pcie? Is this some ARM thing?

The most common point of failure on rpis are sd cards, and the symptoms are similar. If you running it from an sd card it’s recommended to migrate to an usb ssd.

How do you run ha? Hassos, or normal docker?