James Barnett

I'm also hitting this issue. I've implemented an `OperationBuilderPlugin` to add custom `ObjectVendorExtension`s and the value gets wrapped in an `extensions` object. e.g. the following ``` @Component @Order(SwaggerPluginSupport.SWAGGER_PLUGIN_ORDER) public class...

In case it helps anyone else, I've been using the following [jq](https://stedolan.github.io/jq/) command to fix the produced OpenAPI json by moving the `x-` extension property up a level and removing...

Hi, ballachango is correct. The pre-compiled binaries are for x86 only. The easiest way to get it running on a Pi would be to install NodeJS, clone the repo and...

Hey Fazeel Assuming you got the source code via git, the easiest way would just be to run a `git pull` periodically to get the latest changes (and then do...

Hi, thanks for using the project! The plugs don't natively report the energy consumption in a format other than the total daily usage (as a single value), or the current...

Thanks for all the feedback! I've made a start on implementing this feature so hopefully I'll get it into a build within a week or 2

I've added this logging functionality into the latest build (v0.6) [available here](https://github.com/jamesbarnett91/tplink-energy-monitor/releases/tag/v0.6). By default the app will log every minute and keep 24hrs worth of history, but if you want...

@ballachango I'll take a look at the 0 length/byte file issue. It currently assumes that if a file exists it must have created it itself, and so expects it will...

Hi, thanks for the reports. I'll have a look and see if anything in v0.7 could have caused this, or if its always been a problem and needs a fix.

Hey thanks for the report, a few other people have mentioned similar problems so I'll have a look into it.