Ellis Percival

Hey @Gr4ffy thanks! It's currently not implemented I'm afraid. There's no technical reason why it couldn't be, just not enough time in the day 😊

Thanks for the report. Could you also provide the relevant sections of your config, if you're setting the interval there?

What I think might be happening is that it takes a non-trivial amount of time to read the sensor, so it skews the timing when it's set to short intervals....

Interesting idea! There's nothing to stop it from running in docker, but you'd have to work out how to pass the devices through, as you mention. Nobody that I'm aware...

@S-Przybylski @blademckain I've added a Dockerfile now, and published an auto-building image on Docker Hub. Please have a look at the bottom of the readme, which now explains a bit...

@RezzZ did you use `--device=/dev/mem:/dev/mem --device=/dev/gpiomem:/dev/gpiomem` in your `docker run` command? If that doesn't work, perhaps try starting from a raspbian image and installing Python etc.? https://hub.docker.com/r/raspbian/stretch

It may also be an issue with permissions. Double check which user owns the `/dev/mem` device inside the container, and make sure that user exists and is the one the...

Oh interesting. Yeah, I've not considered the output name having a slash in. Thanks for the report, I'll have a look next time I've got some time to work on...

Yeah, this is a known issue at the moment. I've made quite a big update recently that's just waiting for me to have a bit more time to finish fixing...

You can try the `feature/trio` branch if you're able to get it installed with [poetry](https://github.com/python-poetry/poetry). I don't currently have any 'developing' docs, but it should just be `poetry install --no-dev`...