Shaodong

Hi @dakhnod, have you tried "--timestamp" argument? type `modpoll -h` or check [here](https://gavinying.github.io/modpoll/usage.html#Named%20Arguments) for details.

Yeah, that's a nice feature. Also your approach looks good to me. Here are some points for your consideration, 1. Backwards compatibility: Current users don't have to modify their existing...

Hi @mircsicz, thanks for your kind words. Your compose file is almost correct, the only issue is the format of `command` in modpoll service, you could give a quick try...

I think `examples/3-xxx` will do, name it like "3-test-with-local-modsim" or you may suggest a better name for it. Thanks in advance.

Just a reminder in case you need, this repo follows [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/), please follow the convention when you draft commit messages, so that the CI pipeline won't complain about it....

Have you successfully [forked the repository](https://www.digitalocean.com/community/tutorials/how-to-create-a-pull-request-on-github#fork-the-repository)? Once you forked the repository, it will show up in your github account and you will have all permissions (because it is your repository...

@MattCosturos, sorry for the late response. Yes, it might be a good way to handle bit values. Thanks for your suggestion. I'll look into the solution when I am free....

My proposal is as following, 1) Pass in keys via `--build-arg` in all build scripts, ``` --build-arg NEXT_PRIVATE_ENCRYPTION_KEY="$NEXT_PRIVATE_ENCRYPTION_KEY" \ --build-arg NEXT_PRIVATE_ENCRYPTION_SECONDARY_KEY="$NEXT_PRIVATE_ENCRYPTION_SECONDARY_KEY" \ ``` 2) Add a `docker:build` script in root...

It is possible for Modbus TCP devices but not Modbus RTU devices yet.

Since TCP device's IP address info is not included in the config file, so the config can be reused for all same type devices. To connect to multiple devices, I...